UNDO/RESET

Taking moves back — the undo button rewinding a puzzle step, level resets to a clean slate, rewind stacks that store every state, the build tool's ctrl-Z.

• SOLO-DEV COST MEDIUM
• TIMING REAL-TIME / TURN
• COMMON IN PUZZLE · TACTICS · CITY-BUILDER · ROGUELIKE

Puzzle design's modern consensus treats undo as oxygen (Baba Is You and Stephen's Sausage Roll offer infinite undo because their designers want you exploring hypotheses, not re-executing known steps; Into the Breach undoes movement pre-attack and grants one full turn reset — undo as a rationed resource), Opus Magnum-style builders undo freely because iteration is the medium, city builders and factory games vary wildly on demolition refunds (undo priced as economics), and roguelikes define themselves by its absence — permadeath is the deliberate refusal of undo, and the genre's whole psychology flows from that refusal. Designers grapple with undo because it sets the price of experimentation, which silently defines the player's relationship with the game: free undo says 'think by trying' (mistakes are exploration, the game is a conversation), expensive undo says 'think before acting' (commitment is the skill being tested), and no undo says 'live with it' (every action is real, and weight is the point) — three legitimate designs, and choosing the wrong one for the content is a genre-level error (an irreversible-state puzzle without undo tests patience, not insight; a permadeath roguelike with save-scumming tests nothing at all). Undo also has a hidden difficulty function: infinite undo lets designers build crueler puzzles (dead states are affordable when escape is one keypress), so generosity in the interface funds ambition in the content. The reset button is undo's blunt sibling — cheap to implement, essential everywhere states can wedge — and reset-friction (reload times, replayed preambles) is among the most-felt UX qualities in puzzle and challenge design. Key decisions: undo depth and granularity (single-step, infinite stack, or checkpoint-based — and what counts as a step), scope boundaries (undo movement but not combat results, undo placement but not spent resources — partial undo needs crisp legible lines), pricing (free, limited-count as resource like Breach's reset, or economically costed via refund rates), and multiplayer/permadeath contexts where undo's absence is the design and save-scum prevention becomes the engineering. Pitfall: mismatched undo generosity — the most common failure is asymmetry between how much the game punishes mistakes and how easily it lets you retract them: heavy consequences plus no undo drives save-scumming and quits, trivial consequences plus infinite undo drains all tension; the undo policy must agree with the consequence design, because together they are one system — the game's actual statement about what a mistake means.

VIEW “UNDO/RESET” IN THE MAP ▶