is possible to update my game but don´t lose the "save games"? Help.

thejacs

Hi. Each time I want to make a small modification on my game and I upload the new version to the stores, people lose their "save games". Any posibility to update my game but keep the save games of the ussers? Thank you.

Armelline

The default behaviour should be that people's saves aren't affected. If you're uploading an update, and don't "re-save" the values back to their defaults, nothing should be changed regarding their save games. It's most likely something you are doing.

Check every instance of "Save attribute/Save Table" that you're using. The most likely thing is that you're overwriting the game saves yourself.

thejacs

Thank you for your answer.

Well, I´m using a basic behaviour "Save Atribute" and "Load Atribute" just to save level and score.

The problem is that when i want to modify something and I upload to the stores a new version "1.2, for example" is like the store delete the old app version on usser´s device and install the new version again. So, save games get lost :-(

jigglybean

Can't say that I have ever experienced this. I updated a game yesterday on Google Play and the old app gets updated. The high score saves are still there.

jonmulcahy

saved attributes are persistent across updates, UNLESS the user manually removes the game before installing the new version.

saved tables are persistent across updates, UNLESS you alter the number of columns during an update. If a table has 5 columns and increase it to 6, the table will be rolled back to default. I always pad my tables with 10 empty columns just in case.

Chunkypixels

@jonmulcahy Not used tables for a while... but that bit of info is very useful to know... cheers

thejacs

@jonmulcahy said:
saved attributes are persistent across updates, UNLESS the user manually removes the game before installing the new version.

saved tables are persistent across updates, UNLESS you alter the number of columns during an update. If a table has 5 columns and increase it to 6, the table will be rolled back to default. I always pad my tables with 10 empty columns just in case.

But when you generate a new APK through the gamesalad portfolio (I was PRO), is not like build a new app? How "Google play" knows that when you upload the new version of your app it must conserve the "Saved attributres" and delete the rest? Don´t understans exactly how it works :-(
Thank you

jonmulcahy

@thejacs said:
Thank you

Your keeping the same bundle id, as long as that stays the same it will just work.