Quick answer
When a Subnautica 2 bug blocks progress, stop adding new actions. Save the current state if safe, document the location, try the least destructive fix first, then reload only after preserving the route note.
Second-screen dive plan
What to do, what proves it, and when to leave
Stop interacting once the bug state is visible.
Bug state at 00:08
Stop inputs, identify state, try the least destructive fix, then reload only if the save is safe.
Multiplayer Co-op Guide
Bug state
Pause when the stuck state is visible and record what the game is currently doing.
Approach
Stop inputs, identify state, try the least destructive fix, then reload only if the save is safe.
Objective
Bug and stuck-state guide entry for Tadpole dock and hotbar issues.
Return
Use this when a bug blocks progress and you need a safe order of operations before reloading.
Tactical brief
How to use this guide in a real dive
Bug Fixes and Stuck State Guide 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 Bug Fix Troubleshooting Anchor. Treat that marker as a route anchor: Bug and stuck-state guide entry for Tadpole dock and hotbar issues. 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 Bug state (00:08). 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. Pause when the stuck state is visible and record what the game is currently doing.
Route band
Troubleshooting route note, Variable
Stop inputs, identify state, try the least destructive fix, then reload only if the save is safe.
Proof point
Bug state (00:08)
Pause when the stuck state is visible and record what the game is currently doing.
Abort rule
Spamming inputs and making the stuck state harder to describe.
Use this when a bug blocks progress and you need a safe order of operations before reloading.
After this
Multiplayer Co-op Guide
How to split jobs, share discoveries, avoid duplicated work, and keep co-op exploration organized in Subnautica 2.
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.
Bug state
Pause when the stuck state is visible and record what the game is currently doing.
Player action
Current save
Clearance check
Many vehicle issues start as clearance or state problems, not permanent save damage.
Player action
Stop interacting once the bug state is visible.
Unstuck result
Verify the result before saving again so the fix does not preserve a worse state.
Player action
Spamming inputs and making the stuck state harder to describe.
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.
Tadpole dock bug source footage
Watch for: Stuck state, clearance check, input/order of operations, and safe recovery.
Clearance check frame review
Watch for: Start with Tadpole dock bug fix at 00:38. Compare the screenshot cue, route note, and player action before following the guide in-game.
Unstuck result frame review
Watch for: Start with Tadpole dock bug fix at 01:22. Compare the screenshot cue, route note, and player action before following the guide in-game.
Field manual
Bug Fixes and Stuck State Guide 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.
When a Subnautica 2 bug blocks progress, stop adding new actions. Save the current state if safe, document the location, try the least destructive fix first, then reload only after preserving the route note. 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
Troubleshooting
Stop interacting once the bug state is visible.
Best entry habit
Current save
Record the vehicle, door, dock, or hotbar condition.
Stop condition
Spamming inputs and making the stuck state harder to describe.
Try spacing, undock, relog, or input reset steps before risky fixes.
What to watch in the videos
Pause on Bug state and identify the landmark, depth band, or objective state before following the next step.
Use Clearance check to confirm what changed; if the video only shows a close-up, rebuild the route from the previous landmark.
Treat Unstuck result as the exit rule: finish the objective, return, and update storage or crafting before adding side goals.
Decision table
Spamming inputs and making the stuck state harder to describe.
Reset to the last confirmed landmark or objective state, then repeat only the route-critical step.
Reloading before remembering the route or objective state.
Use the video frame as evidence, but record entry, proof, and exit as separate notes.
Assuming a bug fix video still applies after a hotfix.
Return, craft, sort storage, or retest the route before turning this page into a longer objective chain.
Screenshot reading order
Bug state
Pause when the stuck state is visible and record what the game is currently doing.
Player action: Stop interacting once the bug state is visible.
Clearance check
Many vehicle issues start as clearance or state problems, not permanent save damage.
Player action: Record the vehicle, door, dock, or hotbar condition.
Unstuck result
Verify the result before saving again so the fix does not preserve a worse state.
Player action: Try spacing, undock, relog, or input reset steps before risky fixes.
Map intel
Route anchors for this guide
Bug Fix Troubleshooting Anchor
Bug and stuck-state guide entry for Tadpole dock and hotbar issues.
Player use
Use this when a bug blocks progress and you need a safe order of operations before reloading.
Route hint
Stop inputs, identify state, try the least destructive fix, then reload only if the save is safe.
Field checklist
Before leaving base
Current save
Primary action
Stop interacting once the bug state is visible.
Turn back when
Spamming inputs and making the stuck state harder to describe.
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.
Tadpole submersible
Primary mobility reference for deeper biome pushes and co-op hauling.
Found in: Official Steam store description and media.
Action: Plan routes around return oxygen, storage, and safe vehicle access.
Habitat Builder
Core building tool that turns early routes into a working storage and fabricator loop.
Found in: Local base-building footage and early unlock guides supplied for content research.
Action: Unlock it, return, and build the minimum base that shortens the next material and scan routes.
Square Room
Base expansion unlock for storage, Biolab planning, and less cramped crafting workflow.
Found in: Local Square Room databox footage supplied for content research.
Action: Confirm the databox unlock, return to stable power, and build only when the room improves workflow.
Tadpole Depth Module
Vehicle depth upgrade that opens deeper objective and material bands.
Found in: Local Tadpole MK1 and MK2 depth module footage supplied for content research.
Action: Install the module, test on a known route, then use the new depth band with a planned exit.
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.
Tadpole Mobility
Official media for movement, vehicle routes, upgrades, and map pushes.
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.
Bug state
Pause when the stuck state is visible and record what the game is currently doing.
Clearance check
Many vehicle issues start as clearance or state problems, not permanent save damage.
Unstuck result
Verify the result before saving again so the fix does not preserve a worse state.
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.
Stop interacting once the bug state is visible.
Record the vehicle, door, dock, or hotbar condition.
Try spacing, undock, relog, or input reset steps before risky fixes.
Reload only after checking whether the current save is safe.
Submit a community note if the bug repeats in the current build.
Guide notes
Treat bugs like state problems
The useful question is what state the game thinks you are in: docked, undocked, seated, input-locked, blocked, or out of clearance. Solve the state first.
Safe troubleshooting order
Least destructive fixes first: step back, change clearance, re-enter vehicle, reset input, reload, then report. This keeps the save cleaner.
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.
Spamming inputs and making the stuck state harder to describe.
Reloading before remembering the route or objective state.
Assuming a bug fix video still applies after a hotfix.
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.