Does the old Windrose save-recovery procedure apply to me?

The developer's May 4, 2026 patch describes two cases. A broken latest world or character save triggers Data Recovery: quit, or restore the latest available backup offered by the game. A Migration Conflict concerns an old corrupt save that cannot migrate and offers deletion. These are different actions.

Read and capture your actual message first. If it requests deletion or does not match, stop and preserve your files before seeking case-specific advice. Kingy has not tested either dialog on the current build; a successful launch alone does not prove your progress returned.

For the eligible old-save case, the FAQ requires disabling Steam Cloud and copying the entire SaveProfiles folder before changes. Its folder-deletion steps belong to that procedure; they are not routine cleanup.

Its instruction to choose local files in a Cloud conflict follows successful restoration. It is not a rule to overwrite a good cloud copy with any local file.

The dedicated-server guide requires backups, a stopped client and server, and matching versions. It distinguishes legacy RocksDB data, the RocksDB_v2 runtime tree and RocksDB_v2_Backups. Identify the actual source and destination before copying; do not rename world folders.

The server guide's JSON example uses WorldIslandId, while transfer prose also uses WorldIslandID. Kingy has not tested how the game handles those spellings. Inspect the existing generated configuration; do not add a second key on the assumption that both are interchangeable.

Record the save-tree names, selected world and error message for support. Remove passwords, invite codes and personal information before sharing configuration. A server starting successfully does not prove that your intended world was restored.