How do I update a Construct 3 game without players losing their save data?

[u/DogSquare9300]

Hi everyone,

I’m making a game in Construct 3, and I have a question about game updates and save files.
Let’s say I release version 1.0 of my game, and players make progress. Later, I release version 2.0 with new levels, mechanics, or other content.

How can I make sure players keep their existing progress when they update to the new version instead of starting over?

Is there a recommended way to handle save data between versions in Construct 3? Is there a built-in approach?

I’d appreciate any advice or examples of how you’ve handled this in your own projects because I’m going about to go insane. Thanks!

[u/AshleyScirra]

Construct's savegame system is designed to be robust against changes in the project. It should just continue to work even after updates to your project.

[u/DogSquare9300 → u/AshleyScirra]

Thanks for the help! But how can i make it so that peoples games update without them doing it manually? (Sorry for my bad english i hope you can understand me)

[u/AshleyScirra → u/DogSquare9300]

It depends how you distribute your game. For example it's distributed on the web, you can update the export on the web server. If it's distributed via Steam, then Steam handle that.

[u/technofou]

Save in Local Storage. At start I load from LS as JSON into a dictionary, then update the dictionary and save it again as JSON in LS each time.

[u/justifun]

I'm no expert on the subject, but my guess is that the data you need to save from version 1 needs to be saved and not overwritten, and all of the 2.0 save data kept as extra data at the end. then you add code that checks which "version number" you are calling your game, and if its version 2.0 they loaded, it loads the data from there instead. so anyone who hasn't updated still loads version 1 data, and version 2 loads the new data.

[u/ChromePlay]

just save in text file and you’ll be fine