Load an affected world after the save fix

Use the normal load path first

1. Use the current version, announced as 1.0.4 in the October 25 patch. A save made in 1.0.4 cannot open in older versions.
2. Attempt to load the affected existing world normally.
3. Read any repair notification and check that the world opens.
4. If loading still fails, preserve the exact error and version rather than deleting the save as a guessed repair.

Understand the two situations

The patch distinguishes a loading failure affecting some large cleaned worlds from an actually damaged save. In the first case, the developer says the save files were fine. In the second, automatic recovery depends on an available backup or recent snapshot.

That distinction matters: a world that does not open is not enough evidence that all of its data must be discarded.

If it remains unresolved

Keep a concise record of what happens: which world fails, whether a repair message appears and the exact wording of the failure. If you seek support, those details describe a concrete case.

The 1.0.4 announcement publishes a backup folder, but does not give a manual file-replacement sequence or backup-selection menu. Use the automatic load and crash-recovery path first; do not delete saves or substitute an unverified repair download.

What the 1.0.4 backups contain

The game keeps up to five full world backups per save slot, one minute into a session and then every 30 minutes. The official folder is C:\Users\[user-name]\AppData\LocalLow\DragDropGames\MoonSweepers\Backups. These backups are stored outside Steam Cloud.

The announcement says damaged save data is restored from available backups on load, with a notification, and checked on the next start after a crash. It does not establish a manual restore workflow or prove that a particular older session already has a backup.