Moon Sweepers “Could Not Pack a Capsule”: 1.0.4 Status & Checks

01What is confirmed as of October 26?

The latest patch listed in the official news feed at this check is 1.0.4. Its notes explicitly say machines pausing with “Could not pack a capsule,” despite available power and materials, have been fixed. That patch was published October 25 at 20:47 UTC.

A Steam thread posted afterward, on October 26, describes the same error in a Pressure Chamber. Several players report similar stoppages, including a Stone Press. Those reports mean the patch note alone is not enough to promise that updating will restore every affected production line.

If you already have 1.0.4 and still see the message, you are not the only player reporting it. First identify which stage has stopped; then preserve the details for a useful bug report. There is no confirmed, universally successful workaround in the sources below.

02Check the production stage, not just the power bar

A machine can have power while its output is stuck. In the original report, the Pressure Chamber showed 100% stored power, 4/20 kg dust, 10/10 kg sand, and three completed cycles. These are one player's readings, not required recipe values or a setup to copy.

Use the following checks to locate the stoppage. They are diagnostic steps: finding a clear conveyor does not rule out the reported bug, and a full output display alone does not prove a belt is connected incorrectly.

1. 01

   Record the machine and exact message

   Identify whether the error is on a Pressure Chamber, Stone Press, or another machine. Take a screenshot of its whole information panel before changing anything.

2. 02

   Read input, power, output and cycle information together

   Note what material is available, whether the power display changes, whether processed material has reached its displayed capacity, and whether the cycle count advances. A single percentage cannot describe the whole machine state.

3. 03

   Watch where a finished capsule should leave

   Check whether a capsule is created at all. If one appears but stops farther along, inspect that connection and the downstream destination. If no capsule is created and the error persists, record that distinction.

4. 04

   Compare with one nearby production line

   If you already have another machine, check whether it also stalls. Note whether the issue affects one unit, one route, or several machines. Avoid building a large replacement factory just to find this out.

03What your observations can tell you

Also distinguish the production error from JOONAS delivery. A robot can clean and send dust successfully while a downstream processing machine cannot package its output. In that case, moving the robot or adding catchers does not address the stage that is actually failing.

04Keep your 1.0.4 save on a compatible version

Do not use a rollback to 1.0.3 as a fix for this error. The developer explicitly states that saves made in 1.0.4 cannot be opened in older versions. One reply in the error thread also describes multiplayer access problems after attempting a rollback.

Version 1.0.4 adds up to five automatic world backups per save slot, created one minute into a session and then every 30 minutes. The notes place them outside Steam Cloud at C:\Users\[user-name]\AppData\LocalLow\DragDropGames\MoonSweepers\Backups. Automatic repair can use backups for damaged saves, but that is not a documented repair for this machine error.

Another player reports that replacing a machine helped only temporarily before it stuck again. That is not enough evidence to recommend demolishing a working layout. Keep the existing save and wait for a verified fix rather than repeatedly spending resources on replacements.

05If it still stops, send a report that is easy to reproduce

The developer asks for bug reports through the official Discord linked in the patch announcement. Check the official news feed for a newer patch before reporting, and include the version you actually ran. Avoid presenting an old report as a confirmed problem in a later version.