How Windrose saves
- The server saves world data only, and each player's character lives on their own PC.
- During play, Windrose writes a zip copy of the world within a minute of any change. It writes none when the server stops, so a stop, a restart, a crash or an update can lose the last minute of play.
- The newest copy is marked
_Latest, and at every start Windrose builds the world from it. - If a copy breaks, Windrose marks it as broken and falls back to the one before it.
Windrose has no manual save command, so we can't ask it to save before a backup. The Overview page shows when Windrose last wrote a copy.
What a backup holds
Your server's backup holds:
- Every world on your server, with Windrose's own copies of each world, except broken ones
- The settings file
R5/ServerDescription.json, which holds your server's identity, the invite code and the password
It doesn't hold the players' characters, which are on their own PCs.
Clean or mid-play
- While the server is stopped: the backup holds the last copy Windrose wrote, within a minute of the last change in the world, and it's badged Clean.
- While the server is running: it holds the last copy Windrose wrote and is badged Mid-play, so the play since that copy may be missing.
Restore a backup
Press Restore on the backup you want. We take a copy of the current state first, then stop the server, roll the files back and start it again, and Windrose builds the world from the newest copy inside it.
Windrose's world copies
You have two layers:
- Your server's backups: we take them automatically, and you can take one yourself whenever you like. They restore the whole server in one click.
- World backups: the dated copies Windrose writes of the active world, in their own table in the World tab. They take the world alone back to an older copy, and we keep the current copy first.
The details are in the worlds guide.
Did this guide help you?
Improve this guide
Guides are open source. Found a fix or an addition? Open a pull request on github.com/serverkgg/windrose