Stellaris Console Commands Not Working

The Stellaris console is not a mystery, and it is not broken. It is a debug interface with four strict rules, and nearly every failure you will ever hit is one of those rules doing its job. Most troubleshooting advice gets this backwards: it hands you a stack of commands and hopes you notice the fix somewhere in the middle. This page works the other way around. Learn the rules and you can diagnose any failure yourself — on any version, with any mod list, without memorizing a single command.

That matters more here than in most games, because the console doubles as a testing lab. A fleet matchup that would be near-impossible to set up by hand takes about two minutes with commands. Spawning a crisis, flipping an empire's diplomacy, resizing a planet, watching three endgame crises fight each other from observer mode — this is lightweight modding, live, on a running save. The same strictness that makes commands fail silently is what makes them precise once you speak the language.

How the Console Thinks: Four Rules

Every section below is one of these rules expanded. Read them once and the rest of the page becomes a reference instead of a riddle.

Rule one: the console is a debug layer, not a game feature. It exists only in non-Ironman single-player on PC. Ironman saves are cryptographically checksummed, and because any console command would alter that checksum and void achievement eligibility, Paradox does not merely hide the console in Ironman — the engine never registers the keybind in the first place. There is no setting to flip and no launch trick that restores it. If the save is Ironman, "the console will not open" is not a bug to solve. It is the answer.

Rule two: the parser reads literally. The console speaks the game's internal language, not the interface's. Command names must be exact, IDs must carry their prefix, and arguments must come in the right order. research_technology tech_titans works; research_technology titans is dropped without ceremony. The one mercy: many commands accept both the spaced and the underscored form, and Tab completion in your own build always shows the exact spelling it expects. Type whichever your fingers prefer.

Rule three: half the commands are toggles, and many of the rest need a target. These are the two great failure families. "It stopped working" almost always means a toggle got toggled off by the same keypress that turned it on. "Nothing happened" almost always means a scoped command — one that acts on the planet, fleet, or empire under your cursor — had nothing selected. Neither produces an error. Both read exactly like a bug.

Rule four: the game tells you everything, so never memorize — derive. Tab completion lists valid commands and valid IDs. help prints every command your build has. debugtooltip reveals the internal numeric ID of anything you hover. The up and down arrows recall your previous commands. Your game build prints its version on the main menu, and your own console's command list is the final authority on what exists in that build. A player who knows how to look things up in-game is patch-proof; a player who memorizes a command list is one update away from being wrong.

The Console Will Not Open

If no panel appears when you press the key, solve that before testing a single command — nothing else on this page can run until this is fixed. Work the three causes in order of likelihood.

Ironman, first and always. Check the save you loaded, not the one you meant to start. It is easy to click straight past the Ironman checkbox at game creation and then spend an hour troubleshooting a console that was never going to exist. The mechanism is deliberate: Ironman keeps saves on a single autosave chain and checksums them so achievements stay honest, and a console would punch a hole straight through that. Paradox's response is total — the keybind is not suppressed, it is absent. No workaround exists inside an Ironman save, and "disable Ironman" is not an option on a save already created. If you want the console, start a fresh non-Ironman game. If you want achievements, the console is off limits, and the only undo button Ironman allows is force-crashing the game and reloading the last autosave — which typically costs three to six months of progress. That is save-scumming, not the console, and it is the worse deal of the two.

Keyboard layout, second. The console opens with the key that produces tilde or backtick on your layout — the physical key just below Escape on a US keyboard. That key moves around on UK, German, French, and other layouts, which is why "tilde doesn't work" is a keyboard problem, not a game problem. Try these in order:

• ~ (tilde) or ` (backtick) — the standard key on US layouts.
• Shift+Alt+C — the layout-independent fallback. If nothing else opens the console, this should.
• The same key closes the console, so if it appears to "flicker," you are pressing the open and close key in quick succession.

Platform and focus, third. Console Edition on PlayStation and Xbox is a different product with no debug console at all — nothing on this page applies there, and no key combination will change that. On PC, if the console worked a minute ago and now will not, click back into the game window after an alt-tab: a lost input focus swallows the keybind, and it takes one click to cure.

The Command Does Nothing

The panel is open, you type a command, and the galaxy does not care. Before you blame the game, work the two suspects in order: toggles, then prefixes.

Suspect one: it is a toggle, and it is already on. Half of all "this command is broken" reports are toggle commands being switched off by the very press meant to switch them on. Press instant_build once and construction becomes instant; press it again and it stops being instant — and the second press looks, from the outside, exactly like the command failing. The toggles to know:

Command	First press	Second press
instant_build	All construction finishes instantly — for every empire, not just yours	Normal build times return
invincible	Your ships take zero damage	Your ships take damage again
yesman	AI empires accept every diplomatic proposal	AI empires judge proposals normally
noman	AI empires reject every proposal	Back to normal
debugtooltip	Hover tooltips reveal internal IDs	Tooltips return to normal
ai	AI empires stop playing the galaxy	AI empires resume

One toggle conflict deserves its own warning because it looks like a deep bug. yesman forces AI empires to accept your proposals — but only if the AI is running. Toggle the AI off with ai and empires stop responding to diplomacy entirely, so yesman appears to do nothing. Re-enable the AI before testing diplomacy cheats, and the "broken" command starts working on the spot.

Suspect two: the ID is missing its prefix. The parser does not autocomplete missing pieces of an identifier — drop the prefix and it drops your command, silently. Every object family has its own:

Prefix	What it identifies	Examples
(none)	Common resources	cash, alloys, food, minerals, unity, influence
tech_	Technologies	tech_titans, tech_zero_point_power
tr_	Traditions	tr_harmony_adopt
ap_	Ascension perks	ap_one_vision, ap_mind_over_matter
resource_	Advanced resources	resource_consumer_goods, resource_volatile_motes, resource_nanites
sr_	Strategic resources	sr_dark_matter, sr_zro, sr_living_metal

Two argument habits round out the syntax picture. First, most resource commands accept an optional amount and add a fixed default pile if you leave it off — append your own number, as in alloys 10000, to get exactly what you want. Second, research_all_technologies grants every standard technology except repeatable ones; append a 1 and it also sweeps in event technologies — L-gate insights, crystalline hull plating, dragon scale armor. And max_resources is the one-button version for standard resources, with one catch covered below: "standard" is doing real work in that sentence.

Scoped Commands Need a Target

The second great failure family is scope. A large set of commands acts on the scoped object — the planet, fleet, or empire you have clicked and selected. Select nothing and the command has nothing to act on, so it fails silently. No error, no hint, just a galaxy that appears to ignore you. The fix is always the same: click the target first, then type.

Command	Click first	The catch
planet_size 35	A planet	Resizes the selected planet only. No selection, no effect — the command does not pick a planet for you.
damage 800	A fleet	Deals raw hull damage and nothing else — shields and armor do not even notice it.
grow_pops 100	A planet	The number is not a head count (see below). Start small.
own	A planet, then its starbase	Skip the starbase and control slips back to the previous owner.
add_intel 2 70	Nothing — the empire ID is the argument	Additive: 10 intel plus 70 gives 80, not 70.

Three of these carry extra baggage. damage bypasses armor and shields entirely, which makes it a surgical deletion tool rather than a combat simulator — a ship with nine hundred hull taking eight hundred damage is left at death's door no matter how thick its fitting. Use it to remove a specific fleet from a test; do not use it to learn anything about how battles work.

grow_pops is the misleading one. Since the population rework, pops are larger units than they used to be, and the argument no longer maps one-to-one onto heads — typing a thousand produces far more than a thousand pops. Nobody has fully reverse-engineered the scaling, and you do not need to: start with a small number, see what arrives, and adjust. Typing a huge number and waiting is not a shortcut, because the game still has to grow every pop, and enormous values take a long while to process.

own is the one that bites people last. It claims any planet — it even drops a pop onto an uncolonized world and colonizes it on the spot, works on another empire's capital for cross-species testing, and runs a little wonky on gas giants, which is to be expected. The trap is the starbase: claim the planet but not the starbase above it, and control of the planet reverts to the original owner. Own both, in that order, and it sticks.

Stop Guessing, Read the Game

Wrong IDs are the third silent killer, and they are entirely avoidable, because the game will hand you the correct number if you ask. The tool is debugtooltip: toggle it on, hover over an empire, system, species, or leader, and the tooltip reveals its internal numeric ID. Every command that takes an ID — play, force_integrate, add_trait_species, add_trait_leader — wants the number you see there, not a name you invented. Guessing IDs and wondering why nothing happens is the most self-inflicted failure in the console.

Empire switching is the canonical example. play 21 hands you control of empire 21 — but only if 21 is the ID the tooltip showed, because IDs are assigned per save, not per empire name. Your original empire is always index zero, which makes play 0 your permanent way home no matter how far you wander. The full workflow: debugtooltip on, hover the galaxy map, note the number, play into it, and play 0 when the experiment is over. The debugtooltip and IDs guide covers the tooltip system in depth, and the IDs list collects the object identifiers commands accept.

For commands that take a tradition, perk, or technology ID, Tab is the cheapest debugger in the game. Type activate_tradition or activate_ascension_perk and press Tab: the console lists every valid ID the game knows, right there, for your exact build. One keystroke replaces an hour of wiki-scrolling and is never out of date, because it is generated by the game you are playing.

The rest of the discovery toolkit: help prints every console command your build contains, Tab autocompletes command names as you type, and the up and down arrows recall previous commands so you can repeat a test without retyping. When a guide and your game disagree about whether a command exists, your game is right and the guide is old. That principle is the whole game — the full command list is a map, but your console is the territory.

When the Command Works but the Result Is Weird

The third failure family is not a failure at all. The command did precisely what it says — what it says is just not what you assumed. These are the behaviors that generate "the console is buggy" posts, and every one of them is the console being exactly as strict as advertised.

instant_build is galaxy-wide. It makes construction instant for every empire, not just yours. Leave the AI running and the whole galaxy starts building at zero cost, which turns your controlled experiment into noise within minutes. The order of operations matters: toggle the AI off with ai first, then enable instant build. The command has a hidden second half that rewards this setup — it also raises your resource storage cap to a million, which is exactly why max_resources suddenly fills you with a mountain of alloys instead of topping you up to a normal cap. The two commands are a pair; run them together.

max_resources means standard resources. Energy, minerals, alloys, consumer goods, influence — capped and filled. Anything carrying the sr_ prefix sits it out: dark matter, zro, and living metal each need their own command, as in sr_dark_matter 500. If your strategic resources did not move, nothing broke — you just asked for the wrong category.

attack all fleets means all fleets. Every fleet in the galaxy becomes hostile to every other fleet, including your own fleets shooting at each other. That is the feature, not the accident: it lets one empire fight itself, so you never need two rival empires to test a matchup. Twenty battleships against a hundred corvettes, set up and resolved in about two minutes — the battleships win it easily, if you were wondering. Save the game before the fight and you can replay the same battle as many times as you like.

Crisis spawning runs on event chains, and chains have steps. Crises arrive through event commands: event crisis.10 starts the Prethoryn chain and they arrive within a couple of years, or event crisis.12 followed by event crisis.14 hurries them to near-instant arrival. event crisis.1000 drops the Unbidden in directly, in a single step. The Contingency answers to event crisis.2000 for an instant spawn or event crisis.2005 for the natural "go signal" chain. The classic trap: firing both Contingency commands to "speed it up" does not produce one faster Contingency. It produces two Contingencies. Pick one path. Event IDs are internal script references and the most version-sensitive numbers in the console — the wiki keeps the current map for each release, and a throwaway save is the place to try a chain before running it in a campaign you care about.

survey surveys everything at once. Every planet in the galaxy, processed simultaneously. On a large galaxy and modest hardware that is a stutter or a full lockup, because every survey ship goes to work in the same tick. It is not the command misbehaving; it is the command obeying you literally. Save first, and expect the game to think hard.

observer has two modes, and one of them plays the game for you. Enter observer mode and you can watch the galaxy passively — or from another empire's seat, which is how you film three endgame crises fighting each other for a time-lapse. Press Play while observing and the AI takes over your empire and simulates it without you. That is a feature, but it is a surprising one the first time your empire starts declaring wars on its own.

Two small tools that punch above their weight: the period key advances the game by exactly one day, which with instant build active means one ship per keypress cycle — the most underrated console tool for assembling fleets precisely. And for screenshots, gamepad enables controller camera movement with an extra-slow pan on the right trigger, while Ctrl+F9 hides the interface entirely for clean free-cam shots.

Patches, Mods, and Missing Commands

The last two causes sit outside the console itself: the game version, and what is modded into it. Both produce the same symptom — a command that a guide swears exists simply is not there, or behaves differently than described — and both have a clean diagnostic.

Start with the version. The launcher prints it in a corner, and it decides which build of the command set you have. The console itself has been rebuilt over the years: modern builds include a clickable menu with toggles for instant build, max resources, survey, communications, research-all-tech, and more, so half the commands are now clicks rather than keystrokes. If your console does not look like an old screenshot, that is why, and neither of you is wrong. Behavior moves too — grow_pops scaling changed with the population rework, and across Paradox titles commands do get retired entirely; observe, for instance, became an in-game button rather than a console command in some newer releases. A command that "does not work" may simply be gone.

The cure for version drift is rule four in action: do not argue with old screenshots, open Tab. Your own help output and Tab completion are generated by the build you are running, which makes them the only command list that cannot be stale. Anything this page or any list tells you, verify against that source when it matters — it takes one keystroke and settles the question permanently.

Then check the mod list. Mods add resources, rename object IDs, rewrite scripts, and generally invalidate every assumption a vanilla guide makes. A command that targets a resource a mod removed, or expects an ID a mod renumbered, will fail in ways no vanilla troubleshooting predicts. The diagnostic is disciplined and boring: duplicate the save, disable all mods, and confirm the command works clean. Then re-enable mods in groups, one variable at a time, until the culprit confesses. If it works unmodded and fails modded, you are not debugging the console anymore — you are debugging the mod, and the mod page is where that conversation happens.

A Safe Workflow for Console Experiments

The debug and testing corners of the console can crash the game or corrupt a save outright. That is not a reason to avoid them — it is a reason to save first, into a real manual save, not an autosave, before touching anything exotic. With that habit in place, the console stops being risky and starts being a lab.

The standard sandbox recipe, in the order that avoids the galaxy-wide surprises:

1. ai — turn the AI off first. Before instant build, not after, so the whole galaxy does not start constructing at zero cost.
2. research_all_technologies 1 — every technology, event technologies included. Expect a storm of pop-ups; that is the command working.
3. instant_build — instant construction plus the million-resource storage cap.
4. max_resources — which now fills you to that cap. Add sr_dark_matter, sr_zro, and sr_living_metal by hand for the strategic resources.
5. Build the fleets you want to test. The ship design guide covers compositions actually worth testing.
6. attack_all_fleets — let them fight, then save the game to reproduce the result whenever you want.

The discipline around the recipe matters more than the recipe. Duplicate saves before experiments, change one variable per test, and lean on the up arrow to repeat commands exactly rather than retyping them approximately. The console rewards methodical players and punishes button-mashers — the same way modding does, because that is essentially what this is: lightweight modding, applied live, to a running save. Treat it with the same respect and it will teach you more about how Stellaris works under the hood than a hundred normal campaigns.

FAQ

Next Reads

• Stellaris Console Commands and Cheats — the full command reference, once your console is running.
• Stellaris debugtooltip and IDs Guide — reading internal IDs off anything you hover, the skill behind every targeted command.
• Stellaris IDs List — technology, tradition, ascension perk, and resource identifiers for command arguments.
• Stellaris Ship Design Guide — fleet compositions worth building in your sandbox before you set them fighting.
• Stellaris Best Traditions and Stellaris Best Ascension Perks — what to grant yourself with activate_tradition and activate_ascension_perk when testing builds.
• Stellaris Beginner Guide and Stellaris Returning Player Guide — the unmodded fundamentals the console shortcuts skip over.
• EU5 Console Commands Not Working and HOI4 Console Commands and Cheats — the same debug-layer logic, and where it differs, in the other Paradox titles.