Quick answer
Treat Hammerheads as active Early Access tuning targets. Keep a retreat vector, test flare response after hotfixes, and avoid leaving Tadpoles in exposed routes until behavior is verified.
Second-screen dive plan
What to do, what proves it, and when to leave
Approach suspected Hammerhead routes with a visible exit line.
Threat read at 17:43
Approach, test one reaction, retreat, repair, and write the result before changing tools.
Bosses and Threats Overview
Threat read
Use creature posture and route pressure to decide whether Hammerhead contact is safe to observe.
Approach
Approach, test one reaction, retreat, repair, and write the result before changing tools.
Objective
Controlled threat-test anchor for Hammerhead spacing, flare response, and retreat practice.
Return
Use this only as an observation edge; do not bring rare inventory into a tactic test.
Tactical brief
How to use this guide in a real dive
Hammerhead Threat 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 Hammerhead Test Route. Treat that marker as a route anchor: Controlled threat-test anchor for Hammerhead spacing, flare response, and retreat practice. 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 Threat read (17:43). 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. Use creature posture and route pressure to decide whether Hammerhead contact is safe to observe.
Route band
Hammerhead patrol test edge, 500m - 850m
Approach, test one reaction, retreat, repair, and write the result before changing tools.
Proof point
Threat read (17:43)
Use creature posture and route pressure to decide whether Hammerhead contact is safe to observe.
Abort rule
Assuming a previous patch tactic still works.
Use this only as an observation edge; do not bring rare inventory into a tactic test.
After this
Bosses and Threats Overview
A conservative encounter hub for major threats, boss-like moments, escape planning, and Early Access verification.
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.
Threat read
Use creature posture and route pressure to decide whether Hammerhead contact is safe to observe.
Player action
Flares
Scan subject
Scan windows only matter when the escape line remains obvious.
Player action
Approach suspected Hammerhead routes with a visible exit line.
Large creature lane
Large-creature lanes should be crossed with a destination, not explored as open water.
Player action
Assuming a previous patch tactic still works.
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.
Threat read frame review
Watch for: Start with Creatures database guide / Hammerhead threat at 17:43. Compare the screenshot cue, route note, and player action before following the guide in-game.
Scan subject frame review
Watch for: Start with Creatures database guide / Hammerhead threat at 31:01. Compare the screenshot cue, route note, and player action before following the guide in-game.
Large creature lane frame review
Watch for: Start with Creatures database guide / Hammerhead threat at 35:27. Compare the screenshot cue, route note, and player action before following the guide in-game.
Field manual
Hammerhead Threat 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.
Treat Hammerheads as active Early Access tuning targets. Keep a retreat vector, test flare response after hotfixes, and avoid leaving Tadpoles in exposed routes until behavior is verified. Use this threat 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
Hammerhead
Approach suspected Hammerhead routes with a visible exit line.
Best entry habit
Flares
Keep the Tadpole parked where terrain does not trap a fast turn.
Stop condition
Assuming a previous patch tactic still works.
Test flare attraction only with enough oxygen and distance to leave.
What to watch in the videos
Pause on Threat read and identify the landmark, depth band, or objective state before following the next step.
Use Scan subject to confirm what changed; if the video only shows a close-up, rebuild the route from the previous landmark.
Treat Large creature lane as the exit rule: finish the objective, return, and update storage or crafting before adding side goals.
Decision table
Assuming a previous patch tactic still works.
Reset to the last confirmed landmark or objective state, then repeat only the route-critical step.
Leaving an unpiloted Tadpole in a high-traffic threat corridor.
Use the video frame as evidence, but record entry, proof, and exit as separate notes.
Testing mitigation tools with no escape margin.
Return, craft, sort storage, or retest the route before turning this page into a longer objective chain.
Screenshot reading order
Threat read
Use creature posture and route pressure to decide whether Hammerhead contact is safe to observe.
Player action: Approach suspected Hammerhead routes with a visible exit line.
Scan subject
Scan windows only matter when the escape line remains obvious.
Player action: Keep the Tadpole parked where terrain does not trap a fast turn.
Large creature lane
Large-creature lanes should be crossed with a destination, not explored as open water.
Player action: Test flare attraction only with enough oxygen and distance to leave.
Map intel
Route anchors for this guide
Hammerhead Test Route
Controlled threat-test anchor for Hammerhead spacing, flare response, and retreat practice.
Player use
Use this only as an observation edge; do not bring rare inventory into a tactic test.
Route hint
Approach, test one reaction, retreat, repair, and write the result before changing tools.
Creature threat matrix
Behavior cue, safe action, and route impact
Creature pages need more than names. This matrix tells players when to observe, avoid, scan from cover, or abort the route.
Hammerhead
Behavior cue
Vehicle interest or repeated approach pattern
Safe action
Keep the Tadpole pointed out, test mitigation once, then leave.
Route impact
Makes vehicle parking and noisy route choices matter.
Retest reason
Hotfix notes already mention behavior changes.
Field checklist
Before leaving base
Flares
Primary action
Approach suspected Hammerhead routes with a visible exit line.
Turn back when
Assuming a previous patch tactic still works.
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.
Leviathan-class wildlife
High-danger creature tier that shapes scouting, avoidance, and retreat routes.
Found in: Official Steam store description references towering Leviathans.
Action: Scan from safety, keep a return vector, and treat unknown silhouettes as route blockers.
Shiver Leviathan
Named Leviathan-class encounter that should be handled as a high-risk scouting target.
Found in: Third-party Leviathan guides and videos supplied for content research.
Action: Scout from the edge of the reported biome and keep the Tadpole pointed toward open water.
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.
Collector Leviathan
Named Leviathan-class encounter tracked by community location guides.
Found in: Third-party Leviathan guides and videos supplied for content research.
Action: Treat route reports as corridors, verify in the current build, and leave after the first safe observation.
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.
Thrill of the Deep
Official media for dangerous routes, predator awareness, and major threat pages.
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.
Threat read
Use creature posture and route pressure to decide whether Hammerhead contact is safe to observe.
Scan subject
Scan windows only matter when the escape line remains obvious.
Large creature lane
Large-creature lanes should be crossed with a destination, not explored as open water.
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.
Approach suspected Hammerhead routes with a visible exit line.
Keep the Tadpole parked where terrain does not trap a fast turn.
Test flare attraction only with enough oxygen and distance to leave.
Record whether the creature targets player, vehicle, or route noise.
Recheck behavior after every Early Access hotfix before writing fixed tactics.
Guide notes
Why Hammerhead tactics need version notes
Official hotfix notes have already changed how Hammerheads interact with Tadpoles and flares. This page therefore tracks behavior patterns instead of pretending the final tactic is settled.
Safe test pattern
Mark the creature, back out, prepare flare and tool tests, then return with one variable at a time. If the route turns chaotic, leave and update the field note instead of forcing a scan.
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.
Assuming a previous patch tactic still works.
Leaving an unpiloted Tadpole in a high-traffic threat corridor.
Testing mitigation tools with no escape margin.
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.