Permadeath Run Structure
Permadeath means a run ends for good when the character dies, with the save file erased, so every decision carries consequences that reloading cannot undo.
Save exists only to suspend a session, and it is deleted on resumption or on death. Player therefore cannot scout an outcome and retry it, which changes how information is valued: unknown items are gambles, retreat is a real option, and resources hoarded for a later floor may never be used. Difficulty is not about the hardest moment but about surviving a long chain of merely risky ones.
Rogue, written by Michael Toy, Glenn Wichman and Ken Arnold around 1980 on university Unix systems, combined it with generated dungeons because both answered the same constraint. Nobody could author enough content for repeated play, and shared machines made copying a save file both easy to detect and unsporting. Erasing progress also solved a design problem, since when a level is generated fresh, losing a run costs a situation rather than a story.
Consequence attaches emotional weight to ordinary decisions, which is why permadeath produces the anecdotes players tell each other. It also makes games hostile to interruption, punishes learning by exploration, and can turn a long run's ending into wasted time rather than drama. Most modern designs compromise, keeping the deletion but adding something that persists, which is a different mechanic with a different psychology.
Lineage — traced back to a root
Every mechanic in this dataset resolves to an ancestral chain. This one is 3 steps deep, beginning with Numeric Score in 1972.
Descends directly from
Forked into
X-COM: UFO Defense applied it to a squad, Spelunky paired it with short fast runs, and FTL: Faster Than Light made it the story of one voyage.
Carried forward by 31 later games
Everything downstream
6 mechanics ultimately descend from this one.
Look this mechanic up elsewhere
Also called: permadeath, ironman mode, roguelike death