Save Systems Are Ideology

The save system is the least discussed and most consequential decision in a game’s design, and the reason it goes undiscussed is that it looks like plumbing. It reads as a technical concern — where the file goes, how big it is, what gets serialised. It is nothing of the kind. A save system is a formal statement about what a mistake costs, and since the cost of a mistake is what turns a decision into a decision, the save system determines whether the game contains any.

Two games can have identical mechanics, identical enemies and identical maps, and be entirely different objects because one of them lets you press F9.

What quicksave does to a game

Take the purest case. Quake gave us F6 and F9 — quicksave and quickload, bound to adjacent keys, instantaneous, unlimited. The whole PC shooter tradition inherited it and a lot of us learned to press F6 on a rhythm, the way you’d tap a bannister going upstairs.

Consider what that does to a corridor with three enemies in it. The designed experience is a risk assessment: how much health, how much ammo, what’s the opening move, can I retreat. With F9 available, all of that collapses. You don’t assess the corridor; you sample it. Try the doorway, die, reload, now you know where they stand. Try the grenade, reload, try the flank. What was a decision under uncertainty becomes an exhaustive search of a small solution space, and the player is doing it correctly — this is the optimal strategy the system provides, and expecting players to decline free information is not a design, it’s a wish.

The tension didn’t leave because players are cheaters. It left because the save system quietly announced that the past is editable, and a game where the past is editable cannot contain a gamble. Everything becomes a puzzle with a lookup table, and the lookup table is you, doing it manually, at three seconds a consultation.

The ink ribbon is an argument about geography

Now the opposite ideology, from 1996. Resident Evil put saving on a typewriter, in a specific room, and made it cost an ink ribbon you had to find and carry.

Look at how much design is hiding in that. Saving now has a location, so the mansion’s layout acquires a gravity — the save room is a place you think about from three rooms away, and the walk back to it is a decision with a cost. Saving has a price, so every ribbon spent is a ribbon unavailable later, and the question “is this worth recording” is genuinely live. And because ribbons occupy inventory slots, the save system is competing with your ammunition for space on your person.

The result is that the fear in Resident Evil is a fear about distance. You are not scared of the zombie; you are scared of the zombie plus the twelve minutes of progress between here and the typewriter, and that arithmetic is running in your head the entire time you play. It’s the same trick as the tank controls that were the point — friction chosen deliberately, to make a room feel like a room. Capcom knew exactly what it had: the RE2 remake in 2019 shipped Hardcore mode with the ribbons restored, because the studio understood that the difficulty of that mode was the save system rather than the enemy health.

The bonfire says the past is fixed

FromSoftware’s contribution is the strictest position on the board. Dark Souls autosaves continuously to a single slot and gives you no way to undo anything. Kill an NPC by accident and they stay dead. Burn the wrong item, misjudge a covenant, drop your souls in a lava pit — the game records it before you’ve finished regretting it.

That’s an ideology, and a fairly severe one: the past is real and it belongs to you. Everything the games are famous for follows from it. The bonfire matters because you can’t just quicksave in the corridor. The messages and bloodstains mean something because everyone’s world is one continuous unbranching object. The level design that folds back on itself can put a shortcut lever behind an hour of danger because the hour cannot be edited out.

Firaxis found the same idea from a different direction with Ironman in XCOM: one save, overwritten constantly, no reloading a squad wipe. It’s optional, which is the honest version — the studio knows that Ironman is the game, and also that saying so out loud would be rude. Every XCOM player who has reloaded a 95% miss knows precisely what they took from themselves, and does it anyway, which is a sharper piece of design commentary than anything I could write.

The roguelike deletes the file, and means it

The traditional roguelikes went further and built the ideology into the file system. NetHack lets you save, then deletes the save the moment you load it. The save is a suspend — a way to stop playing, with no capacity to become a checkpoint. Try to copy the file out and back, and you are save-scumming, a term the community coined specifically so it could be looked down on.

That deletion is a moral position expressed in code. It says: the run is the unit of the game, the run is unrepeatable, and everything you learn has to live in your head rather than on the disk. It’s the reason the loop is the argument, and the reason permadeath buys the stories it buys — a death that can be undone is an anecdote about nothing.

Pathologic runs the same logic across a twelve-day clock. The days pass, the plague spreads, people you failed to reach die, and the game keeps going with those absences in it. It is a game that wants you to lose, and it can only want that because it refuses to let you take losing back.

The honest middle: rewind as a mechanic

The most elegant solution I know brought the undo inside the fiction. Prince of Persia: The Sands of Time gives you a dagger that rewinds time a few seconds, a limited number of charges, refillable. Mechanically it’s a quickload. Formally it’s completely different, because it’s in the world — it costs a resource, it has a range, it’s a thing the Prince does. And the framing device seals it: the Prince is narrating the whole story in retrospect, so when you die he interrupts himself to say that’s not how it happened, and starts the passage again. Death became a storytelling error. Ubisoft Montpellier took the least examined system in games and made it the plot.

Braid pushed it to the limit by removing failure entirely — rewind is unlimited, death is impossible, and the tension moves to the puzzles, some of which contain objects the rewind doesn’t affect. Jonathan Blow’s move was to notice that if undo is free, undo has to become the subject.

When the save file becomes a character

The logical end of this is a game that knows it has a save file and has opinions about it. Undertale gets there in its first few minutes: Flowey, the talking flower, discusses your ability to save and load as a power he can see you using, and the game’s design proceeds from there. Toby Fox took the one system every player treats as invisible infrastructure and pointed at it.

That’s a stunt, and a good one, and it works because it’s true. The save file is a power the player holds over the fiction — an ability to unmake events that no character in any story has ever had. Most games handle this by pretending it isn’t happening. A few notice, and the noticing is instantly the most interesting thing in the game.

Returnal is the recent case study in how live this all is. Housemarque shipped a roguelike with runs that could last hours and no way to suspend one, which is a coherent artistic position and also an argument with the actual furniture in people’s houses — a two-hour run with no pause is a game for people who don’t share a television. The studio patched a suspend option in later. That patch is an ideological retreat, negotiated in public, and I think it was the right call in a way that costs something real.

The emulator save state, and a confession

I should admit my own position, because it’s inconsistent and I know it.

The games I grew up loading off tape had, in most cases, no save at all. You got three lives and a session, and the session ended when it ended, and that was the arrangement — the patience the tape load taught was partly the patience of losing an evening’s progress to a bad jump. I now play those same games in emulators with a save state on F2 and a restore on F4, and I use them, and the games are visibly less than they were. The C64 shoot ’em up that was a brutal exercise in pattern learning becomes a slideshow I scrub through. I have imported a 2020s ideology into a 1985 object and it has quietly dissolved.

Which is the whole point. Nobody changed a line of that game’s code. The save system changed, and the game changed with it, because the save system was doing the load-bearing work all along, deciding what any of it was worth.

So when you find yourself arguing about whether a game is too hard, check whether you’re actually arguing about where it lets you write to disk. Nine times in ten, you are.