Which of my save changes will break the saves players already have

Adding one tracked detail to your story feels harmless, but a few kinds of change lock out everyone with an older save. This entry compares the old and new layout of a save and sorts the changes into harmless and harmful ones.

Why this works

A saved game was written by an older release and will be read by a newer one. Whatever the new release expects but the old file never held, or holds in another form, is what breaks, so comparing the two layouts predicts the damage before any player meets it.

When not to use it

Not needed while the game is unreleased or the saves are throwaway, for example a short jam game: then simply wipe the old saves. It also cannot tell you what a changed field should mean, so you still decide the conversion.

In the full entry

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

Say this to your AI

Use the Spielerando entry "Which of my save changes will break the saves players already have" (read_entry save-format-change-needs-migration) 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