Stationeers worlds represent a lot of careful work, and the game only writes them out on a save. Knowing exactly when that happens is what protects a base.
When Stationeers actually saves
- On the autosave interval, set by
SaveIntervalinsettings.xml, in seconds. - On a clean shutdown.
- When an admin runs a save command.
Anything else, including the process being killed, loses everything since the last save.
Take a backup
- As an admin in game, run:
or type the save command in the panel Console.serverrun save "myworld" - Stop the server from the panel and wait for it to report it is offline.
- In Files, find the saves folder and download the folder for your world.
Do this before a game update, before a settings experiment, and before anything you would be upset to lose.
Restore a world
- Stop the server.
- In Files, upload your saved world folder back into the saves directory.
- Open
settings.xmland setSaveNameto the folder name. - Start the server and watch the console as the world loads.
The world came back empty
- Check
SaveNameinsettings.xml. A name that does not exist makes the server generate a fresh world, leaving the old one untouched on disk. - Check the saves folder in Files. Folder sizes and modified dates tell you which save is the real one.
- If you edited
settings.xmlwhile the server was running, the change was overwritten on shutdown and the server may have gone back to a different save name.
Lower the risk
- Reduce
SaveIntervalif you lose progress regularly. More frequent saves cost a short pause each time. - Turn on
AutoPauseServerso the simulation is not running unattended between saves. - Take a download before every game update. Stationeers updates occasionally change how worlds load.
What to send support
Open a ticket with the save name you expect, a listing of the saves folder, and the last hundred lines of the console from the start where the world went missing.





