There's one point in VideoGame/SuperMarioRPG where I always save scum: it's in bean Valley with the 5 pipes. three of the pipes have slot machine type chests where you either get completely healed, a flower tab, or a rock candy. I save scum and reset as nessecary until I have gotten a rock candy from all of them.

This was pretty much the only way this editor ever beat ''OregonTrail'' in elementary school.

This Troper had a teacher who figured out how to actually beat the game without savescumming-namely, a callous disregard for the well-being of the party. Running low on food? Continue. Shot yourself trying to shoot a bear? Continue. Dying of dysentery? Continue. Continue, continue, continue. Of course, by the time you actually got to Oregon, there was probably like one of you left, on the verge of death, but since you ''got there,'' you automatically got better instantly and had a much better life because you made it to Oregon.

Your teacher must not have had ''OregonTrail 2'' then. If s/he did, you would have had the option to treat stuff and it continues as normal anyways. (Unless you decide to slow down; I still have people dying of a common cold after I increase fluid intake)

This Troper doesn't remember ever having to do this in this game. Sure, the lose to win ration was around 3 to 1, but it was definitely possible to get at least most of the party to Oregon safe and sound.

Every run for Me always involved saving at "The Dallas", good thing too, I hit a rock on My first run and lost Aren (A Lucario), I obviously restarted

The newer versions of Oregon Trail are ''sadistic'', to the point where you wonder where the metaphor for how tough it was to make the actual journey ends and where the developers' genuine hatred of little children begins. Example: Despite what common sense should dictate, the Oregon Trail is a line that can never be deviated from (except at pre-determined junctions). There are places where you'll have to go up a hill. You can't go around it of course, you have to go up. Only it's raining, and the hill is muddy. If you try and go up your mules will twist their ankles and die. Reload. Try waiting out the rain. It never works. This troper sat through a '' two year rainstorm'' as the party slowly ran out of food and ammunition, broke bones for no particular reason, and died of dysentery.

Obviously, you should have continued.

Sometimes, you actually didn't really have a choice; if you're trying to cross a really really steep mountain range it can be hard to go around.

I never had this problem. Ever. I always arrived safe and happy in Oregon.

This troper has never really had to do that even though he ''has'' saved at some hills or rivers to try doing stuff like see how many times I can tip my wagon by trying to use ropes on an icy hill or doing something my sister did once and trying to ford the river that was 7 feet deep

This troper saved the free Rocket Launcher from ResidentEvil4 to kill Salazar. She kept missing and restarting the boss fight until she won.

This is an absolute must when playing ''MLB Front Office Manager 2009''. The game has a pretty bad AI engine. When you play one of the many baseball games on "simulate" mode, you don't make any choices, you just get the end result of the game. When you get a result you don't like, go back and do it again. This is necessary because the game will make the most stupid choices, such as:

Pulling a good pitcher out of a game to substitute another pitcher, usually the pitcher with the highest ERA, which is the exact opposite of what any human being with experience beyond T-ball would do.

The game features the entire farm system for MLB and MiLB. At times, if you don't look out, the AI will move a plyer up to a higher league after you've sent him down and at other times, will also re-acquire a player you got rid.

When anyone ever have a dream where one goes about one's day. When you wake up, it feels exactly like loading a save game.

In games like Half-Life (2), while I normally did not SaveScum, but just relied on the autosave-points (especially HL2) and/or quick saved every now and then (HL1, as autosave-points are more scarce an less well placed), I would occasionally end up at some point of the game with extremely low health, but then pass an autosave-point and/or accidently hit quicksave. Knowing the previous savestate (i.e. the one before the current, low-health one) is waaaay back, I then would resort to heavy SaveScumming to get through that part until reaching the next bunch of health powerups.

This troper had to do this just to make it out of Hades Island in MegaManBattleNetwork 3, after obtaining the PlotCoupon to continue the tournament. I'd literally take a step or two forward and then save; resetting if I had a random encounter while moving because I was out of healing items, down to only 1HP, and unable to deal heavy enough damage to defeat the power enemies in that area.

This troper was pretty guilty of this as a kid, but I wanted my Groudon dammit.

Oh man... Any "legend" you try to go after without instant win Master Balls (heh heh) you HAVE to save right before it.

This troper views this trope as apostasy against the gaming gods and never does it even when he should. Then he wonders why games are so difficult.

This troper Had to save ALOT in skirmish matches in Tiberian sun Not incase of mistakes but because the damn game had a tendency to crash for no damn reason! Especially when playing Nod

When I first started XCom, I kept no less than four save files for one game: A "Safe" overworld save (saved once a month or so ingame, for when I was sure things were going well), a "Danger" overworld save (when I was about to do something risky), a beginning-of-combat save, and a turn-by-turn combat save. In my defense, this was partly necessary because compatability issues caused the game to repeatedly crash. Can't really say I have an excuse for doing this with SuperRobotWars, though. Furthermore, in {{Civilization}}, I have a "safe" save (done when I'm sure I'm doing well), a "standard" save (done every other turn or so), and a "risk" save (when I'm about to do something I may regret).

I once did this in a particularly epic battle on Age of Empires 3. Me (Ottomans) vs. Sioux vs. Aztec vs. Iroquis vs. Dutch vs. Russians vs. Portugese vs. Germans. Paranoia crept in during the first three minutes. I'm about to attack one Aztec villager about three seconds travel away... too risky, must save first! I'm going to take the six Janissaries instead of a Great Bombard, must save! It has been three minutes since a fight, must save! Twelve save files in the first ten minutes of actual gameplay.

Out of boredom, and because I wanted that Cassus Fett Armor, this Troper won upwards of 15,000 playing Pazaak in the lower city cantina. He and the Rodian at Fazza's lodge are unlimited play.

This Troper did the same thing. I learned my lesson from being a {{Sierra}} jock. Sierra games flat-out tell you "save early, save often." It's also VERY smart to have a ton of saved games and bookmarks if you modify your game. Some mods do not play nicely with one another and the only way to test compatibility and fixes is to save, quit, tinker, then reload.

This troper was able to unlock several achievements in MassEffect2 only available using certain squadmates (Use 2 Biotic Attacks/Overload/Incinerate/Warp 20 times) by SaveScumming specific moments of Freedom's Progress, Horizon, and the Korlus missions with Jacob/Miranda/Kasumi/Mordin freeing me of having to keep Jacob or Miranda with me more than needed.

Due to the number of sadistic DMs I have played with, I now keep a piece of paper with save and load buttons drawn on it, mostly to show when I think they're about to go off the deep end.

Down there where it says "Keep refreshing...". Don't refresh; you need to go to an earlier save.

When I was quite young, and just learning about emulators, I always used save states to beat SNES games like A Link To The Past. Hence I thought those games were much ''easier than they actually were''. Then I learned save states were the "wrong" way to beat a game. When I went back and replayed those games, I was really shamed of finding out I was apparently a worse gamer then I was before, until I remembered I used save states last time.

This troper almost always plays this way, even if she no longer really needs to to beat the games. She finds it easier to beat bosses when she's not worrying about redoing the dungeon if she fails.

I would do this all the time in the early Mario Parties, against the computer anyway. Since the game saved your progress at the beginning of every turn, if the computer made a move that endangered my win, I would turn off the N64 and reload the party, and they would usually do something else entirely.

I do this all the time if I have the chance, especially for hard games like ''Ristar'' and ''Bubsy in Claws Encounters of the Furred Kind''. Pretty much the only time I don't is if I'm playing on Time Attack mode or just messing around.

I do this all the time, too (except for roguelikes, where a large part of the fun IS the randomness). I'm playing for fun, not to brag about completing the game.

This Troper is wondering if the secret bonus of SuperRobotWarsOriginalGeneration 2's stage 15 was possible without SaveScumming.

If I wanted to gold a Burnout 2 championship but lost a particular race, I'd then waste time waiting for those other races to finish, even if I rebooted the machine. Or I could reset the GameCube (or PS2, as that was what I played on) before the "saving" screen and start where I left off with the prior save file.

Since I'm particularly terrible at hacking in {{Bioshock}} I've ended up resorting to this. Sodding ''hate'' the "hacking" minigame.

Kyogre. Oh, gosh, Kyogre.