Please allow me to disable the "save scum event"

[whole prairie]

This event gets bestowed upon you for Save Scumming.

Note that save scumming isn't just for "cheaters" that want hand outs.
There are many genuine reasons that someone might want to reload a quick save, and it's a bit annoying for the game to offer you a "helping hand" like you did it because you're bad.

[broken warren]

Would it technically be meta to save scum immediately? 😭

[whole prairie]

Well.. doing it for the event feels like cheating, and doing it for "genuine reasons" feels like cheating too because of the gimme-event... which is not fun

• eg:

You encountered a bug and want to roll back to work around the bug

• eg Commander not behaving as expected (Coordinated Attack is bugged under certain conditions such as pack-unpack-attack, at least last time I checked it was)

You forget to slot a resource before clicking "end turn" and want to roll back 1 turn just to make a very small adjustment to your turn with no change in decisions on the rest of your turn (you aren't using it to change any of your other decisions)

[broken warren]

I agree

Or make it more than once loading the same autosave?

[whole prairie]

I just don't really see why they would make a narrative event associated with save scumming it just seems kinda gamey..

[agile iris]

Not sure what save scumming is but narrative events get triggered almost every time (maybe every time) the game crashes. I always thought this was a bug that they need to fix

[whole prairie]

Save scumming is basically just reloading an old save to redo a turn. It's just a general gamer turn for trying again cos you didn't like the result instead of living with the outcome.

The only major issue I have is when the outcome is a bug 😂

[dreamy yoke]

I do it when the game says "major victory" and instead my unit dies

[dull linden]

How sure are we that reloading a save is the "true" condition on this narrative event?
And not just the effective trigger due to a coding bug?

i.e. it could hypothetically be possible that this narrative event is designed/intended to have a "normal" in-game (and probably easily-accomplished) condition, but that a bug in the "normal" turn-flow logic results in the narrative event not registering ... and then some difference about the loading-game code-pathway detects that the narrative condition is met but the narrative hasn't been presented to the player yet, and so pops the narrative event.

[vague turtle]

This is also what I think is happening. Or there’s some seed generated on starting a session that determines which events will/wont fire, meaning you get likely get one when it reloads yeah

[whole prairie]

It is a really big coincidence because I'm starting to see a pattern of this exact event when i reload a save.

But yeh if it is a bug and not intended as a save scum trigger, then it would be great for them to fix it I guess.

It's very "gamey" for something like that to seemingly trigger off loading a save

[dull linden]

maybe an exploration/test-case could be doing a "save scum" on like turn 1 or 2 of antiquity, where if it's a "normal" narrative event with a buggy normal-game-flow trigger, then the likelihood of the "normal" conditions for that narrative event already being fulfilled on turn 1/2 is lower.

[whole prairie]

I'll give it a go!

[dreamy yoke]

Event definitely doesnt require save scumming, Ive seen it before

[whole prairie]

Funny it didn't happen to me in my last game, but I had another event already on that turn. So maybe it only procs if there aren't any other events already.