Save scumming: the art of never accepting consequences

You open the rare chest, get a mediocre item, reload the save. You get the same item, reload again. Forty minutes later you're still in the same spot on the map, obsessed with a drop the game simply isn't going to hand you right now. It's called save scumming. And there's a decent chance you do it outside the game too.

What save scumming is, for anyone who doesn't play

Save scumming is the practice of saving the game immediately before a risky action — a dice roll, an important dialogue choice, a hard fight — and reloading the save if the result isn't what you wanted. The goal is to force a favourable outcome without paying the price of uncertainty.

In games with permadeath (where death is final), save scumming is heresy. In any RPG with a free save system, the temptation is always there, blinking in the corner of the screen. Nobody's going to judge you — except yourself, thirty reloads later.

Real-life save scumming goes by other names

Away from the controller, the behaviour shows up in disguise:

• Rehearsing too much before a difficult conversation, to the point where you've already mentally given up on every possible variation before you open your mouth.
• Not sending the email yet because "it needs one more read-through" — for the eighth time.
• Delaying the project launch while waiting for a safer version, better timing, a less risky scenario.
• Leaving the relationship before getting attached, so you don't have to sit through the emotional game over.

The common denominator is always the same: save first, reload later. Control the outcome before taking on the risk.

Why the brain wants a save state

The logic makes sense from an evolutionary standpoint. The brain spends considerable energy trying to predict and avoid negative outcomes — that's adaptive, not weakness. The problem starts when that mechanism begins blocking any action with an uncertain ending.

There's also loss aversion: losing something hurts more than gaining the same thing pleases. The brain treats a badly rolled die as a threat wildly out of proportion to what it actually is — a badly rolled die.

In games, you reload because you can. In life, the illusion of "I can reload later" shows up in subtler forms: procrastinating, over-planning, stacking up so many conditions ("I'll do it when X, Y and Z line up") that the action never arrives.

What you lose to the constant reload

The memorable stories inside an RPG rarely come from the perfect run. They come from what went wrong.

The character who died on a side quest and forced an unexpected change of route. The alliance you didn't want to make but had to, and which became the axis of the whole narrative. The mediocre item you were handed and had to get creative to compensate for.

Games like Dwarf Fortress and Caves of Qud are famous for exactly this: failure generates the story. No possible failure, no narrative. And narrative is what you carry away when the game ends.

In real life, the stories you tell with the most intensity — to friends, in interviews, in the small hours of the morning — are rarely the ones that went right as planned. They're the ones that went wrong in specific, unexpected ways.

When to let go of the controls (without romanticising chaos)

This isn't a manifesto against planning. Planning is useful. Saving the game periodically is smart. The difference lies in the frequency and the trigger: do you save before every step because the next step might be bad — or do you save at logical points because you want to preserve real progress?

A practical way to spot whether you're in save scum mode: count how many decisions from the past week you "rehearsed" until you no longer wanted to make them. How many projects have a final version stored in your head that never shipped because "it isn't ready yet".

In games, the antidote to save scumming is usually playing with permadeath switched on — whatever happens, happens. In life, the equivalent is taking the step before you feel completely ready. The die is already in the air. You just haven't noticed yet.

If you want to keep going down this line, I've already written about what it means to start from scratch with everything you've learned — and about why we want to skip the boring parts instead of walking through them.

If you recognised the pattern — in a game or outside one — tell us in the comments which decision you reloaded the most. And which one you should have reloaded and didn't.