Skip to main content

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

Here are two Linux patches that may fix this. I believe the issue is either the way I named the new title image (used the forbidden space bar by mistake), or because of one of the new plugins added in the update. Please test the title fix first, then the plugin, and if either work please let me know which so I can fix it properly. Thanks.

Title fix: https://mega.nz/file/NGxjCJwb#cIzu9NoY5uF9jQyeoh0RYdLD-jYezTIzKuWPkq7cbYk
Plugin fix: https://mega.nz/file/IWxUTIJZ#U1pFhjSBW3fYTdjdkO3Q5w4t7H0PdnhYyq6C8Oybvg8

Note that if the plugin fix works, it may cause some problems in game as I just turned the plugins off to test. (So if the title fix works do not apply the plugin fix on top.)

(1 edit)

Neither patches work, and there were no warnings or errors when ran from command line. I've also replaced the nwjs files first before trying each patch to no success

It shouldn't have anything to do with the nwjs files/the external files that run the game. I've removed the www folder from the v0.59 version and replaced it with one from v0.58 and the game ran normally as the downgraded version

It's good to know the old www folder worked. I've made a full new download you can try to see if it fixes things. I've changed the file name for the title image again just in case, and it has the new plugins disabled again, as patching plugin changes can be weird sometimes. If that doesn't work, I did also add quite a few new audio files to the game, so it's possible there's some sort of naming issues there. (I would expect that to cause an issue when the audio comes up, rather than on launch, but it's still possible.) So to test that, you could delete the audio folder from the new version inside of the www folder and copy over the old audio folder from 0.58 to see if that fixes things. (If it does, let me know and I'll go double check all the new files and see if there's any obvious naming issues. You'll probably encounter a bug when playing with the old audio if you get somewhere that calls the new audio.)

If neither of those work, my last idea is the fact that I accidentally uploaded version 0.58.4_Linux as a zip rather than a tar file. I would expect that to cause issues, not fix them, but I could try uploading a zip of the newest Linux version if everything else doesn't work. 

New download: https://mega.nz/file/FHJDQChC#w6i3zZfb_4k3iXOhXxVRFFZFpLldr8afi_-48Lbnf0s

(5 edits) (+1)

Unfortunately the download and audio replacement didn't work so I ended up looking through the www folders for the differences between versions (excluding game content like maps or characters) and came across this

--- CiC_0.58.7_Linux/www/js/plugins/SRD_GameUpgrade.js
+++ CiC_0.59.7_Linux/www/js/plugins/SRD_GameUpgrade.js
@@ -625,7 +625,9 @@
  array[i] = "img/" + url;
  });
- _.isNewNWjs = Number(process.versions["node-webkit"].split(".")[1]) >= 13;
+ _.isNewNWjs =
+ process.versions["node-webkit"] >= "0.13.0" &&
+ Utils.RPGMAKER_VERSION >= "1.6.0";



The windows version doesn't use nwjs (node-webkit) so I tried reverting those lines with '+' to the line with '-' and the game was able to run! I then reverted the changes, then replaced the string "0.13.0" with "0.115.0" (the nwjs version I replaced the game with) and that ran too. It seems the problem was a string comparison instead of a number comparison because 115 > 13, but "13" > "115".

This buggy version comparison code is present throughout the file and I wouldn't be surprised if there will be future comments coming from buggy version checks. The older version of this code will break with nwjs of v1.0.0 so the plugin developer should use a proper version comparison library because it's a non-trivial piece of code to write

I'm able to play the game now. Thank you for taking the time to investigate!

Thank you for finding all of that. It looks like that plugin got reverted from changes made in 0.58. There were issues popping up for Linux users with 0.58 initially, and that change you mention to the plugin fixed it. I must have forgotten to apply that to version 0.59, because I was working on that while I fixed 0.58, so I didn't copy the plugin over after it had been fixed. I've got it set up so it should be good to go from now on, and added patch 0.59.7_Linux to the main download folder that should also fix that. Thanks again, it would have taken me forever to notice that was the cause of the issue.