Subnautica 2 Co-op Guide: Playing With Friends Without Chaos

Subnautica used to be the loneliest game around. You, an alien ocean, and whatever just roared somewhere below your feet. Subnautica 2 changes the whole mood: it's the first game in the series with real co-op, so up to four of you can share one world, one base, and one set of nightmares. A group that's set up well moves through the story way faster than any solo diver. A group that isn't gets four people fighting over the same copper rock while nobody has built so much as a locker. The difference comes down to boring stuff - who hosts, what's shared, who does what. None of it's hard. The game just doesn't hold the meeting for you.

Setting Up a Co-op Session

One of you hosts, and it matters more than you'd think

Co-op runs peer-to-peer. One player hosts the world on their machine and everyone else connects to them, and there are no dedicated servers in Early Access to do that work for you. Two things fall out of that.

First, the host's rig and connection set the ceiling for everybody. A host on an aging laptop over hotel wifi means the whole squad stutters. Give hosting to whoever has the strongest machine and the steadiest connection, not whoever feels like it that night.

Second, the world lives on the host's save. The host quits and the session ends for everyone, and that same person has to host again to pick the group's world back up. So choose someone who'll actually keep showing up, and have them quit cleanly after big milestones rather than vanishing mid-build. Figuring out whose save holds the base after three weeks of casual hosting is a bad time.

Invites, friend codes, and crossplay

Starting a session is painless. Start or load a world in multiplayer mode from the main menu, then bring people in. Platform friends can join straight from the in-game friends list or a regular invite. For everyone else, the host generates a friend code, sends it over, and the friend types it into the join screen. That's the whole ritual. Crossplay covers PC (Steam, Epic, and Game Pass) along with Xbox Series X|S, so a Steam diver and an Xbox diver can share a world with no weird workarounds.

Two limits to know up front. There's no split screen, so every player needs their own machine. And there's no server browser or matchmaking with randoms - sessions run on invites and codes only. For a game where half the tension is the quiet, that's a plus.

One more handy thing: a single-player world can be flipped over to co-op later, and back again, from the main menu. Started alone on Monday and a friend showed up Wednesday? No restart needed.

A two-minute pre-flight check

Before anyone gets wet:

1. Confirm everyone's on the same game version. Mismatched versions simply won't connect, and somebody always has a pending update.
2. Lock in the host for the whole run. The save belongs to whoever made it, so swapping hosts mid-world isn't really a thing.
3. Get voice chat sorted on dry land (more on that below). Nobody wants to troubleshoot audio settings from 40 meters down.
4. If a friend code flat-out refuses to connect, strict router NAT is the usual suspect with peer-to-peer games. A router restart has fixed more sessions than any patch note.

Shared Resources and Inventory Rules

What the whole squad shares

The headline: it's one world. One map, one set of outcrops, one story state, one base. If you break an outcrop for titanium, it's gone for everybody. The fish your buddy ate stays eaten. That's exactly why two people farming the same shallows get in each other's way so fast.

The best part of sharing is the scanning. Databank entries, blueprints, and story progression are pooled across the group, so the moment one person scans a fragment, everybody learns it. One scan, four players credited. That's a massive speedup over the old fan-made co-op mods, and it changes how a group should split up a wreck (more on that later).

The base is fully communal too. Every module, every locker, every fabricator. Anyone holding a Habitat Builder can add rooms or tear them down, and anyone can open any locker and help themselves. No permissions, no owner.

What stays personal

• Your inventory. Whatever's on your body is yours until you put it in a locker.
• Your gear. Tools, tanks, and suit loadouts stick with you.
• Your vitals. Oxygen, food, water, and health are all per player. Your friend's full stomach does nothing for your air meter.
• Your respawn point. Each player assigns their own Biobed, so two of you can wake up in completely different places after a bad night.

Here's the part that catches groups off guard: there's no private storage. Every base container is open to all players, all the time - think community fridge, not assigned lockers. Separate inventories are on the roadmap, but for now a "don't touch" stash is a conversation with your friends, not a checkbox. There's no direct player-to-player trading yet either. To hand someone a spare oxygen tank, you drop it in a locker and they fish it out. Clunky, sure, but it works.

Keeping storage from turning into a junk drawer

Four people dumping loot turns any base into a wall of mystery lockers by hour three. Cheap fixes:

• Make one locker the drop-off. All raw materials go in, whoever's crafting pulls out. This one habit kills most of the "where did the quartz go" arguments on its own.
• Label by contents, not by owner. A locker named "metal" beats a locker named "Dave's stuff" every single time.
• Keep one emergency locker and treat it as sacred: charged spare batteries, med packs, a backup tank, a repair tool. Whoever empties it refills it.

Dividing Roles Between Players

The game doesn't enforce roles and nobody's assigning homework. But a loose split of jobs is the biggest difference between a group that creeps along and one that's rolling in vehicles early.

The builder

Owns the Habitat Builder and the base plan. They decide where rooms go, keep the structure sound as it grows, wire up power (solar panels early, a bioreactor once there's biomass to spare), and eventually set up the vehicle chain - Moonpool, Tadpole Dock, Vehicle Fabricator. They mostly stay close to home, which makes them the natural crafter and the first person to notice the storage situation.

The point of having one builder isn't speed, it's veto power. Four people building at once is how you end up with a base that has six hatches and a corridor to nowhere. Let anyone pitch ideas; let one person hold the tool.

The gatherer

Runs the resource loop - out, down, fill the bags, back to the drop-off locker. A good gatherer asks what's short before leaving, not after coming home with a fourth stack of copper. Past the early hours this is also the Scanner Station operator. The station sweeps a 300-meter sphere around your base and pulls up whatever matches its filter, then puts a signal on your HUD that walks you straight to it. One filter runs at a time, each station tracks one signal, and it draws 10 energy a second while active, so it's not free to leave running. Recipe Data Cards found in wrecks and old settlements add more filters later. Titanium today, silver tomorrow, and nobody swims in circles hoping to get lucky.

The explorer

Pushes into new biomes, finds wrecks, scans everything that glows. Because scans are shared, the explorer is quietly unlocking blueprints for the entire squad on every trip - it's the job that lifts the whole group. The explorer should also carry a stack of Beacons. That blueprint comes from scanning two beacon fragments, and each Beacon costs a single Titanium and a single Copper, which is basically nothing. Drop one at a find, name it something better than "beacon 7", and now the whole team can find that wreck or that cave for the rest of the run. You can rename or switch beacons off from the PDA signals tab, and you can pick them up and carry them somewhere else, so they're reusable.

The fourth seat (and smaller groups)

With a full four, the last player usually becomes the vehicle hand once the Tadpole's built - that takes scanning three fragments to unlock, plus the dock setup back at base. From there they run long supply trips and taxi duty, which frees the explorer to keep pushing outward. With three players, run builder, gatherer, explorer, and let the gatherer double up on vehicles later. With two, one builds and crafts while the other handles water duty, then you specialize once the base can stand on its own.

Whoever's left over takes the safety kit: spare batteries, med packs, an extra tank, a repair tool. One person carrying backup gear prevents roughly one death per session, and it's usually somebody else's.

Communicating Threats and Discoveries

Voice chat is bring-your-own right now

Early Access shipped without built-in voice chat. It's on the roadmap along with the rest of the co-op polish, but at launch you'll want an outside app. Discord is the easy answer for mixed groups since it doesn't care whether anyone bought the game on Steam, Epic, or Game Pass. Xbox players can just use a party. Whatever you pick, set it up before the first session, because creature encounters move fast and you can't explain where a leviathan is while swimming for your life.

Beacons and signals are your map

The game doesn't hand you a big map screen, so your shared markers end up doing that job. Beacons are the backbone: cheap, reusable, visible to everyone. Name them with what and depth - "silver wreck 40m" tells the next diver everything, while "look here" tells them nothing. Agree on a naming scheme on day one and the PDA signals tab turns into a genuinely useful index of the world.

The Scanner Station does the same job for materials. Whoever's at the console picks a contact and gets a signal leading right to it, so either tell the team what you marked or have them stop by and grab their own before heading out. A marker nobody knows about is a marker that doesn't exist.

Callouts that actually help

• Direction, distance, depth, thing. "Something big, northwest of base, around 60 meters down" is something a teammate can act on. "GUYS" is not.
• Agree on one word that means stop and back off. When something's chewing on the Tadpole, reactions beat discussion.
• Say rare finds out loud even if it interrupts. A wreck with a Recipe Data Card or a fresh Biobed worth scanning changes the whole day's plan, and the group can't react to what it never heard.
• Pick a caller before deep runs. One person watches depth and calls the turn-back point while everyone else mines and scans. Four people half-watching their gauges is how groups end up reprinting new bodies.

Common Co-op Mistakes That Waste Time

Four people scanning the same wreck

Since every scan is shared, two players swimming to the same fragment means one of them could've been somewhere else learning something different. When you hit a big wreck, split it - one takes the north half, one takes the south, then compare notes. The pooled databank does the rest. The same logic applies to fragment routes in general: covering two areas at once unlocks a tool in half the wall-clock time.

Three copper runs and zero titanium

The classic. Everybody mines whatever's shiny instead of what's needed, and the base sits there unpowered while three people each bring home copper. Keep one running list of what the group is short on - a pinned chat message works fine - and have the gatherer check it before every trip. Between that and the drop-off locker, this problem mostly evaporates.

Deep-diving alone

A lone deep diver faces the same risks as solo play with none of the safety net. When someone dies, they reprint at their assigned Biobed, and everything they were carrying stays back at the death spot in a container. The game doesn't drop a compass marker on it. If that happened 200 meters down next to something with a lot of teeth, the group just invented a rescue mission. So pair up for deep runs, and set your respawn Biobed somewhere sensible before you leave - the default is the one in the Lifepod, which by mid-game is ages from where you actually work. Interact with any Biobed you build to claim it as yours. That same screen is where you change your character's look, for what it's worth.

Building over each other

A shared base means anyone can add or delete anything, and one teammate's quick window is another teammate's weird hole in the bedroom wall. This is the real argument for a single builder, even among friends who "don't need rules." Before anything gets torn down, say it out loud first. Deconstructing might hand back some materials, but it never hands back the time.

The host logs off early

It's ten minutes before the host's dinner and someone just kicked off a big story trigger. Nothing gets finished, everyone logs off annoyed, and the beat sits half-done for a week. Set a stopping time at the start of the session, have the host save after anything that matters, and don't start something huge late in the night. And seriously, don't let the potato laptop host.

Nobody stocked the emergency locker

The cheapest mistake to fix. One locker holding a charged battery, a med pack, and a spare tank has prevented more group disasters than any fancy upgrade you're saving up for. Refill it at the start of every session and the worst night still ends with everyone's gear sitting in the base instead of in a box next to something hungry.