We’re done with the portmanteaus, no more Bakemono or Nisemono, just Monogatari Second Season. It’s a bit of a misnomer really considering we’re thirty episodes deep already with ONAs scattered about like confetti and a series chronology that’s increasingly difficult to cohere into a straightforward story. Straightforwardness is not what you get with the Monogatari franchise though, which is both in its favour and to its detriment; however more than any of the previous series - the watershed Bakemonogatari, Nisemonogatari then Nekomonogatari - this is what everything has been building up to.
this isn’t just fan-service, this is Shinbo x SHAFT fanservice
Not in terms of story mind you, it’s still the dialogue-heavy, supernatural-affliction scaffolding that has driven the plot from the outset. Certainly not in terms of characters either with the return of just about every female lead barring Suruga and barely a handful of new additions, some of which are difficult to tell apart from already established cast members. No, the build up has been there to tear down and put back together, to lay bare the characters and tropes that, to a certain extent, the franchise has built around itself.
I'm on a quest to understand exactly why I like the anime that I do. It's relatively easy to enumerate which ones I like more than others, MyAnimeList exists more-or-less exactly for this purpose, but that doesn't really explore what makes a show excellent beyond an attempt to pattern-match (studio, release year etc.) or to compare with others to find compatibility and recommendations.
...finding interest in the mundane or levity in the absurd.
Teasing an answer more meaningful than "I just do" means examining constituents, and for varying reasons - my continual battle to write creative fiction one - characters, specifically protagonists, stand more prominently than others. To enumerate all the different archetypes would be folly and missing the point: great protagonists - great characters - transcend the clichés imposed upon them by genre or circumstance. All too often though anime lets the archetypes rule - why else would there be the existence of shortcut words like "tsundere"?
Attacking those "random" files a couple of days ago provided enough of a challenge to keep me interested for a few hours, especially as it seemed like I was treading new ground in terms of spec'ing out previously unexplored file formats. It turned out that the files had already been mapped and successfully decompressed and the only thing left to do was build an unpacker which was in the pipeline. It seemed my work wasn't exactly fruitless but other, probably smarter people had everything under control. I wasn't about to let that stop me though.
Note (2008-01-11): The full (official?) SDK for this file format has been located which includes both a packer and an unpacker as well as other tools I'm sure are useful for working on the file format. The full name of the file format is "Yaneurao" with the SDK going by the nomenclature of "yaneSDK" which is the stem for the file format signature of "yanepkDx". There is already a .NET version of the SDK so if you're interested in my deconstruction process then read on, otherwise I would recommend using the official/fully-featured SDKs.
Then, in that moment of lucid elation, I realised exactly what was going wrong.
The compression format was identified as LZSS and reading through severalsites revealed that some of the data I had initially spotted but attributed to SHIFT JIS (or at one point a Unicode Byte Order Marker, perfect for a non-Unicode file) were the tell-tale signatures of LZSS; the gradual degradation into junk data was also typical of the algorithm as the further into the file the stream progresses, the more back references are present.
While I hadn't heard of LZSS, it came as no surprise that it was a modified version of LZ77 which I had come across before though never toyed with. Having to dig through a dense PDF was not my idea of fun and my university days had proven that reading academic proofs rarely lead to workable implementations for me so I searched for a ready-made PHP version which (for reasons which will soon become glaringly apparent) didn't prove fruitful. After coming up against dead-ends with other languages I settled on the defacto C version which seemed most other versions I found were based off.
Out of curiosity and a favour to someone, I decided to take a look at some random .dat files that were ripe for the translating; what ensued was a morning of head scratching, hex scrying and using some of the lesser used PHP functions.
All screenshots taken from data1.dat, sample file 1 and the window is resized for the most appropriate screenshot rather than general workability.
so garbled that it sent a few hundred bell tones to my computer speaker
First thing I did was to crank open the lovely XVI32 hex editor and have a look at the sample files provided, their .dat extension more or less indicated they were a proprietary format and were unlikely to relinquish their secrets easily. What was known was that the files contained a header portion, a bundle of XML files in a contiguous stream and a lot of junk data. The XML files could be seen and their encoding was stated as SHIFT JIS and, after cursing its existence, I attributed the junk data to that which seemed like a good place to start.
The first eight bytes seemed to be a file signature, but Googlesearches for all or parts of the signature were fruitless which meant it was time to pick things apart.
The next four bytes were different for each file and at first I thought it was part of the block format that made up the header part of the file but the section repetition for the header block didn't match up so after converting it to a variety of different number formats (I'm no hex wizard and I originally thought it was only a two byte short rather than a four byte integer or long) and assumed it was an unisgned long (32 bits) in Little Endian order.
