Improved autosave feature

[Pecius]

Autosave now mimics its singleplayer counterpart.

Changes:

• Autosave interval is set in ingame days instead of minutes in real time.
• The countdown is influenced by ingame speed setting which means it also stops when the game is paused.

Notes:

• New default value of 0.5 days is around the old default 8 minutes at normal speed setting.
• Autosave countdown is reset when user invokes a manual save (via /autosave chat command).

[SamboyCoding]

This indentation doesn't look right, but it might be github's fault.

[Pecius]

Ah, that must've slipped in when I changed from tabs to spaces. It's fixed now.

[MilanDierick]

Can we make this change toggable? When I plan out parts of my base without time advancing, no saving is happening, so when a desync happens (game can desync while Not running, happens rarely) or when the game crashes, all my progress from the past 10 minutes or how long it takes for a Day to pass on 1x speed, is going to be löst.

[Pecius]

Can we make this change toggable? When I plan out parts of my base without time advancing, no saving is happening, so when a desync happens (game can desync while Not running, happens rarely) or when the game crashes, all my progress from the past 10 minutes or how long it takes for a Day to pass on 1x speed, is going to be löst.

I don't see a point in disabling the whole feature.
As this version makes sure the save is done every x specified ticks (± current speed value).
Compared to older version where you have a chance to lose (or to simulate back) more ticks depending on the current speed (3 times more at Fast and 6 times at SuperFast).
Also keep in mind that everything you do while your game is paused doesn't add up to simulation time.
But perhaps we could add a switch in options that would let it tick at normal speed while your game is paused.

[MilanDierick]

People (like myself) sometimes like to tinker with and design stuff for more than 30 minutes, all while the game is paused. For some reason, the game desyncs, or just crashes, or something else goes wrong, and I need to reload. When I go and look at the most recent autosave, I see that it's 30 minutes ago, because it only saves your game when you are actually advancing time. That would make me really salty...

[jacobEAdamson]

@Pecius Can we have an option for both in the hosting page? You first specify if it autosaves every X minutes or every X days (Autosave Interval Unit maybe?) and then specify the interval.

I also tend to spend long phases during base development and see potential for desyncs to lose information.

[Pecius]

I added a switch in mod options that you can enable and disable while you're playing.

@Pecius Can we have an option for both in the hosting page? You first specify if it autosaves every X minutes or every X days (Autosave Interval Unit maybe?) and then specify the interval.

Adding an option for both new and old system is an unnecessary over-complication that will be confusing for users.

[MilanDierick]

I added a switch in mod options that you can enable and disable while you're playing.

What do you mean by that? Disable or enable the auto save feature altogether?

[Pecius]

Sorry, I meant that I added a switch that lets you decide if you want to stop the autosave counter when your game is paused.

[MilanDierick]

Sorry, I meant that I added a switch that lets you decide if you want to stop the autosave counter when your game is paused.

Ah, got it, that should work. When the game is paused, does it tick at 1x speed when you enable the option?

[Pecius]

Yes it does tick at 1x speed with that option (disabled) when the game is paused.