Way to avoid resetting tables with updates

WillGreen

Hey everyone,

I made a quiz app for learning English that has a 'level' system, and it takes quite a long time to get through all the levels. This makes it essential that table information (detailing players' progress) is saved. Saving tables isn't a problem, the issue is more that when I want to update the app (for example, from version 1.2 to 1.3) I don't see any way to avoid all the players' saved information being overwritten. Just as someone might not continue playing e.g. Skyrim if their 40+ hour saved files were all corrupted, so I imagine things would be the same here. I've added a cheat so people can unlock all the levels if they press down on a place on the first scene for 8 seconds, but is there a better solution?

The_Gamesalad_Guru

Tables that have been saved are not overwritten with updates. Only newly created tables will be added.

jonmulcahy

another thing to watch out for. if you release version 1.0 with a table with 4 columns or rows, and then in 1.1 decide to add an additional column or row to the existing table, all data in that table is overwritten.

once a version is released into the wild, you should consider that table set in stone.

darrelf

another thing to watch out for. if you release version 1.0 with a table with 4 columns or rows, and then in 1.1 decide to add an additional column or row to the existing table, all data in that table is overwritten.

once a version is released into the wild, you should consider that table set in stone.

Yep, top advice by @jonmulcahy and @FryingBaconStudios

I learnt this the hard way when I updated my game a few months ago. To fix it I had to be pretty creative and release a follow up soon after. I'm now considering this as I'm building my second game - if successful, I want to make it easy for me to update with new levels etc.

I also learned that my app update testing wasn't up to scratch so have also tightened this side up. You live and learn as they say...

WillGreen

Thanks guys!