If a Moon Sweepers save will not load, preserve the current files and identify the exact symptom before replacing anything. Patch 1.0.3 fixed heavily cleaned worlds that appeared corrupted; 1.0.4 added automatic backup repair; 1.0.5 fixed some freezes about 30 seconds after loading. A loading failure alone does not prove the world data is destroyed. S02S03S04S17
Match the behavior to the documented change
| What happens | Relevant developer statement |
|---|---|
| A heavily cleaned world fails to open | 1.0.3 fixed worlds that appeared corrupted while files were intact |
| The world opens, then freezes around half a minute later | 1.0.5 fixed a repeating freeze on both DX11 and DX12 |
| A damaged save is detected | 1.0.4 can repair from available backups during loading |
| A 1.0.4 save is opened with an older build | Developer says that save format cannot load in an older version |
| Game fails before a world is selected | Separate startup/install issue; not established as save corruption |
These statements narrow the next check; they do not prove the cause of a current-build failure.
Preserve evidence and a separate copy
Close the game. Open the official local backup location using:
%USERPROFILE%\AppData\LocalLow\DragDropGames\MoonSweepers\Backups
Copy the containing MoonSweepers folder to a separate dated location. Compare file names, counts and sizes without replacing originals. Record the affected slot, installed build, last successful session, exact error and whether the failure begins before or after world entry. See save location for the full procedure.
Compare the affected slot on the updated build
Check current game updates, then compare the same slot and record the result. If a loading notification mentions backup repair, record that notification as well. Do not downgrade a save to an older incompatible build or rename a random backup to imitate an active slot.
For a freeze, note approximately how long the world runs before it stops and the selected graphics API. The 1.0.5 fix names both DirectX 11 and 12, so merely switching between them is not proof that this specific fault has been repaired.
Installation verification is a separate check
Steam's installation-file verification instructions concern installed game files. They do not establish a method for repairing world-save data. If the game fails at startup, verification may be a relevant install check; keep the separately preserved world files regardless.
If the failure remains, use the developer's bug-report route linked from Steam and provide the recorded behavior and requested files. For backup timing, see automatic backups; for cloud conflicts, see Steam Cloud and backups.
Source references
Sources checked . Source types describe the evidence; they do not imply gameplay testing by this site.
- S02 · OfficialPatch 1.0.3 — 24 October 2026 ↗
- S03 · OfficialPatch 1.0.4 — 25 October 2026 ↗
- S04 · OfficialPatch 1.0.5 — 28 October 2026 ↗
- S06 · OfficialSteam installation-file verification ↗
- S17 · OfficialSteam official developer announcement feed — checked 8 November 2026 ↗