A Low-Spoiler Field Checklist for Subnautica 2 Exploration

Early Access survival games reward preparation, but they also punish over-planning around information that may change in the next patch. For a first Subnautica 2 session, the useful goal is not to memorize every location. It is to build a repeatable field routine that helps you explore, record what matters, and recover when a route becomes unsafe.

1. Start each trip with one question

Give every outing a single objective: confirm a resource area, check a blueprint lead, scout a safe vehicle path, or verify whether an old route still works. A focused trip is easier to evaluate than an open-ended swim. If the objective fails, you still learn exactly which assumption needs updating.

2. Record landmarks before coordinates

Coordinates are precise, but visual landmarks are easier to use when you are moving quickly. Note the biome transition, nearby wreckage, depth change, light conditions, and the direction back to a known base. Add coordinates after that. This produces notes that remain useful even if a marker or route shifts during Early Access.

3. Separate confirmed facts from route ideas

Keep three short lists: confirmed locations, provisional leads, and patch-sensitive observations. Do not promote a rumor or a single failed attempt into a firm rule. When checking a community reference such as the Subnautica 2 Wiki, compare its map, guides, update notes, and data pages against what you can reproduce in your current build.

4. Build a return-safe inventory

Reserve capacity for the trip home. Carry the essentials for navigation and recovery, but leave enough space to bring back the item that motivated the trip. A full inventory at departure often turns useful discoveries into awkward choices. A small buffer also helps when an unexpected detour reveals a rarer material.

5. Review the route after every patch

Patch notes should trigger a short recheck, not a complete restart. Revisit the assumptions most likely to break: resource placement, blueprint requirements, creature behavior, collision problems, and vehicle access. Mark old notes as historical instead of deleting them; the comparison can explain why two guides disagree.

A compact field-note template

• Objective: one thing to confirm.
• Start point: a recognizable base or landmark.
• Route: direction, depth, transitions, and hazards.
• Evidence: coordinates, screenshots, or repeat observations.
• Version: the build or patch when you checked it.
• Confidence: confirmed, provisional, or needs recheck.

This method keeps exploration low-spoiler while still producing notes another player can follow. More importantly, it treats Early Access knowledge as something to verify and maintain, rather than a static checklist copied from an older build.