Most "secret commands" are not hidden cheats. They are usually contextual commands, upgrade-gated commands, or community/modded parser extensions. This page helps you separate reliable workflows from rumor-driven command lists.
These are command patterns players often call "secret." Reliability depends on state, upgrades, and whether your lobby is vanilla or modded.
Many players forget prompt-state commands and assume the terminal is bugged when actions do not execute.
How to use: Use immediately after ROUTE, BUY, or other prompt-driven actions.
Reliability: High when prompt is active.
Door controls are invisible in some states, so players often think these are hidden commands.
How to use: Enter DOORS state first, then run OPEN or CLOSE with team callouts.
Reliability: Medium; depends on current state and ship setup.
These commands appear only when specific upgrades are installed, so they can look like secret unlocks.
How to use: Install the relevant teleporter system, then activate from ship terminal with role coordination.
Reliability: High once upgrade is present.
Player-target syntax differs by lobby behavior, so many crews only discover this through trial and error.
How to use: Use on monitor context to cycle or target teammates during support play.
Reliability: Medium; parser details vary.
Some versions expose bestiary via UI flow rather than terminal text, creating confusion.
How to use: Test with HELP in your current build and use if listed.
Reliability: Low to medium across versions.
These are often shared in community clips as hidden tricks, but most are mod-driven features.
How to use: Treat as optional. Confirm command support in your modpack docs.
Reliability: Low in vanilla, high in matching modded setups.
Most so-called secret commands are actually normal commands that only appear in specific terminal states.
Teleporter-related actions feel like hidden content because command availability changes with upgrade progression.
Clip-worthy shortcuts often spread faster than their compatibility notes. Always test with HELP before relying on them.
Keep your baseline command source in the full terminal commands list and use the terminal guide for stable shorthand patterns.
A command may move between always-visible and contextual-visible behavior across updates.
Even in the same version, terminal state and installed upgrades change which commands execute.
Abbreviations and extra commands may work perfectly in one modpack and fail completely in another.
Older videos or posts may show commands that no longer exist, or that were never vanilla commands.
There is no stable, officially documented list of hidden cheat-style vanilla commands. Most 'secret' behavior is contextual, upgrade-gated, or modded.
Their clip may come from another patch, a different lobby state, or a modded environment with extra parser support.
Use HELP in your current terminal context, test in a low-risk moment, and document whether the command appears and executes consistently.
Treat them as hypotheses. Test locally first, then add only repeatable commands to your team standard list.
Yes. Understanding contextual and upgrade-gated commands prevents many 'terminal is broken' moments in vanilla runs.