Stellaris Console Commands: A Comprehensive Reference for PC Players

Stellaris console commands are a powerful set of developer tools built into the PC version of the game, enabling players to debug, experiment, and customize their playthroughs. This guide explains how to access commands, common syntax patterns, valid country and species IDs, and how to use each category of cheats without breaking your save quality. It provides an evergreen reference for commands related to resources, exploration, research, jobs, and empire management, emphasizing responsible use and compatibility considerations so experienced players can troubleshoot and creative players can experiment safely.

How to Open the Stellaris Console

To use Stellaris console commands, start the game, load or create a campaign, and pause the game while in the campaign view (the Galaxy Map). Press the Ctrl + Shift + C keys simultaneously to open the text console. Type a command and press Enter to execute it. For commands that require an object target, first select the target in the game—such as a planet, star system, or empire—and then focus the galaxy view so the selection is active before entering the command.

Multiple commands can be chained with a pipe character | to run them sequentially. The console is case-sensitive and does not accept typos; incorrect syntax or invalid IDs will typically return an error in the upper-left message area. Save before experimenting with advanced or destructive commands, and note that enabling cheats disables Steam Achievements for that session. Commands remain available in existing games unless a new ironman session is started without cheats enabled.

Enabling Cheats and Managing Compatibility

Cheats must be explicitly enabled before they will function. In the console, type enable_cheats and press Enter. A confirmation message indicates that cheats are active and that Ironman mode is automatically disabled for that session. Some players combine this with free_market to ignore market penalties, or use always_reveal_map to maintain full visibility. After enabling cheats, special administration commands and creative tools become available.

Because cheats disable achievements and some scripted events, it is wise to verify compatibility with your personal goals. Creative modes are ideal for sandbox experimentation, while ironman runs should remain untouched to preserve challenge. When in doubt, create a backup or use a duplicate save file to test new commands.

Basic Syntax and Targeting Rules

Most Stellaris console commands follow a predictable pattern: an action keyword, optional modifiers, and a target. Targets are often selected objects in the galaxy view, identified by IDs such as P0 for your primary empire or S2758 for a specific system. To ensure precision, select the target in the galaxy view, press Tab to cycle through objects if needed, and confirm the selection is highlighted. Use the find command family to locate entities by name or type when IDs are unknown.

Numeric arguments such as amounts, levels, and indices must be exact integers. Negative values are valid for some resource commands but not all. Boolean flags typically use 1 or 0 to enable or disable options. When stacking effects, remember that repeated applications may override previous settings rather than accumulate, depending on the command.

Finding Valid IDs and References

Because many commands require specific IDs, it is essential to know how to locate them. Species IDs follow the internal species key, which can be found in localization files or debug menus. Country IDs correspond to empire names or tags and can be revealed through admin debug panels or scripted events. Star system IDs are numeric and can be identified via map shortcuts or by hovering over system names while holding modifier keys. When in development mode, tooltips in the debug overlay often display these IDs directly.

Resource, Research, and Job Commands

Resource commands let you add or remove common materials such as food, minerals, energy, and alloys. Research commands can instantly complete projects or adjust ongoing progress, while job commands manage workforce assignments across districts and buildings. These are frequently used to accelerate early growth, stabilize economies during crises, or prototype builds without grinding.

For precise adjustments, combine resource commands with balancing parameters. For example, specifying minerals=500 adds half a thousand units, while research commands can target a single technology by exact name. Job commands can shift pops between sectors, ensuring specialized worlds maintain optimal specialization even after unusual events or edits.

Sample Resource Commands

• give_resources minerals=1000 — Adds 1,000 minerals to your treasury.
• set_balance food=50 — Sets your food balance to exactly 50 units.
• research_technology id tech_am_amp_tier_II — Completes a specific technology instantly.
• assign_job district=1 job=engineers_pop=200 — Assigns jobs in a district by index.

Diplomacy, Warfare, and Map Control

Diplomacy and warfare commands allow rapid testing of scenarios without long-term campaign consequences. You can declare war, create federations, or impose embargoes instantly. Map-related commands reveal hidden areas, adjust fog of war, and teleport entities across the galaxy. These are especially useful for narrative playthroughs, designing custom challenge runs, or verifying that scripted galaxies function as intended.

Because diplomatic actions can affect relations and war goals, it is best to test them in non-ironman saves. Some commands apply immediate results, while others introduce cascading effects that depend on existing treaties and rivalries. Reviewing changelogs or patch notes can help anticipate how certain commands interact with current game logic.

Diplomatic and Map Shortcuts

• war [id] — Instantly declare war on the specified target.
• federation [id] — Form a federation with the chosen empire.
• always_reveal_map — Keep the entire galaxy visible.
• teleport id [id] — Move selected fleets or armies to a targeted system.

Debugging, Editing, and Advanced Administration

Debug commands unlock lower-level tools for editing traits, spawning objects, and inspecting internal flags. The admin menu provides buttons and toggles for common adjustments, reducing the need to memorize every key. Commands like create_other and add_trait allow precise modifications to characters and species, which is valuable for writing stories or building themed empires.

Because debug tools can produce unpredictable outcomes if misused, proceed carefully. Editing core species files or trait stacks may affect compatibility with future updates or mods. Record the changes you make and keep original files recoverable. When possible, validate edits in a test save before applying them to a long-term campaign.

Useful Debug and Admin Shortcuts

• debug_menus — Toggles advanced debug and administration panels.
• admin — Opens the in-game administrative control window.
• create_other — Spawns entities or items from a selection menu.
• add_trait [trait] [id] — Applies a trait to a species or character.

Wrap-Up: Command Safety and Best Practices

Stellaris console commands are robust tools for debugging, testing, and creative sandboxing when used with care. Understand how targeting and syntax work, keep backups, and avoid over-reliance on cheats in runs you intend to complete for achievements or leaderboards. With this reference, you can confidently explore, troubleshoot, and customize your Stellaris experience without compromising long-term save integrity.