Saving costs a ribbon in tense games: when it must be free, and when it must not be taken

Limited saves add dread, but players get angry if a failed save still eats a ribbon or if saving twice in a row costs two. Here is a short list of cases where the game must not charge, and what automatic saves do to the count.

Why this works

A price is fair only when the player gets what they paid for. Charging after the save truly worked, and only for something new, keeps the scarcity meaningful and makes tension come from choosing the moment, not from being cheated by the system.

When not to use it

Skip it in a game for a wide, casual audience or one played in short sessions, such as on a phone. Players there expect to leave at any moment; save freely and keep the tension in the story instead.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 24 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 "Saving costs a ribbon in tense games: when it must be free, and when it must not be taken" (read_entry narr-save-token-ink-ribbon-rules) 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