The ghost haunts these skies again! 👻 Good Morning!

By right, I mean properly dated, organized, classified, segregated, even named at points. And internally, that their records don't wind up into recursive rabbit holes where you have to dig deeper than you should to get to the resource.

Oh yeah. NTFS is no bueno for linux gaming. You pretty much stumbled into the reason why. That and differences between naming standards (caps sensitivity) messes up Windows once both OSes share the drive. Basically, better to just reformat to ext4 or btrfs for sanity.

Oh yeah. It sorta goes downhill from here too depending on how you interpret the locked route because that's another doozy. XD

Nice. Shuten is strange when I think of it as a Kodaka game. Focused in a way I never expected him to manage, yet it feels very much like 2nd Scenario in hindsight.

Really though, kudos to Tookyo for doing their thing just making stuff. There's a scrappy spirit in their scenario writing that doesn't always land right, but the creative intent is there. Hundred Line is fun and as scattershot as can be. Shuten was more focused with a stronger payoff.

And somehow, it's rather 2000s coded as a VN. Just the vibe and the latter half events reminds me so much of how VNs during that era finished their stories in a strong melancholic manner. There are no big winners, and everyone's a loser at the end of the day.

As a mystery game, I do appreciate how cozy it feels. The answer's fairly obvious yet understated that it expects you to be aware enough to fit the pieces together. So it's pretty satisfying when you get it right since it all makes sense in hindsight.

This did feel like the one essential route with how meaty it is, but I'm glad I did this after clearing the top half because it would be hard to traverse those routes in hindsight unless you're aiming for the locked route.

Still though, between this and Shuten, Kodaka really wants to say something.

It's all good because I see the intention to make art for the heck of it. Whether it's meant to be read into or not, appreciated or not it simply exists and it's something I wish people did more.

As a player, you can hop off at any point and it doesn't care. It'll welcome you back when you feel like coming back.

You can go though all that effort to open the locked route and it doesn't care. The endings there might not even be for you. None of them might be. Really.

And it's all good.

Don't get me wrong, it was meant to sell and the team hoped it would.

But that's why it's so compelling how indulgent the game is as you finish a couple of runs and eventually try to find a good ending only to realize you're being taken for a ride and it doesn't care. It's so ballsy. XD

Actually, this looks like a copy of the spreadsheet that was going around twitter at the time that I used as the nucleus of this glossary, so these entries are in there. XD

Got it. Thanks!

I know this is gonna sound out of the blue, but I appreciate a lot of the work you do to demystify how the sausage is made and the short and quick #amtranslating posts. If it's not too much of a hassle, do you mind if you can also add them to the J-E media glossary I built? Thanks!
yakuaru.com/add

And yes, for those who have submitted at the start of the year, it's in there now. Sorry. Life came up and I figured I should spend the time making sure this iteration is good so this won't happen again. Thanks for submitting!

Regarding Adding terms, it's more restrictive than before but ensures a good level of consistency. The previous method gave a lot of freedom at the cost of stressing me out whenever new entries came in and it's not fair to hold them there.

Frontend-wise, I've done a few changes here and there, removed Genre since it's clutter and additional complexity, and updated the Resources section.

Backend-wise, I changed how data is handled. It used to be a giant JSON file that slowly became harder to work with and also rather error-prone. So I switched it to a postgres db, which involved quite a lot of work to make sure it's seamless.