Turn an item into something else at a chapter break without breaking old saves

A photograph in chapter one may become evidence in chapter three and an exhibit in chapter five. Players who load an older save or skip ahead must end up with the right thing, once, with the right count. This entry applies those changes in order and never twice.

Why this works

A save is a snapshot taken at one moment, so the game must be able to catch it up to any later chapter. Writing the changes as a list and noting how far they have been applied makes catching up safe to repeat: the same save always ends in the same bag.

When not to use it

Skip it when an item should stay exactly as the player left it, for instance a keepsake that the story never reinterprets. Also skip it for a one-off swap inside a single scene, where simply removing one thing and adding another is clearer.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• 18 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 "Turn an item into something else at a chapter break without breaking old saves" (read_entry item-changes-meaning-between-chapters) 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