After I add or remove a level, players' saved progress points at the wrong levels

You add a level in the middle of your puzzle pack, and suddenly players who finished the early ones are told they finished others, or lose stages they earned. This entry shows how to store progress so a changed level list cannot scramble it.

Why this works

A position in a list changes whenever the list changes, but a level's name does not. Saving names ties progress to the level itself, and a single reconcile step handles whatever the list looks like later.

When not to use it

Skip it if your levels are generated from a number and can never be reordered, such as an endless daily series. A plain counter is fine there.

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
• 26 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "After I add or remove a level, players' saved progress points at the wrong levels" (read_entry saved-progress-breaks-when-levels-reordered) 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