Hmm... This is certainly weird. I do wonder if it's a specific issue with the version that the tool uses by default. To test this out:
Download v0.53.1 of nwjs (the sdk version) from here: https://dl.nwjs.io/v0.53.1/
Then open a command line, cd to the nwjs folder (after unpacking) and run nw.exe --nwapp="<path to the game>" (Replace the <> with the actual path). If it also happens with that, then it's very likely that there's a compatibility issue with nwjs.
I see.
If you are going to stick with version 0.72.0 of nwjs, you can either:
On the Essentials tab, you'll find the setting that selects the version of nwjs. Simply select 0.72.0 from the drop down.
That actually worked! I think the issue was that I accidentally skipped the step where I downloaded my preferred version of nwjs, or I wasn't paying attention to the version the program was downloading.
Either way, thanks so much! Hopefully this helps anyone else with similar problems in the future :)
