Give the team one shared plan before everyone swims in different directions.

Use this center when the problem is not one material or one route, but coordination: who hosts, who scouts, who builds, who banks materials, and when the team should return.

Reviewed Thursday, August 20, 2026 Co-op only Host and role planning Patch-sensitive

Fastest answer

Agree on the host, one session goal, and three jobs before leaving base: route caller, focused gatherer, and base organizer. Co-op gets slower than solo when everyone chases the same material or no one owns the return call.

Subnautica 2 co-op role board showing route caller, gatherer, base organizer, and scout responsibilities.

Role split Assign jobs before the first swim Use this when several players are busy but the save still is not moving forward.

Subnautica 2 co-op host decision visual showing host ownership and session setup checks.

Host rules Set expectations before the session starts Use this when the team is unsure who owns the session, save, or next restart point.

Subnautica 2 co-op shared progress handoff visual showing team checkpoints and progress ownership.

Progress Keep shared progress visible Use this when the group needs a clean rule for unlocks, storage, routes, and return calls.

Best fit

Use this center when the team is slower because decisions, storage, or route ownership are unclear.

Skip this when

The blocker is one named material, one dangerous route, or one base layout problem that a solo guide already answers.

Patch risk

Co-op advice should be rechecked after updates that mention hosting, saves, progression, inventory, or shared systems.

Recommended workflow

Run the co-op session like a small route desk.

Before leaving	Assign this owner	Success looks like	Open next
Session goal	Host or route caller	Everyone can say the one objective before anyone swims away.	Hosting guide
Route and return	Scout / caller	The team knows the landmark, risk edge, and bank point.	Solo vs co-op route
Materials	Focused gatherer	Only one player owns the named batch, so storage does not fill with duplicates.	Resources hub
Base flow	Base organizer	Deposits, power, storage, and next craft stay visible to the whole group.	Co-op base roles

First-session checklist

Check these before the team splits up.

Host agreed: everyone knows who owns the session and restart point.
One goal named: the run has one shared objective, not four personal errands.
Jobs split: route caller, gatherer, base organizer, and scout are assigned.
Deposit rule set: shared materials go to the team lane before personal crafting.
Return call owned: one player can end the trip before greed wastes the whole route.

Common mistakes

Most co-op failures are coordination failures, not skill failures.

Duplicate work

Everyone farms the same material

Fix it by naming one gatherer and one base organizer before the group leaves.

Base roles Material priority

Route drift

No one owns the return call

Fix it by giving one player permission to bank progress before the route gets greedy.

Map routes Turn back rule

Progress confusion

The team cannot explain what carried over

Fix it by checking shared-progress expectations before the next session starts.

Shared progress Update tracker

Visual handoff

Use a role board when the team needs one visible plan.

Subnautica 2 co-op session handoff map showing host, scout, gatherer, base organizer, shared storage, and return call. — Keep one visible handoff: host owns setup, scout owns route clarity, gatherer owns the named batch, base organizer owns shared storage, and the caller owns the return.

Trust and updates

Co-op pages should be treated as patch-sensitive.

Multiplayer advice can age faster than broad beginner guidance because hosting, progression, inventory, and role flow can change with Early Access updates. Use the update tracker after any patch that mentions co-op behavior, saves, hosting, or shared systems.

Patch triage Check co-op changes after updates Use when old session advice no longer matches what the team sees in-game. Reports Send a co-op correction Use when host behavior, shared progress, or route roles need review. Editorial Read the review policy See how route proof, official context, and reader reports are handled.