It’s time to accept save scumming as the best way to play RPGs

polygon.com:

My time playing Baldur’s Gate 3 looks like this: Move my player character toward a quest point, have Shadowheart cast Guidance, hit F5 to save, then try the conversation. Other times I’ll take Astarion to a door, hit F5, then have him pick the lock. Who knows if there will be danger within?

I’ve always been an ardent believer in save scumming — that is, saving right before major decision points and restarting after an unfavorable outcome — through playing role-playing games. And after poring over the game’s subreddit, it’s become clear to me how many other Baldur’s Gate 3 fans approach the game in the same way. It’s key for undoing a bad-luck die roll, correcting a passive perception check, or redoing a battle with a bad outcome. But I’ve long save scummed through RPGs of all stripes — immersion be damned — and I’m finally ready to not only admit it, but advocate for it.

I’ll own up to it. I’ve always been a sore loser in games of luck; I typically prefer management or strategy games where I have more control over what happens. In RPGs especially, I meticulously plan party composition to be able to tackle a range of challenges. It absolutely grinds my gears anytime I fail a die roll that my character has proficiency in — like if Karlach fails to turn a wheel because she fails a strength check, or if Shadowheart fails to persuade a follower of Shar, or if my Druid character (with great nature and animal handling stats) fails to win over an Owlbear looking for refuge.

A more level-headed player might gracefully accept that being skilled at something doesn’t mean you always get the desired outcome. Of course we all have “bad days” where things don’t go our way, despite our talents. But I have not reached that level of