Update old character saves after stats are renamed or removed

An update renames a stat, drops another and adds a new one, and every hero in an old save comes out broken or with a missing value. Here is how to describe each change as a small step, apply the steps in order to any old save, and refuse a save from the future.

Why this works

Old saves belong to players who trusted you. Describing each change as a small step applied in order, on a copy, means any old save can be brought forward without ever damaging the file it started from.

When not to use it

Wrong for a game that has not shipped or a short jam game, where old saves do not exist yet. Then just change the data and start fresh, and keep this for the day players hold progress they would hate to lose.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• A diagram of every state
• 35 lines of example code with 5 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Update old character saves after stats are renamed or removed" (read_entry character-save-migration-steps) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP