Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(2 edits)

Now that’s new, it fails to start through Lutris, with steam-run and the Windows version fails through Wine.

Through Lutris it fails with error while loading shared libraries: libplc4.so: cannot open shared object file: No such file or directory. Adding nspr to Lutris libraries makes it fail with the same but for libgconf-2.so.4. Wait, gconf-2? What is this, 2010? Then libXdamage. Then libnotify. Then it opens a window! For a sec, spamming errors to logs, and crashes with Failed to create ICU number format, are ICU data files missing?. This was actually so esoteric, looking it up pointed me to an old comment on this very game’s comment section and not much else xD With a tip to run nw instead of Game. …which crashed with posix_spawn <gamepath>/chrome_crashpad_handler: Permission denied (13).

I’m running this system for ~4 years now and that’s like the second time I had that many problems trying to run a native game. RPGMaker MV seems to combine the issues of older RPGMakers and the Chromium-based “”“multiplatform””” Electron scourge.

In the previous 2 attempts my horny and patience ran out before going this far troubleshooting. This time it’s not even about horny, it’s a challenge - me versus this godforsaken RPGMaker MV which seems so rare, I might be the second person trying to run a game based on it on NixOS.

Welp. It was the goddamn crash handler. Ironic. The unpacked files don’t have execute permissions. I’ve made Game executable, I’ve made nw executable, but I didn’t realise I have to do this for chrome_crashpad_handler too. Now pointing Lutris to execute nw Just Works™. And with that it still requires nspr and libXdamage as additional dependencies not covered by Lutris Runtime, but loses libnotify and gconf-2 (seriously lol, gconf-2) deps, since they’re common enough that the runtime covers them, and apparently running the game through the Game binary didn’t link to it correctly. Somehow.

Also I tried to patch it with the latest patch, broke it (I guess the patches are incremental?) and thus found out that RPGMaker MV really doesn’t like you trying to downgrade a game back to a previous version, even if you delete the old dir and extract it again, crashing with a Check failed: state.metadata.version() == GetCurrentDatabaseVersion() error. (Which btw broke this year’s record for esoteric errors, with a google query "Check failed: state.metadata.version()" returning one single result that wasn’t helpful.) Turns out it stores some db at ~/.config/KADOKAWA/RPGMV that needed to be purged.

Logging this here so that maybe my suffering can ease someone else’s.

(+1)

I'm not following a lot of what you're saying with the Linux issues, but if you mean the patches are incremental as in you need to download each of them and apply them one-by-one, that shouldn't be the case. You should only need to apply the latest patch to the game, unless something has gone wrong. In what way did the patch break the game?

(+1)

That is what I meant by patches being incremental, glad to hear that they aren’t. I don’t remember the exact breakage, but I just tried patching again and this time it worked, no idea what broke the last time. Thanks for taking an interest <3 The game is worth the trouble.

As for the Linux issues, the best you could do is make the executables zip with the execute permission, so that they have it when unpacked and people don’t need to manually change that. (I don’t know how that works when zipping files on Windows.) A note that it uses RPGMaker MV (so that it’s easier to tell what dependencies it needs) and that in case of issues people should try running it by executing nw not Game would also be useful.

From the quick look I took at zipping and permissions, it doesn't look like that's possible. From the link I found "As far as I know the permission system in Linux is set up in such a way to prevent exactly what you are trying to accomplish." I'd assume it's an intended Linux security measure. I've added a section for Linux in the download notes that mentions the need for giving the executables execute permissions alongside the other things you mentioned, thanks for the notes, as you can probably tell, I know very little about Linux.