Moon Sweepers Co-op Guide

Moon Sweepers Co-op: Plan a Crew of Up to 16

The store lists single-player and online co-op and describes a maximum crew of 16. It does not promise that a full lobby is the fastest or most stable way to play. Choose a group size that can coordinate the same work area and purchases. [1]

• Decide who will host the world you intend to continue.
• Check that everyone has updated before the session.
• Agree on the first job: learn a delivery loop, choose a shared upgrade, or work on one defined area.

Prepare the session before sending an invitation

The official public pages checked for this guide do not document an exact sequence of host, join and invite buttons. Follow the session controls offered by your installed build rather than a guessed menu path. If it presents a Steam invitation, the joining player should use that invitation for the intended host’s session.

• Have the intended host open the world the group wants to use.
• Check the build/version information on each player’s installation.
• Use the host’s available lobby or invitation controls.
• After joining, verify that you are in the expected world before spending resources.
• If the session cannot be found, note the precise error and version information before repeatedly changing settings.

The upgrade matrix is shared from patch 1.0.3

The developer states that the entire crew uses the host’s upgrade matrix and that a purchase upgrades the crew. Existing saves were changed to keep the highest level previously purchased. This confirms the matrix change; it does not establish that every owned brush, wallet entry or personal item behaves identically. [2]

Divide the job without hiding the next step

The store suggests spreading out or cleaning together. For a new group, a clear handoff is usually easier to understand than everyone purchasing infrastructure at once: agree who is cleaning, who checks deliveries, and who records the next spending goal. These are organisational suggestions, not tested productivity multipliers. [1]

• Keep a single shared purchase plan for matrix upgrades.
• Tell the group before changing the delivery workflow.
• Check a short successful delivery together before expanding.
• Do not multiply observed team earnings by the number of players a second time.

Use the documented host controls for disruptive players

Patch 1.0.3 documents the host’s crew controls in the ESC menu under “Your Crew”. The host can kick or ban a player and can remove a ban there; a banned player cannot rejoin that save while the ban remains. This is a specific developer-documented menu location. [2]

Check versions before diagnosing a joining problem

The 1.0.3 release explicitly required all crew members to use that version together. The practical check is to update the entire group to the same current build before treating a connection error as a network problem. [2]

The 1.0.4 notes also address shared ground state and building splitters or mergers on another player’s belts. Read complaints about dust reappearing or crewmate-built machinery against the patch version they describe. A patch note is evidence of a developer-reported change, not proof that a new report cannot occur. [3]

Do not assume a host’s world automatically transfers

Agree on a continuing host and keep the world’s backups safe. The sources checked here do not establish a supported automatic host-migration process or every player’s save ownership rule, so this guide does not promise that changing the host carries the same world with it.

The shared-matrix statement should likewise not be used as a substitute for testing wallet and personal equipment behaviour. Record those mechanics separately when the group needs an exact answer.