Moon Sweepers / Field note

Co-op version checklist: upgrades & saves

Compare installed versions, preserve the historical upgrade/save rules and record 1.0.5 loading or performance symptoms.

Official 1.0.3–1.0.5 statements · multiplayer not tested
Reviewed 29 October 2026 · No hands-on testing

Direct answer

The official 1.0.3 notes say the crew uses the host’s upgrade matrix and a purchase by any crew member upgrades the crew. That is a specific upgrade rule, not proof that every vehicle, save or kind of progress is shared.

Before the next group session

Each player has compared their installed game version; record differences.Everyone knows who is hosting and which world is being continued.The group understands that the documented shared rule concerns the host upgrade matrix.No one is trying to open a 1.0.4 save in an older version.If a problem occurs, record the version, host/guest role and last action before changing anything.

Checks stay in this page’s memory. Nothing is sent or saved.

This preparation list helps establish the group’s version and save context; it does not guarantee a successful connection or repair.

What exactly is shared?

The 1.0.3 announcement states that the whole crew uses the host’s upgrade matrix. When anyone purchases an upgrade, it applies to the crew. For older saves, the announcement says the highest upgrades already obtained are preserved.

Keep that scope precise. The statement does not establish that all vehicles, unrelated progress, guest solo saves or every future lobby share the same state. This guide has not tested guest persistence or purchase behavior.

A historical requirement is not a downgrade instruction

The 1.0.3 notes required every crew member to be on 1.0.3 to play together at that time. That is a dated patch statement, not a current instruction to install or return to 1.0.3. Compare the versions everyone is actually running and consult the current official notes.

The 1.0.4 notes separately state that saves from that version cannot be opened by older versions. Record both the installed version and the save’s originating version if known; do not assume matching lobby versions also proves save compatibility.

Loading or performance trouble in 1.0.5

The developer reports fixing a reproducible freeze in some worlds around 30 seconds after loading, affecting both DirectX 11 and DirectX 12. This is not a statement that every Not Responding message or loading delay has been eliminated.

The notes also report reduced garbage-collection stutter in large bases and fixes for memory leaks associated with leaving a world or removing structures. No measured frame-rate percentage is given. We have not benchmarked these changes.

If trouble remains, record your installed version, graphics API if known, approximate time after loading, solo/host/guest role and the visible symptom. Do not assume switching APIs, starting a new world or overwriting saves is a validated fix from this guide.

Before making a crew public

In 1.0.5, creating a public session or making an existing crew public requires confirmation. The developer says the warning explains other players’ access and points to kick/ban controls in the Esc menu’s crew area. Read that warning before confirming; version checks do not replace an access decision.

Primary sources & limits

Developer 1.0.3 announcement — Published 24 Oct 2026; original checked 26 Oct 2026.
Developer 1.0.4 announcement — Published 25 Oct 2026; original checked 26 Oct 2026.
Developer 1.0.5 announcement — Published 28 Oct 2026 at 00:41 PDT; original checked in cloud browser 29 Oct 2026.

Player questions are not proof of a defect or a workaround. Editorial precautions are not tested game fixes.