Stellaris Console Commands and Cheats List (2026)

The Stellaris console is best treated as a testing rig. It can give resources, reveal hidden IDs, finish research, build fleets instantly, switch empires, trigger events, and repair broken targets, but it becomes unreliable the moment you stop thinking about scope. Good console use changes one variable, checks the result, and leaves you with a save you can still understand.

The Console Mental Model

Do not begin by memorizing a giant alphabetical list. Begin by sorting commands by the kind of thing they change. Once you know the category, the syntax and the risk make sense.

Command type	Examples	Mental model
Value commands	cash 5000, minerals 5000, unity 5000	Add or remove a number from a stored value. Many amount commands also accept negative numbers.
Broad fill commands	max_resources	Skip individual resources and fill storage. Best for sandbox construction, bad for testing a real economy.
Toggle commands	instant_build, ai, debugtooltip, intel	Run once to turn on, run again to turn off. These are the easiest commands to forget.
Target commands	own, planet_class pc_gaia, planet_size 25	Act on the selected planet, fleet, starbase, or object. Select the target before typing.
ID commands	play 2, add_trait_leader [leader id] [trait id]	Need a hidden ID. Use debugtooltip before you touch them.
Script commands	event crisis.10, effect add_deposit = d_arid_highlands	Call the game's scripts directly. Powerful, but easiest to overdo.

That split is the whole game. A resource command is usually safe in a throwaway save. A target command is safe only if the right object is selected. A toggle is safe only if you remember to toggle it back. A script command is safe only when you know the chain you are entering.

The console is also not a private "player only" layer by default. Some commands change the player empire, some change a selected target, and some change simulation rules for everyone. instant_build is the classic trap: if the galaxy is unpaused while it is active, AI empires can also finish queued construction instantly. Pause before toggles, and turn them off before letting time run.

Open the Console

The console works in non-Ironman PC games. If you made the save as Ironman, console commands are the wrong tool for that file. Press Escape and look at the save controls if you are unsure: an Ironman save advertises that it is locked down for achievements. You cannot rescue an Ironman campaign by finding a better command; start or load a normal save instead.

On a US keyboard, the console key is normally ` or ~, just left of the top-row 1 key and below Escape. Other layouts can use Shift+2, ALT+2+1, Shift+3, ^, §, °, ², or Shift+Alt+C. Press the same key again to close the console.

Once the text box is open, type the command and press Enter. The up and down arrow keys move through command history, which is useful when you are repeating the same test with different numbers. If a command does nothing, solve the basic input problem first: non-Ironman save, PC version, correct keyboard shortcut, exact spelling, correct target, and a clean duplicate save if mods are involved.

Use Help and Debugtooltip

help is the command that keeps this whole subject sane. Type help to print available commands. Type help survey, help own, help resource, or help research_all_technologies to see a specific command's syntax inside your game. That matters because Stellaris has years of patches, DLC, and mods behind it, and the console itself can tell you what your install accepts.

debugtooltip is the second command to learn. It toggles extra hover information and exposes the internal IDs used by empire, planet, species, leader, fleet, ship, pop, and event testing commands. Use it before play, own, trait commands, pop commands, and anything that points at a specific object. Run debugtooltip again when you are done so normal tooltips are readable.

You need	How to get it	Why it matters
Command syntax	help [command]	Prevents reversed arguments, missing IDs, and stale copy-paste commands.
Empire ID	Turn on debugtooltip and hover the empire or interface entry.	Needed for play, diplomacy tests, and empire-specific commands.
Planet or object ID	Select the body or use debugtooltip while hovering it.	Needed when own, planet_size, or scripted effects are not using the selected target.
Species or pop ID	Use debugtooltip in population views; add_pops with no arguments can also list species IDs.	Needed for population and species trait commands.
Leader ID	Use debugtooltip on the leader entry.	Needed before adding, removing, or testing leader traits.
Resource or class key	Use command help, autocomplete, or a known in-game ID such as consumer_goods or pc_gaia.	String keys must be exact.

The habit is target first, command second. When beginners break saves with the console, it is usually because they skipped the ID step, not because the command itself was complicated. For a deeper ID workflow, use the Stellaris debugtooltip and IDs guide.

Safe Testing Workflow

Console commands are strongest when you use them like a lab setup. Decide the question first, build the minimum scenario, save, then run the test. If you unlock everything and spawn half the galaxy at once, you may have fun, but you will not learn which mechanic caused the result.

1. Start from a duplicate non-Ironman save. Keep your real campaign untouched.
2. Pause before toggles. This prevents the AI from taking advantage of galaxy-wide tools while you work.
3. Run help and debugtooltip. Confirm syntax and target IDs instead of guessing.
4. Add only the setup you need. For a fleet test, you need tech, resources, ships, and vision. You do not need every planet edited.
5. Save immediately before the experiment. That gives you a reset point for repeat runs.
6. Run the test once and observe. Do not stack extra commands during the result.
7. Change one variable and reload. This is how you compare weapon layouts, crises, diplomacy paths, or economy starts.
8. Turn toggles off or reload the setup save. If you cannot remember whether a toggle is active, re-run it or return to the clean save.

A clean fleet-combat setup looks like this: pause, run research_all_technologies 1, toggle instant_build, run max_resources, toggle ai off, build the fleets, save, then use attackallfleets when you are ready for them to fight. The save point is what makes the test repeatable; without it you are only watching one noisy battle.

For economy tests, resist max_resources unless storage itself is the thing you want. Give a measured amount with cash, minerals, alloys, or resource, then let the month tick and read the income panel. Stellaris is an economy game before it is a fleet game; testing with infinite everything hides the bottleneck you came to study.

Best Stellaris Console Commands

These are the commands worth learning first. They cover discovery, resources, research, visibility, construction, targets, diplomacy, and fleet tests.

Command	Effect	Best use
help	Shows command help.	Run help own or help resource before using commands with arguments.
debugtooltip	Toggles hidden tooltip data.	Find empire, planet, species, leader, pop, ship, and fleet IDs.
max_resources	Fills resource storage.	Fast sandbox setup when scarcity is not the test.
cash, minerals, food, alloys	Adds basic resources.	Use exact amounts to test economy pressure.
influence, unity	Adds political resources.	Claims, diplomacy, traditions, edicts, and leader tests.
physics, society, engineering	Adds stored research points.	Speed research without unlocking the whole tree.
resource	Adds a specific resource by ID.	resource consumer_goods 1000 for targeted stockpiles.
finish_research, finish_special_projects	Completes active research or projects.	Advance one queue without flattening progression.
research_all_technologies	Researches non-repeatable technologies.	Late-game ship, crisis, and megastructure testing.
instant_build	Toggles instant construction and upgrades.	Build test fleets, planets, and starbases while paused.
survey, communications, intel	Reveals surveys, contacts, and map vision.	Remove exploration delay from a test galaxy.
observe, play	Spectates or switches controlled empire.	Watch AI behavior or inspect another empire.
own	Takes selected fleet, starbase, or planet.	Repair ownership or build custom test setups.
attackallfleets	Makes player fleets target other fleets.	Run same-empire fleet combat tests.
debug_yesmen	Makes AI empires accept player proposals.	Diplomacy experiments and stuck negotiation fixes.
ai	Toggles AI behavior.	Freeze the galaxy while setting up scenarios.
event	Triggers an event by ID.	Run scripted chains only from a saved test state.

If you only remember five commands, remember help, debugtooltip, max_resources, instant_build, and own. Those cover discovery, IDs, broad resources, construction, and target control.

Resources, Research, and Instant Build

Resource commands change stockpiles, not income. If your empire is losing 200 Energy Credits per month and you type cash 5000, you bought time; you did not fix the deficit. For economy learning, add a limited amount and watch the monthly tick. For pure sandbox building, use max_resources.

Need	Command	Principle
Energy Credits	cash 5000	Use for maintenance, market tests, and stabilizing a save.
Minerals	minerals 5000	Use for planet and station buildouts.
Food	food 5000	Useful for biological empires and market tests.
Alloys	alloys 10000	The fleet and megastructure shortcut.
Influence	influence 500	Use for claims, expansion, diplomacy, and galactic actions.
Unity	unity 5000	Use for traditions, edicts, and leader-heavy tests.
Research points	physics 5000, society 5000, engineering 5000	Add points without choosing a specific technology.
Specific resource	resource consumer_goods 1000	Use the exact resource key when the simple command is not enough.
Everything	max_resources	Use when the question is about building or combat, not scarcity.

For research, choose the narrowest command that answers the question. finish_research completes current research and preserves the rest of the tree. physics, society, and engineering add points while still making you pick technologies. research_all_technologies wipes out normal tech progression, which is useful for late-game ship tests and poor for learning tech pacing.

research_all_technologies 1 is the quick setup for tests that need space-creature or crisis-related technologies. If you also need repeatables, run help research_all_technologies and follow the parameter order it prints.

instant_build is a toggle, not a one-shot resource button. Pause, run it, queue or finish the construction you need, then run it again before unpausing. Pair it with max_resources for large tests. If storage capacity changes while it is active, read the resource tooltip; the UI will show the cap in your save.

IDs, Targets, and Planets

The console usually targets either the object you selected or the ID you typed. Learn which one the command expects before pressing Enter.

Job	Command	How to use it safely
Take a planet, fleet, or starbase	own	Select the target first. If taking an enemy planet, take the relevant starbase too so system control matches your intent.
Switch empire	play [empire id]	Find the empire ID with debugtooltip. Save first, because the empire you leave can be AI-controlled if time runs.
Observer mode	observe	Return with play [empire id] after confirming your original empire's ID.
Change planet class or size	planet_class [planet class id], planet_size [size]	Select the body first. Use class keys such as pc_gaia only in a test save.
Add pops	grow_pops [amount], add_pops [species id] [planet id], build_pops [amount]	Confirm planet and species IDs; large growth tests still need game time to settle.
Colonize selected body	colonize [pop id]	Use a valid pop ID and avoid uncolonizable targets unless testing edge cases.
Edit traits	add_trait_leader, remove_trait_leader, add_trait_species, remove_trait_species	Confirm the leader or species ID first; these changes can affect many entities.

Planet commands are powerful because one planet holds districts, deposits, pops, jobs, buildings, modifiers, ownership, colony state, and sometimes event state. planet_class changes what the body is. planet_size changes how much room it has. effect add_deposit = [deposit id] changes what it can exploit. Those are different layers.

The safe planet-editing pattern is: select the planet, run debugtooltip, write down the ID and current class, make one change, reopen the planet view, then let the game tick. If the district count, habitability, jobs, or colony state looks wrong, reload instead of stacking more edits.

Galaxy, Fleet, and Crisis Testing

For galaxy-level testing, the goal is visibility and control. survey removes survey delay, communications opens contact with empires, and intel shows the map. Use them together when you want to watch AI wars, crisis movement, diplomacy, or a changed start.

Scenario	Command chain	Why this chain works
Reveal the test galaxy	survey -> communications -> intel	Removes exploration work, enables diplomacy, and gives map vision.
Freeze AI while setting up	ai	Stops AI behavior from changing the scenario while you place ships, planets, or diplomacy.
Build late-game fleets	research_all_technologies 1 -> instant_build -> max_resources	Unlocks designs, removes build time, and fills stockpiles.
Fight two fleets from one empire	attackallfleets	Turns player fleets hostile toward other fleets, so you do not need a second empire for a clean combat test.
Watch AI behavior	observe plus intel	Lets the galaxy run without your orders while staying visible.
Test diplomacy	communications plus debug_yesmen	Contacts the empires and forces acceptance so you can isolate the diplomatic mechanic.
Trigger scripted events	event [event id]	Calls an event directly. Use a saved setup so you can rerun or abandon the chain.

Fleet tests should be repeatable. Build two fleets, place them in a quiet system, save, then start the fight. If you change weapons, admirals, repeatable techs, auras, or ship counts, reload and change only that variable.

Crisis events are script chains, not simple resource cheats. Start the natural chain when you want campaign-like pacing and jump directly only for an immediate stress test. Common examples are event crisis.10 for the Prethoryn chain, event crisis.1000 for the Unbidden, event crisis.2005 for the Contingency chain, and event crisis.2000 for a more direct Contingency spawn. Do not fire both Contingency routes unless duplicate behavior is the experiment.

The same logic applies to story events: start the chain for normal pacing, jump later only for a targeted test, and save first because event chains set hidden flags.

FAQ

Next Reads

• Stellaris Debugtooltip and IDs Guide - the clean way to find empire, planet, species, leader, and pop IDs.
• Stellaris Console Commands Not Working - fixes for Ironman, keyboard layouts, targeting, and command syntax.
• Stellaris IDs List - common IDs and keys for command testing.
• Stellaris Economy Guide - understand the economy before you hide its problems with resources.
• Stellaris Ship Design Guide - build better fleet tests once the console gives you instant ships.
• Stellaris Beginner Guide - the non-cheat foundation for expansion, economy, and war.