RPGM Crossdressing in Camelot [v0.56.3] [Stickyicky]

[StickyIckyCiC]

The Linux version of the game is broken, apparently .zip files failed to preserve correct file permissions, but even after fixing that I only got a black screen. Also package.json has an empty name which causes the game to not run aswell

I managed to get a working version using my RPGMV/MZ conversion script:

You must be registered to see the links

I'll take a look at that. I believe file permissions are usually supposed to be lost to ensure a new unknown program doesn't have permissions off the bat, but I haven't heard about the package.json error before. I've generally just gone with the latest NW.JS when releasing on Linux, but perhaps I should stick to a slightly older one. Thanks for reporting that.

Have not played this game in forever since the start of of farm and now I see majority Chasity cage stuff in the op images. Is it optional going forward?

Chastity is essentially always optional. There's a part of the content with Daddy in the alleyways that requires it, but I'm pretty sure all of his content at that point is chastity, so you'd just no do that if you want to avoid it. Also, in the sixth dungeon, you should try to beat Evelyn. if you do lose to Evelyn, you'll get locked in chastity for a scene. Then after that scene when you find her second bedroom, you'll get locked up again. If you resist the urge to suck her cock and then ask her to unlock you after.

Yeah they keep glitching out for me? I assume im making a mistake maybe?

To be clear, you are viewing alleyway scenes with art, and then they aren't appearing in the scene reviewer?

 

[repomansez]

I'll take a look at that. I believe file permissions are usually supposed to be lost to ensure a new unknown program doesn't have permissions off the bat, but I haven't heard about the package.json error before. I've generally just gone with the latest NW.JS when releasing on Linux, but perhaps I should stick to a slightly older one. Thanks for reporting that.

I've been testing out various RPGMV and MZ games on Linux, and theyre usually extremely picky about the NWJS version, I've had a game fully work and then not even launch from switching from nwjs x.x.0 to x.x.1. And I've seen at least one game which I couldn't get running properly at all under any nwjs versions, it'd always complain about not being able to find files under www/movies no matter what I tried, so yes rpgm is very hit and miss. For example, your game was the first one I ever had issues related to the name variable on package.json, but then I found another one right after lol.

I've been packaging the official Linux version for MudBeu 's games and I settled on packaging them using tar to avoid permission issues, I'd recommend you do the same, I believe 7zip under Windows has tar support.

Feel free to dm me on telegram or discord if you wanna chat about it

 

[anomajou]

I believe file permissions are usually supposed to be lost to ensure a new unknown program doesn't have permissions off the bat

they are not. permissions are not supposed to be lost like that. nwjs is shipped with the right permissions, then your archiver fails to preserve them on repacking.

I've generally just gone with the latest NW.JS when releasing on Linux, but perhaps I should stick to a slightly older one.

no need. switching to older runtime usually leads to crashes because chromium periodically updates it's database format in the game cache, and older versions can't work with that, requiring manually wiping the cache.
newer versions also tend to have better performance (including on windows).
the black screen issue is there because during the nwjs upgrade from 0.12 to 0.13 (all the way back in march 2016) - they deprecated a lot of stupid things, and now they have decided to remove these things for good. this causes some minor issues with badly outdated plugins, in this case www/js/plugins/SRD_GameUpgrade.js using wrong options when creating new window. it can be fixed by adding

if (_isNewNWjs) {
    // remove/rename deprecated values
    const ws = _.windowSettings;
    delete ws.toolbar;
    ws.always_on_top = ws['always-on-top'];
    delete ws['always-on-top'];
}

in there before

//-----------------------------------------------------------------------------
// PIXI
//-----------------------------------------------------------------------------

also, 0.56.3 used nwjs 0.104.1, which is a bit outdated and has problems with canvas rendering mode, 0.106.1 seems to work better.

 

[repomansez]

anomajou that's some pretty useful insight, if you're willing I'd love to pick your brain at some point to help me figure out some issues I've been having with nwjs and RPGM games, lemme know :>