Kingdom Come: Deliverance 2 is brutal, grounded, and unapologetically old-school—and that makes it a perfect candidate for modding. Whether you’re tired of getting your stamina shredded by chain combos or you just want cleaner UI feedback during high-stress fights, mods let you bend the rules without shattering the medieval immersion. The good news is that Warhorse has once again left the door open for PC players to tinker. The bad news is that not everything is fair game.
PC-Only, and Very Much by Design
Modding is strictly a PC feature. Consoles are locked down, and there’s no supported workaround, no matter how tempting it sounds. If you’re on Steam, GOG, or another PC storefront, you’re good to go as long as you’re comfortable touching game folders and reading mod descriptions carefully.
Warhorse hasn’t positioned mods as a fully curated, click-and-play ecosystem. Think of it less like Skyrim’s Creation Club and more like a traditional PC sandbox where responsibility sits with the player. That freedom is powerful, but it also means mistakes can break things fast.
What the Game Actively Supports
At a foundational level, Kingdom Come: Deliverance 2 supports data-driven mods. These are changes that tweak values, rebalance systems, adjust UI behavior, or replace assets without rewriting the game’s core logic. Expect things like combat stamina tuning, economy rebalances, perk adjustments, quality-of-life UI changes, and visual tweaks to be the most stable and common.
The game reads mods from a dedicated Mods directory, loading them on startup alongside the base data. When installed correctly, mods don’t overwrite vanilla files, which dramatically reduces the risk of corrupting your installation or saves. This structure also makes it easier to disable mods without reinstalling the entire game.
What’s Limited or Flat-Out Unsupported
Hard scripting changes are where the line gets drawn. Mods that try to introduce entirely new questlines, rewrite AI behavior at a deep level, or inject new mechanics that require custom code are either extremely unstable or simply not possible right now. There’s no official scripting API exposed for that kind of work.
Multiplayer-style features, online integrations, or anything that alters DRM, achievements, or executable-level behavior are off-limits. If a mod description mentions editing the .exe or bypassing systems, that’s a red flag and a hard skip if you care about stability.
Save Files, Stability, and Performance Realities
Most lightweight mods are save-safe, especially those that adjust values or UI elements. The risk spikes when you remove mods mid-playthrough, particularly ones that touch perks, progression, or world data. Best practice is to treat your mod list like a loadout: lock it in before committing to a long campaign.
Performance is another trade-off players underestimate. Visual mods and reshade-style enhancements can hammer GPU performance, especially during dense towns or large-scale encounters. If your frame rate is already flirting with the edge, mods won’t magically fix that unless they’re specifically designed for optimization.
Why Reading Mod Descriptions Actually Matters
Kingdom Come: Deliverance 2 mods live and die by compatibility. Two mods that touch the same system, like stamina regen or armor values, can silently conflict and leave you wondering why combat suddenly feels broken. Authors usually call this out, but only if you slow down long enough to read.
This isn’t a game where you throw fifty mods into a folder and hope for the best. Modding here rewards patience, backups, and a bit of discipline. Do that, and you’ll have a version of Bohemia that plays exactly the way you want—without turning your save file into a medieval crime scene.
Preparing Your Game for Modding: Clean Install, Backups, and Save Safety
Before you drop a single mod into your Kingdom Come: Deliverance 2 directory, you need to lock down a stable foundation. This is the unglamorous part of modding, but it’s also what separates a smooth, customized playthrough from a corrupted save and a full reinstall. Think of it as prepping your armor before a tournament—skip it, and you’ll feel every hit later.
Start With a Clean, Verified Install
If you’ve already experimented with mods, edits, or half-remembered tweaks, stop and reset. Use Steam or your platform’s verify integrity option to ensure every vanilla file is exactly where the game expects it to be. This clears out silent errors that can break mods before they even load.
A clean install doesn’t always mean reinstalling the entire game. If you’ve only added files to the Mods folder, verification is usually enough. But if you’ve edited config files or overwritten core assets, a full reinstall is the safest reset button.
Know Your Folder Structure Before Touching Anything
Kingdom Come: Deliverance 2 expects mods to live in a very specific place, typically a Mods folder inside the main game directory. Each mod should have its own subfolder, and inside that, the structure must mirror the game’s data layout exactly. If a mod’s files aren’t nested correctly, the game won’t throw an error—it’ll just ignore them.
Never drag loose files directly into the root directory unless a mod explicitly tells you to. That’s how you lose track of changes and make cleanup impossible later. Clean structure equals clean troubleshooting.
Back Up Saves Like Your Campaign Depends on It
Your save files are not stored in the main install directory, which is both a blessing and a trap. Locate your save folder and copy it somewhere safe before installing anything that touches progression, perks, or balance. Cloud saves are helpful, but they’re not a substitute for a manual backup you control.
This matters even more if you plan to test multiple mods. If a mod breaks your stamina curve, quest logic, or combat pacing, rolling back to a clean save is far faster than trying to undo the damage mid-playthrough.
Protect Your Config Files and User Settings
Mods that tweak UI, FOV, difficulty scaling, or camera behavior often interact with config files. Back these up alongside your saves so you can revert instantly if something feels off. A bad config edit won’t always crash the game—it can just quietly ruin combat feel or input response.
Keeping a labeled backup folder lets you experiment without fear. If a mod turns archery into a jittery mess or breaks controller detection, you’re two clicks away from sanity.
Create a Modding Baseline Before You Commit
Once your game is clean, backed up, and understood, launch it once in vanilla. Load a save, run around a town, enter combat, and confirm performance is stable. This baseline tells you exactly how the game behaves before mods enter the equation.
From here on out, add mods slowly and test often. Modding Kingdom Come: Deliverance 2 rewards players who treat their setup like a loadout, not a loot explosion.
Kingdom Come: Deliverance 2 Folder Structure Explained (Where Mods Actually Go)
With your vanilla baseline locked in, this is where modding either clicks instantly or quietly fails. Kingdom Come: Deliverance 2 is extremely strict about folder hierarchy, and it will not warn you if something’s wrong. If a mod doesn’t load, nine times out of ten it’s because the folder structure is off by one level.
Understanding where mods actually live is the difference between a smooth upgrade and wondering why nothing changed after booting the game.
The Core Rule: Mods Never Go in the Root Data Folder
Kingdom Come: Deliverance 2 loads mods from a dedicated Mods directory inside the main game install. You should never drop mod files directly into the Data folder unless a mod author explicitly tells you to do so.
On a standard Steam install, the path looks like this:
Steam\steamapps\common\KingdomComeDeliverance2\Mods
If the Mods folder doesn’t exist yet, create it manually. The game will recognize it automatically on launch.
Each Mod Gets Its Own Folder, No Exceptions
Inside the Mods directory, every mod must live in its own uniquely named folder. Think of this like loadout slots rather than dumping everything into one pile.
For example:
KingdomComeDeliverance2\Mods\BetterCombat
KingdomComeDeliverance2\Mods\EnhancedHUD
Never merge mods together, even if they modify similar systems. That’s how you lose track of changes and create conflicts you can’t diagnose later.
What a Correct Mod Folder Actually Looks Like
When you open a properly packaged mod, you’ll usually see one of two things. Either a mod.manifest file at the top level, or a Data folder that mirrors the game’s internal structure.
A clean example looks like this:
Mods\BetterCombat\
– mod.manifest
– Data\
–– Libs
–– Tables
–– UI
If you open a mod and immediately see Libs or Tables without a Data folder above them, you’re probably one level too deep. That mod will be ignored until the structure matches what the game expects.
The Most Common Mistake: Double-Nested Folders
This is the silent killer of new mod setups. Many mods extract into something like BetterCombat_v1.2\BetterCombat\, and players drop the outer folder straight into Mods.
The result looks like this:
Mods\BetterCombat_v1.2\BetterCombat\Data
The game only checks the first folder level. If mod.manifest or Data isn’t right there, the mod might as well not exist. Always open the archive and make sure the folder you place in Mods contains the mod files directly.
How Kingdom Come: Deliverance 2 Reads Mod Priority
By default, the game loads mods alphabetically. That means naming matters more than most players realize.
If two mods edit the same table or UI element, the one that loads later usually wins. Veteran modders often prefix folders with numbers like 01_, 02_, or 99_ to force priority without touching files.
This is especially important for balance tweaks, perk overhauls, or UI mods that fight for the same screen space.
What You Should Never Touch Unless a Mod Demands It
Avoid editing the base Data folder, executable directory, or engine files. Kingdom Come: Deliverance 2 doesn’t need script extenders or DLL injections for most mods, and forcing changes there risks breaking updates or corrupting installs.
If a mod asks you to overwrite core files, double-check the mod page and comments. Sometimes it’s legitimate. Often, it’s outdated advice from early builds.
When in doubt, if it doesn’t live in the Mods folder, treat it as radioactive until you know exactly why it’s there.
Manual Mod Installation Step-by-Step (The Recommended Method)
Now that you understand how Kingdom Come: Deliverance 2 actually sees mods, it’s time to put that knowledge into practice. Manual installation isn’t just the safest route, it’s the most transparent. You always know what’s being added, where it lives, and why it works.
If something breaks, you’ll also know exactly what to undo. That’s power no mod manager can give you.
Step 1: Locate or Create the Mods Folder
Navigate to your Kingdom Come: Deliverance 2 install directory. By default, this is usually something like Steam\steamapps\common\KingdomComeDeliverance2.
Inside the main game folder, look for a directory called Mods. If it doesn’t exist, create it manually. The folder name must be exactly Mods, capital M included, or the game won’t scan it.
This folder is the only place 99 percent of mods should ever live.
Step 2: Download and Inspect the Mod Archive
Before you drag anything into Mods, open the downloaded archive. Don’t extract blindly. This is where most mistakes happen.
You are looking for a folder that contains either mod.manifest or a Data folder at its top level. If you have to dig through multiple nested folders to find those files, you’re not at the correct level yet.
Once you see the proper structure, that folder is the one you want to extract.
Step 3: Extract the Correct Folder into Mods
Extract the verified mod folder directly into the Mods directory. When you’re done, the path should look like Mods\ModName\mod.manifest or Mods\ModName\Data.
Do not merge folders. Do not copy individual files. Kingdom Come: Deliverance 2 expects self-contained mod folders, not loose assets floating around.
If Windows asks to overwrite anything, stop and double-check. Mods should never overwrite each other during install.
Step 4: Verify Load Order and Naming
Once the mod is in place, take a second to look at its name. Remember, the game loads mods alphabetically.
If this mod is meant to override another, rename the folder with a prefix like 90_ or zz_. If it’s a foundational mod other mods depend on, move it earlier with 01_ or 10_.
This simple habit prevents invisible conflicts that can cause perks not to apply, UI elements to vanish, or values to silently revert.
Step 5: Launch the Game and Test Immediately
Boot the game and load a save as soon as possible. Don’t install ten mods at once and hope for the best. That’s how you end up debugging blind.
Check what the mod is supposed to change. If it’s a UI mod, open the menu. If it’s a combat tweak, test stamina drain or hit reactions. Confirm the mod is actually active before moving on.
If nothing changes, re-check folder depth and load order before assuming the mod is broken.
Step 6: Understand Save Safety and Compatibility
Most Kingdom Come: Deliverance 2 mods are safe to add mid-save, especially UI, audio, and texture tweaks. Balance mods, perk overhauls, and economy changes are usually fine too.
Removing mods is where you need caution. If a mod adds perks, items, or progression systems, removing it mid-save can leave orphaned data behind. Always read the mod description to see if it’s safe to uninstall.
When in doubt, keep a manual backup of your save before testing anything experimental.
Best Practice: One Change at a Time
The golden rule of modding is isolation. Install one mod, test it, then move on to the next.
This keeps performance issues, crashes, or weird behavior easy to trace. If something goes wrong, you’ll know exactly which mod triggered it instead of playing RNG detective across your entire setup.
Patience here saves hours later, especially once your mod list starts growing into veteran territory.
Using Mod Managers: Are They Necessary and Which Ones Work
After walking through manual installs, the big question naturally comes up: do you actually need a mod manager for Kingdom Come: Deliverance 2, or is it just extra overhead? The short answer is no, they aren’t required, but the longer answer is that the right one can save you time once your mod list stops being small.
Kingdom Come’s mod structure is clean, predictable, and file-based. That’s why manual installs work so well and why many veterans still prefer them. Mod managers don’t unlock new functionality here; they automate what you already learned in the previous steps.
When a Mod Manager Makes Sense
If you’re running five to ten mods, manual installation is faster and more reliable. You know exactly what’s in your Mods folder, you control load order through naming, and nothing happens without your consent.
Once you start stacking larger setups, especially with multiple UI mods, balance tweaks, and experimental overhauls, a manager can reduce friction. Enabling, disabling, and testing becomes faster, which matters when you’re isolating bugs instead of brute-forcing fixes.
Think of mod managers as quality-of-life tools, not a requirement or a safety net.
Nexus Mod Manager and Vortex: What Actually Works
Vortex, Nexus Mods’ current manager, technically supports Kingdom Come: Deliverance 2, but with caveats. It can deploy mods into the correct Mods directory, and for basic archive-based mods, it works well enough.
Where Vortex struggles is load order logic. Kingdom Come doesn’t use plugin files or metadata-based priorities, so Vortex can’t reliably manage alphabetical order the way the game expects. You’ll often still need to rename mod folders manually, which defeats half the purpose.
If you use Vortex, treat it as a downloader and deployer, not an authority. Always open the Mods folder afterward and verify naming, depth, and conflicts yourself.
Why There’s No “Perfect” Manager for Kingdom Come
Unlike Bethesda RPGs, Kingdom Come doesn’t rely on ESP files, script extenders, or runtime injection. Mods are read straight from folders, which makes them stable but also limits what managers can automate.
There’s no official load order file, no mod priority system beyond alphabetical naming, and no built-in conflict resolution. That’s why no manager can intelligently resolve overlaps or warn you when two mods touch the same values.
This design is intentional. Warhorse built the system to be transparent, which rewards players who understand it rather than those who rely on tools to guess.
Best Practices If You Choose to Use One
Even with a mod manager, keep your habits from manual installs. Install one mod at a time, deploy, then test in-game before moving on. Don’t batch install and hope the manager sorts it out.
Periodically audit your Mods folder directly. If you can’t explain what every folder does and why it’s named the way it is, you’re setting yourself up for invisible conflicts later.
Most importantly, never assume a mod manager makes your setup safe. Save backups, read descriptions, and remember that you—not the tool—are ultimately responsible for keeping Henry’s world stable.
Load Order, Mod Conflicts, and Compatibility Best Practices
Once you’re installing mods confidently, the next skill that separates stable builds from broken saves is understanding how Kingdom Come: Deliverance 2 actually reads them. This is where most crashes, missing features, and “it worked yesterday” bugs are born.
The game doesn’t negotiate between mods. It obeys rules, and if two mods fight, one simply wins.
How Load Order Actually Works in KCD2
Kingdom Come: Deliverance 2 loads mods alphabetically by folder name, full stop. There are no priorities, no plugin lists, and no override warnings. The last mod loaded wins any conflict, even if that conflict breaks balance, quests, or AI behavior.
That means folder naming is load order. A mod named z_MyCombatOverhaul will always override one named a_VanillaTweaks, regardless of install date or manager settings.
Veteran modders use prefixes to control this. a_, b_, z_, or 00_, 99_ are not cosmetic choices; they’re how you tell the engine what gets final authority.
What Counts as a Mod Conflict
A conflict happens when two mods modify the same underlying file, not when they touch similar gameplay systems. Two armor mods are fine unless they edit the same item definition. Two combat mods become a problem if both change stamina costs, hit reactions, or AI aggression tables.
The game will not crash just because of a conflict. Instead, one mod silently overrides the other, which is why bugs often feel random or inconsistent.
If a mod description mentions edited tables, balance values, or overhauled systems, assume it can conflict unless explicitly stated otherwise.
Hard Conflicts vs Soft Conflicts
Hard conflicts are direct file overlaps. These are non-negotiable, and only one mod’s changes will apply. Examples include economy overhauls, perk reworks, or global combat tuning mods.
Soft conflicts happen when systems interact indirectly. A mod that increases enemy health may technically work with a combat mod, but together they can wreck DPS balance, stamina pacing, or I-frame timing.
Soft conflicts won’t break the game, but they can absolutely break how the game feels. Always test combat, stealth, and dialogue pacing after installing anything systemic.
Safe Load Order Strategy for Most Players
Start with visual and UI mods first. These rarely conflict with gameplay systems and are safe to load early.
Next come quality-of-life tweaks like weight adjustments, UI scaling, or animation smoothing. These usually touch isolated values and behave well.
Finish with major gameplay overhauls. Combat, economy, AI, or progression mods should load last so their design intent isn’t diluted by leftover vanilla values.
Why Testing After Every Mod Matters
Install one mod, launch the game, load a save, and actively test the system it touches. Swing a weapon, trigger a perk, talk to an NPC, or enter combat. Don’t just load in and quit.
Many issues don’t show up until the game actively calls a value. A broken stamina curve might not appear until a long fight. A bad AI tweak might only surface during group aggro.
If something feels off, remove the mod immediately and retest before stacking more changes on top.
Save File Safety and When Mods Lock In
Some mods bake their changes into your save the moment you load it. Perk changes, progression tweaks, and economy overhauls often fall into this category.
Removing those mods mid-playthrough can cause missing perks, broken NPC inventories, or stalled quests. This isn’t corruption, but it is irreversible without reverting to an older save.
If a mod page warns “new game recommended,” take that seriously. That’s not modder paranoia; it’s structural reality.
Keeping Mods Compatible Across Updates
Game patches can invalidate mods even if nothing crashes. A balance patch might overwrite values a mod depends on, causing half-working behavior that’s harder to diagnose than a clean failure.
After every major update, temporarily move your Mods folder out, launch the game once, then reintroduce mods slowly. Check mod pages for update notes before assuming compatibility.
If a mod hasn’t been updated and touches core systems, treat it as suspect until proven stable.
Performance, Stability, and Knowing When to Stop
More mods doesn’t mean better gameplay. Every system overhaul adds CPU overhead, more calculations, and more chances for edge-case bugs.
If you’re seeing frame drops in combat, delayed AI reactions, or inconsistent hit registration, that’s often mod stacking—not your hardware. Remove mods in reverse load order until performance stabilizes.
The best Kingdom Come setups aren’t the biggest. They’re the ones where every mod earns its place and plays nicely with the rest of Henry’s world.
Testing Mods In-Game and Troubleshooting Common Installation Issues
Once your mod list is in place, the real work starts inside the game. Kingdom Come: Deliverance 2 is systemic to its core, and mods don’t truly prove themselves until the engine starts running calculations in real scenarios.
Load a save, play for at least 15–20 minutes, and deliberately interact with whatever the mod changes. If it’s combat-related, get into a fight. If it touches perks, level something up. If it tweaks AI, force a group encounter and watch how aggro and reactions play out.
How to Verify a Mod Is Actually Working
Not every mod announces itself with a popup or UI change. Many operate silently in the background, adjusting values like stamina drain, damage curves, or NPC behavior.
The easiest test is comparison. If you installed a stamina overhaul, sprint and fight longer than usual and see if the pacing feels different. For economy mods, check shop prices or loot values before assuming it failed.
If nothing feels different, don’t immediately assume the mod is broken. Double-check folder structure first, because most “non-working” mods are simply not being loaded at all.
Common Folder Structure Mistakes That Break Mods
Kingdom Come: Deliverance 2 is extremely picky about how mods are placed. Each mod must sit in its own folder inside the Mods directory, and that folder must contain the mod’s Data directory or configuration files directly.
A common error is nesting folders too deeply, like Mods/ModName/ModName/Data. The game won’t detect that. It should be Mods/ModName/Data, clean and simple.
Also watch out for compressed files. If you dragged a ZIP or RAR straight into the Mods folder without extracting it, the game will completely ignore it.
When the Game Crashes on Launch
A crash at startup almost always points to a hard conflict or a malformed mod. Start by removing the most recently installed mod and launching again.
If that doesn’t fix it, move all mods out of the Mods folder and confirm the game launches clean. Then reintroduce mods one at a time, launching between each addition. Yes, it’s slow, but it’s the fastest way to isolate a bad actor.
Mods that alter core systems like combat formulas, AI packages, or progression trees are the most likely to cause startup crashes if they’re outdated or conflicting.
Mods That Work “Halfway” and Why That’s Dangerous
The trickiest problems are mods that seem fine at first but behave inconsistently. Perks that sometimes apply, AI that randomly breaks aggro, or stamina that regenerates unevenly are all red flags.
This usually means two mods are editing the same system without compatibility patches. The game isn’t crashing because the data is valid, but it’s fighting itself behind the scenes.
If you notice inconsistent behavior, don’t ignore it. Disable one mod at a time until the system stabilizes. Leaving half-working mods active is how saves get slowly poisoned over dozens of hours.
Save-Specific Bugs vs Global Installation Problems
If a bug only appears on one save file, it’s likely baked-in behavior from a mod that altered progression, perks, or world states. Testing the same mod on a fresh save is the fastest way to confirm this.
If the issue appears on every save, including a new game, you’re dealing with an installation or compatibility problem instead. Focus on folder structure, load order, and overlapping mods.
Never troubleshoot by piling on more mods to “fix” the problem. That’s how small issues turn into unrecoverable playthroughs.
Best Practices for Stress-Testing a Modded Setup
Once you think everything is stable, push the game a bit. Fast travel, enter towns, trigger random encounters, and get into extended combat where stamina, AI, and hit detection are all firing at once.
Watch for micro-stutters, delayed enemy reactions, or perks failing to trigger. These are early warning signs that your setup is overloaded or conflicting, even if FPS looks fine.
If the game holds up under stress, you’re in a good place. That’s when Kingdom Come modding shines: a tailored experience that feels sharper, deeper, and still unmistakably authentic.
Updating, Removing Mods, and Maintaining a Stable Modded Playthrough
Once your mod list survives stress-testing, the real challenge begins: keeping it stable over a long campaign. Kingdom Come: Deliverance 2 is a slow-burn RPG, and most players won’t notice mod-related damage until 20 or 30 hours deep. Updating and removing mods the right way is how you protect that time investment.
This is also where most broken saves are born. Not from installing mods, but from changing them carelessly mid-playthrough.
How to Safely Update Mods Without Breaking Your Save
Before updating anything, read the mod page. If the author says an update is save-safe, that’s usually reliable. If they warn about progression resets, perk recalculations, or “recommended new save,” believe them.
For manual installs, updating usually means deleting the old mod folder and replacing it with the new version. Don’t overwrite blindly. Leftover files from older versions are a common source of phantom bugs, especially with mods that edit perks, AI behaviors, or stamina formulas.
After updating, load into a low-risk area. Avoid combat, dialogue chains, or scripted quests for a few minutes. If the game holds together during basic movement, menus, and NPC interactions, the update likely applied cleanly.
When It’s Safe to Remove a Mod Mid-Playthrough
Visual mods, UI tweaks, audio replacements, and texture packs are almost always safe to remove. These don’t touch world states or progression data, so the game simply reverts to vanilla assets.
Gameplay mods are a different story. Anything that alters perks, skills, combat math, enemy AI, or economy values can leave permanent fingerprints on your save. Removing these can cause missing perks, broken NPC behavior, or invisible stat penalties that never fully clear.
If you must remove a gameplay mod, load a save from before it was installed if possible. If not, expect side effects and test aggressively afterward. There’s no magic reset button once progression data is altered.
The Clean Removal Process Most Players Skip
Never just delete a mod and continue playing like nothing happened. After removing a mod, launch the game, load your save, and immediately save again under a new slot. This forces the engine to rebuild its active data without the removed files.
Then restart the game entirely and reload that new save. This extra step clears cached references that can otherwise linger and cause delayed bugs hours later.
If something feels off after removal, don’t push forward hoping it fixes itself. That’s how instability compounds. Roll back or restore the mod and reassess.
Why Load Order Discipline Matters Long-Term
Even without a dedicated mod manager, load order still matters. Kingdom Come reads mod folders in sequence, and later mods can overwrite earlier ones silently.
If two mods touch the same system, the one loaded last usually wins. That can be intentional or disastrous depending on compatibility. Keep mods that adjust the same mechanics grouped mentally and avoid stacking multiple “overhaul” mods on top of each other.
When something breaks after an update, the newest mod change is almost always the culprit. Reverting that one mod is faster than tearing apart your entire setup.
Protecting Your Save Files Like a Veteran
Always keep rolling manual saves, especially before installing, updating, or removing mods. Auto-saves won’t save you if corruption creeps in slowly.
It’s also smart to back up your save folder outside the game directory every few sessions. One clean backup can rescue a 60-hour playthrough that would otherwise be lost.
Treat your save like a character build in a hardcore RPG. Careful planning and restraint matter more than chasing every new mod drop.
Long-Term Stability Tips for Extended Playthroughs
Resist the urge to keep adding mods mid-campaign. The more systems you change after progression begins, the higher the risk of desyncs and baked-in bugs.
If you want to experiment, do it on a separate test save. Once you commit to a main playthrough, lock the mod list unless a fix is absolutely necessary.
Kingdom Come: Deliverance 2 rewards patience and immersion. A disciplined mod setup preserves that experience, letting the game’s combat depth, roleplay systems, and brutal realism shine without technical distractions.
Mod smart, respect your save files, and you’ll get the best version of Bohemia possible—one that feels personal, polished, and stable from the prologue to the final quest.