Where to check first
| Setup | Likely place | What to confirm |
|---|---|---|
| SteamCMD install | The folder used with force_install_dir | Look for generated world, save, or server data folders after first launch. |
| Windows home server | The folder where you run the server executable | Check modified dates after stopping the server. |
| Linux VPS | The server user install directory | Check the folder where the launch command runs. |
| Managed host | Provider file manager or backup panel | Download both saves and config before editing. |
Safe way to identify the active save
- Start the server once and let it load the world.
- Stop the server cleanly.
- Sort files and folders by modified time in the server directory.
- Look for save, world, or data folders changed during the last run.
- Compare the world name with the config auto-load value if one exists.
- Copy the save folder and config file together into a dated backup.
Backup package
| File or folder | Why include it | When needed |
|---|---|---|
| World/save folder | Contains settlement progress | Every backup and migration. |
| Config file | Points to the world, password, port, and player settings | Restore, host move, or troubleshooting. |
| Notes file | Records date, server version, and reason for backup | When multiple backups exist. |
Common mistakes
- Backing up server files but not the actual world folder.
- Copying saves while the server is still writing data.
- Restoring a save but leaving config pointed at a different world.
- Uploading saves to a host without downloading a local copy first.
- Deleting the old server before testing the restored world.
Related Romestead server guides
Use the save backup guide for routine backups, update broke save for emergency recovery, move server to another PC for migration, and hosting options if you want easier backup tools.