Subnautica 2 Console Commands Guide

Console commands can be useful when you are testing, recording, building creatively, or recovering from Early Access bugs. They can also ruin the survival loop if you use them before you understand the game.

How to use this console command guide

This page is built for players, not for database browsing. Use it when you are in the middle of a session and need a clear decision about when to use cheats and debug tools safely. The first thing to read is the quick answer, because it tells you what the page is trying to solve. After that, move through the route notes, safety notes, and update notes before you commit to a long dive.

The most important habit in Subnautica 2 is not memorizing every object. It is learning how to prepare before entering a new area. A good console command guide should help you decide what to bring, where to start, when to return, and what to do if the world looks different from the description.

• Read the quick answer before scanning the whole page.
• Check the Last Updated line before following a location-heavy route.
• Bring more oxygen and storage than the minimum recommendation.
• Use related pages when a route mentions resources, fragments, vehicles, or platforms.

What to check before you leave base

Before following any debug session, pause at your base and check your equipment. Make sure you have enough oxygen capacity for the depth you are attempting, enough food and water for the return trip, and enough inventory space to make the trip worthwhile. Players often fail not because the route is difficult, but because they leave with full bags, no spare planning, and no idea where to turn around.

If the guide mentions a deeper biome, a dangerous creature, or an unfamiliar fragment area, treat the trip as a scouting dive first. Your first goal is to understand the route, not to collect everything in one run. Mark useful landmarks, memorize safe surfaces, and return with a better plan.

• Empty your inventory before a resource run.
• Bring only tools that support the goal of the trip.
• Turn back earlier than you think you need to.
• Do not chase unknown sounds into deeper water unless that is the purpose of the route.

How this connects to progression

Console command decisions are progression decisions. A player who knows where to go next spends less time circling the same safe area and more time unlocking meaningful tools, vehicles, upgrades, and base options. The goal is not to remove discovery; the goal is to reduce frustration when the game stops giving obvious direction.

Commands are best used as tools for testing or recovery, not as a replacement for exploration, planning, and progression. In practice, you should connect every guide page to the next action. If you find a resource, ask what it crafts. If you scan a fragment, ask what it unlocks. If you reach a biome, ask whether it is a good base location or only a temporary expedition zone.

Common mistakes

The most common mistake is trying to solve several problems in one dive. Players leave to look for one item, see a new area, chase a creature, scan half a fragment, fill the inventory with random materials, and then realize they have no oxygen path back. A good run has one main target and one optional bonus.

Another mistake is trusting old information without checking the build note. Subnautica 2 is actively changing, and a page that was correct before a patch may need adjustment. That is why every major Sub2Wiki content page includes a Last Updated field and an Early Access note.

• Do not treat every glowing object as the goal.
• Do not enter a new biome with a full inventory.
• Do not ignore sound cues or creature behavior.
• Do not assume every older video still matches the current build.

How to recover if the guide does not match your save

If a location or step does not match your save, slow down and look for the reason before assuming you are lost. Early Access updates can move content, existing saves can behave differently after patches, and some routes are easier to follow from a different landmark than the one you first used.

The best recovery method is to return to a known safe point, reread the route from the beginning, and compare the goal with nearby landmarks instead of forcing the same path again. If the page has a patch note section, read it carefully. If the issue looks like a real change, use the contact page to report it so the guide can be updated.

Solo and Co-op Notes

Solo players should plan for safety and return paths. Co-op players can take more ambitious routes, but they should still organize roles before leaving the base. A simple four-player plan works well: one player scouts, one gathers common materials, one scans fragments and creatures, and one stays responsible for storage, crafting, and route calls. That division prevents the common co-op mistake where everyone swims to the same glowing object, nobody watches oxygen, and the team returns with four copies of the same material but none of the item they actually needed. If you play with friends, use guide pages as shared checklists. Read the quick answer together, agree on the target, and decide who carries what.

Early Access Version Notes

Because the game is in Early Access, this page should be reread after major updates. If a route no longer works, the best response is not to assume the guide is useless; it may simply need a version note. Check whether the page has a newer Last Updated line, whether the official patch notes mention changed resources, and whether your current save was created before or after a large update. For a wiki about a living game, freshness is part of accuracy. Sub2Wiki pages are structured so that changed locations, changed recipes, changed platform notes, and changed progression steps can be updated without rewriting the entire guide.

Related Sub2Wiki Pages