Kingdom Come: Deliverance 2 doubles down on realism, systemic depth, and punishing consequences, and that’s exactly why the developer console matters more than ever. When a quest NPC breaks their daily routine, your stamina soft-locks mid-combat, or RNG decides your perfectly built longsword Henry suddenly can’t land a hit, the console becomes more than a cheat menu. It’s a precision tool for power users who want control over a deeply simulated world that doesn’t always behave.
This isn’t Skyrim-style god mode fantasy. Kingdom Come’s CryEngine backbone exposes a low-level command system originally designed for debugging AI, physics, quests, and timeflow. Used correctly, it lets you fix bugs, test builds, skip grind-heavy mechanics, and experiment with systems the vanilla UI never explains.
What the Console Is Actually Designed For
At its core, the console exists for developers and testers, not casual players. Most commands interact directly with CryEngine subsystems like entity spawning, AI states, inventory flags, and time scaling. That’s why many commands feel raw, numeric, or unintuitive, but also why they’re incredibly powerful in the right hands.
You can manipulate stats, inject items, alter perks, force quest states, and even override AI behavior. For modders and theorycrafters, this is the fastest way to validate DPS calculations, stamina breakpoints, stealth visibility thresholds, or perk synergies without replaying a 40-hour save.
What the Console Cannot Do
The console does not magically make the game stable, balanced, or safe. Some commands bypass scripts the game expects to run naturally, which can desync quest logic, break NPC schedules, or corrupt saves if used carelessly. There are also hard limits: certain cutscenes, quest flags, and progression gates are locked behind compiled scripts the console simply cannot rewrite on the fly.
It also won’t turn Kingdom Come into an arcade RPG. You can’t disable hitboxes, rewrite combat animations, or ignore physics entirely without deeper mod-level changes. The console tweaks the simulation; it doesn’t replace it.
PC-Only Power, With Real Risks
Console commands are a PC-only feature. They are not supported on PlayStation or Xbox, and never will be due to platform restrictions. Even on PC, Warhorse treats console usage as unsupported behavior, meaning you’re on your own if something breaks.
Achievements may be disabled depending on how commands are used, especially those that modify progression, inventory, or character stats. Smart players keep manual backup saves and test commands on a separate profile before touching a long-term playthrough.
Why This Guide Matters
Kingdom Come: Deliverance 2 does not surface its console commands in-game, and many legacy commands from the first title behave differently or have been renamed. Some still work. Some are deprecated. Others are newly added and undocumented.
This guide exists to cut through that chaos. Every command listed is contextualized, categorized, and explained so you know not just what it does, but when it’s safe to use, when it’s risky, and when it’s the only fix that actually works.
How to Enable the Developer Console (Launch Options, Config Files, and Mod Dependencies)
Before you can spawn items, nudge AI behavior, or brute-force a broken quest state, you need to actually unlock the console. Kingdom Come: Deliverance 2 does not expose it by default, and the method you use depends on how clean or modded your setup is. The good news is that Warhorse still relies on CryEngine’s developer framework, so the entry points are familiar if you’ve tinkered before.
Method 1: Steam Launch Options (Fastest and Safest)
For most players, launch options are the cleanest way to enable the console without touching game files. Open Steam, right-click Kingdom Come: Deliverance 2, select Properties, and paste the following into Launch Options:
-wh_pl_showfirecursor 1
This flag enables the developer input layer and allows the console to be opened in-game. Once loaded into a save, press the tilde key (~) or sometimes the grave key (`) depending on your keyboard layout. If the console is active, a translucent input bar will appear at the top of the screen.
This method has the lowest risk of breaking updates or triggering file integrity issues. It also survives patches, making it the recommended baseline even for heavily modded installs.
Method 2: Editing system.cfg (Advanced and Persistent)
If launch options fail or you want more control, you can force-enable the console through configuration files. Navigate to your main game directory and locate system.cfg. If it doesn’t exist, you can safely create it using a plain text editor.
Add the following lines:
sys_EnableDevConsole = 1
log_verbosity = 3
Save the file and launch the game normally. This approach forces CryEngine to expose developer hooks every time the game boots, even without Steam flags.
Be aware that config edits are more fragile after major patches. If the game suddenly crashes on launch after an update, this file should be the first thing you temporarily remove to isolate the issue.
Keyboard Layouts and Input Conflicts
Not every keyboard opens the console with the same key. On US layouts it’s typically ~ or `, but on EU layouts it may be ^, ö, or a key next to left Shift. If nothing happens, check your Windows keyboard language and try switching layouts temporarily.
Also note that some keybinding mods or accessibility overlays can intercept the console key. If the console refuses to open despite being enabled, disable overlays like Steam Input, ReShade toggles, or third-party macro tools and test again.
Mod Dependencies That Affect Console Access
Certain mods rely on the console being active, while others quietly disable or override it. Hardcore overhauls, total conversions, and UI replacement mods are the most common culprits. If you’re running a mod manager, load order matters more than most players realize.
Mods that modify input handling, HUD layers, or CryAction scripts should always load after core framework mods. If a mod includes its own system.cfg or autoexec.cfg, check for conflicting dev console flags. Duplicate or contradictory values can silently block console initialization.
Verifying the Console Is Fully Functional
Opening the console isn’t enough; you need to confirm it’s actually executing commands. Type a harmless query like:
wh_sys_dump
or
help
If the console returns output instead of doing nothing, you’re good. If commands echo without response, the console is in read-only mode, usually caused by missing dev flags or a mod conflict.
At this point, make a manual save. Treat this as your clean testing baseline before issuing any commands that touch stats, inventory, AI, or quest states. From here on, you’re operating with developer-level access, and the game will assume you know exactly what you’re doing.
Essential Console Usage Rules: Syntax, Parameters, IDs, and Common Mistakes
Once you’ve confirmed the console is live and responding, the real learning curve begins. Kingdom Come: Deliverance 2 uses CryEngine’s developer console, which is extremely literal and completely unforgiving if you get the syntax wrong. One missing space, an invalid ID, or a misplaced quotation mark is enough to make a command fail silently.
Think of the console less like a cheat menu and more like a developer API. You’re issuing direct instructions to game systems that were never meant to hold your hand, and the engine expects precision every single time.
Command Structure and Syntax Rules
Most commands follow a strict pattern: command_name parameter value. Spaces matter, capitalization sometimes matters, and extra characters will break execution. If a command doesn’t return feedback, assume it didn’t work rather than assuming nothing happened.
Some commands require quotation marks, especially when referencing strings, quest names, or entity identifiers that contain spaces. If you forget the quotes, the engine will read each word as a separate parameter and discard the command entirely.
Also be aware that CryEngine supports chaining commands with semicolons, but Kingdom Come 2 is inconsistent about it. For safety, run one command at a time unless you’re testing in a throwaway save.
Understanding Parameters, Values, and Data Types
Parameters are not interchangeable. If a command expects a number and you give it text, it won’t auto-correct or warn you. Health values, skill levels, item quantities, and time modifiers all rely on raw numerical input with no safety rails.
Floats versus integers matter more than most players expect. For example, some stat-related commands accept decimals like 2.5, while others will round down or outright fail if you don’t use whole numbers. When in doubt, start with conservative values and scale up.
Boolean parameters usually use 0 and 1 rather than true or false. This trips up even experienced modders, especially when toggling AI, HUD elements, or simulation layers.
Item IDs, Entity IDs, and Why Names Rarely Work
One of the most common mistakes is assuming item names equal item IDs. They don’t. The console doesn’t recognize “Longsword” or “Savior Schnapps” unless the command explicitly supports name lookup, which most don’t.
Item spawning, inventory editing, and equipment manipulation almost always require internal IDs. These are typically long, case-sensitive strings defined in the game’s data tables. If you’re guessing, you’re doing it wrong.
Entity IDs are even more dangerous. These reference live objects in the world, including NPCs, horses, containers, and quest triggers. Targeting the wrong entity can despawn characters, soft-lock quests, or permanently break AI routines tied to your save.
Context-Sensitive Commands and Player State
Some commands only work if Henry is in the correct state. Mounted, in combat, mid-dialogue, or during a scripted sequence can all block execution. The console won’t always tell you this, so if a command fails, check what Henry is doing first.
Location matters too. Commands that manipulate NPCs, AI behavior, or world events often require you to be in the same loaded cell. Trying to affect something across the map usually does nothing or targets the wrong instance.
Saving and reloading can also reset temporary console effects. If a command works until reload, it was likely a runtime tweak rather than a persistent change.
Common Mistakes That Break Saves
The fastest way to corrupt a save is touching quest variables without understanding their dependencies. Quest states are interconnected, and forcing one stage forward can invalidate triggers the game expects to fire naturally.
Another frequent issue is over-stacking stats. Setting skills, perks, or attributes far beyond intended caps can cause UI glitches, broken calculations, or AI scaling issues that persist even if you revert the value later.
Spawning duplicate key items is equally risky. The game often assumes certain items are unique, and having more than one can confuse quest logic or block progression checks.
Achievements, Flags, and Invisible Consequences
Using the console doesn’t always disable achievements immediately, but certain commands flip hidden developer flags in the background. Once triggered, these flags can permanently mark a save as modified.
Even if achievements still pop, future patches or validation checks may retroactively invalidate them. If you care about a clean run, keep a separate console-testing save and never cross-contaminate.
Finally, remember that the console doesn’t ask for confirmation. There’s no undo button, no rollback, and no warning popup. Every command assumes you’re a developer with full intent, so treat each line you enter like it’s final.
Core Gameplay Cheats: God Mode, Health, Stamina, Combat, Crime, and Reputation
With the safety rules out of the way, this is where most players actually start bending the game. These are the commands that let you brute-force difficulty spikes, test builds without hours of grind, or recover a save that got soft-locked by bad RNG or buggy AI.
Every command below assumes the console is already enabled and that Henry is in free control. If you’re mid-cutscene, in dialogue, or hard-locked by a quest script, expect inconsistent results.
God Mode and Player Invulnerability
True god mode exists, but it’s not a magical “win everything” switch in every scenario. When active, Henry ignores incoming damage, stamina drain, and most physics-based knockdowns, but scripted quest damage can still punch through.
wh_pl_setgodmode 1
wh_pl_setgodmode 0
Use this for testing encounters, exploring high-level zones early, or debugging broken combat states. Leaving god mode enabled during quests can cause progression bugs if the game expects Henry to fail or retreat, so toggle it off once you’re done.
Health and Stamina Control
Direct stat manipulation is safer than god mode and more flexible if you want challenge without punishment. These commands instantly refill or hard-set Henry’s core survival values.
wh_pl_sethealth X
wh_pl_setstamina X
Replace X with a numeric value. Setting health absurdly high can break UI scaling or combat feedback, so staying within 100–300 keeps things stable. Stamina affects combat flow heavily, and infinite stamina trivializes timing, perfect blocks, and clinches.
Combat Tweaks and Damage Control
Combat commands are ideal for experimentation, especially if you’re testing weapon balance, perk synergies, or enemy AI behavior. These don’t always show obvious feedback, so test them in live combat to confirm they applied.
wh_combat_ignorestamina 1
wh_combat_ignorestamina 0
wh_combat_setdamage X
Ignoring stamina removes one of the game’s core skill checks, effectively turning fights into DPS races. Damage scaling is global, meaning it affects both Henry and enemies, so pushing values too far can make combat feel broken or inconsistent.
Crime, Wanted Level, and Law System Control
Crime in Kingdom Come isn’t just a number; it’s a web of guards, witnesses, and reputation modifiers. These commands let you instantly clear or manipulate that system when it spirals out of control.
wh_crime_clear
wh_crime_setwanted X
Clearing crime wipes active pursuit and jail flags, but it doesn’t always reset NPC memory. Setting wanted level manually is risky, as guards may aggro without proper escalation logic, especially in towns with layered security zones.
Reputation and Social Standing
Reputation governs prices, dialogue options, guard behavior, and even quest availability. Tweaking it is useful for testing speech builds or recovering from accidental crime sprees.
wh_reputation_add X
wh_reputation_set X
Positive values improve local standing, while negative values simulate notoriety or fear-based reactions. Reputation is often tracked per region, so results may appear inconsistent unless you’re standing in the affected area when applying the command.
When to Use These Cheats (and When Not To)
These cheats are best used surgically, not permanently. Fix a broken fight, escape a bugged jail state, or test a perk interaction, then revert to normal play.
Leaving core cheats active long-term can desync systems that expect natural failure, exhaustion, or punishment. If something starts feeling “off” after using them, reload a clean save before assuming the game is broken.
Items, Money, and Inventory Commands: Spawning Gear, Groschen, Quest Items, and Debug Objects
Once you start bending combat, crime, or reputation systems, the next pressure point is always inventory. Whether you’re testing armor breakpoints, validating quest logic, or skipping early-game poverty, item and money commands are the fastest way to remove friction without rewriting your entire save.
These commands are also where most players accidentally break progression. Spawning gear bypasses crafting, NPC vendors, and perk-gated availability, so use them with intent, not impulse.
Spawning Items Directly into Inventory
The backbone command for inventory manipulation is item injection. It places objects straight into Henry’s inventory, ignoring weight checks, vendor scarcity, and progression locks.
wh_cheat_additem X Y
X is the internal item ID, while Y is the quantity. Item IDs are case-sensitive and must be exact, which is why most modders pull them from unpacked game files or community-maintained lists rather than guessing.
If the item fails to appear, it usually means one of three things: the ID is invalid, the item is region- or quest-locked, or the object expects a container spawn instead of direct inventory placement.
Adding Groschen Instantly
Money manipulation is far safer than item spawning and rarely causes downstream bugs. If you’re testing speech checks, merchant scaling, or training costs, this is the cleanest shortcut.
wh_cheat_money X
X is the amount of Groschen added directly to your purse. The value stacks instantly and doesn’t trigger theft flags, reputation changes, or guard suspicion.
Avoid pushing absurd values early in a save, as some scripted events assume poverty thresholds. Extremely high totals can also trivialize economy-based perks, making testing inaccurate.
Weapons, Armor, and Clothing Spawns
Weapons and armor spawned via console arrive in pristine condition by default. This makes them ideal for DPS testing, armor penetration checks, and durability drain analysis.
However, these items bypass blacksmith quality tiers and maintenance loops. If you’re testing realism or balance, manually damage them afterward through combat or repair systems rather than assuming default stats reflect normal acquisition.
Some late-game armor sets also lack NPC ownership flags when spawned, which can confuse guards if worn in restricted areas.
Quest Items and Progression Objects
Quest items are where console power becomes dangerous. Many quests track states through invisible variables, not just inventory presence.
wh_cheat_additem quest_item_id 1
This can unblock a stuck quest stage, but it will not retroactively fire dialogue, reputation changes, or NPC schedule updates. In some cases, the game will accept the item but still treat the quest as incomplete.
Use this only to recover from broken triggers, not to skip narrative steps, unless you’re prepared for inconsistent outcomes later.
Debug Objects and Test Assets
Developers leave behind test items, placeholder gear, and debug-only objects. These are invaluable for modders and system testers but should never be used in a normal playthrough.
Spawning debug items can introduce missing textures, broken physics, or inventory crashes when the game tries to reference unfinished assets. Some objects also lack proper cleanup routines and persist across saves even after being dropped.
If you’re experimenting here, isolate it to a disposable save file and never overwrite your main progression slot.
Inventory Limits, Weight, and Stack Behavior
Console-spawned items ignore carry weight at the moment of creation, but the game recalculates load immediately afterward. This can instantly over-encumber Henry without warning.
Stackable items like arrows, food, or alchemy ingredients sometimes spawn as separate stacks, which can confuse sorting logic. Manually consolidating stacks through inventory menus usually fixes this, but edge cases exist.
If your inventory UI starts behaving erratically after heavy spawning, reload the save rather than continuing to pile on items.
Best Practices for Safe Item Cheating
Spawn only what you need, then stop. Every injected item bypasses systems that other mechanics assume are intact, and problems often surface hours later, not immediately.
For build testing, spawn a single representative weapon or armor piece instead of full sets. For economy testing, add money instead of selling spawned loot, which avoids skewing vendor inventories and price curves.
If something breaks after item spawning, it’s rarely the game’s fault. Reload a clean save, adjust your approach, and treat the console like a scalpel, not a sledgehammer.
Skills, Perks, and Character Progression Commands: Levels, XP, Stats, and Build Testing
Once you move past item spawning, the next logical step is touching progression itself. Skills, perks, and stats are tightly interlocked in Kingdom Come: Deliverance 2, and the console gives you direct access to systems that normally take dozens of in-game hours to shape.
Used carefully, these commands are perfect for testing builds, validating perk synergies, or recovering from bugged XP gains. Used recklessly, they can desync perks, soft-lock skill trees, or leave Henry with stats the UI can’t correctly display.
How Character Progression Actually Works Under the Hood
KCD2 still runs on CryEngine’s layered progression model. XP feeds individual skills, skills feed levels, and levels unlock perk tiers that may modify hidden variables like stamina regen, damage multipliers, or dialogue checks.
The important thing to understand is that perks are not purely cosmetic flags. Many perks register callbacks when learned, and skipping those triggers by brute-forcing levels can leave bonuses inactive until the game refreshes the skill.
Because of this, adding XP is almost always safer than directly setting levels unless you’re doing controlled testing on a throwaway save.
Adding Skill XP Safely
The most stable progression command family revolves around XP injection. These simulate legitimate skill use without triggering every animation or condition tied to the action.
wh_pl_addexp [skill] [amount]
The skill parameter must match the internal skill ID, such as strength, agility, vitality, warfare, sword, bow, defense, speech, alchemy, herbalism, lockpicking, stealth, hunting, horsemanship, or maintenance. XP values scale aggressively at higher levels, so small numbers go a long way.
This method correctly triggers level-ups, perk unlock thresholds, and UI refreshes, making it ideal for natural-feeling progression or restoring lost XP after a bugged quest.
Directly Setting Skill Levels
For build testing, speedrunning theorycraft, or mod validation, you may want to bypass XP entirely. That’s where direct level assignment comes in.
wh_pl_setlevel [skill] [level]
This instantly forces a skill to a specific level, regardless of prior XP. The downside is that perks tied to earlier thresholds may not auto-unlock or initialize properly until the skill is used or the game reloads.
If perks don’t appear after setting a level, gain a small amount of XP in that skill or reload the save to force a recalculation.
Primary Stats: Strength, Agility, Vitality, and Speech
Core attributes still underpin everything from weapon handling to dialogue checks. These stats influence derived values like carry weight, stamina pool, and persuasion rolls.
wh_pl_setstat [stat] [value]
wh_pl_addstat [stat] [value]
Valid stat names include strength, agility, vitality, and speech. Values outside normal progression ranges can work, but extreme numbers may cause animation oddities or stamina bugs, especially in combat.
If you’re testing heavy armor or high-DPS melee builds, adjust strength and vitality first before touching combat skills.
Perks: Unlocking, Resetting, and Testing Synergies
Perks are where most builds live or die. They’re also one of the easiest systems to break if you don’t respect activation order.
wh_pl_setperk [perk_id] 1
wh_pl_setperk [perk_id] 0
Setting a perk to 1 unlocks it; 0 removes it. Perk IDs must match internal names, not the localized perk titles shown in menus, which makes trial and error unavoidable unless you’re referencing perk lists from game files or mods.
There is also a global reset command used internally for testing.
wh_pl_resetperks
This wipes all perk selections and refunds perk points. Use this only after backing up your save, as perk dependencies can behave unpredictably if you’ve force-leveled skills beforehand.
Combat Skills and Weapon-Specific Progression
Weapon skills like sword, axe, mace, unarmed, and bow scale independently and feed directly into hit chance, stamina drain, and combo execution windows.
Adding XP here is far safer than setting levels, especially for melee weapons, since many combat perks register timing and animation modifiers that expect proper initialization.
For bow testing in particular, artificially high levels can break sway calculations. Increment gradually and test in live combat scenarios.
Build Testing Without Breaking Your Save
The cleanest workflow is to start with a fresh save, add XP to reach target levels, manually select perks, then test. Avoid mixing direct level setting with perk forcing unless you know exactly which perks rely on passive hooks.
If you’re comparing builds, document your stat and perk states externally. Reload between tests rather than respecing repeatedly, which reduces the risk of hidden modifiers stacking incorrectly.
Above all, treat progression commands like precision tools. They’re unmatched for experimentation, but they demand discipline if you want reliable results.
World, Time, and Systems Control: Time Skips, Weather, Fast Travel, and Event Triggers
Once your character build is locked in, the next layer of mastery is the world itself. Kingdom Come: Deliverance 2 runs on tightly interlinked systemic simulation, meaning time, weather, AI schedules, and quest logic all talk to each other. Console commands here are less about raw power and more about control, letting you test encounters, bypass grind-heavy downtime, or recover a save that’s soft-locked by world state bugs.
This is also where players accidentally break things. Unlike stats or perks, world commands can affect every NPC and script currently loaded, so restraint matters.
Time Control: Skipping, Setting, and Freezing the World Clock
Time drives nearly everything: NPC routines, shop inventories, crime reporting, hunger, fatigue, and even some quest triggers. The most commonly used command is a straight time skip.
wh_time_skip [hours]
This advances the global clock by the specified number of in-game hours. It’s safer than hard-setting time because it allows scripts to resolve naturally as time passes.
For precise testing or quest troubleshooting, you can directly set the time.
wh_time_set [hour] [minute]
This instantly moves the world to a specific time of day. Use this sparingly, as jumping over scripted windows can prevent certain events from initializing.
There is also a freeze toggle used for internal testing.
wh_time_freeze 1
wh_time_freeze 0
Freezing time pauses daily AI schedules and environmental updates while still allowing player movement. It’s useful for combat testing or cinematic screenshots, but leaving it enabled during quests can desync NPC behavior.
Weather and Environmental Simulation
Weather isn’t just visual flair. Rain affects visibility, NPC perception, noise generation, and even some combat edge cases. For controlled testing, you can override the weather system.
wh_weather_set [weather_id]
Weather IDs are internal values such as clear, cloudy, rain, storm, or fog. The exact naming depends on the build and can vary, so experimentation or mod documentation helps here.
To return control back to the dynamic weather system, reload the area or skip time forward. Permanent weather locks can cause lighting and audio bugs if left active across multiple regions.
Fast Travel, Teleportation, and Map Navigation
Fast travel in KCD2 is heavily restricted by narrative state, enemy presence, and stamina simulation. The console bypasses all of that.
wh_rpg_fasttravel [location_id]
This triggers fast travel logic without using the map UI. It respects loading boundaries but ignores most restrictions, making it ideal for quest testing.
For absolute control, direct teleportation is available.
wh_rpg_teleport [x] [y] [z]
This instantly moves Henry to world coordinates. It’s powerful, but dangerous. Teleporting into unloaded or invalid geometry can soft-lock your save or drop you under the map.
When testing quests, it’s safer to fast travel first, then teleport short distances within a loaded cell.
Event Triggers and Quest State Manipulation
Advanced users and modders often need to manually trigger world events or quest logic, especially when scripts fail to fire correctly.
wh_event_trigger [event_id]
This forces a specific world or quest event to execute. Event IDs are entirely internal and usually pulled from game files or community documentation.
There are also quest-state helpers used during debugging.
wh_quest_complete [quest_id]
wh_quest_fail [quest_id]
These commands brute-force quest outcomes without running intermediate objectives. They should only be used to recover broken progression, not for normal play, as they can skip reputation changes, rewards, or follow-up triggers.
AI Schedules, World Resetting, and Safety Warnings
Some world commands affect NPC brains directly, which is where things get risky.
wh_ai_reset
This reloads AI states and schedules for nearby NPCs. It’s useful when characters freeze or loop animations, but it can interrupt combat or scripted dialogue mid-execution.
Whenever you manipulate time, weather, or events, assume achievements are disabled for that session and that save corruption is possible. Always back up your save before heavy world testing, especially if you’re chaining commands.
Treat these tools like a level designer would. Used carefully, they turn KCD2 into a sandbox for experimentation. Used recklessly, they turn a perfectly good save into a medieval horror story.
AI, NPC, and Quest Debug Commands: Fixing Broken Quests, NPC States, and Combat Behavior
Once you start forcing events or skipping objectives, the weakest link is almost always AI logic. Kingdom Come: Deliverance 2 runs layered NPC brains on top of CryEngine schedules, and when those desync, you get frozen quest givers, immortal bandits, or guards stuck in infinite aggro loops.
This is where AI and quest debug commands become less of a cheat and more of a repair kit. Used correctly, they can salvage dozens of hours on a bugged save without restarting the campaign.
Resetting NPC Behavior and Broken AI States
When an NPC stops responding, refuses to talk, or gets locked into the wrong animation, their AI state is usually stuck.
wh_ai_reset
This refreshes AI logic, daily schedules, and behavior trees for nearby NPCs. It’s the first command you should try if a character won’t advance dialogue or won’t exit combat stance after a fight.
Be careful using it during active quests. Resetting AI mid-script can cancel conversations, interrupt escorts, or despawn temporary quest NPCs if they’re not flagged as persistent.
Forcing NPC Aggro, Calm, and Combat Resolution
Combat bugs are common after teleporting or forcing events, especially when enemy groups lose their leader or target reference.
wh_ai_clear_aggro
This command wipes hostility from nearby NPCs. It’s extremely useful if guards remain aggressive after serving jail time or if bandits keep chasing you across cells with no line of sight.
If combat encounters refuse to end, this effectively hard-resets the fight state without killing NPCs or affecting reputation systems.
Respawning and Reloading NPCs
Sometimes an NPC simply vanishes, falls through the map, or dies when they shouldn’t.
wh_npc_respawn
This forces missing NPCs to reload at their default spawn location. Quest-critical characters often reappear after this, though their dialogue may reset to an earlier state.
Do not use this on companions or scripted followers mid-quest. Respawning them can break escort logic or permanently detach them from the quest chain.
Quest Objective and State Debugging
If a quest marker won’t update or an objective refuses to complete, the underlying state machine is usually stalled.
wh_quest_complete [quest_id]
wh_quest_fail [quest_id]
These commands forcibly resolve quests without checking objectives. They’re lifesavers for progression blockers, but they bypass reward scripts, reputation changes, and follow-up events.
A safer alternative when available is triggering the missing event directly.
wh_event_trigger [event_id]
This replays the exact logic that should have fired naturally, preserving downstream quest behavior. The downside is that event IDs aren’t exposed in-game, so you’ll need modding tools or community lists to identify them.
Resetting World AI and Encounter Systems
For deeper issues involving multiple NPCs or entire locations behaving incorrectly, a broader reset is sometimes necessary.
wh_ai_reset
Used again here intentionally, this command also refreshes encounter logic and patrol routes. It can fix towns where guards stop enforcing laws or camps where enemies never respawn.
Expect side effects. Resetting AI globally can interrupt background simulations, including crime reporting, sleeping schedules, and scripted ambient events.
Critical Warnings for Quest and AI Debugging
AI and quest commands interact directly with systems never meant to be player-facing. Achievements are typically disabled for the session once these are used, and some changes are written permanently to your save.
Always hard-save before touching quest states or AI resets. If something goes wrong, there is no undo, and autosaves will happily overwrite your last stable checkpoint.
Think like a developer. Fix the smallest broken piece first, test the result, then escalate. That discipline is the difference between rescuing a save and turning Bohemia into a very angry, very broken medieval sandbox.
Stability, Save Safety, and Achievement Risks: What Can Break Your Game and How to Recover
By this point, you’ve seen how powerful Kingdom Come: Deliverance 2’s console really is. That power cuts both ways. The same commands that rescue a soft-locked quest can also quietly poison a save hours before the damage becomes visible.
Understanding what actually breaks the game, how achievements are flagged, and how to recover when things go wrong is the difference between controlled experimentation and a dead campaign.
How Console Commands Affect Save Integrity
Not all commands are equal. Visual tweaks, camera controls, and read-only debug queries are usually safe, while anything that modifies quest states, AI logic, inventories, or character stats writes directly into the save file.
Once written, those changes persist even if you disable the console later. Reloading an earlier autosave won’t help if that autosave already inherited corrupted state data.
The most dangerous commands are the ones that skip logic rather than resolve it. Forcing completion, teleporting NPCs mid-script, or spawning items tied to quests can leave invisible flags permanently misaligned.
Commands Most Likely to Corrupt or Destabilize Saves
Quest resolution commands like wh_quest_complete and wh_quest_fail are the highest risk. They bypass reward distribution, reputation updates, and conditional follow-ups that future quests expect to find.
Global AI commands, including wh_ai_reset, can also destabilize long-running saves. They rebuild behavior trees and schedules, but they don’t always rebind story-critical NPCs correctly.
Aggressive stat editing, such as pushing skills, perks, or reputation far beyond intended ranges, can break scaling systems. Combat AI, perk triggers, and economy balance all rely on expected value ranges.
Achievement Disabling: What Actually Triggers It
Achievements in Kingdom Come: Deliverance 2 are session-flagged, not permanently disabled. The moment you use most gameplay-altering console commands, the game marks that session as ineligible for achievements.
Restarting the game clears the session flag, but only if the save itself wasn’t altered in a way the achievement system detects. If a command permanently modifies tracked progression, that achievement may be unobtainable on that save.
Cosmetic commands and diagnostic reads usually don’t trip the flag. Quest manipulation, inventory spawning, skill edits, and AI overrides almost always do.
Best Practices for Safe Console Use
Hard-save manually before every console experiment. Do not rely on autosaves, and never overwrite your last known stable save.
Use incremental testing. Apply one command, exit the console, play for a few minutes, and confirm nothing else broke before stacking changes.
When possible, prefer event triggers over forced completion. Triggering missing logic preserves downstream systems far better than brute-forcing outcomes.
Recovering a Broken Save
If a save starts behaving strangely, stop immediately. Continuing to play can bake the corruption deeper into world simulation data.
Reload the last clean hard save and avoid repeating the same command sequence. If no clean save exists, try isolating the damage by reverting recent actions and avoiding global resets.
As a last resort, community save editors and modding tools can sometimes repair flags manually, but this requires CryEngine familiarity and is never guaranteed.
Final Tip Before You Go Full Power User
Treat the console like a developer tool, not a cheat menu. Use it to diagnose, correct, and experiment, not to bulldoze systems you don’t fully understand.
Kingdom Come: Deliverance 2 thrives on interconnected mechanics, and every shortcut has ripple effects. Respect the simulation, keep clean backups, and the console will turn a fragile medieval RPG into one of the most flexible sandboxes on PC.