A very simple suggestion: append the world seed onto the autosave files. This would mean that if I have two worlds, World A and World B, and I play in World A for a bit, then the autosaves would be _autosave1_53894, _autosave2_53894. and _autosave3_53894 (assuming the seed was 53894). Then if I played on World B for a bit, then the World B autosaves would not overwrite the World A autosaves, as they would have a different world seed, say 46578. The World B autosaves would look like _autosave1_46578, _autosave2_46578 and _autosave3_46578.
Alternatively, you could name each world on creation, and then prepend that to to the autosave name.
I suggest this because I have just lost several hours of gameplay due to the autosaves being lost.
EDIT: I have just thought of another, related, suggestion: make _autosave1 always the most recent, and move the previous _autosave1 to _autosave2, and the previous _autosave2 to _autosave3. _autosave3 is deleted.
My (probably) final suggestion is that you should be able to make worlds save in custom folders, rather that just the default all the time.
Improved autosaving system.
Moderator: ickputzdirwech
-
- Manual Inserter
- Posts: 4
- Joined: Thu Jun 04, 2015 8:26 pm
- Contact:
Improved autosaving system.
Last edited by Dumbgenius on Thu Jun 04, 2015 9:46 pm, edited 1 time in total.
-
- Burner Inserter
- Posts: 7
- Joined: Thu Jun 04, 2015 3:23 pm
- Contact:
Re: Improved autosaving system.
Worldname makes more sense, so can you play two times AT the Same seed and can try difrent ways.
-
- Manual Inserter
- Posts: 4
- Joined: Thu Jun 04, 2015 8:26 pm
- Contact:
Re: Improved autosaving system.
It would certainly be more user-friendly, but it might be harder to code into the game (new UI elements etc.)Projekt_13 wrote:Worldname makes more sense, so can you play two times AT the Same seed and can try difrent ways.
Re: Improved autosaving system.
I think the concept of world names is very useful for much more stuff like this.
https://forums.factorio.com/forum/vie ... f=6&t=7035 Save game names
https://forums.factorio.com/forum/vie ... f=6&t=7050 World Names - New worlds have a (default) name
https://forums.factorio.com/forum/vie ... %2A#p11245 This was discussed, when the map exchange string was introduced.
https://forums.factorio.com/forum/vie ... ld+name%2A Would be useful, for many stupid things
https://forums.factorio.com/forum/vie ... f=6&t=3344 Minecraft-like World Screen
https://forums.factorio.com/forum/vie ... ?f=6&t=327 Configurable additional filename character whitelist
https://forums.factorio.com/forum/vie ... f=6&t=7035 Save game names
https://forums.factorio.com/forum/vie ... f=6&t=7050 World Names - New worlds have a (default) name
https://forums.factorio.com/forum/vie ... %2A#p11245 This was discussed, when the map exchange string was introduced.
https://forums.factorio.com/forum/vie ... ld+name%2A Would be useful, for many stupid things
https://forums.factorio.com/forum/vie ... f=6&t=3344 Minecraft-like World Screen
https://forums.factorio.com/forum/vie ... ?f=6&t=327 Configurable additional filename character whitelist
Cool suggestion: Eatable MOUSE-pointers.
Have you used the Advanced Search today?
Need help, question? FAQ - Wiki - Forum help
I still like small signatures...
Have you used the Advanced Search today?
Need help, question? FAQ - Wiki - Forum help
I still like small signatures...
-
- Manual Inserter
- Posts: 3
- Joined: Tue Mar 15, 2016 5:25 pm
- Contact:
Re: Improved autosaving system.
Hello,
At the moment, the naming of the autosaves follows a naming rotation.
First ever made autosave is called _autosave1.zip, then the following will have increased numbers until the maximum autosave count is reached and the autosave iterator is set to 1.
This results in the problem, that you can never know without seeing the dates, which has been the recently created autosave. This feels a bit random, based on the current state of the autosave iterator.
Example: Like Dumbgenius sayd I think it would be better to save the latest autosave always as _autosave1 and rename the other, then you always know which is the latest and which one is the oldest save.
Reason for me:
I have a 24/7 running game on my cloud server. If I stop the server instance and restart it again, I have to copy the latest autosave to a new static file name which I use as parameter for the start command.
This must be done because the original save game is not overwritten (like in Minecraft)
Cause of the current autosave system, I have to use some shell commands to search the latest save game which I want to continue.
Have a nice day!
I just want to show my support for this idea, I had the same idea today!Dumbgenius wrote: EDIT: I have just thought of another, related, suggestion: make _autosave1 always the most recent, and move the previous _autosave1 to _autosave2, and the previous _autosave2 to _autosave3. _autosave3 is deleted.
At the moment, the naming of the autosaves follows a naming rotation.
First ever made autosave is called _autosave1.zip, then the following will have increased numbers until the maximum autosave count is reached and the autosave iterator is set to 1.
This results in the problem, that you can never know without seeing the dates, which has been the recently created autosave. This feels a bit random, based on the current state of the autosave iterator.
Example: Like Dumbgenius sayd I think it would be better to save the latest autosave always as _autosave1 and rename the other, then you always know which is the latest and which one is the oldest save.
Reason for me:
I have a 24/7 running game on my cloud server. If I stop the server instance and restart it again, I have to copy the latest autosave to a new static file name which I use as parameter for the start command.
This must be done because the original save game is not overwritten (like in Minecraft)
Cause of the current autosave system, I have to use some shell commands to search the latest save game which I want to continue.
Have a nice day!
Re: Improved autosaving system.
That idea is good, but the change is not transparent, cause: What if you play two worlds; one day world1, the next world2? What is the "latest" save for world2 then? And does that mean, that all saves of world1 are deleted then?
Cool suggestion: Eatable MOUSE-pointers.
Have you used the Advanced Search today?
Need help, question? FAQ - Wiki - Forum help
I still like small signatures...
Have you used the Advanced Search today?
Need help, question? FAQ - Wiki - Forum help
I still like small signatures...
-
- Manual Inserter
- Posts: 3
- Joined: Tue Mar 15, 2016 5:25 pm
- Contact:
Re: Improved autosaving system.
Thats right. Considering multiple worlds, we should definiteley make the autosave world specific.
In my screenshot, the latest autosave should be named MyWorld_autosave1.zip.
Then we have multiple autosaves (based on the setting) for each world.
In fact I also like the idea of just overwriting the current world (without creating autosave files), especially in headless server mode. Than it would be like minecraft and you can always stop and start your server with the same command for the same world.
But maybe this would be a huge change in comparition to the current behavior and the user loses the possibility to go back to an older autosave.
In my screenshot, the latest autosave should be named MyWorld_autosave1.zip.
Then we have multiple autosaves (based on the setting) for each world.
In fact I also like the idea of just overwriting the current world (without creating autosave files), especially in headless server mode. Than it would be like minecraft and you can always stop and start your server with the same command for the same world.
But maybe this would be a huge change in comparition to the current behavior and the user loses the possibility to go back to an older autosave.
Re: Improved autosaving system.
I'm reasonably sure that you can do this with the headless server already. Just use the command line arguments to say 'only one autosave slot', and load autosave 1.Fensterbank wrote:Thats right. Considering multiple worlds, we should definiteley make the autosave world specific.
In my screenshot, the latest autosave should be named MyWorld_autosave1.zip.
Then we have multiple autosaves (based on the setting) for each world.
In fact I also like the idea of just overwriting the current world (without creating autosave files), especially in headless server mode. Than it would be like minecraft and you can always stop and start your server with the same command for the same world.
But maybe this would be a huge change in comparition to the current behavior and the user loses the possibility to go back to an older autosave.
-
- Filter Inserter
- Posts: 587
- Joined: Sun Jun 09, 2019 10:40 pm
- Contact:
Re: Improved autosaving system.
Since this is the closest topic to what I came to ask: I'd like to second this. My immediate problem is that I have the occasional crash (or regrettable life choice) and load from an _autosave file.Fensterbank wrote: ↑Wed Mar 16, 2016 10:48 amConsidering multiple worlds, we should definiteley make the autosave world specific.
Then I spend, like, five hours saving under the name "_autosave2" because i forgot to save it back to the original name the first time. Even just `_autosave2_autosave3` would be an improvement. -_-
Ideally, though, I'd love the game to strip the autosave suffix smartly, so loading "foo_autosave" would save as "foo" by default, but I recognise that is problematic for ... many cases, compared to just "autosave based on the current name of the game world"