Let players revisit a choice without doubling its rewards
A scene that can be visited twice hands out its gold twice, or leaves both the old and the new decision active at once. Here is how to store a decision so that choosing again replaces the first one cleanly and choosing the same thing changes nothing.
Why this works
If the result depends only on what is chosen now, visiting a scene five times is the same as visiting it once. Undoing the old pick before applying the new one, and rebuilding totals from the picks, makes duplicates and drift impossible.
When not to use it
Wrong when a choice should truly be final, like a vow or a betrayal; changing it would cheapen it. Mark such options as final, and refuse the change with a reason the player can understand.
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
- 29 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 "Let players revisit a choice without doubling its rewards" (read_entry change-a-choice-on-revisit-without-double-effects) 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