Quick Answer
Stellaris console commands usually stop working because the save is Ironman, the wrong keyboard shortcut is being used, the player is on Console Edition, the command is misspelled, the target is wrong, debugtooltip was not used to confirm IDs, a patch changed command behavior, or mods changed the expected object. Start with a non-Ironman PC save and the full Stellaris console commands list.
This troubleshooting guide is for players who can open Stellaris but cannot get a command to run, cannot open the console at all, or are unsure whether the command is failing because of the save, keyboard, platform, target, patch, or mod setup.
Source checked: Updated May 5, 2026 against the local Stellaris console commands article, the preferred Stellaris Paradox Wiki console commands page, and the local Stellaris audit. Direct wiki access may be blocked by tooling challenges, so exact syntax should be verified with in-game help, autocomplete, and debugtooltip in the current PC build.
Table of Contents
- Fast checks before troubleshooting
- The console will not open
- A command runs but does nothing
- Debugtooltip and target IDs
- Patch changes and mods
- PC vs Console Edition
- Safe testing workflow
- FAQ
Fast Checks Before Troubleshooting
| Check | What to confirm | Fix |
|---|---|---|
| Ironman | The save is not Ironman. | Use a non-Ironman save. Console commands are not for achievement runs. |
| Platform | You are on PC, not PlayStation or Xbox Console Edition. | Use PC guidance only for the PC version. |
| Keyboard shortcut | Your layout matches the console hotkey you are trying. | Try ~, `, Shift+2, ALT+2+1, Shift+3, ^, or Shift+Alt+C. |
| Command spelling | The command name and arguments are exact. | Use help, autocomplete, or the main command list. |
| Target | The correct planet, fleet, ship, species, or empire is selected. | Use debugtooltip and verify IDs before running target commands. |
| Mods | Mods are not changing scripts, resources, IDs, or command expectations. | Test in an unmodded duplicate save. |
The Console Will Not Open
If the console never appears, solve that before testing commands. The most common causes are Ironman, keyboard layout differences, wrong platform, and focus issues after alt-tabbing.
| Symptom | Likely cause | Try this |
|---|---|---|
No console on ~ | Different keyboard layout. | Try alternate shortcuts: `, Shift+2, ALT+2+1, Shift+3, ^, or Shift+Alt+C. |
| Console worked before but not now | Ironman save or input focus issue. | Confirm save mode, click back into the game, and test in a new non-Ironman save. |
| Playing on PlayStation or Xbox | Console Edition is not the same as PC command console. | Do not expect PC console command instructions to apply. |
| Some keys type characters but no console opens | Keyboard layout/localization issue. | Cycle through common shortcuts and check OS keyboard layout. |
A Command Runs but Does Nothing
When a command appears to run but nothing changes, the problem is usually syntax, missing arguments, wrong target, unsupported context, or a patch/mod mismatch. Do not repeat commands randomly in your main save. Use a duplicate save and change one thing at a time.
| Problem | Example | Fix |
|---|---|---|
| Missing amount | Resource command needs a number. | Try the command format from the main command guide. |
| Wrong ID | Planet, species, leader, or empire ID is not what you thought. | Turn on debugtooltip and hover the exact object. |
| Wrong selection | A planet command runs while no planet is selected. | Select the target first, pause, then run the command. |
| Unsupported save state | Ironman or achievement-focused save. | Use non-Ironman for testing. |
| Changed command | Patch changed syntax or removed behavior. | Use in-game help and current reference pages. |
Debugtooltip and Target IDs
debugtooltip is the command user’s diagnostic tool. It can reveal IDs and internal information when you hover objects or interface elements. If a command needs an empire ID, planet ID, species ID, leader ID, ship ID, or fleet/object target, do not guess.
- Open the console in a non-Ironman PC save.
- Type
debugtooltipand press Enter. - Hover the relevant object or interface element.
- Write down the ID and object type before running the command.
- Turn
debugtooltipoff when finished if the extra UI text is distracting.
For a full workflow, use the Stellaris debugtooltip and IDs guide.
Patch Changes and Mods
Stellaris changes often, and mods can change more than visuals. A modded save can add resources, rename scripted effects, alter objects, or change the context where a command works. If a command fails in a modded game, test the same command in a clean non-Ironman save before assuming the command itself is broken.
| Cause | How it breaks commands | Best test |
|---|---|---|
| Patch update | Syntax, effects, or object names may change. | Use in-game help and current command references. |
| Total conversion mod | Resources and scripted effects may be different. | Test in unmodded Stellaris, then ask the mod documentation. |
| UI mod | May hide or alter where you find IDs. | Disable UI mods and test debugtooltip again. |
| Old save | Patch migration can produce unexpected state. | Create a fresh test save on the current patch. |
PC vs Console Edition
This article is about the PC command console. Stellaris Console Edition on PlayStation and Xbox has different version timing, interface assumptions, and command availability. If you are on console, do not troubleshoot PC keyboard shortcuts as if they should work on a controller.
Safe Testing Workflow
- Duplicate the save before running commands.
- Confirm the duplicate is non-Ironman.
- Open the console with the correct keyboard shortcut.
- Run
debugtooltipwhen a command needs IDs. - Run one command, check the result, and write down what changed.
- Reload if the command affected the wrong target.
- Use the Console Commands hub for related command guides.
Stellaris Console Commands Not Working FAQ
Why will the Stellaris console not open?
The usual causes are Ironman, the wrong keyboard shortcut, wrong platform, or a keyboard layout issue. Test in a non-Ironman PC save and try alternate shortcuts.
Do Stellaris console commands work in Ironman?
No. Console commands are for non-Ironman testing and sandbox play. Use a duplicate non-Ironman save when experimenting.
Why does my planet command affect the wrong planet?
The target or ID is probably wrong. Select the planet, enable debugtooltip, confirm the ID, and run the command only after verifying the target.
Can mods break Stellaris console commands?
Yes. Mods can change resources, scripts, IDs, UI behavior, and command context. Test in an unmodded save before blaming the command.
How do I find empire or species IDs?
Use debugtooltip, then hover the relevant empire, species, leader, planet, ship, or fleet interface element. The debugtooltip guide covers the workflow.
Where is the full Stellaris command list?
Use the Stellaris console commands and cheats list for command examples, resource commands, debugtooltip notes, and troubleshooting basics.