0 Favourites

Can you change web storage directory in NW.js?

  • Been having some problems getting my old saves to work with the new NW.js without messing with the save files themselves.

    C:\Users\Sapphire Dragon\AppData\Local\EternalStep

    was the old save space.

    C:\Users\Sapphire Dragon\AppData\Local\EternalStep\User Data

    is the new save space.

    If I drag all the files into a user data folder the save files work but I need the saves to work without having to mess with them for people on steam who have bought my game.

    Anyone who can code know of anywhere in the nw.js code I can remove the, \User Data, to make it use the old directory?

  • You cannot. The new NWjs and Chromium build changed the way they handle save data, including the folder structure. [Why they did that, is beyond stupid TBH!]

    It also ignores the set-path arg that works on prior NWjs.

    NWJs file read/write works and it's what i did to make a custom save-system that is based on arrays and JSON text files instead.

  • That's a shame. I'll look into different ways of saving for any new game but I guess i'm stuck with going to the old versions of c2 for my current game, if I can get one.

  • Yup, me too, I am not upgrading from R218 and NWjs 0.13 alpha 7 because it just works. Older versions are crap with memory leaks. Newer versions crash.

    Upgrading C2 makes it crash with the NWjs alpha.. it's a messed up situation again.

  • Construct 3

    Buy Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Buy Now Construct 3 users don't see these ads
  • Silverforce can you just make a new version that blows away old saves so that it works going forward? are you just saying there's a problem with saving the "old way"? what is actually crashing on newer versions?

  • Silverforce can you just make a new version that blows away old saves so that it works going forward? are you just saying there's a problem with saving the "old way"? what is actually crashing on newer versions?

    Newer C2 than R218 does not work with NWjs 0.13 alphas (Chromium 47). The alphas are the only NWjs that actually works with no issues. The new 0.13.0 betas are based on Chromium 48 which has introduced some bugs.

    Newer C2 is designed for Chromium 48 based NWjs, ie the 0.13.0 betas, which is pointless because it's broken**.

    **

  • Silverforce wow.. what a mess.. too many dependencies: C2, Chrome and NWjs

  • Silverforce wow.. what a mess.. too many dependencies: C2, Chrome and NWjs

    Add GreenWorks into the mix for folks who want Steam features.

    Rather than Game Engine < - > Steam SDK... it's: Engine < - > NWjs/Chromium < -> Greenworks < - > Steam SDK...

  • Silverforce have you tried the suggested solution for the lingering dead nw.js apps? (rename the project and/or get rid of old data folders)

    Because I don't seem to get them anymore when making a completely new project.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)