Moon Sweepers Patch Notes: 1.0.5 — October 28, 2026
Published October 28, 2026 at 00:41 PDT in America/Los_Angeles, or 07:41 UTC. This was the newest announcement returned by the official developer feed at the source check. The developer describes building, logistics, reward-state and stability changes; read the full original before applying a control or interpreting an old report. [1][2]
| Area | Developer-reported change | What it changes for the reader |
|---|---|---|
| Construction and relocation | Building can take place on dusty ground, a building piece can be moved together with what stands on it, and removing building pieces refunds their full cost. | Recheck an old clearing-first instruction or a budget based on the former 75% removal refund. This is not a refund promise for all vehicles or upgrades. |
| J.O.O.N.A.S. catcher routing | Targets the emptiest catcher in the nearest group; the notes group catchers within 100m of one another and switch groups when every catcher in a group is over 80%. | A 1.0.4 description saying only nearest catcher no longer gives the whole routing rule. The 100m figure is a grouping rule, not a verified maximum throwing range. |
| Completion and rewards | Addresses remote hexes stuck at 99.9% without completion/payment and rechecks incorrectly empty 0% sectors when the world loads. | Separate a ground-completion reward from the payment for a depot delivery. Do not assume any historical missing funds are guaranteed to return. |
| Packing and export | Reports packing fixes involving the Q action, Auto Packer and machines on large bases with many capsules on belts; the garage silo now explains why it is not exporting. | Record the exact error or export reason before rebuilding a working layout. |
| Freezing and performance | Reports a freeze about 30 seconds after world load on DX11 and DX12, plus garbage-collection stutter and memory-leak fixes. | Record the build and timing of a remaining freeze rather than treating every problem as a renderer-setting issue. No FPS increase is measured here. |
1.0.4 — October 25: automation, maps and save protection
Published October 25, 2026 at 13:47 PDT. This earlier update introduced robot, map, backup and compatibility changes that remain useful context. Its catcher description should be read alongside the later 1.0.5 routing changes above. [3]
The same notes reported a capsule-packing stoppage fix even when power and materials were available. The later 1.0.5 packing work is a separate follow-up; neither announcement establishes that every new stoppage is impossible. [3]
| Area | Developer-reported change | What to recheck |
|---|---|---|
| J.O.O.N.A.S. | Described continued work away from players and capsules sent toward the nearest catcher. | Use the later 1.0.5 group-routing rule when evaluating a current setup. |
| Moon map | Right-click interactions, robot activity markers and robot-type filters. | The installed interface and the version used by an older control guide. |
| Saving | Local automatic backups and damaged-save repair. | Preserve existing files and read the compatibility warning below. |
| Multiplayer | Ground synchronisation and building on crewmates’ belts. | The versions and host/client roles involved in a new mismatch. |
| Windows / AMD | DirectX 11 became the default to address AMD GPU crashes; an explicit DX12 override was documented. | Whether an old launch override is present; the requirements table alone does not require it. |
| Steam Deck / Linux | Startup fixes involving older Proton versions. | The actual OS and Proton build; this is not a native Linux release or a performance certification. |
Developer message — October 24: the launch context
Published October 24, 2026 at 08:20 PDT, after the 1.0.3 announcement. The developers acknowledged launch issues involving crashes, performance, multiplayer, automation and balance, and described their work priorities. It is evidence of what they were investigating at that time. [4]
Read this message as historical context for early reports. Subsequent 1.0.4 and 1.0.5 announcements describe delivered changes; the older message should not be used to label those changes as an unreleased future update or to promise a date for another fix.
1.0.3 — October 24: shared upgrades, intake payments and garages
Published October 24, 2026 at 02:03 PDT. The patch moved the crew to the host’s upgrade matrix: matrix purchases benefit the crew, and older saves keep the highest previously purchased levels. That confirms matrix progression, not every wallet, personal-item or host-transfer rule. [5]
The intake payout was corrected to match its display, and the notes say dust and stone arriving by belt are paid as they enter. Keep that rule separate from the manual delivery-and-shipment loop described on the store page. [5]
Garage changes allow owned vehicles to be recalled, stored and upgraded through any garage. The notes also describe the host’s kick/ban controls and performance work. These remain dated developer statements rather than a complete vehicle-price or multiplayer-ownership table. [5]
Keep the save warning with the backup feature
The 1.0.4 announcement says each save slot keeps up to five local full backups, initially about one minute into a session and then every 30 minutes, outside Steam Cloud. It also warns that saves created in 1.0.4 cannot be opened in older versions. Preserve existing files before manual intervention or a proposed downgrade. [3]
Automatic repair and a manual file-restoration procedure are different things. These notes do not establish every filename mapping needed for a verified manual restore. A missing world should be approached by preserving the original host/device files and recording what happened, rather than overwriting the only copy.
Follow the change to the task it affects
Use the version entry to decide which part of a guide you need to recheck. A new feed check does not silently refresh every old source, prove every instruction on an older page or replace measurements taken in a different build. These links lead to the normal workflow or a relevant diagnostic branch.
- Money and delivery checkpoints Keep manual shipments, belt arrivals and one-off rewards separate when measuring income.
- Upgrades and buying decisions Use current displayed costs and scope rather than an old assumed refund or universal optimal order.
- Co-op and host context Check crew versions and the shared matrix without generalising every ownership rule.
- PC requirements and renderer context Compare the stated requirements with a documented default or deliberate launch override.
- Platforms, controllers and Proton A compatibility fix does not establish a new native platform or a Valve rating.
- Troubleshooting by symptom Record the failed checkpoint and choose a small, non-destructive check.
How to verify an announcement and report a remaining fault
Every entry here corresponds to one developer announcement returned by the official Steam feed. The source-check time is when we reviewed it; the publication date is when the developer posted it. The original links below let you inspect the full wording and look for newer announcements.
Compare the installed build on your device with the version in the report. If the issue persists, retain the exact symptom, host/client role where relevant and a small reproduction. The 1.0.5 announcement directs reports to the developer’s Discord; use that official route rather than an invitation this site has not verified. A listed fix is not a promise that this guide has reproduced it or can recover your world. [2]
Sources and verification
- Official developer announcement feed, checked October 28, 2026 ↗
Checked 2026-10-28 - DragDrop Games: Moon Sweepers 1.0.5 Patch — October 28, 2026 ↗
Checked 2026-10-28 - DragDrop Games: Moon Sweepers 1.0.4 Patch — October 25, 2026 ↗
Checked 2026-10-28 - DragDrop Games: A Message From the Developers — October 24, 2026 ↗
Checked 2026-10-28 - DragDrop Games: Moon Sweepers 1.0.3 Patch — October 24, 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.