Moon Sweepers Depot: Locate the Material and the Payment
Begin with a small amount you can recognise. Note where it is held, the funds shown before delivery and the amount still present afterward. Material in a container, a capsule on its route and material that has actually reached an intake are different states. No visible payment alone does not prove that the material was deleted.
Keep other spending and deliveries out of this short observation when possible. In co-op, record whose display you are observing and whether you are host or client; the sources used here do not establish every wallet or inventory-ownership rule. This is a way to make the evidence interpretable, not a new claim about how crew funds are shared.
Match the payment checkpoint to the delivery method
For a belt-fed payout, diagnose arrival at the intake instead of assuming it requires an extra manual launch. For a manual delivery, do not assume material near the depot has already completed the shipment. Follow the controls shown by your installed build; these sources do not establish a universal shipment key, timer or minimum load.
| Situation | Documented checkpoint | What to observe |
|---|---|---|
| Manual collection and delivery | The official store describes taking dust to a depot and launching shipments to get paid. [1] | Whether the current shipment workflow completed, and the funds before and after. |
| Dust or stone arriving by belt | Patch 1.0.3 says belt arrivals are paid as they enter the intake; it also corrects intake payout to match the displayed amount. [2] | Actual arrival at the intake, its display and any funds change. |
| A cleaned hex or sector lacks its reward | Patch 1.0.5 reports completion/payment fixes for specific sector-state faults. [4] | The completion state and installed version; this is not evidence of a failed depot sale. |
Run these checks in order without destroying the setup
Change one relevant condition at a time so you can tell what affected the outcome. Demolishing a line, deleting a world or overwriting a backup is not an observation step. No refund or move feature replaces preserving evidence of a material-loss report.
| Step | Check | Keep or record before moving on |
|---|---|---|
| 1 | Note the game build, world and host/client role. Compare it with the dated patch history. | The exact version and the original symptom. |
| 2 | Locate one small amount before delivery and note the funds. | Its material type, amount and current container or route. |
| 3 | Choose the manual-shipment or belt-intake checkpoint from the table above. | The action you actually completed, rather than a guessed payment step. |
| 4 | Watch where that material goes. On a line, inspect the first visible point where input stops reaching the next stage. | A short route description or screenshot of the stop. |
| 5 | Read the device’s own message. On 1.0.5, inspect the garage silo’s export-reason information and its outfeed connection. [4] | The exact reason text and whether the connection exists. |
| 6 | If the route can be tested safely, repeat only the same small delivery while observing its payment checkpoint. | Funds and material before/after, with no unrelated purchase in between if possible. |
| 7 | If it still fails, stop large repeat deliveries and report the reproduction. | The unmodified setup and the smallest sequence that demonstrates the fault. |
Separate developer-reported fixes from a new failure
A launch-day complaint can identify a useful symptom without describing the current mechanism. Conversely, a patch note saying a fault was fixed does not invalidate a new, versioned reproduction. Keep the build and exact error with the report.
| Version | Developer-reported change | Scope of the check |
|---|---|---|
| 1.0.3 · October 24 | Intake payout matches its display; belt-fed dust and stone pay on arrival. [2] | A payment rule and correction for the intake, not a complete automation-profit table. |
| 1.0.4 · October 25 | Machines pausing with a capsule-packing error despite available power and materials were addressed. [3] | Record whether the exact message still occurs on your installed build. |
| 1.0.5 · October 28 | The garage silo explains why it is not exporting, such as an outfeed-belt connection problem. [4] | Read the actual displayed cause before rebuilding the silo. |
| 1.0.5 · October 28 | Capsule packing fixes cover the hand-packing action, Auto Packer and machine cases on large bases with many capsules on belts. [4] | A developer change does not prove that every current stoppage has the same cause or is impossible. |
Treat a missing sector reward as its own branch
Patch 1.0.5 reports a fix for remotely cleaned hexes remaining at 99.9% without completion or payment. It also says that incorrectly empty sectors showing 0% are checked when the world loads, then completed and paid. These are developer-reported sector-state corrections, not a statement that depot arrivals need a world reload. [4]
Record which state you see, the version and whether the missing reward concerns a sector or a delivery. Do not repeatedly send more dust to a depot to test a ground-completion reward. Preserve the world and the visible sector state if the same fault persists on the updated build; this guide does not promise that a particular restart recovers a missing payment.
Do not fill gaps with guessed rates or recovery rules
The sources do not establish a universal shipment timer, minimum load, processing multiplier, expected credits per kilogram or every crew-wallet rule. Use the displayed values in your build and report the exact result. A missing number in this guide should not be replaced with a figure from a different delivery method or an undated post.
If material left a device but its next state cannot be identified, preserve the setup rather than claiming a confirmed deletion or a guaranteed refund. This page helps distinguish the checkpoints; it does not provide a verified reconstruction recipe for every machine layout.
Report the route, the version and the observed result
The 1.0.5 announcement asks players to report bugs through the developer’s Discord. Follow the route in the official announcement rather than an unverified invite copied elsewhere. A report is useful evidence, not a promise of reimbursement or a particular response time. [4]
| Include | Why it helps |
|---|---|
| Game version, world and host/client role | Keeps the report tied to a particular build and session. |
| Material and delivery method | Identifies the manual-shipment, belt-intake or sector-reward branch. |
| Material and funds before and after | Makes the claimed loss or missing payout observable. |
| The first stopped device and exact error text | Separates export, transport, packing and intake faults. |
| A short repeatable sequence or screenshot | Shows a developer where to begin without replacing the entire line. |
Sources and verification
- Official Steam store: game description and PC requirements ↗
Checked 2026-10-28 - DragDrop Games: Moon Sweepers 1.0.3 Patch — October 24, 2026 ↗
Checked 2026-10-28 - DragDrop Games: Moon Sweepers 1.0.4 Patch — October 25, 2026 ↗
Checked 2026-10-28 - DragDrop Games: Moon Sweepers 1.0.5 Patch — October 28, 2026 ↗
Checked 2026-10-28
Official statements, source-led explanations and hands-on testing are different evidence types. Our editorial policy explains how we label them.