Multiplayer setup, shared saves, and server checks

Co-op & Server

Keep multiplayer simple enough to trust on every session.

Use this page when the problem is wider than one guide and the session is shared.

The point here is to keep invite flow, save ownership, and base support visible before anyone blames the game, the patch, or one narrow route.

What to check

Most co-op problems fall into a small set of repeat checks.

Invite flow

Make sure everyone is joining the same world and version first.

Best when the room exists but the session still feels split between players.

Save ownership

Decide who controls the main world, backup, and update checks.

Best when a shared save is drifting after a patch or a role change.

Shared base

Keep storage, food, and return flow simple enough for more than one player.

Best when the team keeps wasting time on the same support tasks.

Connection fixes

Check support and correction pages before assuming the game itself is broken.

Best when the symptom is broad and the cause may be setup, not gameplay.

Best next pages

Open the page that matches the shared-session problem first.

Returning player helpUseful when one player is coming back to an old save.UpdatesUseful when version drift may have changed old co-op habits.ContactUseful when the page still misses a shared-session edge case.FixesUseful when the blocker is broad and still unnamed.

Subpages

Use these when the co-op problem already has a shape.

Invite flowJoining the same world and version cleanly.Version matchChecking patch drift before deeper troubleshooting.Shared save ownershipKeeping the main world and backup path clear.Shared base flowMaking the base easy for more than one player to read.Backup handoffMaking the main save and backup owner explicit.Dedicated host checkSeparating host setup from gameplay trouble.Latency and lag checkConfirming delay is not just a baseline problem.Invite baselineProving the shared world and version are stable.

Shared base flow

If the run is shared, the base should be easy to read for everyone.

Base & AutomationUse support-flow pages when the shared base needs a cleaner repeat loop.Locations databaseUse this when the co-op problem is really a landmark or route question.Returning player reviewUseful when one player is returning and the shared save no longer feels familiar.

Spotlight

These update pages belong next to multiplayer and shared-save questions.

Co-op server after updateA focused recheck for shared worlds, save ownership, and version drift.Returning-player checklistUseful when one player is coming back to an old save and needs a fresh baseline.