Modding Kingdom Come: Deliverance II often feels like a gamble between visual splendor and silent technical failure. Given that the game utilizes a sophisticated version of the CryEngine, checking whether a mod is active involves more than just glancing at the screen. Many players on Reddit frequently encounter the "stealth fail"—where the game launches perfectly, but none of the installed modifications are actually functioning. Confirming mod activity requires a combination of log file analysis, directory verification, and in-game testing.

The definitive proof: Analyzing kcd.log

The single most reliable way to know if Kingdom Come: Deliverance II has recognized and initialized your mods is to check the kcd.log file. This file is generated every time the game starts and records the engine's initialization process, including the mounting of external data packages.

To find this file, navigate to the root directory of the game (where KCD2.exe is located). Open kcd.log with any text editor and use the search function (Ctrl+F) to look for the term "mod".

In a successful setup, you will see entries like [Mod] 'ModName' version [X] loaded. If the engine attempted to load a mod but failed, it will often log an error such as [Mod] Failed to find manifest or [Mod] Data mismatch in .pak. If you see no mention of your mods at all, the engine isn't even looking in the right folder, or a configuration file is blocking the scan. This log is the only way to distinguish between a mod that isn't loading and a mod that is loading but has broken functionality.

Proper folder structure and the manifest requirement

KCD2 is strict about where it looks for modifications. By default, mods must reside in a folder named mods within the main game directory. However, the internal structure of each individual mod folder is what usually trips up users.

A functional mod directory should look like this:
Kingdom Come Deliverance II/mods/[ModName]/
Inside this folder, there must be a mod.manifest file and a Data folder containing the .pak files.

The mod.manifest is a small XML or text-based file that tells the game the mod’s name, version, and which game version it is compatible with. If this file is missing, the game engine will ignore the entire folder, regardless of how many .pak files are inside. Many older mods or those manually extracted from archives might lack this file or have it in the wrong sub-directory. If your kcd.log says a mod was skipped, verify that the manifest is sitting directly in the root of that specific mod's folder.

The mod_order.txt whitelist trap

A common issue discussed in community circles involves the mod_order.txt file. This file is optional but powerful. If it exists in your mods folder, it acts as a mandatory whitelist. Any mod folder not explicitly named inside mod_order.txt will be completely ignored by the game, even if it is correctly structured.

This file is often automatically generated by mod managers like Vortex or when downloading mods through the Steam Workshop. If you are manually adding a new mod from a source like Nexus and it refuses to load, check for the existence of mod_order.txt. You have two choices: either delete the file (which allows the game to load all mods in alphabetical order) or manually add the name of your new mod folder to the list. For complex setups involving many mods that edit the same game tables, maintaining this file is necessary to ensure the correct load priority, as the mod listed last will overwrite the changes made by mods listed above it.

In-game verification through visual and mechanical changes

Once the logs confirm the mod is loaded, the next step is verifying its impact within the world of Bohemia. This varies depending on the type of mod installed.

UI and Graphic Mods

These are the easiest to verify. If you have installed a UI transparency mod or a different crosshair, the changes should be immediate upon reaching the main menu or loading a save. For Reshade setups, there is usually an overlay (Home key by default) that confirms the injection was successful. If the UI looks vanilla despite the logs saying otherwise, there is likely a conflict where a later-loading mod is overwriting the UI files.

Gameplay and Mechanic Mods

Verifying mods that change stamina regen, carry weight, or NPC behavior requires specific testing. For instance, if you installed a mod to increase Henry’s carry capacity, check your inventory screen immediately. If the numerical value remains at the vanilla base, the mod is not functioning. For "Hardcore" overhaul mods, look for changes in the map or the absence of the player icon; these are deep-coded changes that are hard for the game to ignore if the mod is active.

Script and XML Mods

Many mods for KCD2 edit .xml tables (like rpg_param.xml). These often require a corresponding .tbl file to be present. In the previous game engine version, these files needed to be empty "zero-length" files to force the engine to read the XML. In KCD2, ensure that the .pak file containing these edits is not being overridden by a higher-priority mod. A quick way to test this is to temporarily remove all other mods except the one you are testing.

Using the Developer Console for debugging

If you are still unsure, the in-game developer console is a powerful tool. Access it by pressing the tilde key (~). While not all mods have dedicated console commands, you can often use engine commands to check variables that the mod was supposed to change.

For example, if a mod is supposed to change the gravity or movement speed, you can query those variables via the console. If a mod adds new items to the game, use a cheat command or an item spawner command to see if the item ID exists in the game’s database. If the console returns an error saying the item ID is unknown, the mod’s data has not been merged into the game’s active tables.

Steam Workshop vs. Manual Installation

In 2026, the KCD2 Steam Workshop is a primary source for mods, but it handles files differently than manual installs. Workshop mods are often stored in a separate workshop/content/1259420 directory. The game engine is designed to mount these automatically, but conflicts arise when you mix Workshop mods with manual mods in the mods folder.

If Workshop mods aren't working, it is often because a manual mod_order.txt is overriding the Workshop's auto-load sequence. Additionally, the game prioritizes manual mods over Workshop mods in many cases. If you suspect a conflict, try unsubscribing from the Workshop version and installing the mod manually to the mods folder to see if the behavior changes. Consistency in installation method is usually the key to a stable modded experience.

Why mods might fail on existing saves

A frequent point of confusion is whether a mod is "working" versus whether it is "compatible with your save." Some mods, particularly those that alter world-state, quest logic, or initial character stats, only initialize properly when starting a New Game.

If you have a mod that alters the economy or shop prices, try visiting a merchant in a town you haven't visited in a while. If the prices are still vanilla, the data might be baked into your current save file. To verify this, start a New Game and play through the prologue to see if the changes appear. If the mod works on a fresh save but not your 50-hour career save, the mod itself is working fine, but your save file is incompatible with the changes.

Handling "Data Mismatch" and Versioning

As Warhorse Studios releases patches for KCD2, mods will inevitably break. If your kcd.log shows a "version mismatch," the game engine has detected that the mod was built for an older version of the game’s Data.pak. While some mods are "version-agnostic" (like simple texture swaps), anything that touches the core scripts or the AI navigation mesh will likely cause the game to ignore the mod or, worse, crash on startup.

Always ensure that your mods are updated to match the current game build. If a mod hasn't been updated in months, it may require manual editing of the mod.manifest to force-load it, though this is risky and can lead to corrupted save files.

Summary Checklist for Verification

If you are troubleshooting a mod that doesn't seem to be active, follow this sequence:

  1. Check kcd.log: Look for the specific mod name and any load errors.
  2. Verify Manifest: Ensure mod.manifest exists in the mod's root folder.
  3. Check mod_order.txt: Delete it to test if a whitelist is blocking your mod.
  4. Isolate the Mod: Move all other mods to a backup folder and test only the problematic one.
  5. Console Test: Try to summon modded items or check variables via the ~ console.
  6. New Game Test: Determine if the issue is a save-game conflict.

By systematically ruling out these common failure points, you can move past the frustration of non-functional mods and get back to enjoying a customized experience in the lands of 15th-century Bohemia.