Dragonwilds: Saves and Backups

The dedicated server writes the world to disk on a timer and does not write an extra save when it shuts down, whether you pressed Stop or a restart ran. That is how the game is built. What you can change is the timer: the game's own default is 5 minutes, Haptic sets it to 20 minutes, and the Autosave interval setting takes anything from 1 to 60 minutes. A shorter interval means less can be lost when you stop the server; a longer one means fewer save pauses.

Automatic update restarts only happen once the server is empty, so they never cut anyone off mid-session. With Wake & Play, a server that empties waits for its next autosave before it goes to sleep, so nothing is lost when it sleeps.

In practice: if your group finishes a build and you stop the server right away, everything since the last autosave (up to 20 minutes on the default) can be gone when you start again. Have everyone quit to the menu first, then stop.

To see when the world last saved, open the Console and look for the newest line ending in Save completed SUCCESSFULLY. The server prints one every time it saves, so if that line is recent, stopping now loses little.

The save is rsdw-saved/SaveGames/<world name>.sav, one file per world, named after the world. Next to it the server keeps the previous save as <world name>.sav.backup. You can see both on the Files card or over SFTP.

Characters are not on the server at all. Each player's character (inventory, skills, quests) is saved on their own device, so world backups hold the world only. Restoring a world never rolls back anyone's character, and a player's character goes with them to any world they join.

• Every time the server stops. A backup is taken as the server goes down, so it captures the last autosave, not the moments after it.

• Once a day while the server is running.

• On demand. Take one yourself from the Backups card before a risky change, such as uploading a different world or adding a mod.

Backups live in cloud storage, outside the server, and each one holds the .sav as it was at that moment. Restoring one puts that file back and the world loads from it on the next start. To keep a copy on your own PC, download the world: download your world.

1. Stop the server.

2. Open the Backups card and pick the backup from before the change you want to undo.

3. Restore it. A backup of the world as it is now is taken first, so a restore is itself undoable.

4. Start the server. The world name has not changed, so friends join exactly as before.

The server loads SaveGames/<World Name>.sav by name. Rename the file, or change the World Name setting, and the server starts a brand new, empty world with the new name. The old file is not deleted; set the name back and it loads again. If you ever start the server and find a fresh world, check the name on your card against the file names in SaveGames before assuming anything was lost.

• Stopping the server to force a save. Stop does not save; it only takes a backup of the last autosave. Lower the Autosave interval instead, or have everyone quit to the menu before you stop.

• Editing the world name to get a "clean" save. That starts a new world instead.

• Hoping the daily backup caught the last hour. Daily is once a day; for the recent past, the stop-time backup or a manual backup is the one to use.

Ask in Discord or email support@haptic.gg with your world name and roughly when the missing progress happened. We can tell you which backup holds it.