Autosave to primary file
Posted: Wed Apr 19, 2017 8:59 am
Good day,
I have read a few forums, some reddit etc.
It seems that when running a headless server, the autosave feature works as intended.
However, with a headless server powering off forcefully (windows updates, power shortage, hardware failure, human error) everything comes back online after solving the issues.
The problem really is, that the autosave is saved, but the server will load the fixed - predefined - savegame.
This in turn would mean having to rename the autosave to the savegame and replacing this manually.
Now obviously, people can write scripts, bots, executables whatever to do this automatically, but this seems trivial.
The obvious immediate solution would be to limit the server to 1 autosave file and configure the server to load just that file. But i can understand that this leads to some issues.
Is there a way to force this from a configuration point of view? Maybe an implementation idea for 0.15 or 0.16?
Say something like ... autosave.zip equals loadsave.zip
I have read a few forums, some reddit etc.
It seems that when running a headless server, the autosave feature works as intended.
However, with a headless server powering off forcefully (windows updates, power shortage, hardware failure, human error) everything comes back online after solving the issues.
The problem really is, that the autosave is saved, but the server will load the fixed - predefined - savegame.
This in turn would mean having to rename the autosave to the savegame and replacing this manually.
Now obviously, people can write scripts, bots, executables whatever to do this automatically, but this seems trivial.
The obvious immediate solution would be to limit the server to 1 autosave file and configure the server to load just that file. But i can understand that this leads to some issues.
Is there a way to force this from a configuration point of view? Maybe an implementation idea for 0.15 or 0.16?
Say something like ... autosave.zip equals loadsave.zip