Moon Sweepers Not Working? Troubleshooting Guides

Moon Sweepers Not Working: Choose the Failed Checkpoint

Describe the first thing that fails, rather than calling the whole session broken. Dust sitting before an intake, a completed delivery without an observed payout and a clean sector without its completion reward are different reports. A short test of the correct checkpoint gives you more useful evidence than changing several machines or settings together.

Deposits and conveyors: trace one small delivery

For manual deliveries, the store describes taking collected dust to a depot and launching shipments to get paid. For dust or stone arriving by belt, 1.0.3 says the intake pays on arrival. Watch the actual arrival or shipment outcome before deciding that dust has vanished. [4][5]

If the material stops upstream, note the first device that still has input and the first place that no longer receives output. The new garage-silo reason display in 1.0.5 can identify an export problem such as a missing outfeed connection. Reading that message is a check; it is not proof that every stalled line has the same cause. [2]

• Troubleshoot a depot or shipment ↗Numbered, non-destructive checks for manual deliveries, belt intake and sector rewards.
• Review the normal dust-to-money loop ↗Use this when the payment checkpoint itself is unclear.

Joining and shared state: check the crew context

Record the host, the world being opened and the version used by each player. The 1.0.3 release explicitly required matching versions; its shared upgrade-matrix rule applies to the host’s matrix, not every possible wallet, inventory or host-transfer question. [4]

The 1.0.4 notes report ground synchronisation changes and shared belt-building fixes. A new report should say whether the mismatch is visible to the host, a client or both. Agree on a small observation to compare, rather than replacing the host or starting another world before preserving the original context. [3]

• Check co-op versions, host and shared progression ↗Use the documented crew scope instead of assuming that every player-owned item follows the same rule.

Crashes and low FPS: record timing before changing settings

Write down the game build, operating system, GPU, any launch override and the action immediately before the failure. Separate an exit or crash from a temporary freeze and from consistently low frame rate. These observations help match the report to an actual developer change.

Patch 1.0.5 reports a freeze about 30 seconds after world load affecting both DirectX 11 and DirectX 12, along with garbage-collection stutters and memory-leak fixes. Patch 1.0.4 had changed the Windows default to DirectX 11 for AMD crashes. Neither note supports adding a renderer override as a universal repair. Compare the installed version and existing override before changing one variable. [2][3]

For Deck or Linux, record the OS and Proton version as well. A native Windows listing, a Proton-specific fix and a measured result on a particular handheld are different kinds of evidence.

• Compare the official PC requirements ↗Requirements are a compatibility baseline, not a promised frame rate.
• Check native platforms and Proton evidence ↗Keep a compatibility-layer result separate from a native Linux release.
• Match the symptom to the dated patch notes ↗

Lost or damaged worlds: preserve files first

Stop making changes to the only remaining copy. Close the game before copying its files, retain the original save material and local backups, and note which computer or host last had the expected world. Do not delete the world or downgrade as the first experiment. These are file-preservation precautions, not a verified manual restoration recipe.

The 1.0.4 announcement documents up to five local backups per save slot, outside Steam Cloud, and automatic damaged-save repair. It also warns that saves created in 1.0.4 cannot be opened by older versions. A Steam Cloud feature does not establish that these separate local backups moved to another device. The original announcement is the source for that distinction. [3]

• Read the save and version warning in the update history ↗Preserve the warning with the backup feature before considering a rollback.
• Review the host and world context ↗Changing a host is not a documented automatic world-transfer procedure.

Keep a small reproduction and use the official reporting route

Record the starting state, the single action you tried and the result. Include the version, host/client role, delivery method or device configuration that matters. Keep an error message exact and explain whether the issue repeats. A useful report can be short when it identifies the failed checkpoint clearly.

The 1.0.5 announcement directs bug reports to the developer’s Discord. Open that official announcement and follow its current route; this guide does not supply an unverified invitation link. For a mistake in this fan guide, use our Contact page and include the affected page and source. [2]

• Open the official announcement sources and version history ↗
• Report a correction to this fan guide ↗Game bugs belong with the developer; factual errors in our pages belong with the editorial desk.