· 5 min read
Failure needs a short commute
When a game expects repeated failure, retry boundaries should return players to the skill they are learning unless the wider reset changes enough to make the next attempt new.
Kill the player on the last jump of a room, then respawn them before the easy corridor, ladder, door animation, and empty landing they already solved. On attempt twelve, all of that material is familiar while the jump the player is trying to learn waits at the far end for another thirty seconds of admin.
When failure is expected, the retry boundary belongs near the unanswered part of the problem. A wider reset can work when it changes the next attempt enough to justify the trip, but replaying solved setup turns difficulty into waiting. Recovery sets the rhythm looked at what the player does after taking damage. Death asks the same design question at a larger scale: what should they have to do again?
Keep the mistake in frame#
Maddy Thorson's “Celeste & Forgiveness” lays out the tiny favors hiding inside a notoriously difficult platformer: coyote time, input buffering, corner correction, and several wider-than-they-look action windows. Those allowances keep a demanding jump focused on the movement the level asks you to learn instead of every tiny timing error around it.
The official changelog is gloriously fussy about the other end of that loop. Version 1.2 added Quick Restart and fixed cases that could force a restart from the previous checkpoint. The same release corrected missing spawn points that sent Madeline to the wrong place after death when a room had been entered from an unexpected direction. Dull patch notes, until you imagine making the same failed jump after each one.
Some of those spawn corrections are plainly correctness bugs, and the changelog leaves their design motive unstated. The practical effect is still worth staring at: fewer unrelated actions sit between the failed attempt and the next try. The designer gets more repetitions of the actual skill before attention cools off.
The commute becomes part of the test#
A long runback changes what a difficult encounter measures. The player has to preserve concentration through material they already mastered and may need to conserve healing on trivial enemies along the way. Sometimes that pressure belongs there. An attritional game can make the approach part of the encounter because arriving depleted is one of the questions being asked.
A fixed corridor with no meaningful resource cost has a weaker defense. The player demonstrated the route before reaching the failure point, so repeating it supplies almost no new information to either side. This is the irritating cousin of the mistake in Let the easy fight live: repetition can establish rhythm, while compulsory repetition after every death can flatten that rhythm into a toll booth.
A wide reset can earn itself#
Hades deliberately throws the player much farther back, and Supergiant's official FAQ gives the reset plenty to carry. A run is expected to end in death, the next escape attempt is randomized, god combinations change, and new story events can appear between attempts. Characters remember what happened. Even God Mode increases damage resistance after deaths, so failure can alter the conditions of the next run.
The House of Hades, the next build, and the next sequence of chambers can all be different after a loss. Shortening that loop to the last room would amputate systems that depend on death reaching back into the rest of the game. I would not use the same excuse for a hallway whose only update is that its enemies have respawned in the same spots.
Buried in Celeste's changelog is the wonderfully unglamorous version of the whole problem: a missing player spawn point could make death return Madeline to the wrong place after she entered a room from an unexpected direction. The player died in one room, and the game answered from somewhere else.