Subnautica 2 is a very different Discord-design problem from an MMO, competitive shooter, or dedicated-server survival game. Its current Early Access multiplayer is optional four-player co-op: one Pioneer can play alone or a crew of up to four can explore the same alien ocean together. The community therefore needs to organize around crew compatibility, Stable versus Experimental, cross-platform play, shared story progression, base-building plans, spoiler boundaries, session ownership/stewardship, and the fact that Early Access itself is changing under the group while they play.
The most common Discord mistake would be to treat Subnautica 2 like a generic public survival server and build channels for raids, clans, server wipes, and a five-player LFG template. That is not the game that is live in September 2026.
A better model asks:
- Stable or Experimental?
- PC or Xbox Series X|S?
- Is this a continuing co-op world or a one-night session?
- Who is responsible for the shared save/session?
- Story progression or spoiler-free exploration?
- Base building, resource gathering, creature scanning, wreck exploration, or general progression?
- Is the crew using in-game Proximity Voice or Discord?
- Are community mods enabled?
- Is everyone on the same build after an Early Access update?
This guide builds a fictional 244-member community called Abyssal Relay. It supports solo players socially, four-player Stable crews, cross-platform PC/Xbox co-op, Early Access testing, spoiler-controlled story discussion, base-building showcases, creature/scanning research, and community feedback nights. It does not pretend to operate a persistent dedicated Subnautica 2 server.
YourBot handles the Discord-side foundation and coordination. Subnautica 2 remains authoritative for the co-op world, save files, Pioneers, inventory, base state, Biomods, vehicles, discoveries, story progress, revives, trading, and Experimental compatibility.
Start With the Right Subnautica 2 Community Model
Early Access is live now
Subnautica 2 entered Early Access / Xbox Game Preview on May 14, 2026.
The current verified launch platforms are:
- Windows PC through the current PC ecosystem, including Steam and Xbox on PC
- Xbox Series X|S
- Xbox Cloud Gaming where supported through Game Pass
Steam identifies the game as:
- Single-player
- Online Co-op
- Cross-Platform Multiplayer
- Early Access
Xbox describes it as:
- Online co-op 2–4
- online multiplayer 2–4
- cross-platform multiplayer/co-op
- Xbox Play Anywhere
The important Discord rule is simple:
Current co-op crews are built around up to four players.
Do not create an eight-player "community world" and imply all eight can inhabit one co-op session together.
Four players is the actual co-op ceiling
Unknown Worlds describes Subnautica 2 as playable alone or with up to three friends.
That means:
1 host/player + up to 3 friends = 4 total
Use four for:
- continuing story crews
- exploration sessions
- base-building sessions
- resource runs
- wreck/ruin exploration
- creature/scanning expeditions
- Experimental test crews
A Discord event can have more than four attendees only if it represents:
- multiple independent four-player worlds
- community discussion
- VOD/screenshare review
- build showcase
- feedback workshop
Do not call that one eight- or twelve-player Subnautica 2 world.
Cross-platform co-op is a real current feature
Unknown Worlds' Xbox launch material explicitly says players can invite friends on Xbox and friends on other platforms.
Steam marks the game as cross-platform multiplayer.
That makes cross-platform crews one of Subnautica 2's strengths.
A practical Discord can use roles such as:
- Steam PC
- Xbox PC / Game Pass PC
- Xbox Series X|S
- Crossplay Crew
Do not create a false division where Steam PC and Xbox players are assumed incompatible.
At the same time, do not promise a platform the developers have not currently shipped in Early Access. This guide does not treat PlayStation as a current Early Access co-op platform because the verified May 2026 release sources identify PC/Xbox Series, not a live PlayStation Early Access release.
Stable and Experimental are separate compatibility pools
Subnautica 2 added an Experimental branch in August 2026.
The current official guidance is unusually clear:
- Experimental is opt-in
- it previews upcoming changes
- it may be unstable or game-breaking
- Experimental saves are separate from Stable saves
- saves cannot be imported/exported between the Stable and Experimental branches
- Experimental players can only play multiplayer with other Experimental players
This is a first-class Discord compatibility field.
Every Experimental listing should say:
Branch: Experimental
Every normal community crew should default to:
Branch: Stable
Do not let Experimental become a casual notification role with no operational meaning.
No official dedicated-server workflow was verified
During this research pass, the verified first-party Steam/Xbox material describes friend-hosted four-player online co-op, not a separate persistent dedicated-server product.
No first-party dedicated-server application or public dedicated-server workflow was verified.
That means this guide does not tell members to:
- rent a Subnautica 2 server
- paste an IP/port
- run SteamCMD server files
- store an RCON password
- treat a world as always-online
Instead, it treats each continuing crew as a shared co-op world with designated save/session stewards.
The live game also exposes Cloud Save / Save Code functionality in the current UI and patch notes. That is useful for operational planning, but it should not be confused with a 24/7 dedicated server.
Current live branch: Early Access 1.2 — Buddy System
As of September 25, 2026, the current major Early Access update is:
Early Access 1.2 — Buddy System
It released August 19.
Major current co-op features include:
- Proximity Voice Chat
- Player Revives
- Emotes
- direct Player Trading
- new Pioneer character options
- multiplayer base-building improvements
- Cloud Save code UI improvements
- many multiplayer desync/fix improvements
The September 1 hotfix, with an additional September 3 fix, addressed:
- base and save issues
- client object movement
- Collector Leviathan pathing
- inventory sharing
- Proximity Chat push-to-talk
- incompatible-save protection
- Powerplant Turbine progression issue
- additional stability work
This matters because the Discord should treat the game as actively changing Early Access software.
A crew returning after a patch should verify:
- all players updated
- everyone is on the same branch
- mods are disabled/revalidated
- the world loads
- the base and critical progression still behave correctly
before planning a four-hour story session.
Community mods need caution
The current official hotfix notes explicitly warn players using community mods to disable/remove them after game updates until mod authors update compatibility.
That makes mod policy a real Discord workflow.
Abyssal Relay uses:
Vanilla Stableas the default community recommendation- separate
Moddedrole/discussion - no requirement that a new player install community mods
- no random executable "mod managers"
- version notes for modded crews
- mod troubleshooting separated from official-game bug reporting
If a bug disappears after mods are removed, that matters when deciding where to report it.
Story and spoilers need their own architecture
Subnautica 2 is a narrative exploration game.
The community will contain people at very different points:
- just launched
- early wreck exploration
- Biomod progression
- advanced zones
- current Early Access story endpoint
- Experimental players seeing unreleased material
A generic #general channel can easily ruin the experience.
Abyssal Relay therefore uses spoiler tiers:
Spoiler-Free
Early Access Story
Late EA / Current Endpoint
Experimental Spoilers
Screenshots, creature names, locations, and narrative discoveries can all be spoilers.
Do not force a brand-new player to mute the whole Discord just to preserve discovery.
The Community We Will Build
Abyssal Relay is a 244-member Subnautica 2 Discord.
Community types
- solo explorers
- continuing Stable co-op crews
- Xbox/PC crossplay crews
- base builders
- scanner/research completionists
- story-focused groups
- spoiler-sensitive newcomers
- Experimental testers
- community mod users
- feedback/bug-reporting enthusiasts
Recurring activities
- four-player story sessions
- base-build nights
- resource expeditions
- creature scanning
- wreck/ruin exploration
- Biomod progression
- Tadpole expeditions
- spoiler-controlled discussion
- Stable update test night
- Experimental feedback night
- screenshot/build showcases
YourBot's role in the community
| Service | Community use |
|---|---|
| Welcome | Collect platform, Stable/Experimental, spoiler preference, co-op/solo, building, story, and testing interests. |
| Sentinel | Reduce phishing, malicious mods, fake save tools, impersonation, harassment, spoiler trolling, spam, and raids. |
| Tickets | Route co-op/save issues, bug triage, moderation reports, crew conflicts, and feedback-event requests privately. |
| Group Finder | Match four-player Stable/Experimental crews for story, exploration, bases, scanning, and resource runs. |
| Beacon Events | Schedule continuing crew sessions, multi-crew community nights, update tests, build showcases, and feedback sessions. |
| Join-to-Create Voice | Create optional four-player crew voice while respecting current in-game Proximity Voice. |
| Announcements | Publish current EA version, branch compatibility, update/hotfix notices, community spoiler policy, and event schedule. |
| Social Feeds | Follow official Subnautica 2 Steam publisher announcements manually with App ID 1962700. |
| Analytics | Measure Discord onboarding, crew formation, event attendance, support load, and channel health—not in-game progress. |
| Giveaways | Run Discord-side drawings without implying YourBot grants the game, Game Pass, items, saves, Biomods, or Pioneer unlocks automatically. |
1. Create the Foundation With Start Your Server
Subnautica 2 should have a small, calm Discord structure.
Do not build one channel per biome, creature, base room, tool, or story objective.
That would become a spoiler index.
Copy-ready community brief
Design a Subnautica 2 Discord called Abyssal Relay.
Community:
- About 245 Discord members.
- Early Access community.
- Supports solo players socially and co-op crews operationally.
- Current co-op maximum is 4 total players.
- Current verified Early Access platforms include PC and Xbox Series X|S.
- Cross-platform co-op is supported across current supported platforms.
Branch compatibility:
- Stable is default.
- Experimental is separate.
- Stable and Experimental multiplayer cannot mix.
- Experimental saves are separate and cannot be imported/exported to Stable.
- Experimental can be unstable and should not be used for a long-term Stable crew world.
Current live:
- Early Access 1.2 Buddy System.
- Proximity Voice Chat.
- Player Revives.
- Player Trading.
- Emotes.
- multiplayer/base fixes.
- September hotfix current.
No dedicated-server assumption:
- Do not build dedicated-server/RCON/IP workflows.
- No official dedicated-server product was verified in current first-party sources.
- Model continuing groups as shared co-op crews/worlds with a designated primary save/session steward and backup steward.
Roles:
Owner
Administrator
Moderator
Event Host
Crew Lead
Mentor
Member
New Pioneer
Self-select:
Steam PC
Xbox PC / Game Pass PC
Xbox Series X|S
Crossplay
Stable
Experimental
Solo
Co-op
Story
Base Building
Exploration
Scanning / Research
Biomods
Vehicles
Modded
Feedback / Testing
Spoiler-Free
Story Spoilers
Experimental Spoilers
Do not self-select:
Moderator
Crew Lead if it grants private crew-management access
trusted/staff roles
Channels:
START HERE: welcome, rules, choose-roles, announcements
SHALLOWS: general, questions, screenshots, builds
CREWS: lfg-listings, lfg-forum, crew-schedules
EXPLORATION: spoiler-free-exploration, research-and-scanning
BUILDING: base-design, resource-planning
STORY [ROLE GATED]: story-discussion
EXPERIMENTAL [ROLE GATED]: experimental-testing, experimental-spoilers
UPDATES: subnautica-2-updates
HELP: open-a-ticket
VOICE: join-crew, build-room, feedback-room
STAFF: staff-chat, sentinel-logs, ticket-log
Spoiler rules:
- #general stays spoiler-free.
- Use spoiler tags outside gated channels.
- Experimental discoveries stay in Experimental areas.
- Do not put late-game creature/location/story names in public channel names.
Safety:
- Never request Steam/Microsoft/Xbox/email passwords.
- Never request 2FA/recovery codes, session tokens, payment information, save-account credentials, or remote-control access.
- Treat fake mods, fake save editors, malicious executables, phishing, impersonation, harassment, and deliberate spoiler abuse as moderation risks.
- YourBot does not control saves, bases, inventories, Biomods, Pioneer characters, trades, revives, or story progress.
Configure all ten built-in services:
Welcome
Sentinel
Tickets
Group Finder
Beacon Events
Join-to-Create Voice
Announcements
Social Feeds
Analytics
Giveaways
YourBot specifics:
- Subnautica 2 is not in the currently inspected Group Finder automatic detection list.
- Generic Quick Group = 5 is wrong.
- Create explicit four-player Subnautica 2 templates.
- Subnautica 2 is not in the inspected curated Social Feeds catalog.
- Add generic Steam source App ID 1962700.
- Announcement schedules and Social Feed subscriptions require manual finishing.
- Preserve current structure.
- Keep deletions off first build.
- Preview New Pioneer, Member, Crew Lead, Experimental Tester, and Moderator perspectives.
A compact channel plan
ABYSSAL RELAY
├─ START HERE
│ ├─ #welcome
│ ├─ #rules
│ ├─ #choose-roles
│ └─ #announcements
├─ SHALLOWS
│ ├─ #general
│ ├─ #questions
│ ├─ #screenshots
│ └─ #builds
├─ CREWS
│ ├─ #lfg-listings
│ ├─ #lfg-forum
│ └─ #crew-schedules
├─ EXPLORATION
│ ├─ #spoiler-free-exploration
│ └─ #research-and-scanning
├─ BUILDING
│ ├─ #base-design
│ └─ #resource-planning
├─ STORY [ROLE GATED]
│ └─ #story-discussion
├─ EXPERIMENTAL [ROLE GATED]
│ ├─ #experimental-testing
│ └─ #experimental-spoilers
├─ UPDATES
│ └─ #subnautica-2-updates
├─ HELP
│ └─ #open-a-ticket
├─ VOICE
│ ├─ 🔊 Join Crew
│ ├─ 🔊 Build Room
│ └─ 🔊 Feedback Room
└─ STAFF
├─ #staff-chat
├─ #sentinel-logs
└─ #ticket-log
Review before applying
Preview as:
- New Pioneer
- Member
- Crew Lead
- Experimental Tester
- Moderator
Confirm a spoiler-free newcomer cannot see channel titles or previews containing late-story information.
Keep deletion disabled on the first pass.
Announcements schedules and Social Feed subscriptions require manual finishing steps.
2. Welcome: Branch Before Crew
Onboarding order:
- spoiler rules
- Stable or Experimental
- platform
- solo/co-op
- playstyle interests
Useful roles:
- Stable
- Experimental
- Steam PC
- Xbox PC / Game Pass PC
- Xbox Series X|S
- Crossplay
- Solo
- Co-op
- Base Building
- Exploration
- Scanning / Research
- Story
- Modded
- Feedback / Testing
- Spoiler-Free
- Story Spoilers
- Experimental Spoilers
A concise greeting:
Welcome to Abyssal Relay. Current co-op supports up to four players. Stable and Experimental are separate compatibility pools and use separate saves. Keep #general spoiler-free; use the gated Story and Experimental areas for discoveries. PC/Xbox crossplay is supported on the current Early Access platforms.
Test: Join with a clean test account, select Stable, Xbox Series X|S, Co-op, and Spoiler-Free; verify no Experimental or Story-spoiler channels appear.
3. Sentinel: Protect Mods, Saves, Accounts, and Spoiler Boundaries
Subnautica communities share:
- screenshots
- build designs
- mods
- save troubleshooting
- performance tools
- feedback links
- bug workarounds
Focus Sentinel on:
- phishing
- fake Steam/Microsoft logins
- malicious executable "mods"
- fake save-repair tools
- impersonation
- harassment
- spam/raids
- deliberate spoiler dumping
- suspicious URL shorteners
Do not block the ordinary words:
- Experimental
- mod
- save
- crash
- Leviathan
- Biomod
Those are normal game discussions.
The current official hotfix explicitly warns mod users to disable/remove community mods after updates until mod authors confirm compatibility.
Make that a community standard:
After a major patch/hotfix, reproduce the issue in vanilla before calling it a game bug.
Test: Post a staff-only dummy malicious-mod URL and an intentional spoiler dump. Confirm the correct moderation/logging behavior without blocking legitimate Steam/Unknown Worlds links.
4. Tickets: Crew Problems, Save Issues, Bugs, and Moderation Need Different Paths
Co-op / Crew Issue
Ask for:
- Stable or Experimental
- platform
- current game version/build
- crew size
- invite/join problem
- exact error
- whether everyone updated
Save / Progression Issue
Ask for:
- branch
- platform
- current world/crew
- what progression changed
- whether the issue began after an update
- screenshot/error
- whether community mods are enabled
Do not ask members to upload sensitive account files indiscriminately.
Bug Triage
Ask for:
- Stable or Experimental
- game build
- host/client role if relevant
- reproducible steps
- mods disabled? yes/no
- screenshot/video
- whether in-game feedback was submitted
YourBot is not Unknown Worlds support.
Crew Conflict
Ask for:
- crew/world name
- members involved
- what was agreed about story progression, base edits, inventory, or spoilers
- Discord evidence
Do not claim YourBot can reverse an in-game trade or base edit.
Moderation Report
Ask for:
- Discord user
- message link
- harassment/phishing/spoiler issue
- evidence
Test: Open one Stable multiplayer bug ticket and one Experimental bug ticket. Confirm they are visibly separate.
5. Group Finder: Four Players, Not Five
Read-only inspection of YourBot's current develop revision shows Subnautica 2 is not in Group Finder's automatic game-detection list.
The generic setup would create a five-player Quick Group.
That is incorrect.
First template
Template Name: Subnautica 2 — Continuing Crew
Game: Subnautica 2
Default Party Size: 4
Default Expiry: 3 hours
Description: Four-player co-op crew. Require Stable/Experimental, platform/crossplay, existing-world vs new-world, spoiler level, progression goal, primary save/session steward, voice preference, and session duration.
Additional templates
| Template | Target | Required context |
|---|---|---|
| Continuing Story Crew | 4 | Branch, world, spoiler checkpoint, progression goal |
| New World Crew | 4 | Branch, platforms, Survival/Creative, spoiler policy |
| Base Build Crew | 4 | World, base project, materials, build owner/steward |
| Exploration Dive | 4 | Region/objective, spoiler level, Tadpole/gear |
| Research / Scan Run | 4 | scan goal, biome spoiler level, completion target |
| Experimental Test Crew | 4 | Experimental only, test goal, disposable/testing mindset |
| Feedback Session | 4 | current branch/build, specific feature being tested |
Example Stable listing
Title: Stable Story Crew — 1 Spot
Branch: Stable
Platforms: Steam PC + Xbox Series X|S
Crossplay: Yes
Target: 4
Current: 3/4
World: Existing continuing world
Spoiler Level: Early Story only
Goal:
- wreck exploration
- Biomod progression
- resource gathering
Voice:
- in-game Proximity Voice preferred
- Discord optional
Primary World Steward: Assigned
Backup Steward: Assigned
Session: ~3 hours
Experimental example
Title: Experimental Test Crew
Branch: Experimental
Target: 4
Current: 2/4
Goal: Test upcoming multiplayer/base behavior
Save Policy: Experimental-only; no expectation of Stable compatibility
Bug Reporting: In-game feedback encouraged
Do not let a Stable member join accidentally because "it's only one session."
Test: Fill a Stable crew to four and confirm a fifth waits. Then create an Experimental listing and verify its branch field is mandatory.
6. Beacon Events: Continuing Worlds and Parallel-Crew Nights
Beacon is useful for:
- weekly continuing crew
- base-build night
- update validation
- Experimental feedback night
- community screenshot tour
- parallel four-player crew event
- spoiler discussion after a milestone
Continuing world session
Event: Abyssal Crew Alpha
Branch: Stable
Capacity: 4
Platforms: Crossplay
World: Alpha Continuing Save
Spoiler Checkpoint: Current crew milestone
Primary Steward: Mira
Backup Steward: Cole
Goal:
- complete current investigation
- expand deep base
- scan remaining nearby fauna
Voice: Proximity Voice
Parallel community dive
Event: Community Exploration Night
Total Attendance: 12
Structure:
- Crew A: 4
- Crew B: 4
- Crew C: 4
Branch: Stable
Each crew uses a separate world.
Twelve Discord attendees do not make a twelve-player Subnautica 2 session.
Experimental test night
Event: Experimental Branch Feedback Night
Branch: Experimental
Attendance: 8
Structure:
- two crews of 4
Stable Saves: Not used
Expectation: bugs/instability possible
Beacon does not:
- create the game session
- transfer saves
- invite Xbox/Steam friends
- revive players
- trade items
- synchronize Stable/Experimental data
Test: Create a 12-person community night as three crews and verify the event never calls it a 12-player world.
7. Join-to-Create Voice: In-Game Proximity Chat Changes the Need
Early Access 1.2 added Proximity Voice Chat.
It supports:
- always on
- push to talk
- always off
That means Discord voice is no longer automatically the best co-op default.
Abyssal Relay uses:
Join Crew
- limit 4
- for players who prefer Discord voice
Build Room
- limit 4
- useful when discussing design/material plans
Feedback Room
- larger
- post-session discussion
Crew listings should say:
Voice: In-game proximity / Discord / text-only
Proximity voice can make exploration more immersive because a teammate becomes harder to hear as distance grows.
Discord bypasses that.
Use whichever experience the crew wants.
Test: Fill a four-person Join Crew room and confirm the fifth cannot enter. Verify members can choose a no-Discord voice workflow without losing LFG access.
8. Announcements: Early Access Versioning Matters
Announcements should clearly distinguish:
- Stable
- Experimental
- current major update
- hotfix
- mod compatibility warning
- community spoiler policy
Current example:
Subnautica 2 — September 2026
STABLE:
- Early Access 1.2 — Buddy System
- Proximity Voice
- Player Revives
- Player Trading
- Emotes
- new Pioneer options
- current September hotfix
EXPERIMENTAL:
- separate opt-in branch
- separate saves
- Experimental multiplayer only with other Experimental players
- more bugs/unfinished content expected
CREW RULE:
- max co-op size: 4
- confirm everyone is on the same branch/build before continuing a shared world
MODS:
- after game updates, disable community mods until compatibility is confirmed.
Do not announce an Experimental feature as guaranteed Stable content until Unknown Worlds ships it.
Use:
@Stable Updates@Experimental@Co-op@Testing
Test: Schedule an Experimental notice five minutes ahead and verify it pings only Experimental members.
9. Social Feeds: Add Subnautica 2 Manually Through Steam
Read-only inspection of YourBot's current Social Feeds catalog shows no curated Subnautica 2 entry and no App ID 1962700 entry.
The verified Steam App ID is:
1962700
Create:
Source: Steam
Steam App ID: 1962700
Display Name: Subnautica 2 — Official Updates
Destination: #subnautica-2-updates
Ping Role: None by default
Digest: Off or hourly
The inspected YourBot Steam adapter uses:
- public ISteamNews
- numeric App IDs
- publisher
steam_community_announcements - default interval of 900 seconds
This is particularly useful for Subnautica 2 because Unknown Worlds currently publishes:
- major Early Access updates
- hotfixes
- Experimental notices
- development vlogs
- community announcements
through the Steam announcement surface.
Do not claim the feed sees every Nolt suggestion, Discord post, support article, or Xbox Insider update.
Test: Add App ID 1962700, preview it in the updates channel, and verify no unwanted role ping.
10. Analytics: Measure the Discord, Not the Ocean
Analytics can answer:
- Do newcomers finish spoiler-safe onboarding?
- Are Stable or Experimental members more active?
- Are crews filling?
- Do continuing-world events retain members?
- Are build/research channels active?
- Is support volume rising after patches?
Analytics does not know:
- world progress
- host/save state
- Biomods
- scans
- recipes
- base contents
- inventory
- Tadpole upgrades
- deaths/reprints
- story checkpoint
- Experimental save compatibility
- creature discoveries
Do not score players by Discord activity.
Test: Generate public discussion, one LFG, and voice activity; confirm Story/Experimental private channels and Tickets follow the intended analytics privacy settings.
11. Giveaways: Keep Discord Draws Out of Early Access Progression
Safe prizes:
- choose next community build theme
- choose next screenshot challenge
- temporary Discord cosmetic role
- community art
- legitimate game/platform code fulfilled manually
Do not imply YourBot grants:
- Subnautica 2 ownership
- Game Pass
- Pioneer characters
- Biomods
- items
- save access
- Experimental access
- world progression
Never ask for account credentials.
Test: Run a staff-only giveaway for Choose next build challenge, verify winner/reroll behavior, then use a similarly safe public prize.
Treat Stable and Experimental Like Different Games Operationally
They share the title, but a community should behave as if they are two incompatible environments.
Stable
Use for:
- continuing worlds
- long-term bases
- story progression
- cross-platform community crews
- normal screenshots/build projects
Experimental
Use for:
- upcoming-feature testing
- bug reproduction
- short-lived test worlds
- feedback nights
- players comfortable with instability
Because saves are branch-specific and incompatible, do not schedule:
Crew Alpha continues our Stable story world tonight on Experimental.
That is exactly the confusion the Discord should prevent.
Make Spoiler Control a Core Community Feature
Subnautica's discovery is part of the game.
A strong spoiler policy distinguishes:
Spoiler-Free
Allowed:
- general survival tips
- controls
- broad base advice
- non-specific screenshots
- multiplayer troubleshooting
Avoid:
- unrevealed creature names
- late areas
- story terminals
- exact progression solutions
Stable Story Spoilers
Current public Early Access content.
Experimental Spoilers
Anything visible only through Experimental or unreleased testing.
Never put Experimental discoveries in #general simply because "everyone will see them eventually."
Co-op Crew Roles Should Be Functional, Not Class-Based
Subnautica 2 has no MMO class system.
Useful crew responsibilities can include:
- Navigator / Exploration
- Builder
- Resource Gatherer
- Scanner / Research
- Vehicle / Tadpole
- Story Lead
- Base Logistics
These are session responsibilities, not permanent character classes.
A four-person crew might use:
Explorer
Builder
Resource / Logistics
Research / Scanning
and swap freely.
Do not create a "Healer" slot simply because Player Revives now exist.
Use Buddy System Features as Co-op Etiquette
Early Access 1.2 makes multiplayer much more socially expressive.
Proximity Voice
Decide whether the crew wants immersion or constant Discord comms.
Revives
If someone goes down, teammates can revive them before reprinting.
A revived player retains equipment and regains some oxygen.
That creates a useful crew norm:
Call out/downed location before immediately choosing reprint if the situation is recoverable.
Player Trading
Players can directly exchange inventory items.
That means the community can coordinate:
- build materials
- food/resources
- tools
- expedition supplies
but should still agree on shared-base storage etiquette.
Emotes
Useful for casual/non-voice crews.
These features reduce the need for Discord to micromanage every resource movement.
Add a Crew World & Expedition Ledger Only When You Need It
Abyssal Relay can launch with built-ins.
Group Finder handles today's crew. Beacon handles recurring sessions. Tickets handle bugs/crew conflicts. Announcements handle updates.
A custom plugin becomes useful if continuing crews repeatedly ask:
Which world are we continuing, who is responsible for the current save, which branch/build is it on, what was our last spoiler-safe checkpoint, and what base/resource tasks are next?
Before building, check the Marketplace for a maintained solution. If none fits, create Crew World & Expedition Ledger.
Copy-ready Plugin Builder specification
Plugin Name: Crew World & Expedition Ledger
Purpose:
Maintain Discord-local metadata for continuing Subnautica 2 co-op worlds, crew membership, branch/version compatibility, spoiler checkpoint, base projects, and expedition tasks without accessing game saves or duplicating Group Finder, Beacon Events, Tickets, or Announcements.
Version 1 network policy:
No external network access.
No Steam API.
No Xbox API.
No Cloud Save API.
No save-file access.
No game process integration.
Never request/store:
- Steam/Microsoft/Xbox passwords
- 2FA/recovery codes
- session tokens
- payment information
- raw private cloud credentials
- remote desktop credentials
Roles:
Administrators:
- Administrator
- Moderator
Crew editors:
- Crew Lead
- World Steward
Member:
- view worlds they are authorized to see
- update own task/readiness
- acknowledge current branch/build
World record fields:
- world_name
- branch:
Stable | Experimental
- game_update:
text, e.g. EA 1.2
- build_note:
optional text
- platform_mix:
Steam PC | Xbox PC | Xbox Series | Crossplay
- max_crew:
4
- current_crew_members:
max 4 Discord users
- primary_world_steward
- backup_world_steward
- survival_or_creative:
Survival | Creative
- spoiler_level:
spoiler_free | early_story | current_stable_endpoint | experimental
- last_session_at
- next_session
- current_progression_note
- current_base_note
- current_vehicle_note
- modded:
yes/no
- mod_revision:
optional
- save_backup_confirmed_at:
manually maintained status/date only
- status:
active | paused | completed | archived
Task fields:
- world_name
- category:
exploration
base_build
resources
scanning
biomod
vehicle
story
testing
- task_title
- spoiler_level
- assigned_members
- status:
planned | in_progress | done | blocked
- notes
Experimental test record:
- world_name
- Experimental build
- test_feature
- reproduction_steps
- bug_observed:
yes/no
- feedback_submitted:
yes/no
- status
Leadership-only:
- conflict_note
- moderation_note
- recovery_note
- reviewed_by
- reviewed_at
Suggested commands:
- /sub2-world create
- /sub2-world view
- /sub2-world roster
- /sub2-world set-branch
- /sub2-world set-build
- /sub2-task create
- /sub2-task assign
- /sub2-task complete
- /sub2-experimental test
- /sub2-world archive
Dashboard member view:
- authorized crew worlds
- Stable/Experimental label
- crew roster
- next session
- spoiler checkpoint
- current projects/tasks
- steward contacts
- mod status
Dashboard staff/crew view:
- all authorized world metadata
- stale worlds
- version mismatches
- backup-confirmation dates
- Experimental test records
- audit history
Authorization:
- every read/write server-side authorized
- only assigned crew members can view private crew worlds if configured that way
- only Crew Lead/World Steward can edit world metadata
- members can update assigned task status
- revoking Crew Lead/Steward removes privileged access on next request
- direct record URLs enforce the same policy
- data isolated by Discord server ID
- exports, if added, authorized staff/crew-lead only and audited
Security/privacy:
- do not store actual account passwords
- do not store raw save files in version 1
- do not store cloud transfer secrets beyond community-approved non-sensitive references
- do not expose Experimental spoilers to spoiler-free users
Explicit non-capabilities:
- Does not host Subnautica 2.
- Does not create a dedicated server.
- Does not upload/download game saves.
- Does not import Cloud Save codes.
- Does not verify world progress.
- Does not read inventory, base, Biomods, scans, or story flags.
- Does not invite players.
- Does not revive/trade items.
- Does not synchronize Stable and Experimental saves.
- Does not replace Group Finder.
- Does not replace Beacon.
Acceptance tests:
1. Crew Lead creates a Stable world capped at 4 members.
2. Fifth member cannot be added as active crew without removing/reclassifying someone.
3. Experimental world is visibly labeled and cannot be merged with Stable world record.
4. Spoiler-free member cannot open Experimental-spoiler record.
5. Member updates assigned resource task.
6. Revoking World Steward removes edit access.
7. Direct URL cannot bypass spoiler/crew authorization.
8. Server A Discord cannot read Server B data.
9. Archived world disappears from active list.
10. No workflow requests account credentials or reads a save file.
Review, test, and continue through the SDK
Review:
- plan
- source
- manifest
- capabilities
- spoiler authorization
- crew authorization
- audit behavior
Version 1 should need no external network access.
Test as:
- New Pioneer
- Stable crew member
- Experimental tester
- Crew Lead
- World Steward
- Moderator
- revoked Steward
Test direct URLs, spoiler separation, four-player roster validation, archive behavior, and cross-Discord isolation.
Continue with the current YourBot SDK workflow:
yourbot new
yourbot dev
yourbot dev --watch
yourbot validate
yourbot doctor
Marketplace publication is optional.
Passing validation does not mean the save is healthy or compatible with a future game update.
Run a Complete First-Week Member Journey
| Scenario | Successful result |
|---|---|
| New Xbox player joins | Selects Stable/Crossplay/Spoiler-Free and sees no Experimental spoilers. |
| Continuing crew | Group Finder caps at 4 and records the correct branch. |
| Mixed PC/Xbox crew | Crossplay listing works without splitting compatible players. |
| Experimental session | Only Experimental players join; Stable world is not treated as transferable. |
| Buddy System voice | Crew intentionally chooses in-game proximity voice or Discord. |
| Base night | Four-player event tracks resources/project without turning everyone into a permanent "Builder class." |
| Patch arrives | Announcement tells modded crews to revalidate mods before continuing. |
| Community night | 12 attendees are explicitly organized as three independent four-player worlds. |
| Crew ledger | World steward/version/spoiler metadata stays separate from actual save files. |
Fix branch, spoiler, and world-stewardship confusion before adding more automation.
Frequently Asked Questions
Is Subnautica 2 playable now?
Yes. It entered Early Access / Xbox Game Preview on May 14, 2026.
How many people can play together?
Up to four total players—one player plus up to three friends.
Does Subnautica 2 support crossplay?
Yes. Current Steam/Xbox material confirms cross-platform multiplayer/co-op across the currently supported PC/Xbox ecosystem.
Is PlayStation part of the current Early Access release?
The verified May 2026 Early Access launch sources used for this guide identify PC and Xbox Series X|S. This guide therefore does not advertise PlayStation as a current Early Access co-op platform.
What is the current major update?
Early Access 1.2 — Buddy System.
What did Buddy System add?
Proximity Voice Chat, Player Revives, direct Player Trading, Emotes, two additional Pioneer character options, and numerous multiplayer/base improvements.
Can Stable and Experimental players play together?
No. Experimental multiplayer is limited to Experimental players, and Stable/Experimental saves are separate and incompatible.
Does Subnautica 2 have official dedicated servers?
No official dedicated-server workflow/tool was verified in the first-party sources used for this September 2026 guide. Current verified product material describes four-player online co-op.
Does YourBot automatically detect Subnautica 2 in Group Finder?
Not in the read-only develop revision inspected for this guide. Create explicit four-player templates.
Is Subnautica 2 in YourBot's curated Social Feeds catalog?
Not in the inspected catalog. Add the generic Steam source manually with App ID 1962700.
Can YourBot read my world, bases, Biomods, scans, or story progress?
Not through the built-in services. The optional Crew World & Expedition Ledger stores manually maintained coordination metadata, not game-save data.
Build the Discord Around the Crew and the Version They Are Actually Playing
Subnautica 2 already has the game-side systems for four-player co-op, cross-platform invitations, bases, exploration, trading, revives, proximity voice, Biomods, vehicles, saves, and Experimental testing. A useful Discord should make those systems easier to coordinate without pretending the game is a persistent public survival server.
Start Your Server creates the spoiler-safe shell. Welcome makes branch/platform expectations clear. Sentinel protects mod/save/account discussion. Tickets separate bugs from crew conflict. Group Finder uses the real four-player cap. Beacon schedules recurring worlds and parallel crew nights. Temporary voice complements rather than replaces Proximity Chat. Announcements keep Stable, Experimental, hotfixes, and mod compatibility visible. Social Feeds uses official Steam publisher announcements.
Subnautica 2 remains authoritative for the world, save, inventory, base, Biomods, story state, revives, trades, Pioneer characters, and branch compatibility.
Use Start Your Server to establish or refine the Discord foundation. Add Plugin Builder only when persistent world/steward/task coordination becomes a real recurring need the built-in services do not already solve.