Video walkthrough
Watch the route, then follow the written steps
Video references
Watch or inspect the route before you dive
Click YouTube cards to load the player. Open frame cards to compare local screenshot notes. Use the evidence to confirm landmarks, movement, and encounter pacing, then follow the written checklist below.
Blackbox Ruby walkthrough reference
Watch for: Ruby Blackbox cleanup, route proof, and lore-evidence sequencing.
Blackbox route frame review
Watch for: Start with All Blackbox locations / Ruby walkthrough at 01:14. Compare the screenshot cue, route note, and player action before following the guide in-game.
Cleanup proof frame review
Watch for: Start with All Blackbox locations / Ruby walkthrough at 02:40. Compare the screenshot cue, route note, and player action before following the guide in-game.
Video watch notes
What to pause, compare, and write down
Do not watch the video like entertainment only. Use these notes as a second-screen checklist: pause on landmarks, confirm the player action, then return to the written route.
Watchlist
Pause on Route clue and identify the landmark, depth band, or objective state before following the next step.
Use Blackbox route to confirm what changed; if the video only shows a close-up, rebuild the route from the previous landmark.
Treat Cleanup proof as the exit rule: finish the objective, return, and update storage or crafting before adding side goals.
Route clue
Use the route clue to keep Ruby cleanup from becoming a broad collectible sweep.
Action: Start from the correct route cluster.
Blackbox route
The Blackbox route should show approach, proof, and return order.
Action: Confirm the Ruby log pickup or Blackbox state.
Cleanup proof
Cleanup proof prevents repeated evidence runs through the same area.
Action: Mark the item complete in the checklist.
Video route timeline
Turn the video into playable checkpoints
Use this section like a second-screen route sheet. Open each checkpoint, compare the frame, do the action, then stop if your route no longer matches the video evidence. It keeps the guide useful even when Early Access shifts small placements or creature behavior.
00:18Checkpoint 1: Start from the correct route cluster.Use the route clue to keep Ruby cleanup from becoming a broad collectible sweep.Expand
Route clue
Use the route clue to keep Ruby cleanup from becoming a broad collectible sweep.
Player action
Start from the correct route cluster.
Proof before moving on
Use the route clue to keep Ruby cleanup from becoming a broad collectible sweep.
Watch this timestampIf this fails
Reset to the last confirmed landmark or objective state, then repeat only the route-critical step.
01:14Checkpoint 2: Confirm the Ruby log pickup or Blackbox state.The Blackbox route should show approach, proof, and return order.Expand
Blackbox route
The Blackbox route should show approach, proof, and return order.
Player action
Confirm the Ruby log pickup or Blackbox state.
Proof before moving on
The Blackbox route should show approach, proof, and return order.
Watch this timestampIf this fails
Use the video frame as evidence, but record entry, proof, and exit as separate notes.
02:40Checkpoint 3: Mark the item complete in the checklist.Cleanup proof prevents repeated evidence runs through the same area.Expand
Cleanup proof
Cleanup proof prevents repeated evidence runs through the same area.
Player action
Mark the item complete in the checklist.
Proof before moving on
Cleanup proof prevents repeated evidence runs through the same area.
Watch this timestampIf this fails
Return, craft, sort storage, or retest the route before turning this page into a longer objective chain.
00:18Checkpoint 4: Return before chaining unrelated rooms.Use the route clue to keep Ruby cleanup from becoming a broad collectible sweep.Expand
Route clue
Use the route clue to keep Ruby cleanup from becoming a broad collectible sweep.
Player action
Return before chaining unrelated rooms.
Proof before moving on
Use the route clue to keep Ruby cleanup from becoming a broad collectible sweep.
Watch this timestampIf this fails
Reset to the last confirmed landmark or objective state, then repeat only the route-critical step.
Gameplay evidence
Screenshots to match before you keep swimming
Use these frames as visual checkpoints. If the terrain, lighting, or landmark does not match, slow down and re-check the route instead of forcing the next step.
Route clue
Use the route clue to keep Ruby cleanup from becoming a broad collectible sweep.
Blackbox route
The Blackbox route should show approach, proof, and return order.
Cleanup proof
Cleanup proof prevents repeated evidence runs through the same area.
Route decision lab
Decide if this route is worth running now
This section turns the video into a practical in-game decision. Use it before leaving base, after the first landmark, and again before entering a deeper or darker area.
Route purpose
Clear Blackbox Ruby by treating it as one collectible route cluster. Confirm entry, collect the log, check proof, and leave before the route turns into a full structure sweep.
Visual checkpoint
Use the route clue to keep Ruby cleanup from becoming a broad collectible sweep.
Map anchor
Blackbox Ruby Evidence Anchor in Ruby evidence cleanup route. Use it for use this when story cleanup needs proof instead of repeating broad collectible sweeps.
Abort rule
Trying to clear every Blackbox in one route.
Field manual translation
Clear Blackbox Ruby by treating it as one collectible route cluster. Confirm entry, collect the log, check proof, and leave before the route turns into a full structure sweep. Use this completion 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
Blackbox Ruby - Start from the correct route cluster.
Best entry habit
Route cluster - Confirm the Ruby log pickup or Blackbox state.
Stop condition
Trying to clear every Blackbox in one route. - Mark the item complete in the checklist.
Patch-safe reading
Exact item positions can shift during Early Access. The useful part of this page is the route logic: what to prepare, what visual cue to confirm, what objective to finish, and when to turn back.
Updated
2026-06-12 / tracking / Early Access
What this guide covers
Requirements
- Route cluster
- Log pickup
- Exit line
Use this if
You want a route you can follow from video evidence without needing exact official coordinates. The screenshots and steps are written to help you recognize areas, landmarks, and decisions while playing.
Early Access can move details. Treat this as a video-based walkthrough and verify landmarks in your own build.
Step-by-step walkthrough
Follow the video route without guessing
Start from the correct route cluster.
Use this step as a route checkpoint, not as a promise that every object spawns in one exact coordinate. Match the landmark, compare the screenshot, then continue only if the return path is still clear.
If your game build looks different, stay with the same decision: keep oxygen safe, scan or collect the current blocker, and return before pushing into the next unknown area.
Use the route clue to keep Ruby cleanup from becoming a broad collectible sweep.
Confirm the Ruby log pickup or Blackbox state.
Use this step as a route checkpoint, not as a promise that every object spawns in one exact coordinate. Match the landmark, compare the screenshot, then continue only if the return path is still clear.
If your game build looks different, stay with the same decision: keep oxygen safe, scan or collect the current blocker, and return before pushing into the next unknown area.
The Blackbox route should show approach, proof, and return order.
Mark the item complete in the checklist.
Use this step as a route checkpoint, not as a promise that every object spawns in one exact coordinate. Match the landmark, compare the screenshot, then continue only if the return path is still clear.
If your game build looks different, stay with the same decision: keep oxygen safe, scan or collect the current blocker, and return before pushing into the next unknown area.
Cleanup proof prevents repeated evidence runs through the same area.
Return before chaining unrelated rooms.
Use this step as a route checkpoint, not as a promise that every object spawns in one exact coordinate. Match the landmark, compare the screenshot, then continue only if the return path is still clear.
If your game build looks different, stay with the same decision: keep oxygen safe, scan or collect the current blocker, and return before pushing into the next unknown area.
Use the route clue to keep Ruby cleanup from becoming a broad collectible sweep.
After-action plan
What to do after the guide works
Bank the result
Return before chaining unrelated rooms.
Clean the inventory
Move route-critical materials into labeled storage so the next dive starts with empty space and a clear job.
Pick the next guide
A completion-focused Blackbox route guide for log pickups, route order, screenshot checkpoints, and avoiding repeated cleanup sweeps.
Next route queue
Use these as the next blockers to solve after this route. Each queue card keeps the same evidence style: source video, gameplay frames, and a written checklist.
Best immediate follow-upAll Blackbox Locations
A completion-focused Blackbox route guide for log pickups, route order, screenshot checkpoints, and avoiding repeated cleanup sweeps.
Use if the route branchesBlackbox Quaker Walkthrough
A Blackbox Quaker walkthrough for route entry, log pickup proof, room-state checks, and avoiding repeated Old Habitat cleanup.
Save for the next diveStory and Lore Guide
A spoiler-aware story and lore guide for colonist logs, Axum clues, Old Habitat context, and what Early Access currently explains.
Detailed notes
Blackbox log route route plan
Blackbox Ruby Walkthrough is useful when the route is treated as a focused job instead of a full-map sweep. Start by naming the blocker, checking the loadout, and matching the first landmark before copying the video. The player goal is not to memorize every second of movement; it is to understand why the route begins there, what proves progress, and when the route should stop.
Route type: Blackbox log route
Proof to confirm: Blackbox Ruby pickup confirmation
Primary blocker: Route cluster
Best follow-up: Return before chaining unrelated rooms.
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
How to use the video evidence
Watch for the entry frame, the proof frame, and the exit frame. The entry frame tells you whether you are in the right terrain band. The proof frame tells you whether the scan, pickup, blueprint, puzzle state, or build decision actually happened. The exit frame protects the run from turning into a panic search after the objective is already solved.
Entry frame: match terrain before diving deeper
Proof frame: confirm Blackbox Ruby pickup confirmation
Exit frame: return before adding side goals
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Stop rule
Stop after Ruby is checked off and update the story evidence route. If the route fails, change one variable before trying again: bring the missing tool, empty inventory, approach from a clearer landmark, or wait until oxygen, vehicle depth, or defensive options match the route. That makes the next attempt safer and gives the page useful field notes instead of repeated guesswork.
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Video route notes
Blackbox Ruby Walkthrough should be followed as a completion route, not as a memory test. Start by watching the first route movement and naming the entry condition before copying the path in-game. Start from the correct route cluster. Then pause again when the video reaches the first visible proof point, because that is where the guide changes from general advice into an action you can repeat. Confirm the Ruby log pickup or Blackbox state. If the route starts to feel different in your build, keep the same player goal: finish the unlock cleanly and know whether a return trip is needed.
Entry check: Route cluster
Route action: Start from the correct route cluster.
Proof to look for: scan or pickup proof
Version note: Early Access / tracking
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Screenshot checkpoints
Use screenshots as checkpoints instead of decoration. The first image should answer where the route begins, the second should show what confirms progress, and the third should explain what to do after the scan, pickup, puzzle state, or threat read is visible. Mark the item complete in the checklist. This is especially important in Early Access because exact positions can drift while landmarks, depth bands, room states, and player decisions stay useful. A good screenshot lets you say, "I am at the right kind of place," before you risk oxygen, storage space, or vehicle safety.
Entry frame: match the landmark before moving deeper
Proof frame: confirm scan or pickup proof
Exit frame: know the return direction before adding side goals
Loadout frame: check Log pickup
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Stop rule and next dive
The most useful part of this page is the stop rule. Trying to clear every Blackbox in one route. Skipping pickup proof before leaving the room. When the objective is confirmed, return and convert it into progress: craft the upgrade, sort the material, save the route note, or mark the blocker as solved. If the route fails, do not repeat the same swim blindly. Change one variable at a time: enter from a clearer landmark, reduce inventory clutter, bring the missing tool, or wait until oxygen and vehicle support match the route. That turns a failed completion route into better field knowledge instead of another untracked cleanup sweep.
How to use this in-game
Turn this note into one action before leaving base: decide the objective, keep only the materials or tools that support it, then stop the route once the scan, pickup, or landmark is confirmed. This keeps the guide useful even when Early Access patches move small details.
Common mistakes
Trying to clear every Blackbox in one route.
Skipping pickup proof before leaving the room.
Mixing story logs with rare-material farming.
FAQ
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.