Console Commands — After Strategy

Europa Universalis V Console Commands: Test a Campaign Without Breaking It

Tue, 12 May 2026 00:00:00 GMT

Europa Universalis V can make a losing position look deceptively simple. The treasury is empty, the army will not recover, a neighbour is suddenly too strong, or a market seems to be swallowing every ducat. The console will happily let you bulldoze all of that. It is more useful when it helps you identify which problem is actually holding the campaign back.

That calls for a separate save. Copy the campaign, name the copy after the question you want to answer, and leave the original untouched. A small cash test, a quick look at another country, or one controlled event can tell you whether the next real decision should be an economic reform, a delayed war, a different ally, or simply more time.

Enable debug mode, then find the right key

EU5’s console is part of debug mode. Enable debug mode before launching the game, load a non-Ironman test save, and try the binding for your keyboard layout. The Europa Universalis V console reference lists several possibilities because Paradox shortcuts vary by layout:

Layout	Keys worth trying
US/UK QWERTY	`, then `~`
French AZERTY	`²`, then `Alt + C` or `Shift + Alt + C`
German QWERTZ	`§` or `^`
Spanish layouts	`°` or `Shift + 2`

Do not assume a missing console means the game is broken. Check that the test save is non-Ironman, that debug mode was enabled before launch, and that a mod has not changed the interface. Pressing Tab after the start of a command can autocomplete it; the arrow keys revisit earlier entries.

Start with `help`, not a cheat sheet

The safest first command is help. It prints the available commands; help [command] asks for the description of a specific command. That matters because old EU4 lists often circulate under EU5 searches, while a patch or a mod can also change what is useful in your setup.

helplog is even better when you are diagnosing a difficult case. The EU5 wiki documents it as a way to write the command list and descriptions into a local log. It is a calmer workflow than trying to memorize dozens of strings mid-campaign: look up the exact command, test it once on the copy, then decide whether the result is meaningful.

The commands that answer real campaign questions

This is not an exhaustive command dump. These documented commands cover the investigations that most often help a player understand a campaign.

Question	Command	What to do with the result
Is the immediate problem simply a lack of money?	`cash [amount]`	Add a modest amount on the copy. If the plan still fails, the issue is probably costs, trade, control, manpower or timing rather than the treasury alone.
Is a resource constraint distorting the decision?	`Manpower [amount]`, `Sailors [amount]`, `Stability [amount]`, `Prestige [amount]`	Change one resource, let time run briefly, then compare the queue, war capacity or domestic pressure.
What does the other country actually have?	`tag [CountryTag]`	Switch only long enough to inspect its position, then reload your own save. Do not turn the copy into an alternate campaign by accident.
Is the AI behaviour the real variable?	`ai [CountryTag]`	Test an AI state carefully and observe diplomacy or military movement before drawing a conclusion.
What happens if nobody is steering?	`observe`	Watch the simulation for a short period to see whether the balance changes without player action.
Does a specific event change the plan?	`event [eventid] [target]`	Trigger it only after confirming its syntax with `help`; event IDs and targets are where stale guides cause the most damage.

The syntax above comes from the current community-maintained EU5 reference. It is not a promise that every parameter will behave identically in every patch, localisation or mod list. When a command matters to a long-running save, verify it with help in the game first.

Three tests worth running before you restart a campaign

Is this an economy problem or a planning problem?

Suppose the treasury is empty and a war is approaching. Add a limited amount of cash on the copied save instead of an absurd number. Record the monthly balance, the army cost, the market situation and the date. Let a few months pass.

If the money creates enough room to complete a plan, the real campaign might need a smaller army, a postponed building programme or a different tax and trade decision. If the balance immediately consumes the buffer, you have learned something more useful: money was only the symptom.

Is the neighbour stronger, or just better positioned?

Use tag to inspect a rival on the copied save. Look at their manpower, allies, geography and the fronts an army would need to cross. Then reload your own country before making a decision.

The useful outcome is rarely “I can win because I saw their data.” It is a practical adjustment: wait for a truce to end, secure access through a third country, preserve manpower, or abandon a war whose timing is wrong. EU5 rewards timing as much as raw numbers.

Is an event worth changing the entire plan for?

Before building a strategy around an event, test it on the copied save with the documented syntax. Pause first. Read the resulting choices, their target and their consequences. Then restore the untouched campaign and ask whether the plan still makes sense without assuming the best outcome.

This is where debug mode earns its place. It removes uncertainty just long enough to make a better decision, rather than removing every consequence from the campaign.

Debug tools for modders and persistent problems

Some commands are more useful to modders than to ordinary campaigns. The EU5 reference documents tools for logging, errors, reloading and observation alongside gameplay-facing commands. helplog, error, gamelog, reload and the debug information tools can help isolate a faulty event, a broken localisation line or a mod conflict.

Keep those tests isolated. Disable one mod at a time, note the game version and preserve the save that reproduced the issue. A clean report is far more valuable to a mod author or Paradox support channel than a vague account of a console command that “did not work.”

What not to do with the console

Do not use a copied test to convince yourself that an impossible war is winnable. A console can give money, change countries or force an event; it cannot tell you whether the real campaign can support the consequence afterwards.

Avoid broad scripts copied from old guides, especially commands presented as universal shortcuts. Check them with help, test one variable, and reload. The campaign remains interesting when you carry only the insight back to the real save.

For adjacent EU5 context, read our six-month review, the Urban Rights patch analysis and the Fate of the Phoenix preview.

Conclusion

EU5 console commands work best as a workshop, not a replacement for the campaign. Make one test on a clearly named copy, observe what changes, then return to the unmodified save with a decision you can defend. That keeps Europa Universalis V’s uncertainty intact while making a difficult empire easier to read.

For the full, evolving command list and keyboard notes, consult the Europa Universalis V console reference.

Victoria 3 Console Commands & Cheats: Complete Guide 2026

Thu, 05 Feb 2026 00:00:00 GMT

Victoria 3 is Paradox’s industrial grand strategy game (1836-1936). Managing pop-based economy, industrialization, revolutions and colonial diplomacy is as thrilling as it is complex. Victoria 3 console commands let you test economic scenarios, force revolutions, or simply unlock progression. Here’s the complete guide.

Copy the campaign first and name the save after the question you are testing. Record its date, weekly balance, construction queue and key market price. A controlled test should answer one question, then send you back to the clean campaign with a decision.

Enable V3 debug mode (mandatory)

Like Crusader Kings III, the V3 console is not enabled by default. You must enable debug mode.

On Steam

Right-click Victoria 3 in your library
Properties → Launch Options
Type -debug_mode
Confirm, restart the game

Verification

A message in the top right confirms debug mode. Steam achievements are disabled while this flag is present.

Opening the V3 console

Once in debug mode, in-game:

US/UK QWERTY: ~
German QWERTZ: §
French AZERTY: ²
Fallback: Shift + Alt + C

⚠️ No console in Ironman or multiplayer.

Victoria 3 console commands

Economy and treasury

Goal	Command
Add money (£)	`money [amount]`
Innovation (research)	`innovation [amount]`
Diplomatic influence	`influence [amount]`
Authority	`authority [amount]`
Bureaucracy	`bureaucracy [amount]`

Politics and legitimacy

Goal	Command
Prestige	`prestige [amount]`
Radicalism	`radicalism [amount] [TAG]`
Pop loyalty	`loyalty [amount] [TAG]`
Government legitimacy	`legitimacy [amount]`
Add strategic interest	`add_interest [region] [TAG]`

Construction and production

Goal	Command
Instant build	`instabuild`
Finalize production	`instant_production`
Set pop type	`set_pop_type [pop_id] [type]`

Diplomacy and nations

Goal	Command
Switch country	`tag [TAG]` (FRA, GBR, GER, USA, RUS, JAP…)
Observer mode	`observe`
Annex country	`annex [TAG]`
Add claim	`add_claim [TAG] [state_id]`
Force peace	`peace_offer [TAG]`

Events and debug

Goal	Command
Trigger event	`event [id]`
Test event	`testevent [id]`
List commands	`help`
Help for command	`help [name]`
Reload interface	`reloadinterface`

3 interesting V3 scenarios

Lightning Industrial Revolution — tag FRA, money 99999999 + innovation 999999 + instabuild. Build 50 factories in 1 year. Observe societal and pop effects.
Hyperactive colonial empire — tag GBR, add_interest africa_west [GBR] + add_interest india [GBR], money 50000000 and colonize Africa in 5 years.
Socialist revolution in Russia — tag RUS, radicalism 99 RUS + event socialist_uprising.1 to force a socialist revolution as early as 1860.

Recommended V3 mods

Morgenröte — Content expansion, more historical events, AI improvements.
More Focus Trees V3 — Adds per-nation focus trees (HOI4-inspired).
Economic Overhaul — More realistic economy rework.

Conclusion

Victoria 3 cheats are particularly useful to understand the game’s complex economic systems without waiting decades of real play. The pops + production goods + political laws system being labyrinthine, the console lets you quickly test configurations.

For Paradox’s official list: Victoria 3 wiki.

Use the console as an economic workshop

Start with help, then check help plus a command name before entering syntax copied from an old guide. money [amount], observe, research and state-level tests are useful when each answers a limited campaign question. Adding everything at once only proves that constraints matter.

Is debt the cause or the symptom?

On a copied save, add a modest amount of money and let several weeks pass. Compare the weekly balance, construction queue, interest, infrastructure and input prices. If the buffer disappears immediately, the real answer may be to pause construction, import an input, change a production method or delay an institution rather than simply borrow more.

Is industry short of technology or inputs?

Test one research choice, then inspect the coal, tools, engines, labour and infrastructure it would require. A technology can look like the answer while the market cannot support its buildings. The useful conclusion is a normal decision: build railways, secure a trade route, staff a state or postpone the expansion.

Is the diplomatic play premature?

Use observe on the test save to read fronts, allies, interests and likely mobilisation. The result may be a delay, a treaty, a port or a different target. What matters is not whether a debug command can force victory, but whether it reveals the missing decision in the real campaign.

A repeatable test protocol

Make one change, let time pass, compare the same numbers, then reload the untouched save. For an economy, note weekly balance, construction, a key input price, unemployment and infrastructure. For politics, note legitimacy, radicals, interest groups and the proposed law. For war, note the target, allies, fronts and mobilisation. This keeps the experiment readable.

Politics: test the timing, not the outcome

Political pressure is another place where a copied save helps. Before attempting a law, note legitimacy, the strongest interest group, radical growth and the movement opposing the change. Test one cabinet or timing change, let a short period pass, then compare those same values. A successful forced law tells you almost nothing about the real country. A test that shows legitimacy recovering after an election, or radicals easing after wages improve, gives you a route you can actually play.

The same restraint applies to revolutions. A debug command can create or remove one, but the important question is why the movement grew: an unpopular law, an excluded group, poor living standards or a reform launched at the wrong moment. Keep the test narrow enough to distinguish those causes.

Markets, states and construction queues

Victoria 3 economies often look healthy in the national budget while one state is choking on missing inputs or infrastructure. On the copied save, select the state where the queue is stalled and compare local employment, infrastructure, a key good price and building throughput. Then alter one condition. Build transport, pause a factory, change a production method or secure a trade route. Let the market update before deciding what the result means.

This is also the right way to use ownership and state-level tools. Do not redraw a region simply because a command permits it. Use a temporary state test to understand whether access to a market, a resource or a coastline would solve the actual problem. Return to the clean save and seek the equivalent normal route through diplomacy, investment or gradual expansion.

Keep debug saves disposable

Name the copy clearly and never rely on it as evidence that an achievement, multiplayer or long-term campaign will behave identically. Debug mode, mods and patches can change the environment. The value is the observation you carry back: one input is too expensive, one state lacks infrastructure, one law needs political preparation, or one war should wait.

Stellaris Console Commands: Test Your Empire Without Ruining a Save

Sun, 01 Feb 2026 00:00:00 GMT

Stellaris is Paradox’s space grand strategy game, where an empire can fail for several different reasons at once: a shortage of alloys, an overextended fleet, unhappy planets, weak research, or a crisis that arrives before the economy is ready. The console is useful when it helps isolate one of those problems on a working save. Your main empire should remain clean.

Open the Stellaris console

The key depends on the keyboard layout. On a US or UK QWERTY keyboard, try ~.

On a German QWERTZ layout, try §. French AZERTY players should try ².

If neither works, test Shift + Alt + C before assuming the console is unavailable.

⚠️ Steam achievements disabled the moment you use the console. ⚠️ No console in Ironman or multiplayer.

Essential Stellaris console commands

Resources and economy

Goal	Command
Add energy	`cash [amount]`
Add minerals	`minerals [amount]`
Add alloys	`alloys [amount]`
Add food	`food [amount]`
Add consumer goods	`consumer_goods [amount]`
Add influence	`influence [amount]`
Add unity	`unity [amount]`
Add dark matter	`dark_matter [amount]`

Research and tech

Goal	Command
Finish all research	`research_technologies`
Include rare techs	`research_all_technologies`
Add specific tech	`research_technology [tech_id]`
Gain +10 years of tech	`add_tech [amount]`

Construction and fleets

Goal	Command
Instant build	`instant_build` (toggle)
Add ship	`add_ship [name]` (e.g. `add_ship Titan`, `add_ship Colossus`)
Spawn system	`spawn_system [star]`
Reveal whole map	`debugtooltip` → `observe` to see everything

Empires and diplomacy

Goal	Command
Switch player empire	`play [empire_ID]`
Galactic observer mode	`observe`
Force empire surrender	`surrender [target TAG]`
AI accepts everything	`yesmen`
Add rival	`add_rival [TAG]`

Planets and populations

Goal	Command
Acquire planet	`own [planet_id]`
Add pop	`add_pop [species_id]`
Kill pop	`kill_pop [pop_id]`
Add anomaly	`add_anomaly [category]`
Instant terraform	`finish_terraform`

Crises and events

Goal	Command
Trigger End-Game Crisis	`event crisis.10`
Trigger the Scourge (Prethoryn)	`event crisis.1000`
Trigger the Extradimensionals	`event crisis.2000`
Trigger the Contingency	`event crisis.3000`
Trigger Fallen Empire awakening	`event fallen_empire.100`
Trigger any event	`event [id]`

Utilities and debug

Goal	Command
List commands	`help`
Help for command	`help [name]`
Show IDs on hover	`debugtooltip`
Reload interface	`reloadinterface`
Clear console	`clear`

Three Stellaris tests that help a real empire

Is the economy short of resources or short of structure?

Copy a save where the economy is stalling. Add a limited alloys 500 or minerals 500, let one or two in-game months pass, and watch the stockpile, jobs and construction queue. If that small buffer clears the problem, your empire may only need a better production rhythm. If it disappears immediately, the issue is more likely districts, upkeep, trade, population or too many simultaneous projects.

Is the fleet weak, or is the war badly timed?

Use a working save and test one research or one ship addition rather than an entire armada. Inspect the enemy empire with play [empire_ID] or observe, then return to your own empire. Compare fleet power, starbase position, allies and travel routes. The useful answer may be that the war should wait for a defensive pact, a chokepoint or an alloy reserve, not that every ship needs to appear instantly.

Can the crisis plan actually hold?

An end-game crisis test is most useful when it is scoped. Trigger one event on a disposable save, pause, check fleet capacity, gateways, fortress worlds and supply routes, then run the scenario. If the empire collapses, change one preparation element and try again. Three simultaneous crises create spectacle; one controlled crisis reveals whether your defence plan has a gap.

Treat the console as an empire workshop

Before entering a command, duplicate the save and name it clearly, for example United-Nations-alloy-test. Define one question: does this planet lack consumer goods, does this fleet need a technology, or does the crisis frontier lack a fortified chokepoint? Then modify one variable. A small amount of energy, minerals or alloys, one technology, or a brief switch to another empire can be enough to reveal the answer.

Note the date, fleet power and monthly alloy balance before the test. Those three values make the outcome comparable after reloading the clean save.

Start with help, then use help plus a command name if you are unsure about syntax. The Stellaris console reference is safer than a guessed event ID or an old video. Mods can alter technologies, ships, empires and events, so repeat any test in the exact Steam Workshop playset used by the campaign.

Resources, research and construction

cash, minerals, alloys, consumer_goods and instant_build are most useful when they test a bottleneck. Add a limited resource, observe the empire, and reload the clean save. If the command makes a meaningful difference, turn that observation into a normal decision: change a district, reduce upkeep, postpone a megastructure, or alter the fleet timetable.

research_technology and research_technologies can clarify what a missing technology actually unlocks. Use them to compare a specific ship component, building or doctrine on the copied save. Do not mistake a late-game tech tree for a solution to an empire that cannot support the fleet it already owns.

Empires, planets and crises

play [empire_ID] and observe are magnifying glasses. Use them briefly to read another empire’s fleets, planets, diplomacy and borders, then return to your own country. own, add_pop and crisis events are stronger interventions. They belong in explicit what-if scenarios, not in a save you still want to judge as a normal campaign.

The real question is always what you will do after reloading. What matters is not whether the console can create a stronger empire, but whether it exposes the one missing decision: build a gateway, reinforce one system, sign an alliance, rebalance an economy, or delay a war. The console has done its job when it makes that decision clearer without replacing it.

Mods to extend Stellaris cheats

Cheat Menu — GUI for all commands (Steam Workshop).
Instant Colonization — Colonize a planet instantly.
Fast Exploration — Ultra-fast science ships.

Conclusion

Stellaris console commands are at their best when they turn a confusing empire problem into a testable one. Keep resource, research, fleet and crisis commands on a working save, then return to the clean empire to make the real decision. That preserves the uncertainty and consequences that make a galactic story worth finishing.

For Paradox’s official list: Stellaris wiki.

EU4 Console Commands: Test a Campaign Without Ruining the Save

Wed, 21 Aug 2024 00:00:00 GMT

EU4’s console has a reputation as a button for making every problem disappear. That is the least interesting use of it. A campaign can fail because of debt, bad war timing, an exposed fort line, exhausted manpower, an impossible alliance web, or a province whose details are not obvious on the map. The console is useful when it lets you isolate one of those causes.

Create a copy of the save first. Give it a name such as France-war-test-1512, then decide what you are trying to learn. A limited cash injection, a short switch to a rival country, or a controlled province test can turn a vague frustration into a practical decision for the real campaign. Write down the date and the condition you are testing before entering the first command.

Open the EU4 console safely

Use a non-Ironman single-player save for testing. The EU4 console reference lists several keys because the binding varies by keyboard layout.

Keyboard	Keys to try
US/UK QWERTY	` or `~`
French AZERTY	`²`, then `Alt + C` or `Shift + Alt + C`
German QWERTZ	`§` or `^`
Other layouts	`Shift + 2`, `Shift + 3` or the layout-specific option in the reference

If nothing appears, check the game mode before trying random shortcuts. Ironman and multiplayer are not the place for an experiment. Mods can also alter interfaces and command behaviour, so repeat an important test with the exact playset used by the campaign.

Start with `help`, not a giant cheat list

Type help before you do anything ambitious. It lists available commands; help [command] gives you a description for a named command. This habit matters because a lot of EU4 search results blend old patch advice, mod commands and commands that only make sense in a particular scenario.

Use debug_mode when the question is about the map rather than the outcome. It can expose useful information while hovering a province, including IDs and country tags. That is often more valuable than instantly changing ownership or starting an event you cannot undo cleanly.

Commands that answer a campaign question

These are not an invitation to run every command in sequence. They are the documented tools that help answer a specific question on a copied save.

Question	Command	What the test can reveal
Is a shortfall really about money?	`cash [amount]`	Add a modest amount, let time pass, and watch the balance. If the money vanishes immediately, the real problem is structural.
Is manpower the actual bottleneck?	`manpower [amount]`	Test a limited reserve before blaming battle tactics, forts or allies.
Would monarch points change the plan?	`adm [amount]`, `dip [amount]`, `mil [amount]`	Check a core, technology or diplomatic choice without pretending the points are free in the real save.
Which province or country is involved?	`debug_mode`	Read the relevant ID and tag before using a province or country command.
What is the rival really doing?	`tag [TAG]` or `observe`	Inspect another country’s position briefly, then reload your own campaign.
Is a diplomatic proposal possible in principle?	`yesman`	Test the shape of a peace or alliance on the copy, not as a permanent campaign state.
What happens after a specific event?	`event [ID] [TAG]`	Confirm the syntax with `help` and test it only on the working save.

Commands such as own, control, annex and winwars are much more invasive. They can be useful for a deliberately artificial scenario, but they rarely teach much about whether your normal campaign can survive the next decade.

Three tests that make a real campaign clearer

Is the economy broken, or merely under pressure?

Copy a save that is close to bankruptcy. Add a small amount with cash, note the monthly balance, then let one year pass. If the buffer disappears, inspect army maintenance, forts, interest, autonomy, trade and the number of simultaneous projects. If it creates room to finish a plan, the real campaign may only need a delay or a smaller commitment.

The command has not solved EU4 for you. It has told you whether money is the cause or the symptom.

Was the war unwinnable, or badly timed?

Before declaring war, make a copy. Use a limited manpower or military-point test, then replay the first engagements. If the result barely changes, numbers were not the decisive factor. Terrain, a fort line, naval access, morale, technology, allies or the date of the declaration may matter more.

Record the date, available manpower and the first battle result. Those details make the comparison useful once you reload the unmodified save.

What would an alternate history actually require?

Byzantium surviving the Ottomans is a good example. A copy can test a fleet, a cash buffer, a single ally or a different opening. You can also use tag to inspect the Ottoman position for a moment. The useful conclusion is not that unlimited resources make survival possible. It is whether timing, naval control, debt, allies and defensive terrain create a plausible route in a normal run.

Keep the test smaller than the campaign

The best rule is simple: one question, one variable, one observation. Do not add cash, manpower, cores and instant wars at the same time, then try to infer why the campaign improved. A small test remains legible. What matters is the comparison: the date, the reserve you added, the battle or monthly balance you observed, and the clean save you can still return to.

After the test, reload the clean save and make the real choice. Build fewer forts, wait for an ally, protect the trade route, avoid a bad terrain fight, or postpone a core. The useful question is not whether the console can make a country stronger; it is whether it reveals the decision the normal campaign was missing.

That distinction keeps a long EU4 run honest. A France that only survives because of permanent cash and winwars has stopped being a strategic problem. A France that survives because a test exposed a costly fort network or a mistimed war is still your campaign, with its consequences intact.

For a different kind of fresh EU4 campaign, see our best EU4 mods guide. If the question is whether to move on, our EU4 versus EU5 comparison puts the two games in context. You can also browse the Europa Universalis IV game hub.

Conclusion

EU4 console commands are strongest as a workshop for a difficult decision. Keep them on a copied save, use help before an unfamiliar command, and carry the insight back to the campaign you actually want to finish. That preserves the tension of Europa Universalis IV while making its systems easier to read.

For the evolving command list and exact syntax, consult the EU4 console reference.

Imperator Rome Console Commands: Test a Campaign Without Ruining It

Sat, 11 Feb 2023 00:00:00 GMT

Imperator: Rome is Paradox’s ancient grand strategy game about the classical Mediterranean. The console is most useful when a campaign raises a question you cannot answer from the normal interface: is a war failing because of money, manpower, diplomacy, or a decision made twenty years earlier? A test save can isolate that question. Your main campaign should stay clean.

Open the Imperator Rome console

The key depends on your keyboard layout. On a US or UK QWERTY keyboard, try ~.

On a German QWERTZ layout, try §. French AZERTY players should try ².

If neither works, test Shift + Alt + C before assuming the console is unavailable.

⚠️ Steam achievements disabled the moment you use the console. ⚠️ No console in Ironman or multiplayer.

Essential console commands

Economy and population

Goal	Command
Add gold	`cash [amount]`
Add population	`add_population [amount] [province ID]`
Add food	`food [amount]`
Add civic tech	`add_civic_tech [amount]`
Add military tech	`add_military_tech [amount]`
Add religious tech	`add_religious_tech [amount]`
Add oratory tech	`add_oratory_tech [amount]`

Army and war

Goal	Command
Add manpower	`manpower [amount]`
Add military tradition	`add_military_tradition [amount]`
Win all wars	`winwars`
Siege province	`siege [ID]`
Disable fog of war	`fow`

Nations and diplomacy

Goal	Command
Switch country	`tag [TAG]` (ROM, MAC, SEL, EGY, CAR…)
Observer mode	`observe`
Annex country	`annex [TAG]`
Add casus belli	`add_cb [CB] [TAG]`
AI accepts everything	`yesman`

Government and characters

Goal	Command
Add prestige	`add_prestige [amount]`
Add stability	`add_stability [amount]`
Clear corruption	`clear_char_loyalty`
Kill character	`kill [ID]`
Convert province	`convert_province [ID]`

Utilities and debug

Goal	Command
List commands	`help`
Help for command	`help [name]`
Reload UI	`reloadinterface`
Clear console	`clear`

Scenarios to try

Rome: money or timing? Copy a save, use a small cash 500, then replay a few years. If the plan still stalls, money was not the real problem.
Carthage: wealth or manpower? Test cash and manpower separately. The contrast tells you whether a war is constrained by income, losses or recruitment.
The Diadochi: observe first. Use observe, then a brief tag switch to inspect alliances, armies and stability before trying to change anything.

Recommended Imperator Rome mods

Invictus — massive content overhaul, events, missions (widely considered the unofficial expansion Paradox never shipped).
TerraIndomita — another popular content expansion.
Steam Workshop is full of visual and gameplay additions.

Use a test save like a lab

Before entering a command, duplicate the campaign or start a short disposable run. Name it clearly, for example Carthage-console-test. That small bit of housekeeping matters. A command can change an outcome, but it can also erase the evidence you were trying to study: a deficit, a depleted army, a difficult treaty or a province that will not settle down.

Start with help, then use help followed by a command name when you are unsure about its arguments. The Imperator console reference is the right place to verify syntax instead of guessing from an old forum post. IDs and tags are especially easy to mistype, and a command that works in vanilla can have a different effect in a modded campaign.

Economy: test the smallest useful intervention

cash [amount] is tempting because it produces an immediate result. It is also easy to misuse. A huge sum proves almost nothing: every army can be reinforced and every building can be rushed. A small amount is more revealing. Add enough to remove a short-term bottleneck, then let the game run. If the plan now works, you may have found an economic timing issue. If it still fails, the problem may be military, political or diplomatic.

Use the same discipline with manpower [amount]. A controlled reserve can show whether a front collapsed because of attrition or recruitment. An infinite reserve turns a war into a different game. The point is not to be virtuous about cheats; it is to keep the test legible.

Diplomacy and tags: look before you steer

tag [TAG] is a powerful magnifying glass. Switch briefly to Rome, Carthage, Egypt or the Seleucids to inspect resources, alliances and ongoing wars, then return to your own country. This can explain why an AI neighbour made an apparently strange choice. Staying there for years, however, lets the AI take over your original country and makes the comparison meaningless.

observe is often the cleaner first step. Let the world run for a while, then inspect the states that prospered or collapsed. You may find that a regional crisis came from disloyalty, trade, culture or a chain of wars rather than a single battle. Imperator’s population, characters and provinces interact; the console is useful when it helps separate those layers.

Commands to keep away from a campaign you value

annex, winwars and yesman have legitimate uses for a what-if scenario. They are poor fixes for a campaign you still want to evaluate. Forced peace removes the cost of war, instant annexation changes the map before the internal systems can react, and universal acceptance creates diplomatic arrangements the AI would normally refuse.

If you want to see the aftermath of a particular conquest, use one of these commands on the copied save, observe the result, and reload your real campaign. That gives you an answer without pretending that the result was earned naturally.

A repeatable test is better than a spectacular one

Try to give every Imperator campaign test a single question. For example: can cash 500 keep Carthage supplied through a three-year war, or does it need manpower 500 because the army is the real constraint? Does a neighbouring province collapse because of troops, diplomacy or internal politics? Write down the date, change one command, and let the campaign run for the same amount of time. The result will not be laboratory-perfect, but it is far more informative than stacking five commands at once.

This method also works with mods. First test the same cash, tag ROM or observe question in a clean Steam Workshop playset. Then add the mod and repeat it. If the outcome changes, you have learned something concrete about the new campaign rules instead of merely feeling that an economy or war became easier or harder. Keep screenshots or a short note if the scenario is worth revisiting later.

Conclusion

The best Imperator console session ends with you returning to a clean save carrying a better idea. Maybe Carthage needed a more sustainable army, maybe Rome expanded before its economy could support it, or maybe a mod changed an assumption in your plan. That is a far more useful outcome than a map painted in one evening.

For source syntax and the complete command list, use the Imperator console wiki. For a new modded campaign, see our Imperator mods guide.

CK3 Console Commands & Cheats: Complete Guide 2026

Sat, 16 Jul 2022 00:00:00 GMT

Crusader Kings III is a medieval dynastic grand strategy game where the complexity of family, religious and diplomatic intrigues can quickly turn labyrinthine. CK3 console commands let you test scenarios, unblock situations, or simply bend the rules for fun. Here’s the complete guide updated for 2026.

Enable CK3 debug mode (mandatory)

Unlike EU4 and HOI4, the CK3 console is not enabled by default. You must first enable debug mode:

On Steam

Right-click Crusader Kings III in your library
Properties → General tab
Launch Options: type -debug_mode (with the dash)
Confirm and launch

On GOG

Create a game shortcut and append -debug_mode to the target.

Verification

On launch, a message in the top right confirms debug mode. Steam achievements are disabled while this flag is present on any save.

Opening the console

Once in debug mode, in-game:

US/UK QWERTY: ~
German QWERTZ: §
French AZERTY: ²
Fallback: Shift + Alt + C

The console appears at the bottom of the screen.

Essential CK3 console commands

Personal resources

Goal	Command
Add gold	`gold [amount]`
Add prestige	`add_prestige [amount]`
Add piety	`add_piety [amount]`
Add dynasty renown	`add_dynasty_renown [amount]`
Add stress	`add_stress [amount]`

Character and family

Goal	Command
Play as another character	`play [ID]`
Observer mode	`observe`
Add trait	`add_trait [trait] [ID]`
Remove trait	`remove_trait [trait] [ID]`
All lifestyle perks	`gain_all_perks [ID]`
Impregnate a woman	`pregnancy [mother_ID] [father_ID]`
Kill a character	`kill [ID]`
Alternative “murder”	`die [ID]`

Titles and lands

Goal	Command
Grant a title	`give_title [title] [ID]`
Add claim	`add_claim [title]`
Kill all soldiers	`kill_soldiers [ID]`
Fill domain treasury	`instabuild`

Schemes and intrigue

Goal	Command
Discover all schemes against you	`know_schemes`
Cancel all schemes against you	`end_schemes`
Change sexuality	`set_sexuality [id] [ID]`

Events and debug

Goal	Command
Trigger event	`event [event_id] [ID]`
Test event without triggering	`testevent [event_id] [ID]`
List commands	`help`
Reload interface	`reloadinterface`
Clean screenshot (hide UI)	`cache`

Star commands

`gain_all_perks`

Use it on a working save to see how a lifestyle tree affects a specific character, then reload your main campaign before deciding how to educate an heir. It is a comparison tool, not a replacement for a dynasty’s choices.

`add_trait giant`

add_trait is most useful for checking how one trait changes a relationship, education or event. Make a single temporary change, read the character panel, and reload if you want to preserve the dynasty’s natural story.

`play [ID]`

Switch briefly to another character to inspect titles, alliances and resources. It is a magnifying glass for a neighbour or heir; stay there too long and the AI will change your original realm.

Three CK3 test scenarios that help a real campaign

A succession about to divide the realm

Copy the save before a ruler dies. Use play [ID] briefly to inspect the titles, alliances and resources held by each heir, then reload your main character. You are not choosing a winner through the console. You are learning why a partition is dangerous and which decisions, while the ruler is alive, can limit it.

A vassal whose loyalty is hard to read

On a working save, inspect the character’s traits, claims and relationships in debug mode. A temporary add_trait can help show how a personality change affects opinion or an event. Do not keep the change. The useful question is whether the conflict comes from a trait, title, opinion or succession dispute.

A war that appears financially impossible

Test a limited gold 200, not an infinite treasury. Replay a few months, look at army maintenance and alliances, then reload. If a small amount changes everything, the war may have a timing problem. If it changes nothing, reconsider the army, diplomatic support or objective.

Use a disposable save like a workshop

Debug mode gives immediate access to information and commands that can transform a dynasty. That is exactly why a test must stay separate from the campaign that matters. Create a copy with a clear name, such as Capet-succession-test, and ask one question: what happens if this heir receives a duchy? Does the war become viable with a slightly larger treasury? Which vassal is really threatening the council?

Start with help, then use help plus a command name when you are unsure about syntax. The CK3 console wiki is a better reference than an old video or a guessed ID. Titles, characters and scripted effects depend on context, and modded campaigns deserve extra caution.

This discipline does not make CK3 less playful. It protects the campaign whose consequences you want to keep. You can explore an extravagant scenario on the copy, then return to your ruler with a clearer reading of heirs, titles, alliances and risks. What matters is the decision you make afterwards.

A five-minute check before you keep any result

First, make sure the command affected the intended character or title. Debug mode exposes a lot of information, and it is easy to use an ID from a child, spouse or vassal when you meant to target the ruler. Read the character panel after add_trait, play or a title-related command. Then let one in-game month pass. Opinion, income, army maintenance and event prompts can reveal consequences that are not obvious on the same day.

Second, ask whether the result survives without the command. If a gold 200 test makes a war possible, try to identify a legitimate source of income, an alliance or a smaller objective that creates the same room in the real campaign. If switching with play shows that an heir holds a dangerous claim, use that knowledge to plan marriages, titles or contracts before succession happens.

Finally, do not carry a console result into a modded campaign without repeating the test. A total conversion, character expansion or bookmark mod can change titles, events and balance. Record the playset name with the test save. That tiny note saves time when you revisit a dynasty after a patch or when a friend wants to reproduce the same scenario.

Mods that extend cheats

Cheat Menu — GUI for all commands (Steam Workshop).
More Bookmarks+ — more starting points, useful with cheats for historical scenarios.
Character Editor — direct character editing without console commands.

Conclusion

CK3 commands are most valuable when they clarify a medieval saga instead of flattening it. Keep gold, add_trait, play and debug mode on a test save, then return to the clean campaign to act. That preserves the consequences, risks and political reversals that make a dynasty memorable.

For Paradox’s full list, the official CK3 wiki is the ultimate reference.

HOI4 Console Commands & Cheats: Complete Guide 2026

Thu, 14 Jul 2022 00:00:00 GMT

Hearts of Iron IV is a grand strategy game whose depth can overwhelm. HOI4 console commands and cheat codes let you quickly simulate scenarios, test unit builds, or just play with less friction. Here’s the complete guide updated for 2026.

How to open the HOI4 console

The key depends on your keyboard layout. On a US or UK QWERTY keyboard, try ~.

On a German QWERTZ layout, try §. French AZERTY players should try ².

If neither works, test Shift + Alt + C before assuming the console is unavailable.

⚠️ Warning: in HOI4, using the console disables Steam achievements for the current game (unlike EU4). If you’re achievement-hunting, keep a clean save before cheating.

⚠️ No console in Ironman or multiplayer modes.

Essential HOI4 console commands

Resources and economy

Goal	Command
Add manpower (default 1M)	`manpower [amount]`
Add political power	`pp [amount]`
Add equipment	`add_equipment [amount] [type]`
Example: 1000 German rifles	`add_equipment 1000 infantry_equipment_1`
Commander XP	`xp [amount]`
All army/air/navy experts	`research all`
Finish research on click	`research_on_icon_click`

Construction and factories

Goal	Command
Instant construction	`instantconstruction` (alias `ic`)
Disable instant construction	same command again
All strategic resources	`add_resources [amount]`

War and combat

Goal	Command
Win all your wars	`winwars`
Adjust warscore	`ws [TAG]`
Instant war goal	`instant_wargoal`
Instant naval prep	`instant_prepare`
Force diplomatic action	`allowdiplo`
Win a tile battle	`debug_winwar`

Nations and diplomacy

Goal	Command
Switch country	`tag [TAG]` (e.g. `tag GER`, `tag SOV`, `tag USA`)
Observer mode	`observe`
Annex country	`annex [TAG]`
Reveal war fog	`debug_nuking` → full vision
AI accepts everything	`yesman`
Add opinion	`add_opinion [source TAG] [target TAG]`

Debug and utilities

Goal	Command
List all commands	`help`
Help for command	`help [command]`
Reload interface	`reloadinterface`
Reload text	`reloadtext`
Clear console	`clear`

Focus: the most powerful commands

`instantconstruction`

Alias ic. Use it on a working save to compare two factory or fortification plans, then reload before the main campaign. It can reveal a bottleneck; it should not erase the cost of every building.

`research_on_icon_click`

Activate it, then click a technology to test how a doctrine, tank or support weapon changes a frontline. The useful question is what the technology enables in a particular war, not how quickly it can make every research screen disappear.

`tag [CODE]`

Use it briefly to inspect another country’s stockpiles, armies, alliances and war goals. Switch back quickly: it is a magnifying glass for the AI, not a way to run two countries for years.

Three HOI4 test scenarios that help a real campaign

Germany: production or timing? Copy a 1939 save, use a modest add_equipment amount for one infantry model, then replay a few weeks. If the front still fails, the problem may be supply, doctrine or the battle plan rather than equipment alone.
Japan: fleet or diplomacy? Inspect the navy with tag JAP, then use observe to see which alliances and wars change the Pacific. This separates a naval preparation issue from a strategic commitment you cannot sustain.
Soviet Union: research or logistics? Test one relevant technology with research_on_icon_click, then look at supply, divisions and terrain on a copied Barbarossa scenario. A stronger tank model does not automatically solve an overstretched frontline.

Treat the console as a campaign workshop

Before entering a command, make a copy of the save and give it a clear name such as France-supply-test. Define one question: does this offensive fail because of equipment, manpower, supply or a missing ally? Then change one variable. A small manpower injection, a single technology, or a brief country switch can be enough to reveal the answer.

Start with help, and use help followed by a command name when the syntax is unclear. The HOI4 console reference is a better source than a guessed tag or an old video. Equipment identifiers, scripted events and modded content can all change the expected result.

Production and construction

instantconstruction is useful when you want to compare the strategic value of civilian factories, military factories, forts or infrastructure without waiting through years of building. Run the comparison on the copied save, look at supply and production lines, then reload. If a new railway or factory changes the campaign, you have learned something actionable about the real build order.

Frontlines and diplomacy

tag [TAG], observe and small equipment tests help explain an AI decision that looks irrational from the outside. Switch to a neighbour, inspect its divisions and stockpiles, then return to your own country. The real insight may be that the enemy lacks fuel, that an ally never joined, or that a front is consuming more supply than the map can deliver.

Commands such as winwars, annex and yesman are best reserved for an explicit what-if. They can show the aftermath of a peace settlement, but they remove the very attrition, diplomacy and war score that make a normal HOI4 campaign interesting. Use them on the test copy, observe the consequences, and keep the clean campaign honest.

A pre-offensive test checklist

Before blaming a division template, pause the copied campaign and inspect five things: available equipment, manpower, fuel, supply hubs and the number of divisions already assigned to the frontline. Use the console only to test the uncertainty you cannot isolate otherwise. For example, add a limited amount of infantry equipment, run the offensive for a few days, and compare the supply map with the original save.

Do the same with technology. A clicked research can show whether a support company or doctrine changes the battle enough to matter. If it does not, the answer may be terrain, planning bonus, air superiority or a missing railway rather than a research delay. This is why a short controlled scenario is valuable: it directs your attention toward the actual constraint instead of making every loss feel random.

When the test is finished, reload the clean save and turn the observation into a normal decision. Build the infrastructure, wait for equipment, shorten the frontline, request an ally, or postpone the war. The console has then done its job without replacing the campaign.

Extend cheats via mods

Several Steam Workshop mods enrich the experience:

Cheat Menu — GUI for all commands, no typing.
Dev Tools for Modders — advanced test tools (scripts, global variables).
No-Step-Back Cheat Console — commands for the No Step Back DLC.

Conclusion

HOI4 console commands are most useful when they turn one confusing campaign moment into a testable question. Keep manpower, add_equipment, tag and research commands on a working save, then return to the clean campaign to make the real choice. That protects the uncertainty and consequences that make a war plan worth playing.

For the official exhaustive list, the HOI4 Paradox wiki remains the reference.

Console Commands — After Strategy

Europa Universalis V Console Commands: Test a Campaign Without Breaking It

Enable debug mode, then find the right key

Start with help, not a cheat sheet

The commands that answer real campaign questions

Three tests worth running before you restart a campaign

Is this an economy problem or a planning problem?

Is the neighbour stronger, or just better positioned?

Is an event worth changing the entire plan for?

Debug tools for modders and persistent problems

What not to do with the console

Conclusion

Victoria 3 Console Commands & Cheats: Complete Guide 2026

Enable V3 debug mode (mandatory)

On Steam

Verification

Opening the V3 console

Victoria 3 console commands

Economy and treasury

Politics and legitimacy

Construction and production

Diplomacy and nations

Events and debug

3 interesting V3 scenarios

Recommended V3 mods

Conclusion

Use the console as an economic workshop

Is debt the cause or the symptom?

Is industry short of technology or inputs?

Is the diplomatic play premature?

A repeatable test protocol

Politics: test the timing, not the outcome

Markets, states and construction queues

Keep debug saves disposable

Stellaris Console Commands: Test Your Empire Without Ruining a Save

Open the Stellaris console

Essential Stellaris console commands

Resources and economy

Research and tech

Construction and fleets

Empires and diplomacy

Planets and populations

Crises and events

Utilities and debug

Three Stellaris tests that help a real empire

Is the economy short of resources or short of structure?

Is the fleet weak, or is the war badly timed?

Can the crisis plan actually hold?

Treat the console as an empire workshop

Resources, research and construction

Empires, planets and crises

Mods to extend Stellaris cheats

Conclusion

EU4 Console Commands: Test a Campaign Without Ruining the Save

Open the EU4 console safely

Start with help, not a giant cheat list

Commands that answer a campaign question

Three tests that make a real campaign clearer

Is the economy broken, or merely under pressure?

Was the war unwinnable, or badly timed?

What would an alternate history actually require?

Keep the test smaller than the campaign

Conclusion

Imperator Rome Console Commands: Test a Campaign Without Ruining It

Open the Imperator Rome console

Essential console commands

Economy and population

Army and war

Nations and diplomacy

Government and characters

Utilities and debug

Scenarios to try

Recommended Imperator Rome mods

Use a test save like a lab

Economy: test the smallest useful intervention

Diplomacy and tags: look before you steer

Commands to keep away from a campaign you value

A repeatable test is better than a spectacular one

Conclusion

CK3 Console Commands & Cheats: Complete Guide 2026

Start with `help`, not a cheat sheet

Start with `help`, not a giant cheat list

`gain_all_perks`

`add_trait giant`

`play [ID]`

`instantconstruction`

`research_on_icon_click`

`tag [CODE]`