No, I’m offering an alternative to savescumming in a thread specifically about player behaviour surrounding failed checks. Try thinking outside the box: game design doesn’t have to delight in wasting the player’s time and disincentivising certain behaviour through load screens just because ‘that’s how it’s always been done’.
Earlier in this thread you said “Simple: They'll allow it. It's up to the player to decide if they want to save-scum or not.“ Please explain why this ‘It’s up to the player to decide...’ logic applies to savescumming, but *doesn’t* apply to an optional setting which achieves the exact same thing as savescumming but bypasses the load screens.
There’s also the functionality of allowing players to roll their own dice on checks to consider, which I expect some will want to do if the game is going to keep the ‘hold everything, we’re doing a dice roll’ mechanism on checks.
You are equating the ability of players to reload with manually entering numbers into every dice roll if they don't like it. Would you prefer if the game keeps one save file and one save file only and overwrites it, writing to the hard disc, with each and every dice roll, just to prevent some random people from possibly save-scumming?
If you say you do prefer that ridiculous, resource-intensive system, you are trolling, go away. If you say you do NOT prefer that system, you only bothered equating the two things to stir up trouble. Hence, you are
still trolling, go away.
