Save Scumming

Save Scumming is the practice of saving before a risky or randomized moment — a dialogue check, a gacha pull, a dangerous fight — and reloading if it goes badly, repeating until the outcome the player wanted comes up. It turns a game's stated stakes into something closer to an infinite-retry vending machine: the risk was real only for players who choose not to do this.

Whether it counts as cheating depends entirely on what the save system was designed to be. A game with manual, unlimited saves at any moment is implicitly tolerating it — the option is right there in the menu, unhidden. A roguelike or an "ironman" mode is built specifically to close the loophole: Permadeath removes the save to reload back to, and some designs go further by writing the save file over itself on every action rather than at checkpoints, so there's no earlier state left to return to at all. Seeded Randomness closes a subtler version of the same door — fixing the random seed at the start of a run means reloading and retrying the exact same input sequence reproduces the exact same "random" result, so scumming a seeded roll accomplishes nothing.

The interesting question isn't whether scumming is possible but whether it's rational. A player facing a single unrecoverable dice roll with permanent consequences and no in-fiction justification for retrying is, in a real sense, being asked to gamble with stakes the designer didn't actually want enforced that harshly — reloading in that case reads less like cheating and more like a sane response to a poorly calibrated risk. A design that truly wants its randomness respected has to make the save discipline part of the contract, the same way Soulslike makes its checkpoints (rather than an undo button) the honest cost of failure.