Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

It seems that does work! So it needed both the game's executable and the crash handler to be marked as executable. These two commands did the trick (within the Cycle of Corruptions directory in terminal):

chmod +x nw
chmod +x chrome_crashpad_handler


Thanks kohlrak for figuring it out! I guess the game wouldn't proceed until it could have the crash handler process running in the background or something. Oh and if anyone does this and it launches the game without audio, just relaunch the game. The first time after getting it to run it was mute but afterwards it seemed to work just fine.

Great to hear! Thanks for the confimration!

(1 edit) (+1)

I'm going to assume you're not familiar with linux. In linux, that which gets executed directly, whether (so not including SO/DLL files) requires execution permission. Similarly, a "full path" or "relative path" is needed to execute programs (that way no one places a "dir" executable as a virus into a folder to get the user to execute it when they're trying to find out what's in the folder). This is why execution in linux requires "./" in front of the executable "./" is a shortcut for "current directory".

What happened here is that the crash handler gets called as a child process so that it can run separately in case the program crashes it can handle the crash without crashing too, however without execute permissions it's not allowed to run and the "nw" executable did not include a handler for this and thus crashed without the crash handler handling (the creators of RPG maker never considered that the engine could crash *because* of the crash handler not having permission to run).