Windrose Dedicated Server Loads a New World? Check WorldIslandID and Backups Safely

Protect the original before diagnosis

A server that opens a blank/new world can be selecting the wrong world ID, or its saved data may fail to load. Those cases need different next steps. Before changing any file, stop the dedicated server and game client, make a separate copy of the full save and configuration folders, and keep the copy untouched. Do not delete, rename or move the only original.

1. Close the game and stop the dedicated server fully; confirm its process is no longer writing to the save.
2. Copy the server's entire saved-data directory and `ServerDescription.json` to a separate backup location. Keep the original and backup distinct.
3. Record the game/server version and the exact directory names present. The official migration guidance names `RocksDB`, `RocksDB_v2`, and `RocksDB_v2_Backups` for a particular version transition; it is not a universal path map for every future build.
4. Do not edit the live `RocksDB_v2` runtime folder; the official FAQ explicitly warns against touching it.

References: Windrose Official FAQ & Troubleshooting · Windrose Official Dedicated Server Guide · Windrose Official Steam Announcements and Patch Notes

Check whether the server selected the intended world

The dedicated-server guide says `WorldIslandId` in `ServerDescription.json` must match the island/world ID in a `WorldDescription.json` file. Compare the identifier to the intended world's actual folder/metadata while the server is stopped. Similar-looking names are not sufficient; don't rename a world folder to force a match.

References: Windrose Official Dedicated Server Guide · Windrose Official FAQ & Troubleshooting

Treat migration folder names as version-scoped evidence

Windrose's FAQ associates `RocksDB_v2` and `RocksDB_v2_Backups` with the 0.10.0.5.120 migration. It describes `RocksDB_v2` as a runtime folder that the game recreates and says not to touch it. That source is version-specific: check the installed build and current official FAQ before applying a path from an older guide to a newer server.

1. Write down the exact game client and server versions. The official server guide recommends keeping them matched.
2. Use the live FAQ to determine whether your install has passed the relevant save migration and which folder is live data versus backup for that build.
3. Inspect copies, not originals. The official FAQ's recovery steps involve backup dates and folders; verify each path before copying anything back.
4. If a correct ID still produces a fresh world, switch to a recovery diagnosis and official support instead of trying random folder renames or overwriting existing data.

References: Windrose Official FAQ & Troubleshooting · Windrose Official Dedicated Server Guide · Windrose Official Steam Announcements and Patch Notes

When to stop and request help

The FAQ calls out a wrong World ID as one explanation for a newly generated world; it also says that a matching ID with a new world can indicate corrupted save data. A browser guide cannot inspect the database or establish whether a backup is valid. If the world matters, stop and preserve copies before attempting restoration.

1. Keep the unmodified backup and note which original folders were present.
2. Record the server build, client build, whether the server was updated/migrated, and whether the ID matched the intended world.
3. Use the official support path for a matching-ID failure or uncertain migration state. Remove usernames, account IDs, tokens and private server addresses from anything posted publicly.
4. Only test recovery against a copied world and after confirming the current official instructions; do not practice on the sole surviving save.

References: Windrose Official Support · Windrose Steam Community Discussions

Before you play

• Stop both client and server before inspecting or changing files.
• Copy the full server save and configuration folders to a separate, untouched backup.
• Compare `WorldIslandID` with the intended world's actual ID; do not rename world folders.
• Check version-specific paths in current official documentation; do not edit the live `RocksDB_v2` runtime folder.
• If the ID is correct but a new world still appears, treat save corruption as possible and stop before overwrite/recovery attempts.

Frequently asked questions

Sources & revision notes

Editorial revision: November 6, 2026; not a gameplay test date. The reference notes identify source limits and version differences.

1. Windrose Official FAQ & Troubleshooting (Official)

   Official troubleshooting page checked November 6, 2026. The relevant save-recovery and connection sections still describe client/server and folder behavior using the 0.10.0.5.120-era migration names; confirm your installed version and make a separate backup before touching any files.

2. Windrose Official Dedicated Server Guide (Official)

   Official server guide checked November 6, 2026; the page itself says it was last updated May 18, 2026 for 0.10.0.5.120-073042fb. Use it for documented settings and scenarios, not as proof that every field or screen remains unchanged in a later build.

3. Windrose Official Steam Announcements and Patch Notes (Official)

   Official announcement feed checked November 6, 2026. The visible patch list includes version 0.10.0.9 dated August 25, 2026, while the October 29 Ashlands post describes work in progress. This dated snapshot is not a claim about the newest build installed by a reader.

4. Windrose Steam Community Discussions (Community)

   External user-generated Steam discussions, not official support or verified GamerWin advice. No post, comment, screenshot or guide text is reproduced.

5. Windrose Official Support (Official)

   Official support destination linked by Windrose's documentation. Use it for unresolved account, save or server issues; never send passwords, private keys or unredacted public IP details in a public discussion.