Subnautica 2 console commands and map safety
Short answer: Use console-command information conservatively during Early Access. This page does not invent command lists; it explains how to keep coordinate testing separate from normal map route planning and sends players back to source-backed marker data.
Use the page as a route decision, not a thin article
1. Do not treat commands as route truth
Commands may help testing, but the user-facing route should still rely on marker source, depth, biome, and confidence.
2. Keep normal map tasks first
Search a marker, read its evidence, then decide whether a debug/test path is appropriate.
3. Avoid unsupported syntax claims
Early Access command details can change. This guide intentionally avoids publishing unverifiable command tables.
Source-backed cards and internal map actions
Coordinate safety
Coordinates are shown with precision and source context so players can test route clues without assuming exact guarantees.
Map evidence first
The map shows source, confidence, update date, and local route hints before any external debugging workflow.
No fake command list
A thin command list without verified source depth would be worse than no page; this page marks that boundary explicitly.
Public-reference source cards
Coordinates and marker details are the stable site-side evidence.
confidence: public_reference · last_updated: 2026-05-20
Resource route testing should still return to source-backed map markers.
confidence: public_reference · last_updated: 2026-05-20
Subnautica2Maps is fan-made and unaffiliated. It does not rehost official screenshots, logos, key art, copied maps, copied guide images, or competitor assets. YouTube/video references, when present, must remain click-to-load/source-card only.
Subnautica 2 console commands and map safety questions
Does this page list every Subnautica 2 console command?
No. It avoids unsupported command tables and focuses on safe map-coordinate usage.
Can console commands replace the map?
No. Use source-backed map markers for normal player tasks; command workflows are optional and version-sensitive.
Why is this in the sitemap?
The page answers command-intent safely by setting boundaries, linking to coordinate guidance, and avoiding fabricated command syntax.