CK3 Console Commands & Cheats: Complete Guide 2026

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

1. Right-click Crusader Kings III in your library
2. Properties → General tab
3. Launch Options: type -debug_mode (with the dash)
4. 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

Character and family

Titles and lands

Schemes and intrigue

Events and debug

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.