Kingdom Come: Deliverance doesn’t advertise it, but beneath its ultra-hardcore medieval sim veneer is a fully functional developer console inherited from CryEngine. This console is the pressure valve for a game that prides itself on realism but isn’t immune to bugs, brutal RNG, or time-warping save corruption. Used correctly, console commands don’t cheapen the experience; they let you take control when the systems push back too hard.
For PC players especially, console commands act like a diagnostic toolkit. They can restore broken quests, undo soft-locks, test builds, or simply let you bypass grind-heavy systems after your tenth reload. Think of them less as cheats and more as surgical tools for a game that’s as unforgiving as it is ambitious.
How to Enable and Use the Console
The console in Kingdom Come: Deliverance is accessed by pressing the tilde key, usually located just below Esc. On some keyboard layouts, it may be the grave key or require a language switch to register properly. When it opens, you’ll see a simple command line overlay where you can type instructions directly into the engine.
Most commands execute instantly after pressing Enter, with no confirmation prompt and no safety net. That immediacy is powerful but dangerous, especially when modifying stats or quest states. Always hard-save before experimenting, because some changes are permanent within that save file.
Core Utility Commands You’ll Use the Most
A handful of commands form the backbone of most console use. “wh_cheat_money X” instantly grants Groschen, making it invaluable for testing gear builds or skipping late-game economy grind. “wh_rpg_getLocation” helps diagnose quest bugs by showing your exact position data, which is critical when NPC triggers fail.
Another staple is “cheat_set_wanted_level=0,” which clears guards’ aggro instantly. If you’ve ever been chain-arrested due to a stolen item bug or broken witness logic, this command is a lifesaver. It doesn’t erase crimes in the narrative sense, but it restores playability.
Stat and Skill Manipulation
Commands like “wh_rpg_setstat” allow direct manipulation of core attributes such as Strength, Agility, Vitality, and Speech. These are best used for testing combat thresholds, dialogue checks, or rebuilding a character after a mod conflict wipes progression. They bypass normal XP curves entirely, so using them casually will flatten the game’s difficulty fast.
Skill-level commands are especially useful when the game fails to register training or book bonuses correctly. If your Warfare or Defense stalls due to a known bug, manually correcting it is often cleaner than grinding random encounters. Just remember that enemy scaling doesn’t adjust dynamically, so overleveling breaks encounter balance.
Item Spawning and Inventory Fixes
The “wh_cheat_addItem” command lets you spawn any item in the game using its internal ID. This is essential for restoring lost quest items, bugged armor sets, or unique weapons that vanish during cutscenes. It’s also how modders test loadouts without replaying hours of content.
That said, item spawning can wreck progression if abused. High-tier plate armor trivializes early combat, eliminating stamina management and directional strikes entirely. Use this command to recover or experiment, not to skip the learning curve that the combat system demands.
Combat, Health, and Survival Tweaks
For troubleshooting combat bugs, commands that affect health and stamina are invaluable. “cheat_set_state immortal=1” allows you to test encounters without dying, useful for diagnosing animation lockups or AI behavior. You can also heal Henry instantly if a bleed or poison effect refuses to clear.
These commands are best reserved for testing or escaping broken encounters. Using them to brute-force fights removes the tension that makes Kingdom Come’s combat so distinctive. Directional blocking, stamina drain, and clinch mechanics lose meaning when death is off the table.
Quest Progression and Debug Commands
Quest-related console commands are the most dangerous but also the most necessary. When an NPC fails to spawn or a trigger doesn’t fire, advancing or resetting a quest stage can save an entire playthrough. These commands interact directly with the game’s scripting layer, bypassing normal checks.
The risk is sequence-breaking the narrative. Advancing a quest incorrectly can lock out future objectives or break character schedules permanently. Only use quest commands when you’re truly stuck, and always document what you changed in case you need to roll back.
Limitations, Risks, and Responsible Use
Console commands disable achievements in many setups, especially when paired with mods. They can also create instability if used mid-cutscene or during scripted events. CryEngine doesn’t always validate state changes cleanly, which is why some effects persist longer than intended.
The smartest way to use console commands is reactively, not proactively. Fix what’s broken, test what’s unclear, and customize when the systems fail you. Kingdom Come: Deliverance rewards mastery, but it also respects players who know when to step behind the curtain and take control.
How to Enable the Developer Console (Steam Launch Options, Mods, and Verification)
Everything discussed so far hinges on one gatekeeper: the developer console itself. Kingdom Come: Deliverance doesn’t expose it by default, and Warhorse intentionally hid it to preserve immersion and progression. If you’re troubleshooting broken quests, testing mechanics, or recovering a save, enabling the console is the first and most important step.
The good news is that CryEngine still ships with a fully functional console under the hood. You just need to tell the game you’re allowed to use it.
Method 1: Steam Launch Options (Vanilla, No Mods)
The cleanest way to enable the console is through Steam’s launch options. This method works on a completely unmodded install and is the least likely to introduce instability.
Right-click Kingdom Come: Deliverance in your Steam library, select Properties, then find Launch Options. Add the following parameter exactly as written:
-devmode
Close the window and launch the game normally. This flag tells CryEngine to expose developer functionality, including the console and debug commands.
Opening the Console In-Game
Once the game is running, press the tilde key (~) to open the console. On some keyboard layouts, especially non-US keyboards, this may be the key under Escape or the key used for accents (such as ^ or `).
If the console opens as a transparent overlay at the top of the screen, the dev mode flag is working. If nothing happens, double-check the launch option spelling and keyboard layout before assuming it failed.
Method 2: Mods That Enable or Extend Console Access
Several community mods enable console access automatically or expand its functionality. These are useful if you want additional cheat menus, persistent commands, or safer toggles for testing.
Most console-related mods work by injecting config files or exposing prebuilt command bindings. They often live in the Mods folder and do not require the -devmode flag, though using both together is generally safe.
The tradeoff is control. Mods can silently disable achievements, override values you didn’t intend to change, or persist changes across saves. If you’re diagnosing a single broken quest, vanilla dev mode is usually the better option.
Verifying That the Console Is Fully Functional
Opening the console isn’t enough. You need to confirm that it’s actually accepting commands and returning feedback.
Type a harmless command like:
help
If the console returns a list of available commands or categories, you’re fully enabled. If it returns nothing or errors immediately, the game may be blocking command execution due to mod conflicts or incorrect launch parameters.
Common Issues and Fixes
If the console opens but closes instantly, the most common culprit is a conflicting mod or outdated config file. Temporarily remove mods and test again using only -devmode.
If commands work but achievements stop unlocking, that’s expected behavior in many setups. CryEngine flags developer states aggressively, especially when cheats or stat edits are detected.
Finally, avoid enabling the console mid-cutscene or during scripted quest moments. Even with dev mode active, CryEngine can mis-handle state changes during these sequences, leading to bugs that commands can’t easily undo.
Console Basics: Syntax, Parameters, Targeting, and Common Error Messages
Now that you know the console is live and responding, it’s time to understand how Kingdom Come: Deliverance actually interprets what you type. CryEngine’s console is powerful, but it’s also literal, unforgiving, and prone to silent failure if your syntax is even slightly off.
Think of console commands less like cheat codes and more like low-level instructions. You’re issuing direct orders to the engine, not asking it politely.
Command Syntax: How the Engine Reads Your Input
At its simplest, a command is structured as: command parameter value. Some commands need only the command itself, while others expect one or multiple parameters in a strict order.
For example, adding Groschen typically looks like:
wh_cheat_money 1000
There’s no equals sign, no parentheses, and no commas. Spaces separate arguments, and extra characters will usually cause the command to fail without explanation.
Case sensitivity is inconsistent. Most commands aren’t case-sensitive, but object IDs and certain stat references are. When in doubt, match the exact capitalization used in guides or the help list.
Parameters and Values: Numbers, Strings, and IDs
Parameters define what the command affects, and values define how much. Numeric values are the most common, especially for money, stats, or quantities.
Strings are used when referencing items, NPCs, or quests. These must be typed exactly as the engine expects, often using internal IDs rather than in-game names. Typing “Longsword” won’t work if the engine expects something like weapon_sword_long_01.
Item and quest IDs are where most players stumble. Kingdom Come exposes very little of this information in-game, so external lists, mod documentation, or trial-and-error are often required.
Targeting: Player, NPCs, and the World State
By default, most commands target Henry, the player character. That’s why stat, perk, and money commands usually work without extra qualifiers.
Targeting NPCs is more fragile. Some commands act on the NPC you’re currently looking at, others require a unique entity ID, and many simply don’t support NPC targeting at all. If you’re not sure, assume the command is player-only unless documented otherwise.
World-state commands, like time skips or weather changes, operate globally. These can have cascading effects on AI schedules, quest triggers, and aggro states, so use them sparingly, especially mid-quest.
Chaining and Repeating Commands
CryEngine does not support true command chaining with separators like semicolons. Each command must be entered and executed individually.
However, the console does remember previously entered commands. You can use the up and down arrow keys to cycle through your history, which is invaluable when testing values or correcting minor typos.
This also means mistakes persist. If you accidentally set a stat to an extreme value, the engine won’t warn you, and rolling it back requires knowing the original number.
Common Error Messages and What They Actually Mean
The most common response you’ll see is nothing at all. No confirmation, no error, just silence. In Kingdom Come, silence usually means the command wasn’t recognized or failed validation.
If you see “Unknown command,” the command name itself is wrong or unavailable in your current build. This can happen after patches or when using commands pulled from outdated guides.
“Invalid parameter” means the command exists, but one of the arguments doesn’t. This is often caused by typos in item IDs, missing values, or passing a string where a number is expected.
Silent Failures and Hidden Restrictions
Some commands are context-sensitive and will fail if used at the wrong time. Trying to complete or advance a quest step during a cutscene or scripted conversation is a common culprit.
Other commands are quietly blocked to prevent hard crashes. Quest manipulation, in particular, is heavily guarded. The console may accept the input but refuse to apply it if the engine detects a broken state.
When diagnosing issues, always test commands in a neutral state: standing still, out of combat, not in dialogue, and ideally after a manual save.
Using the Help Command Effectively
Typing help without arguments dumps a massive list, but it’s more useful when narrowed down. Some builds support help followed by a category or partial command name, which can reveal related functions.
Even when a command appears in the help list, it’s not guaranteed to be fully functional. Some are legacy hooks, debug-only remnants, or partially implemented tools left over from development.
Treat help as a map, not a promise. The real test is whether the command produces a tangible result in-game.
Why Precision Matters in Kingdom Come
Unlike more arcade-style RPGs, Kingdom Come ties systems together aggressively. Stats affect combat timing, perks influence dialogue checks, and quest flags can alter entire regions’ behavior.
A single sloppy command can unbalance progression, break immersion, or soft-lock content hours later. That doesn’t mean you shouldn’t experiment, but it does mean you should understand exactly what you’re telling the engine to do.
Mastering console basics isn’t about cheating faster. It’s about controlling a complex simulation without accidentally tearing it apart.
Essential Quality-of-Life Commands (Money, Weight, Saving, Fast Travel, Time Control)
Once you understand how fragile Kingdom Come’s systems can be, quality-of-life commands become less about cheating and more about damage control. These are the tools players use to recover broken saves, test builds, or strip away time-wasting friction without rewriting the entire simulation.
Used carefully, these commands let you experiment freely while keeping the game’s deeper mechanics intact.
Money Control: Skipping the Early-Game Grind
If you’ve already proven you can survive Skalitz with a club and bad armor RNG, repeating the early money grind isn’t sacred. The most reliable way to inject Groschen directly into Henry’s purse is:
cheat_add_money 1000
The number is fully adjustable, and the money is added cleanly with no vendor flags or stolen status. This avoids issues tied to spawning high-value items that can confuse merchants, economy balance, or quest triggers.
Avoid extreme values unless you’re stress-testing perks or dialogue checks. Flooding the economy can trivialize reputation-based systems and undercut skill progression tied to trading.
Weight and Inventory: Breaking the Encumbrance Ceiling
Encumbrance is one of Kingdom Come’s most aggressive realism mechanics, and also one of its most frustrating during crafting, looting, or mod testing. To bypass it instantly, use:
player.setweight 0
This effectively nullifies carry weight, letting you move at full speed regardless of inventory mass. It’s ideal for bulk looting, alchemy sessions, or diagnosing item bugs without constantly dumping gear.
Be aware that setting weight too low for long stretches can distort stamina drain and movement pacing. If you care about balance, toggle it temporarily rather than leaving it active for an entire playthrough.
Saving Without Saviour Schnapps
Few systems spark more debate than Kingdom Come’s save restrictions. Whether you’re debugging a quest or testing combat scenarios, relying on consumable saves can slow everything down.
The cleanest manual save command is:
wh_sys_save
This triggers a full, legitimate save identical to sleeping or using Schnapps, without touching inventory. It’s the safest way to protect yourself before running experimental commands or entering unstable quest states.
Make a habit of saving before and after console use. CryEngine does not forgive experimentation without backups.
Fast Travel Overrides and World Movement
Fast travel can be disabled by quests, combat states, or scripted restrictions, sometimes longer than intended. If the system gets stuck, you can re-enable it manually with:
cheat_allow_fast_travel 1
This doesn’t teleport you or skip encounters. It simply restores access to the fast travel map when the game refuses to cooperate.
Do not use this to bypass active quest sequences on purpose. Fast travel during the wrong narrative window can desync objectives or skip critical triggers entirely.
Time Control: Forcing Day, Night, and Testing Schedules
Time governs everything in Kingdom Come, from NPC routines to crime detection and quest availability. When you need precise control, two commands matter most.
To set the time directly, use:
wh_time_set 12
The number corresponds to the hour of the day, making it perfect for forcing daylight, curfews, or shop hours. For more extreme testing, time progression itself can be frozen or restored with:
wh_time_speed 0
wh_time_speed 1
Freezing time is invaluable for scouting, stealth testing, or diagnosing NPC behavior without schedules shifting underneath you. Just remember to re-enable it, or the world will remain permanently suspended.
These commands don’t just save time. They give you control over a simulation that otherwise assumes you’ll always play by its rules, even when those rules malfunction.
Character & Stat Manipulation Commands (Skills, Perks, Health, Stamina, and Level Scaling)
Once you’ve taken control of time and movement, the next logical step is Henry himself. Kingdom Come’s progression is deliberately slow, tied to repetition, RNG, and survival pressure, which is immersive until you’re testing builds, recovering a broken save, or replaying content for the third time. Console commands let you bypass the grind without dismantling the game’s underlying systems, if you know exactly what to touch.
This is where restraint matters. Changing stats mid-playthrough won’t instantly break the game, but overcorrecting can trivialize combat, soft-lock perk progression, or invalidate quest checks that assume natural skill growth. Always save before experimenting, and adjust incrementally rather than maxing everything in one go.
Player Level and Core Attributes
Henry’s overall level is derived from his main stats, not set independently, which means direct level-setting commands don’t exist. Instead, you manipulate Strength, Agility, Vitality, and Speech, and the character level recalculates automatically behind the scenes.
To directly modify an attribute, use:
player.setstat strength X
player.setstat agility X
player.setstat vitality X
player.setstat speech X
Replace X with the desired value. Values between 10 and 20 are considered high but still “legit” by the game’s balancing logic. Pushing past 20 can cause exaggerated stamina pools, absurd carry weight, and combat outcomes that skip intended hit reactions.
Strength directly affects melee damage and encumbrance. Agility governs speed, stealth effectiveness, and weapon handling. Vitality is the backbone of stamina regen and survivability, while Speech controls dialogue checks and reputation outcomes.
Skill Manipulation (Combat, Stealth, Crafting, and Social)
Skills can be raised or lowered individually, which is ideal for testing perk synergies or correcting a build that went sideways. The command structure mirrors attribute editing but targets specific skill trees.
For example:
player.setskill sword X
player.setskill bow X
player.setskill stealth X
player.setskill alchemy X
player.setskill lockpicking X
Every skill caps at 20 under normal play. Setting a skill above that may display correctly in the UI, but perks tied to those thresholds can fail to unlock or behave inconsistently.
Combat skills influence hit chance, stamina drain, and animation recovery windows. Raising Sword or Axe skill doesn’t just boost DPS, it tightens attack chains and reduces the punishment for mistimed strikes. Stealth and Lockpicking are especially sensitive; even small increases dramatically change detection cones and minigame tolerance.
Perks: Unlocking Without Leveling
Perks are normally gated behind skill thresholds and level-ups, but the console allows you to bypass those requirements entirely. This is powerful, but also the easiest way to break internal progression if abused.
To add a perk directly, use:
player.addperk perk_name
Perk names must be entered exactly as defined internally, which means some experimentation or external reference is required. Not all perks are safe to add early, particularly those that modify core systems like stamina regeneration, bleeding, or combo windows.
Avoid stacking mutually exclusive perks or adding perks tied to tutorials you’ve already skipped. The game doesn’t always reconcile those flags cleanly, and you can end up with perks that exist but never trigger.
Health, Stamina, and Survival Values
Health and stamina are dynamic systems influenced by Vitality, injuries, hunger, and exhaustion. You can override them directly, but doing so repeatedly can mask underlying problems like permanent debuffs or bugged injuries.
To restore values instantly, use:
player.setstat health X
player.setstat stamina X
Setting health above your natural maximum will often snap back down once the game recalculates, especially after combat or sleep. Stamina behaves more predictably but can still desync if time is frozen or perks are added mid-session.
If you’re troubleshooting a stuck injury or testing endurance-heavy combat, temporarily boosting Vitality is usually safer than hard-setting raw values. It keeps regeneration logic intact and avoids strange UI behavior.
Experience Scaling and Responsible Power Curve Control
Kingdom Come is extremely sensitive to power spikes. Raising multiple skills at once can cause enemy AI to underperform, especially in early zones where bandits and guards are balanced around low-stat Henry.
If your goal is testing or recovery rather than domination, raise one stat or skill at a time, then play for a few minutes to let the simulation stabilize. Watch stamina drain, enemy reactions, and perk triggers before committing further changes.
The console is a scalpel, not a nuke. Used carefully, these commands let you fine-tune Henry into the exact build you want, whether that’s a speech-focused noble, a stealth assassin, or a combat monster designed purely to stress-test the game’s systems.
Items, Gear, and Inventory Commands (Spawning Weapons, Armor, Consumables, and Quest Items)
Once you start manipulating stats and perks, inventory control becomes the next pressure point. Kingdom Come’s economy, equipment progression, and quest logic are tightly intertwined, and brute-forcing items can destabilize balance faster than raw skill boosts.
Used responsibly, item commands are invaluable for recovering lost quest gear, testing builds, or bypassing grind-heavy repair and crafting loops. Used carelessly, they can break quest states, overload encumbrance calculations, or introduce items the world isn’t ready to acknowledge yet.
How Item Spawning Works Under the Hood
Kingdom Come uses internal item IDs tied to CryEngine entity templates. The console doesn’t care where an item “should” come from, only whether the ID exists and whether Henry has inventory space to receive it.
The core command you’ll use is:
wh_cheat_addItem ItemID Quantity
ItemID must be exact, including capitalization. Quantity is optional but defaults to 1, which is ideal for weapons and armor to avoid duplication bugs.
If nothing appears, the item either doesn’t exist in the current build, is gated behind a quest flag, or you mistyped the ID. The console won’t warn you when this happens, so always double-check.
Spawning Weapons for Testing or Recovery
Weapons are generally safe to spawn, especially common swords, axes, maces, and bows. This is useful if a quest weapon despawned, broke permanently due to a bug, or you want to compare DPS and stamina drain across weapon types.
Example:
wh_cheat_addItem longsword_herodsword 1
After spawning, re-equip the weapon through the inventory menu rather than hot-swapping mid-combat. This forces the game to correctly recalculate reach, combo availability, and stamina modifiers.
Avoid spawning unique or narrative-critical weapons before their associated quest triggers. The weapon may function mechanically, but the quest may never recognize it as valid.
Armor, Clothing, and Encumbrance Pitfalls
Armor pieces, especially layered gear like gambesons and chausses, interact heavily with visibility, noise, and stamina regen. Spawning full plate early can trivialize combat while silently breaking stealth systems you’re not expecting to affect.
Example:
wh_cheat_addItem plate_cuirass_milanese 1
After adding armor, open the character screen and wait a few seconds. This allows the game to recalculate armor ratings, noise values, and encumbrance thresholds, which can otherwise lag behind reality.
If Henry suddenly moves slower or drains stamina faster than expected, check total weight. Encumbrance penalties stack aggressively and aren’t always obvious at a glance.
Consumables, Potions, and Alchemy Shortcuts
Consumables are among the safest items to spawn, making them ideal for players testing combat scenarios or recovering from failed experiments. Potions obey normal cooldowns and perk interactions even when spawned.
Example:
wh_cheat_addItem potion_saviour_schnapps 5
This is especially useful for modders or testers who need rapid iteration without replaying large sections. That said, overusing savior schnapps can desync the save system if you’re also manipulating time or quest states.
Food items can also be spawned, but hunger recalculation may lag. If nourishment values don’t update immediately, wait or sleep to force a system refresh.
Money, Groschen, and Economic Control
Groschen is technically just another item, and it’s handled the same way. This makes money injection simple, but also dangerously tempting.
Example:
wh_cheat_addItem money 1000
Inflating wealth too early can break vendor progression and reputation pacing. Armorers and swordsmiths become irrelevant when you can instantly buy their top-tier stock, which cascades into combat balance issues.
If your goal is recovery rather than domination, add only what you lost. The economy in Kingdom Come is a progression system, not just a currency check.
Quest Items and Why They’re Risky
Quest items are where things get volatile. Many are tied to invisible flags that only trigger when acquired through scripted events.
Spawning a quest item may give you the object, but not the state the quest expects. This can result in NPCs acting as if you don’t have the item, or worse, soft-locking the quest entirely.
If a quest item was lost due to a bug, try reloading an earlier save first. Only spawn quest items as a last resort, and be prepared for inconsistent behavior.
Inventory Cleanup and Best Practices
The console doesn’t provide a clean item removal command, so inventory mistakes are harder to undo than stat changes. Selling, dropping, or storing unwanted items is safer than trying to overwrite them.
Spawn items one at a time, then open and close the inventory to force synchronization. This reduces the chance of ghost items or mismatched UI values.
Think of inventory commands as surgical tools. They’re perfect for testing, recovery, and controlled experimentation, but once you flood Henry’s pack with gear the game never intended him to carry, the simulation starts pushing back.
Combat, AI, and World State Commands (God Mode, NPC Behavior, Crime, Reputation, and Factions)
Once you move past inventory manipulation, console commands start touching the actual simulation layer of Kingdom Come: Deliverance. This is where combat math, NPC behavior, and the game’s reactive world systems live.
These commands are powerful, but they’re also the fastest way to destabilize a save if used recklessly. Treat them like developer toggles, not cheat codes you leave running permanently.
God Mode and Combat Overrides
God Mode is the most famous command for a reason. It disables incoming damage and effectively removes Henry from the combat equation, letting you test encounters, survive bugged fights, or bulldoze through unfair ambushes.
Example:
wh_cheat_godMode 1
Turning it off is just as important:
wh_cheat_godMode 0
God Mode doesn’t freeze stamina drain, bleeding, or status effects in every case. You can still get tackled, staggered, or locked into animations, which means positioning and AI behavior still matter even when you’re technically immortal.
AI Behavior and NPC Control
AI commands let you pause, disable, or reset NPC logic, which is invaluable when guards bug out, enemies get stuck in combat loops, or towns turn hostile for no clear reason.
Disabling AI globally is often used for testing or recovery:
ai_disable 1
Re-enable it immediately after:
ai_disable 0
While AI is disabled, NPCs won’t react, pathfind, or update schedules. Leaving it off for too long can desync daily routines, especially in towns where crime, reputation, and scripted events constantly evaluate NPC states.
Crime, Wanted Status, and Guard Aggro
Crime in Kingdom Come is a layered system involving witnesses, regional reputation, and guard awareness. Clearing a wanted state can save a playthrough if the game incorrectly flags Henry as hostile.
A commonly used recovery command is:
cheat_clearwanted
This clears active pursuit and guard aggression, but it doesn’t always reset underlying reputation penalties. If guards remain suspicious after clearing wanted status, leave the area, sleep, or wait to force a world-state refresh.
Reputation Manipulation and Social Systems
Reputation governs prices, dialogue options, and whether NPCs treat you as a hero or a liability. Console commands can directly override this, but doing so skips dozens of invisible checks the game normally tracks.
Example structure often used by modders:
wh_cheat_setReputation faction value
Faction names and valid values aren’t always exposed cleanly, and incorrect inputs may silently fail. Use reputation boosts to recover from bugs or accidental mass hostility, not to max every region instantly.
Factions, Hostility, and World Alignment
Faction relationships dictate who attacks on sight, who calls guards, and who will even speak to you. Forcing faction alignment can fix broken hostility flags, but it can also erase carefully scripted tensions between groups.
Faction-level commands are best treated as experimental tools. Always test them on a manual save, then verify behavior by approaching guards, civilians, and enemies tied to that faction.
Changing faction states mid-quest is especially dangerous. Quests often assume hostility or neutrality at specific stages, and overriding that logic can cause objectives to stall or auto-fail.
Best Practices for Combat and World Commands
Never stack multiple world-altering commands at once. Toggle one system, test it in-game, then move on to the next.
If combat feels broken after using commands, reload the area by fast traveling or sleeping. CryEngine recalculates AI awareness and combat states during world transitions, which can fix lingering bugs.
Think of these commands as tools for diagnosis and recovery. They’re excellent for escaping broken encounters, clearing unfair crime flags, or testing combat scenarios, but the closer you push the game toward full sandbox control, the more fragile the simulation becomes.
Quest, Debug, and Recovery Commands (Fixing Broken Quests, Teleporting, and Softlock Prevention)
Once you start manipulating factions and world states, the next logical safety net is quest and recovery control. Kingdom Come: Deliverance is famously systemic, which also means it’s vulnerable to edge cases where scripts fail to fire, NPCs vanish, or objectives refuse to update. This is where console commands stop being cheats and start being essential tools.
These commands are best treated like a dev kit. They won’t fix every bug, but they can pull a save back from the brink when the alternative is losing dozens of hours.
Enabling Console Access and Safe Usage
On PC, the console is opened with the tilde key (~). For advanced quest and debug commands, the game must be launched with the -devmode parameter in Steam’s launch options, otherwise many commands will silently do nothing.
Always create a manual save before touching quest or debug commands. CryEngine does not always validate state changes, and a single bad flag can permanently block progression. Think of each command as a scalpel, not a hammer.
Teleportation Commands (Escaping Terrain Traps and Missing NPCs)
Teleporting is the fastest way to recover from physics bugs, stuck mounts, or falling through the map. The most reliable command is:
goto x y z
This instantly moves Henry to exact world coordinates. Coordinates can be pulled from community maps or debug readouts, making this ideal for returning to quest locations that failed to load correctly.
For NPC-related issues, entity teleporting is safer than raw coordinates:
wh_cheat_teleport_to_entity entity_name
This is invaluable when a quest giver spawns under the terrain, inside a wall, or miles away due to AI pathing failure. If the entity name is incorrect, the command will fail without feedback, so double-check spelling.
Quest State Manipulation and Objective Recovery
Broken quests are usually caused by a missed trigger, not the entire quest collapsing. In many cases, forcing the quest to reinitialize is enough to restore progress.
Commands like:
cheat_start_quest quest_id
cheat_complete_quest quest_id
can brute-force progression, but they are extremely dangerous mid-quest. Skipping stages can prevent rewards, break follow-up quests, or permanently remove NPCs from the world.
A safer approach is using these commands only when a quest is clearly unrecoverable, such as an objective that will not update despite meeting conditions multiple times. If possible, advance only one stage, test, then continue.
Debugging NPC AI and World States
When NPCs refuse to talk, move, or acknowledge objectives, the problem is often AI state desync rather than quest logic. CryEngine tracks awareness, schedules, and priorities separately from quests.
Forcing a soft reset can help:
ai_debug_draw 0
ai_debug_draw 1
Toggling AI debug forces recalculation of awareness and behavior trees. Pair this with sleeping or fast traveling to reload the area and clear stuck states.
If guards, quest NPCs, or enemies remain frozen, leaving the region and returning after a time skip often resolves the issue without touching quest flags.
Softlock Prevention and Emergency Recovery
Some softlocks aren’t obvious. Being stuck in combat state, flagged as trespassing forever, or locked in a dialogue loop can all halt progression.
Emergency recovery commands include restoring health, stamina, or consciousness if Henry is downed in an unwinnable scenario:
cheat_set_health value
cheat_set_energy value
These won’t fix the underlying bug, but they let you escape the immediate lock and reposition. Pair recovery with teleportation and a world reload to stabilize the simulation.
If all else fails, console commands can be used to salvage a playthrough long enough to reach the next autosave checkpoint. That alone can be the difference between abandoning a save and finishing a 100-hour run.
Used carefully, quest and debug commands are not about skipping content. They’re about preserving the integrity of a playthrough when the game’s systems turn against themselves.
Limitations, Risks, and Best Practices (Achievements, Save Integrity, Mods, and Responsible Use)
Console commands are a powerful safety net, but they are not a free pass. Kingdom Come: Deliverance was built around layered simulation systems, and forcing one layer to behave can destabilize others. Understanding where commands help and where they harm is the difference between saving a playthrough and silently corrupting it.
Achievements and Progression Flags
On PC, using console commands does not globally disable achievements, but that doesn’t mean they’re safe. Many achievements rely on hidden progression flags, reputation values, or cumulative stats tracked over time. Spawning items, skipping quests, or force-completing objectives can prevent those flags from ever triggering.
Achievements tied to hardcore conditions, crime, reputation, or long-term stat growth are especially fragile. If you care about 100 percent completion, treat commands as a last-resort recovery tool, not a convenience shortcut. Always assume that brute-forcing progress carries invisible consequences.
Save Integrity and Long-Term Stability
The biggest risk with console use isn’t crashes, it’s delayed damage. A save can appear stable for hours before broken AI schedules, missing NPCs, or desynced quest states surface later. This is especially common after teleporting mid-quest or skipping scripted transitions.
Best practice is simple: manual save before every command session. If a fix works, keep playing for at least 10 to 15 minutes, change regions, and trigger a new autosave. If problems appear later, roll back immediately instead of compounding the damage.
Mods, Load Order, and Command Conflicts
Mods and console commands often touch the same systems, and they don’t always play nicely together. Economy overhauls, AI behavior mods, combat tweaks, and perk rebalances can override values you’re manually changing. This can lead to stats snapping back, perks failing to apply, or NPCs behaving inconsistently.
If you’re running mods, use commands sparingly and test one change at a time. Avoid mixing quest commands with heavily scripted mods unless the mod author explicitly supports it. When troubleshooting, temporarily disable mods to confirm whether the issue is systemic or mod-induced.
Responsible Use and Self-Imposed Rules
The healthiest way to use console commands is to define boundaries before you need them. Decide whether commands are for bug recovery only, experimentation on a test save, or limited quality-of-life fixes like undoing lost progress. Having rules prevents the slow slide into trivializing the game’s core systems.
Kingdom Come: Deliverance is designed around friction, preparation, and consequence. Removing all resistance can flatten the experience, even for hardcore players. Use commands to restore fairness, not erase challenge.
Final Advice Before You Open the Console
If a problem can be solved by sleeping, traveling, reloading, or waiting, do that first. If a command fixes something, stop and observe before stacking more changes. And if you’re ever unsure, back up your save and test on a duplicate.
Console commands are not cheating tools by default, they’re precision instruments. Used carefully, they can rescue broken quests, preserve long-running saves, and let you finish one of the most demanding RPGs ever made on your own terms.