What the site is trying to do
Answer the next useful Subnautica 2 question quickly instead of pushing readers into a giant archive first, with separate rooms for beginner, building, crafting, progress, and troubleshooting needs.
Site overview
Why this guide site is built for quick answers, not long scrolls.
Subnautica 2 Guide Hub is designed to help players solve specific Subnautica 2 problems fast. The goal is simple: one clear answer per page, strong internal links, and a structure that can scale as the game grows.
What makes this site trustworthy
The site tries to behave like a maintained guide project: public policy pages, visible update notes, open correction paths, and clear source boundaries between official facts and fan-made gameplay guidance. If you want to challenge a page, use the correction path or see Community.
Player-first start
Built for players who need one calm first answer
The site works best when it turns early-game panic into one safe route and one clear next click.
Useful systems
Built to connect materials, routes, and upgrades cleanly
It should feel like a live game guide site, not a pile of disconnected articles or filler pages.
Live support
Built to stay useful as co-op and patch-sensitive questions grow
The structure is there to keep pages fresh and make the next step clear as the game changes.
How guides are supposed to read
Each page should answer one main problem near the top, say when the advice is risky, and point to one clean next step.
Who this is built for
Players who search while they play, usually on mobile or with the game open, and need something practical fast.
Why the structure stays strict
If the site stops narrowing decisions and starts sounding like filler, it becomes slower, harder to trust, and less useful mid-run.
What we are updating
What the team is focused on right now.
Core entry pages now have clearer roles
Homepage, Guides, Database, Tools, News, and Early Access now describe their jobs more clearly so readers can choose the right room faster.
Core pages show better fit signals
More guide pages now tell readers whether the advice fits first sessions, route expansion, base timing, or co-op use.
Patch-sensitive topics stay near the front
Routes, resources, dangerous zones, and multiplayer rules get checked sooner than broad evergreen advice.
Reader reports are meant to be practical
The fastest fixes come from one guide URL, one changed section, one patch context, and one proof screenshot.
Reviewed Wednesday, September 2, 2026
Homepage routes tightened
Guide-fit labels expanded
Corrections open
What gets checked first
Route-sensitive guides, update-sensitive pages, and the pages readers reach most often from search.
What the team tracks
Reviewed dates, media fit, correction requests, and whether a page still points to the next useful answer.
What should feel current
The homepage, resources hub, map hub, update tracker, and co-op pages should feel current, not frozen.
Independence and safety
What this site is, and what it deliberately does not provide.
Subnautica 2 Guide Hub is an independent fan-made guide site. It is not an official Unknown Worlds or Krafton website, and official release status, patch notes, trailers, store details, and official announcements should always be checked through official channels first.
The site is built for guide reading only. It does not host or point readers toward unauthorized files, unsafe account services, restricted commercial offers, mature-content material, or misleading install pages. If a page links outside the site, the link should help a reader verify official context or continue practical gameplay research.
| Trust area | Site rule | Why it matters for readers |
|---|---|---|
| Official facts | Use official pages first for release dates, update names, and confirmed feature changes. | Players should not have to guess whether a date or patch claim is invented. |
| Gameplay advice | Write route and progression help as practical guidance, not permanent canon. | Early Access balance and map details can change, so risky advice needs review labels. |
| Content boundaries | Keep the site focused on articles, checklists, maps, and safe external verification links. | Readers should never be pushed toward unsafe files, fake unlocks, or unrelated offers. |
Editorial identity
The site uses one transparent review team instead of invented staff names.
Public guide pages are attributed to Subnautica 2 Guide Hub Team. That label is used because the site should not pretend to have named staff writers unless those contributors are real, verified, and meant to be shown publicly.
The review team is responsible for page dates, patch-sensitivity labels, correction handling, and source-order notes. Readers can challenge a page through the correction path or review the full editorial policy.
About the team label
The site uses one public team label so it does not invent named writers or fake expert profiles that cannot be verified.
How pages get challenged
Readers can challenge route, resource, co-op, or visual advice through the correction path, reader reports, or the public community hub.
Where maintenance shows up
Changes should appear in update notes, review dates, route warnings, and better next-step links instead of silent cosmetic edits only.
Originality and source boundaries
What is original here, and what is official-source context.
The original work on this site is the player-facing judgment: route order, stop rules, material priority, co-op role splits, base timing, comparison tables, checklists, and next-step links. Confirmed facts such as release timing, official feature names, trailers, and publisher statements should point back to official channels instead of being rewritten as if the site discovered them independently.
| Content layer | How readers should understand it | Trust signal |
|---|---|---|
| Original guide judgment | Practical advice shaped for one player problem, such as what to do first, where to stop, or what to build next. | Quick answer, scenario table, checklist, and next useful link. |
| Official context | Release status, naming, and announced features are treated as externally confirmed facts. | Official-source wording and links from the news or Early Access pages. |
| Reader-tested updates | Reports can trigger retesting, tighter warnings, or clearer route boundaries. | Visible review date, maintenance note, and correction path. |
Visual-first guide system
The site now uses diagrams to help readers scan faster.
High-quality guide sites help players scan before they read. These visual previews turn route, resource, and update questions into clearer guide cards instead of long text walls.
Real player situations
These are the gameplay moments the site is actually trying to support.
A guide brand looks more real when the about page points back to visible player situations, not just abstract editorial language.
Exploration support
Players need route confidence before they need more words.
That is why route, landmark, and danger content is structured around narrower next moves instead of broad archive browsing.
Open route hub
Risk support
Patch-sensitive and higher-risk pages need clearer trust boundaries.
The site is meant to say when advice is still useful, when it needs rechecking, and when the safer answer is to back up into a calmer lane.
Open update tracker
Session support
The best pages remove wasted session time, especially in co-op.
That means clearer role splits, better host guidance, and links that move readers into the next useful question quickly.
Open co-op guideEditorial Standards
How each guide is supposed to earn trust
Update Workflow
How the site stays useful after launch
1. Watch high-intent player questions
Resource routes, oxygen pressure, co-op rules, and base systems usually surface first.
2. Refresh winner pages first
The most useful evergreen pages get reviewed before long-tail experiments.
3. Keep the archive connected
Every guide should point into the next useful lane so readers can keep moving without re-searching.
How We Update Guides
What gets reviewed first when the game changes
- High-risk pages first: map routes, dangerous zones, rare materials, and co-op behavior.
- Then practical systems: scanner upgrades, base power, storage flow, and vehicle routes.
- Then broader evergreen pages: first-hour priorities, route planning principles, and glossary-style help.
Guide Trust Signals
How readers can judge whether a page is likely current
- Core guides show a `Last reviewed` date and patch sensitivity level.
- The Update Tracker ranks which clusters are most likely to need review after patches.
- Correction requests are encouraged when route safety, unlock paths, or co-op behavior no longer match the live build.
- Map coordinates should only go live after a proof bundle and version context are captured.
Source Hierarchy
How information is weighted before it becomes guide advice
- Official Unknown Worlds posts, trailers, dev vlogs, showcases, and patch notes come first for names, dates, systems, and confirmed feature changes.
- Practical route advice is treated as gameplay guidance, not permanent canon, and should be revisited when map layout, creature pressure, or balance changes.
- Reader corrections are used to flag pages that need retesting, especially for co-op behavior, resource routes, and dangerous-zone safety.
Uncertainty Labels
What readers should double-check after patches
- Low sensitivity: broad beginner principles and general preparation advice.
- Medium sensitivity: upgrade order, base priority, and route efficiency advice.
- High sensitivity: map routes, rare materials, creature danger, and multiplayer save behavior.
Editorial Review Method
How we separate official facts from practical route advice.
Who This Helps
Built for players who search while they play
- New players who need a calmer first-hour route.
- Mid-run readers who only want the missing material, system, or co-op answer.
- Returning players who want to see what changed without reading a full patch archive.
Trust Signals In Place
The site now shows maintenance more clearly
- Higher-use pages now mix real gameplay screenshots with diagrams where route advice is easiest to misunderstand.
- Guide pages now show review date, patch sensitivity, build cue, and platform cue so readers can judge whether the advice still fits.
- Correction requests now ask for page URL, patch or build context, platform used, and proof so risky pages can be rechecked faster.
About help
What readers should understand before trusting the site structure.
This page should explain the site\'s purpose fast: answer one player problem, show where the next page lives, and make the review trail visible enough that the site feels maintained instead of assembled.
- The site is built for practical problem solving.
- Public trust pages explain how corrections and media are handled.
- Readers should use the narrowest page that solves the current blocker.
- Thinking the site is official because the pages are polished.
- Using About as a replacement for policy, contact, or editorial detail.
- Skipping the next-step page after finding the main answer.
- Open Editorial Policy for source and correction rules.
- Open Contact for direct reports or partnerships.
- Open Version History to see how the site has changed.