Dragonwilds Server Backups & World Migration

Always stop the server before copying or replacing save files.

Back up a server

1. Stop the server cleanly.
2. Copy the entire RSDragonwilds/Saved/SaveGames folder to another disk or cloud location.
3. Put the date and server version in the backup folder name.
4. Keep more than one restore point.
5. Restart and confirm the world loads before deleting any older copy.

Keep at least one backup away from the server itself. A copy on the same disk does not protect against disk failure, accidental instance deletion, or a hosting account problem. For an active group, combine provider snapshots with periodic downloads you control.

What to preserve

At minimum, preserve the complete SaveGames directory rather than selecting one unfamiliar file. Also export the dedicated-server configuration and record:

• the current client and server version;
• world and server names;
• Owner ID and access settings without publishing passwords;
• enabled crossplay state;
• installed mods and their versions;
• the date and reason for the backup.

Move a local world

Local Windows saves are normally under:

C:\Users\YOUR_NAME\AppData\Local\RSDragonwilds\Saved\SaveGames

Stop the dedicated server, back up its current SaveGames directory, empty the live folder, copy the local .sav file into it, then start the server. The dedicated server loads the latest available save.

For a managed host, use its file manager, SFTP access, or documented migration tool. Upload while the service is stopped. If the provider creates a default world on first boot, download that world before replacing it so the rollback path remains available.

Move to another provider

1. Stop the old server and create a final dated backup.
2. Download the complete save directory and relevant configuration.
3. Create the new server but keep it stopped before uploading the old world.
4. Back up or remove the new provider's automatically generated test world.
5. Upload the transferred save and apply supported configuration values.
6. Start the new server and join before cancelling the old service.
7. Confirm character progress, buildings, storage, world settings, and player access.

Do not cancel the source host until someone outside the administrator's local network has joined the destination successfully.

Restore a backup

Stop the server, download the current broken state for later diagnosis, and place a copy of the chosen restore point in the live save directory. Start the server and verify the world before discarding anything. If a current 1.0 save-corruption issue is involved, review known issues before attempting community recovery steps.

Do not edit a save directly. Test migrations with copies and keep the untouched source until every player confirms the correct world and characters.

Source: official dedicated-server world-management steps.