# Savescumming - Allow it? — retained record

> Retained reddit record from reddit:gamedev.

Canonical: https://highsignal.app/data/records/c4fa85513c5c7e64

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:gamedev)  published 2026-10-20 23:33 ingested 2026-10-21 02:37

[original source ↗](https://www.reddit.com/r/gamedev/comments/1xb7m3u/savescumming_allow_it/)

## retained text



```
**TL;DR: Guard against save scumming, or allow free use of it if the player desires?**  
  
My game involves a series of missions (levels) where failing has very steep consequences, to the point where a series of failures will result in the player failing the final mission and getting a "bad ending", effectively having to start over from the beginning for the "good ending".

Since I allow users to freely save any time they're not in a mission, they could easily forfeit a bad state and retry from their last save point for a more favorable outcome.  Or make multiple unique saves as "checkpoints".

Currently, I'm preventing the user from doing this at all.  If the player enters a mission, the game writes that the mission was launched in the save file.  On mission complete, the results (pass or fail) is similarly written to the save file.  However, if the user force closes the game mid-mission and the game is launched with a mission in the "launched, but incomplete" state, the game immediately writes this mission as failed and the player suffers the relevant consequences.

The second case where the user makes multiple unique saves is technically not completely possible to guard against, as the user can find the save file data on their hard drive and make backup copies there.  But in the game itself, there is no way to record multiple files at different states, it always overwrites the same file no matter what.

All this to say, I'm kind of basing this off of vibes and maybe as something I can use as a selling point.  I want the player to really feel that actions have consequences in my game.  If they launch a mission, they better be ready to see it through and live with the results.

Some additional context: this game takes some inspiration from roguelikes in that each "playthrough" will have heavy randomness to it with some guardrails, in hopes that it will provide some replay ability and make everyone's playthrough unique.  The actual game isn't really roguelike though, as a "run" will take several hours and potentially many play sessions.  The closest thing I'm inspired by is the management side of the X-COM games.

Thoughts?
```



document fetched 2026-10-21 00:25 · canonical https://reddit.com/r/gamedev/comments/1xb7m3u/savescumming_allow_it
