Crimson Moon co-op: disconnects at map changes, joiners stuck on the title screen, host progress not saving

By DayOneFix Editorial · September 2, 2026

Work through these

0 / 5 done

Ticks are saved on this device — close the page and pick up where you left off.

Acknowledged by the developer: clients freezing or disconnecting in Moore Manor; false 'Player has left the session' messages; invites that leave the joiner stuck on the title screen; host mission progress not always awarded. A first hotfix is being prepared.
Host: stay in the hub to invite. Players report the joiner gets stuck when the invite is accepted mid-load. Send the invite from the Church, wait for the join, then start the mission.
Expect the drop at the start of map two. The most common report is the client losing connection the moment the second map begins. Save-scum nothing — just know the run may end there until the hotfix.
Loot is not instanced. Drops are shared between both players. That is design, not a bug.
Back up your save before any update. Save loss on update is a separate, high-priority official known issue.

Lag or disconnects on launch day?

Half the launch-week "server errors" we trace are routing problems between you and the game servers, not the servers themselves. A game booster reroutes that path. GearUP is the one we point people to: it supports most new releases within a day of launch.

Use code DAYONEFIX at checkout for 10% off (new users, any plan).

Try GearUP Booster →

Affiliate link: if you subscribe through it we earn a commission. It does not change which fixes we recommend, and we say so when a fix does not need it.

Crimson Moon is a 2-player online co-op game at its core, and co-op is where the launch build is weakest. Roughly a quarter of the negative Steam reviews in our 100-review sample mention co-op or connection problems; the Steam forum’s most active launch threads are Consistent connection loss in co-op and Multiplayer Progression Not Shared?. This page separates what the developer has confirmed from what players are reporting, and lists what you can actually do about it today.

What is officially acknowledged

ProbablyMonsters’ Known Issues (Launch Day) article lists four multiplayer items, in their words:

Co-op players may occasionally receive an incorrect “Player has left the session” message.
Clients may freeze or disconnect while playing in Moore Manor.
In some circumstances, accepting a co-op invitation can leave the joining player stuck on the title screen.
Mission progress may not always be correctly awarded to the host during co-op play.

The same article says Team Metal is “preparing our first hotfix”. No date is given; when a patch note names any of these, the live tracker flips that row.

What players are reporting beyond that

The map-two drop. The clearest pattern in the connection-loss thread: two players clear the first map fine, then the client loses connection the moment the second map starts — “every single time, and then we have to restart from mission one”. Several players describe the same sequence with the friend hosting. It is not on the official list by name, but it overlaps with the Moore Manor freeze and the false “left the session” message.

Lobby churn. Some players report joining hosts, waiting through the host’s blacksmith and merchant visits, then being kicked or dropping before the mission starts. If you are hosting, finishing your hub business before inviting removes most of that window.

Progress and loot. Reports on whether the joining player’s quest progress carries are mixed — one player got side-quest progress in a friend’s lobby, others say they got nothing. What is consistent: loot is not instanced, so both players draw from the same drops. Treat “who gets the item” as something to agree on beforehand.

One more thing several replies point out: Crimson Moon runs on Steam’s networking, so on days Steam itself has outages, a lost connection to Steam ends the session too. That is not this game’s bug, but it looks identical from inside a run.

What to do today

Host from the hub, invite, wait, then start. Do not send invites during a load or after a mission has begun.
Keep runs short until the hotfix. If your group hits the map-two drop, the run is gone; there is no rejoin-in-progress.
Agree on loot before the run. Shared drops are by design.
Back up the save folder before updating. The save-loss-on-update issue is separate and officially high priority; the hotfix that fixes co-op is itself an update.
Check Steam’s status if both of you drop at once — that pattern is usually not the game.

Sources

The acknowledged items are quoted from ProbablyMonsters’ Known Issues (Launch Day) article on the Crimson Moon support site (updated 1–2 September) and Team Metal’s launch announcement on Steam. Player reports are from the Steam discussion threads Consistent connection loss in co-op and Multiplayer Progression Not Shared?, read on the morning of 2 September, and our count across the 100 most recent negative English reviews at the same time. The hub-first invite routine and the loot agreement are our advice built on those reports, not developer guidance.