Quick answer
Debug mode = launch CK3 with -debug_mode in your launch options. It unlocks five toolsets: the console window, the debug menus (including the portrait editor), debug character interactions, Ctrl/Alt-click portrait shortcuts, and a file watcher for modding. It disables achievements while active.
Most players meet debug mode through one narrow door — they want gold 1000 — and never learn that the console is only a fifth of what the mode actually switches on. This guide maps the whole toolbox, because two of the other tools (the portrait editor and the debug character interactions) solve problems players routinely try to brute-force with commands.
What debug mode actually enables
Enabling debug mode turns on all of the following at once:
| Tool | What it does |
|---|---|
| Console window | Accepts typed commands — the familiar cheat interface |
| Debug menus | Portrait Editor, GUI Editor, Tweak Menu, and other developer panels |
| Debug character interactions | Right-click any character for instant options: change opinion, imprison, and more |
| Portrait shortcuts | Ctrl+click a portrait to take control of that character; Alt+click to kill them |
| File watcher | Auto-reloads changed game and mod files into memory as you edit them |
The setup itself is covered step by step in how to open the console: add -debug_mode to your launch options on Steam or the Paradox launcher, or to a shortcut target on Game Pass. What follows assumes debug mode is already running.
The console window
The console is the typed interface — over two hundred commands from resource cheats to full effect script blocks. Rather than duplicate the list here, use the searchable command table, which covers every command with parameters and copy-ready examples. Three habits make console work faster: the up/down arrows cycle your command history; hovering a portrait shows that character’s ID for use as a command parameter; and commands typed without a character ID default to your own ruler.
The portrait editor and other debug menus
Type portrait_editor in the console (or open it from the debug menu bar) and CK3 hands you the same tool its artists use to compose character appearances. You can load any character’s look, adjust every gene slider the game has, and export the result as a DNA string. This is the engine behind the most-searched debug workflow in the game — copying a real character’s appearance into the ruler designer — which has its own dedicated walkthrough in our DNA guide.
The GUI editor and tweak menu are aimed at mod developers: the GUI editor lets you inspect and live-edit interface files, and the tweak menu exposes toggles for game systems. For non-modders they are safe to ignore, but they explain why debug mode exists at all — it is a development kit that happens to double as a cheat panel.
Debug character interactions
With debug mode on, character right-click menus grow a set of instant interactions: set opinion, imprison without cause, and similar shortcuts. These are worth knowing because they answer situations the console handles clumsily. Adjusting one character’s opinion of you via console means looking up IDs and syntax; the debug interaction does it in two clicks. The same goes for the portrait shortcuts — Ctrl+click to switch and play as any character on the map (the console equivalent is the play command with a character ID), and Alt+click to kill a character outright.
A word of restraint from experience: the kill shortcut is the single easiest way to accidentally destabilise a campaign you cared about. One mis-aimed Alt+click on your own heir has no undo. If you are experimenting, experiment in a throwaway save.
The file watcher (for modders)
The file watcher monitors game and mod files and reloads changed ones into memory automatically, and the console’s reload command forces the same on demand — press Tab after typing reload to see the many valid targets. Combined with the run command, which executes a text file of commands from Documents/Paradox Interactive/Crusader Kings III/run, this is the core loop of CK3 script development: edit file, watch it hot-reload, re-run your test script. If you have ever wondered how mod authors iterate quickly, this is the answer.
Observer mode
The observe command detaches you from your character and lets the world run on its own — the classic “AI-only world” toy. To get back, use the play command with your character’s ID (hover a portrait to read an ID). Getting stuck in observer mode without noting your own ID first is a rite of passage; the fix is finding your character on the map and using Ctrl+click or play to return.
Turning debug mode off
Remove the -debug_mode launch option and restart the game. Two asymmetries to remember: debug mode can be disabled from inside a session via the console, but it cannot be re-enabled from inside that session — only a relaunch with the flag brings it back. And achievements remain disabled for any session that started in debug mode, regardless of what you toggled mid-session.
Frequently asked questions
Does debug mode work in ironman games?
No. Ironman blocks the console and debug tools; that is what keeps ironman achievement-eligible. Use a normal (non-ironman) save for debug sessions.
Will debug mode corrupt my save?
The mode itself does not touch your save — but the tools it unlocks certainly can, in the sense that killing half of Europe with Alt+click is permanent. Keep a backup save before heavy experimentation.
Can I use debug mode in multiplayer?
Debug mode in multiplayer is controlled by the host and applies to the session. Coordinate with your group before enabling it.
Why did my debug menu disappear after a patch?
If you enabled debug tools through a mod rather than the launch flag, the mod likely needs an update for the new patch. The launch flag itself survives patches unchanged.