I reordered my levels, and now the old and new numbers cannot be compared

After you move, merge or cut levels, "level 12" means something else than last week, and the comparison between versions quietly measures the wrong levels. This entry shows what to log instead of a position, how to carry old results over and what cannot be carried at all.

Why this works

A position in a list is a label that changes when you reorder, but a level is the same level wherever it sits. A permanent name keeps the comparison about the same thing, and counts can be added together where rates cannot.

When not to use it

If you changed the level itself, not just its place, the old numbers describe a different level and carrying them over misleads. Treat it as a new level and start counting again. A split level cannot be carried over honestly either.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 29 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 "I reordered my levels, and now the old and new numbers cannot be compared" (read_entry renumbered-levels-break-before-after-comparison) 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