Subnautica 2 Guide Hub Guides, Map, Database, Tools

Shelf-style database

Base pages should answer why the base helps, not just how it looks.

Use this shelf when the base topic is named and the real question is timing, location value, build order, or cleanup priority.

Base entries

Use the row that matches the base question.

Base topic Main value When it matters most Best next page
Build now or wait Prevents premature building When the base sounds useful but the run still may be too fragile Build now or wait
First base location Turns home into a route anchor When the site choice matters more than room count First base location
Build order Places useful pieces before decorative ones When the base exists in theory, but not yet in practical form Build order
Cleanup Fixes clutter, power, and flow after the first build When the base works but still wastes time After first base

Base shelf notes

What this base shelf should settle before the player builds.

The base shelf should help players decide whether a base will remove travel or storage friction. If the page does not make the usefulness obvious, the answer is probably to wait and keep moving.

Quick answer
  • Build only when the base will save time in the next few runs.
  • Pick a safe site with useful returns.
  • Place storage and power before decorative expansion.
Common mistakes
  • Building a base before knowing what it is supposed to fix.
  • Letting layout style outrun function.
  • Expanding before the first base actually feels useful.

Base value check

What the shelf should decide after the base topic is already named.

A base page should tell the player whether the next base really saves time, whether the current site is the right one, and whether the build order or cleanup is the actual next task.

Quick answer
  • Use the base only when it shortens the loop.
  • Pick storage, power, and layout before extra rooms.
  • Return to route or vehicle planning if the base does not change anything useful.
Common mistakes
  • Building a large base because the topic sounds important.
  • Ignoring whether the site is actually useful for future trips.
  • Expanding before the first build has earned its keep.

Base database depth

What the base shelf should answer before the reader compares locations.

Base database pages should show why one site is useful, what the build needs, and what kind of player problem it solves. That keeps the shelf useful as a decision desk rather than a decor gallery.

Quick answer
  • Show the practical role of the base before layout details.
  • Compare location value against travel savings and safety.
  • Link to the planner or building page when the reader is ready to commit.
Common mistakes
  • Describing the base without saying what problem it solves.
  • Leaving the reader with a site name but no reason to pick it.
  • Failing to hand off to the build or planner page.

Base shelf triage

How to tell which base page should be opened next.

The base shelf has value when it sends the reader to the correct kind of help: timing, location, build order, or cleanup. That prevents one broad database page from pretending to be every base guide at once.

Base questionBest next answerWhy
You are not sure whether to build yetBuild base now or waitIt protects materials from a premature build.
The location is the hard choiceFirst base locationIt ties site choice to route value.
The first base exists but feels messyMessy first base fixIt fixes storage, power, and movement friction.
The base is useful but expansion is unclearBase PlannerIt keeps expansion tied to practical payoff.

Base shelf rule

Use the shelf to answer whether the base still saves time.

A base entry should say if the location pays off, if the build is too early, and whether the next page is planning or cleanup. That makes the shelf feel like a decision helper instead of a label list.

Timing

Use when the question is build now or wait.

Location

Use when the right site is the real blocker.

Cleanup

Use when the base exists but the layout still wastes time.