Quick answer
Read patch notes as route changes: creature behavior, progression fixes, graphics settings, and multiplayer stability can all make an old guide partially wrong. Re-test high-risk pages after each hotfix.
Second-screen dive plan
What to do, what proves it, and when to leave
Scan the hotfix for creature, progression, multiplayer, and performance changes.
Patch headline at 00:10
Retest blockers first, then threats, then material routes, then visual or performance notes.
Bug Fixes and Stuck State Guide
Patch headline
Patch-note pages should start by identifying which gameplay systems changed.
Approach
Retest blockers first, then threats, then material routes, then visual or performance notes.
Objective
Hotfix tracker marker for pages that need retesting after updates.
Return
Use this after each Early Access patch to find which routes, creatures, puzzles, or bugs changed.
Tactical brief
How to use this guide in a real dive
Patch Notes and Hotfix Tracker is useful when the player needs a repeatable decision path, not just a short answer. Start with the page objective, then compare the map anchor, the first evidence frame, and the current Early Access status before committing to a longer dive. This keeps the guide practical when Subnautica 2 routes shift between patches.
On the atlas, this guide is tied to Patch and Hotfix Retest Hub. Treat that marker as a route anchor: Hotfix tracker marker for pages that need retesting after updates. The important player action is not simply reaching the dot, but using it to decide when to approach, what to scan or gather, and how to leave cleanly.
The first visual check is Patch headline (00:10). Use that frame as the reading order for the rest of the article: identify the landmark, confirm the objective, then watch for the mistake that would force a reset. Patch-note pages should start by identifying which gameplay systems changed.
Route band
Version tracker, System
Retest blockers first, then threats, then material routes, then visual or performance notes.
Proof point
Patch headline (00:10)
Patch-note pages should start by identifying which gameplay systems changed.
Abort rule
Treating an old video as current after creature tuning.
Use this after each Early Access patch to find which routes, creatures, puzzles, or bugs changed.
After this
Bug Fixes and Stuck State Guide
A practical troubleshooting page for stuck Tadpole states, dock clearance, hotbar input issues, and when to reload safely.
Visual route
Follow the guide by screenshot evidence
Use these frames as a quick watch order: landmark first, objective second, exit condition third. It keeps the article useful even before you read every paragraph.
Patch headline
Patch-note pages should start by identifying which gameplay systems changed.
Player action
Current build
Creature changes
Creature tuning can invalidate old threat advice even when the route still exists.
Player action
Scan the hotfix for creature, progression, multiplayer, and performance changes.
Fix list
Progression, multiplayer, and graphics fixes decide which guide pages need retesting first.
Player action
Treating an old video as current after creature tuning.
Video references
Watch or inspect the route before you dive
Open frame cards to compare local screenshot notes. Use the evidence to confirm landmarks, movement, and encounter pacing, then follow the written checklist below.
Hotfix and patch-note source footage
Watch for: Creature tuning, DLSS or graphics notes, progression fixes, and retest priority.
Creature changes frame review
Watch for: Start with Hotfix 3 update review at 01:28. Compare the screenshot cue, route note, and player action before following the guide in-game.
Fix list frame review
Watch for: Start with Hotfix 3 update review at 02:56. Compare the screenshot cue, route note, and player action before following the guide in-game.
Field manual
Patch Notes and Hotfix Tracker field manual
Built from the supplied route videos and local frame captures so the article teaches what to watch for, not only what to click.
Read patch notes as route changes: creature behavior, progression fixes, graphics settings, and multiplayer stability can all make an old guide partially wrong. Re-test high-risk pages after each hotfix. Use this progression route manual as a second-screen checklist: identify the entry condition, confirm the objective with a visual proof point, then stop when the return rule is met. This keeps the article practical for Early Access patches without pretending every coordinate or state is final.
Primary job
Early Access
Scan the hotfix for creature, progression, multiplayer, and performance changes.
Best entry habit
Current build
Tag affected guide pages by route, item, puzzle, or threat.
Stop condition
Treating an old video as current after creature tuning.
Retest only the pages touched by the update first.
What to watch in the videos
Pause on Patch headline and identify the landmark, depth band, or objective state before following the next step.
Use Creature changes to confirm what changed; if the video only shows a close-up, rebuild the route from the previous landmark.
Treat Fix list as the exit rule: finish the objective, return, and update storage or crafting before adding side goals.
Decision table
Treating an old video as current after creature tuning.
Reset to the last confirmed landmark or objective state, then repeat only the route-critical step.
Updating a page title without retesting the route.
Use the video frame as evidence, but record entry, proof, and exit as separate notes.
Ignoring multiplayer or input fixes that affect FAQ pages.
Return, craft, sort storage, or retest the route before turning this page into a longer objective chain.
Screenshot reading order
Patch headline
Patch-note pages should start by identifying which gameplay systems changed.
Player action: Scan the hotfix for creature, progression, multiplayer, and performance changes.
Creature changes
Creature tuning can invalidate old threat advice even when the route still exists.
Player action: Tag affected guide pages by route, item, puzzle, or threat.
Fix list
Progression, multiplayer, and graphics fixes decide which guide pages need retesting first.
Player action: Retest only the pages touched by the update first.
Map intel
Route anchors for this guide
Patch and Hotfix Retest Hub
Hotfix tracker marker for pages that need retesting after updates.
Player use
Use this after each Early Access patch to find which routes, creatures, puzzles, or bugs changed.
Route hint
Retest blockers first, then threats, then material routes, then visual or performance notes.
Field checklist
Before leaving base
Current build
Primary action
Scan the hotfix for creature, progression, multiplayer, and performance changes.
Turn back when
Treating an old video as current after creature tuning.
Write down
Early Access / tracking / 2026-06-12
Database cards
Entities in this guide
These cards give players the scan target, material, creature, or structure they should be watching for while following the guide.
Hammerhead
Predator behavior currently affected by Early Access tuning.
Found in: Steam news and hotfix notes mention behavior and Tadpole interest.
Action: Carry mitigation tools, watch aggro timing, and re-check patch notes before writing fixed tactics.
Rare materials
Crafting bottlenecks that should be tracked by biome and recipe value.
Found in: Early Access content model; exact material tables need verified field data.
Action: Store separately, label the source route, and spend only on route-changing recipes.
Sulfur
Material commonly associated with early thermal or volcanic terrain and the Welcome Center route direction.
Found in: PC Gamer, Polygon, and community material guides supplied for content research.
Action: Use thermal terrain as the clue, collect a small confirmed haul, and leave before heat or oxygen pressure stacks.
Welcome Center
Early route anchor that turns the first objective chain into a readable progression path.
Found in: GameSpot walkthrough and first-route guides supplied by the user.
Action: Visit after stabilizing oxygen, food, water, and inventory, then return to craft after each new signal.
Evidence board
Media and verification
Each guide now reserves space for footage, screenshots, map notes, and patch checks so the page can grow with real player evidence.
Early Access Development
Official media tied to Early Access scope, patch changes, and version tracking.
Video references
3 embedded source cards
Route checks
5 checkpoints
Screenshot queue
Ready for owned gameplay captures
Gameplay frame gallery
Visual checkpoints from source footage
Frames are center-cropped from local research footage to keep the article focused on landmarks, nodes, creatures, and route cues.
Patch headline
Patch-note pages should start by identifying which gameplay systems changed.
Creature changes
Creature tuning can invalidate old threat advice even when the route still exists.
Fix list
Progression, multiplayer, and graphics fixes decide which guide pages need retesting first.
Loadout and prerequisites
Route timeline
Follow the run in order
Built for second-screen use: complete each checkpoint, then move to the next landmark before detouring for extras.
Scan the hotfix for creature, progression, multiplayer, and performance changes.
Tag affected guide pages by route, item, puzzle, or threat.
Retest only the pages touched by the update first.
Update page status from tracking to field-tested when evidence is current.
Keep outdated claims conservative until screenshots or player reports confirm them.
Guide notes
Hotfixes change guide confidence
A patch note does not always change a route, but it changes how confident the page should sound. Threat, puzzle, and bug pages need the fastest retest loop.
Retest queue
Sort retests by player pain: crashes and blockers first, then threats, then resource routes, then visual or performance notes.
Risk controls
Common mistakes
These are the actions most likely to waste oxygen, lose the route, or turn a clean scan into a failed attempt.
Treating an old video as current after creature tuning.
Updating a page title without retesting the route.
Ignoring multiplayer or input fixes that affect FAQ pages.
FAQ
Fast answers before you dive
Is this guide for the current Subnautica 2 build?
This page is written for Early Access and includes a visible update date. Treat exact values as tracking notes until the current build is field-tested.
Does this page use official screenshots?
Pages combine attributed official Steam / Unknown Worlds media, local gameplay frame captures, and source-video evidence cards. New player-submitted captures should keep the route, timestamp, and build context attached.
Community notes
Add a field report
Player reports enter a moderation queue. Approved notes can load from Supabase; pending drafts stay visible in this browser for follow-up.
Near starter shallows
Approx. 70-120m from pod
Confirm oxygen before leaving the first landmark. The route is much safer when you mark the return path before collecting side materials.
Guide-wide
N/A
Creature patrol ranges and fragment placement can shift between builds, so treat exact distances as field estimates until multiple players confirm them.