Automation

Moon Sweepers Automation: Packing, Catchers and Silo Output

Start with the affected system: read the garage's output message for silo trouble, compare capsule-packing symptoms with the documented 1.0.4 and 1.0.5 fixes, and inspect robot activity and fill indicators. For catcher routing, 1.0.5 targets the emptiest catcher in the nearest group, then moves to the next group when every catcher in the current group is over 80% full.

Start with the relevant symptom

The checks here use the developer's 1.0.4 and 1.0.5 notes. As checked on October 31, 2026, the newest released patch visible in the official feed is 1.0.5, dated October 28, 2026. Reported fixes identify known symptoms; they do not prove that every similar stoppage is resolved. Source: official developer feed.

Garage silo not exporting dust

  1. Read the garage's displayed explanation for why its silo is not sending dust out.
  2. If it asks for a conveyor belt at the outfeed, connect a conveyor belt there.
  3. If it displays a different reason, use that message as the starting point rather than assuming the same cause.

Patch 1.0.5 adds these output explanations, including an instruction to connect a conveyor belt to the outfeed. The evidence does not provide a complete list of messages or remedies. Source: developer garage-output notes.

Auto-Packer or machine capsules not packing

Compare your symptom with the dated developer reports:

Symptom described by the developerReported fix
Machines pause with the message “Could not pack a capsule” despite available power and materialsPatch 1.0.4, October 25, 2026
Capsules fail to pack in large bases with many capsules on belts, affecting Q, the Auto-Packer and machinesPatch 1.0.5, October 28, 2026

Check the version involved before treating either report as an explanation for your case. The evidence establishes these reported fixes, not a universal reset procedure or an Auto-Packer upgrade requirement. Source: developer packing-fix notes.

J.O.O.N.A.S. filling an unexpected catcher

Use the newer 1.0.5 routing description rather than a simple nearest-catcher rule:

  1. Compare the layout with the documented groups: the notes describe grouped catchers as within 100 m of each other.
  2. Compare fill levels within the nearest group. J.O.O.N.A.S. targets that group's emptiest catcher.
  3. Check whether every catcher in that group is over 80% full. That is the documented condition for sending capsules to the next group.

The notes do not explain the exact grouping algorithm for chained or overlapping layouts, so those arrangements cannot be diagnosed precisely from the distance description alone. Source: 1.0.5 catcher-routing notes.

Check robot activity and fill state

Open the map to inspect robots and their current activity. The 1.0.4 notes say all robots appear there, with toggles for each robot type. For J.O.O.N.A.S., look at the robot to expose its information panel; its gauge flashes red when full. Source: developer robot-status notes.

The same patch describes J.O.O.N.A.S. continuing to clean without nearby players. Do not treat a player's absence alone as the documented explanation for it stopping. Source: 1.0.4 robot behavior notes.

When these checks do not explain the stoppage

The verified notes do not supply robot-retrieval procedures, machine ratios, throughput targets or a fix for every automation failure. If the displayed status and documented symptoms do not match, the cause remains unconfirmed.

See building and relocation for layout controls, or crashes and saves if the problem is a freeze rather than a logistics stoppage.

Sources and verification