Ore Factory Squad Co-op Disconnect After Contract Completion

Quick answer

If a guest is already inside the lobby and disconnects exactly when the host completes a contract, treat it as a narrow reproduction case—not as a normal invite failure. Back up the host save, confirm both players are on the same current game version, reproduce the same contract-completion action once, and record what each player sees. The developer has asked for logs for this report, but no universal cause or reliable local fix has been published.

Confirm this is the same problem

This page matches only when all of these are true:

• the guest successfully joined and could play before the event;
• the host completed a contract and used its completion action;
• the guest disconnected at that point;
• the failure can be described separately from an invite, lobby-code, or initial join problem.

If the guest cannot enter at all, use the co-op join and Steam invite guide. Do not rebuild network settings or change save files based on a different symptom.

Run one controlled retest

1. Close the session and make a dated copy of the host's save using the save backup guide.
2. Record the game version shown by the host and guest.
3. Reopen with the same host and guest roles.
4. Choose one contract and note its type before completion.
5. Have both players record the moment the host uses the completion action.
6. Stop after one repeatable result instead of completing more contracts or overwriting the backed-up state.

The goal is to identify the trigger and preserve evidence. This retest is not a promise that the session will remain connected.

Record both sides of the disconnect

Ask the host and guest to record:

• current game version and platform;
• who hosted and who joined;
• whether play worked before contract completion;
• the exact host action immediately before the disconnect;
• any message shown to either player;
• whether the same pair can rejoin afterward;
• requested logs, plus screenshots or video when available.

Keep expected behavior and observed behavior separate. “The guest should remain connected” is the expectation; the exact disconnect message and timing are the observation.

Report it without claiming a cause

Use the bug report and log-files guide to package the host and guest evidence. Link the report to the narrow trigger and include the contract context. The current developer reply requests logs so the cause can be investigated; it does not confirm whether the failure comes from the contract, host, save, Steam session, or another system.

For contract handling that works outside this disconnect case, use the contracts and Pallet Packer guide. For broader issue routing, return to Troubleshooting.

Sources

• Current Steam report: guest disconnects after contract completion — single player-reported reproduction and developer request for logs; not proof of a universal bug
• Pinned developer bug-report instructions — official reporting destination and evidence boundary
• Official Ore Factory Squad v1.1.1 hotfix — current version boundary; it does not publish a fix for this disconnect