Subnautica 2 Wiki Subnautica 2 Wiki
Menu
Update

Early Access Roadmap Sets the Update Rhythm

The first Early Access roadmap set the sequence: EA1.1 quality-of-life work has shipped, co-op improvements are next, and larger world and story expansions remain later goals.

Checked for
Early Access launch
Last checked
2026-07-17
Source status
Officially confirmed · Official
Spoilers
None
On this page

Player impact

What to do now

01

EA1.1 shipped as Adaptive Measures, delivering the roadmap's first quality-of-life pass.

Who should care
Players dealing with biomods, blight encounters, wreck routes, vehicle docking, PDA flow, storage, and the lack of sprint.
What to do
Update to EA1.1 or later and use the Adaptive Measures page before following launch-era route or system advice.
Recheck
Resource routes, vehicle setup advice, scanner/base guidance, and beginner recommendations now need an EA1.1 review.
02

EA 1.2 is the co-op-focused update on the public roadmap.

Who should care
Co-op groups planning roles, rescue rules, trading, signals, base building, and shared resource runs.
What to do
Do not lock in current co-op advice as final; use launch pages for the current version and wait for EA 1.2 before making durable co-op guides.
Recheck
Any future co-op FAQ or route should be rechecked for voice chat, revive, trading, player signals, base builder improvements, and pinned recipes.
03

Later roadmap drops will add world, biome, creature, resource, tool, vehicle, and story content.

Who should care
Players following story routes, deep biome advice, vehicle progression, or long-term save planning.
What to do
Use current guides as launch-build help, not final 1.0 walkthroughs.
Recheck
Do not freeze story, biome, or vehicle progression pages until the relevant expansion content is live.

Roadmap priorities

Unknown Worlds published the first Early Access roadmap one day after launch. It shows what the studio plans to work on first: polish the current build, improve co-op, then expand the game world.

The official post says updates will vary between focused improvements, hotfixes, and larger expansions. It also says the roadmap can change based on feedback, so do not read the list as fixed dates or locked patch contents.

EA1.1 shipped as Adaptive Measures

The first planned update was framed around quality-of-life. It shipped on July 8, 2026, as Adaptive Measures, covering Biomods, blight encounters, wrecks, vehicle docking and fabrication, PDA and audiolog flow, storage, passive Biomod slots, and sprint.

Hotfix 4 followed on July 14 to fix Angel Comb progression, currents inside bases, the Xbox FOV slider, and two crashes. Launch-era pages for these systems now need an EA1.1-or-later check rather than another wait-for-the-patch warning.

EA 1.2 is where co-op should start feeling less bolted on

The second planned update is the one co-op groups should watch. The official post frames it as requested co-op improvements and additions, and public roadmap coverage names voice chat, emotes, player trading, player revive, additional customization, HUD signal improvements, base builder improvements, and pinned recipe improvements.

For solo players, that may sound optional. For a group, revive, trading, and better signals change how a team splits exploration, resource runs, building, and rescue moments.

Bigger world, later story, fewer permanent guides

The future-expansion part is broader: larger world areas, new biomes, new creatures, resources, tools, vehicles, and the next story chapter. That is the section that should make players cautious about treating any current route as final.

If you are reading a guide during Early Access, check the last verified date. A guide about resources, biomes, vehicles, or story pacing can become outdated even if the page was accurate on launch week.

What the community is really asking for

Community discussion around Early Access is split between patience and pressure. Some players want the community to use Early Access for constructive criticism instead of hand-waving every flaw away. Others argue that the game already has a strong foundation and needs time.

Vague feedback helps less. Reports should name the system, route, co-op problem, creature interaction, patch version, and what happened in the save.

Sources used

Continue reading