Subnautica 2: prepare a co-op session and a recovery plan

Agree on a small shared objective

A useful co-op session starts with one objective that every player can state: collect the missing ingredients for a blueprint shown in your current build, test a piece of equipment, or explore a short route with an agreed return point. The goal is an editorial suggestion rather than a required quest sequence.

Record the build on each device and decide who is hosting. Confirm that everyone can join, see the same intended object and recognize the return point before extending the dive. Do not use an old Early Access guide as proof that an ingredient, prompt or save behavior is unchanged.

Voice and trading: verify the result, not only the button

Buddy System added cross-platform proximity voice with always-on, push-to-talk and always-off choices. Distance affects audibility. It also added direct player inventory exchanges. Read the currently displayed bindings and microphone choice rather than assuming a key from another platform.

1. Choose a voice mode that everyone is comfortable using.
2. Test a short message at close range and at the distance you expect to work.
3. Agree on an alternative if distance or device settings make voice unreliable.
4. Exchange one low-value item and check both inventories before trading a session-critical item.

An inaudible message can come from range, microphone permissions, an input device or a setting. Changing all of them at once obscures the cause. When troubleshooting, keep the players close and vary one choice.

Know the recovery choice before an emergency

The August update introduced reviving another player before reprinting. Its notes say revived players keep equipment and regain a small amount of oxygen; a downed player can instead choose immediate reprinting at the assigned Biobed. The notes do not establish an exact oxygen quantity or a universally safe rescue distance.

Before leaving, agree on what “return now” means for the group. A second player should not turn one downing into multiple failures by following an unknown route without a return margin. Follow the current prompts and keep any rescue decision conditional on the situation actually shown in the game.

Separate host and joining-player observations

The same patch included multiplayer building and interaction fixes. A developer’s reported fix is useful context; it does not prove that every save is unaffected. Keep a record of a mismatch before rebuilding a base or replacing local data. Use supported save and support procedures on your platform.