[2.0.72] Autosave index jumps backward after loading older saves

[AntiElitz]

With many autosave slots (e.g., 1000), loading an older save makes the autosave counter jump back to earlier numbers.
Example: at autosave ~600, loading a save from 1 hour ago causes new autosaves to start around ~540.
This overwrites recent autosaves even though free slots exist.

Expected:
Autosaves should continue from the latest index, not move backwards on load.

[Rseding91]

Thanks for the report however autosave indexes are based off the time in the save file and are not shared/incremented across different saves.

Specifically the autosave index used is computed as: (update-tick / autosave-interval - 1) % autosave-slots + 1

[AntiElitz]

Thanks for the report however autosave indexes are based off the time in the save file and are not shared/incremented across different saves.

Specifically the autosave index used is computed as: (update-tick / autosave-interval - 1) % autosave-slots + 1

I see that it works this way. However I am not sure that this is reasonable? It kind of defeats the purpose of having multiple autosave files a bit. Maybe another method would work better to serve the autosaves idea of having the recent backups not override each other.