KCD2 Mods: Workshop, Vortex, Recovery

KCD2 mods are a PC job. Official Deep Silver / Warhorse docs recommend Steam Workshop: Subscribe, wait for the download, launch. Manual KCD2 mods go in the game-root mods/ folder with mod.manifest in the first child. Third-party managers exist and are not officially supported. A green Subscribe button is not proof the current build likes that package.

Quick answer: Workshop first. One package, then a disposable save. If Workshop KCD2 mods are subscribed but invisible, check Steam Properties → Workshop for a 0 byte download, then look for a Vortex mod_order.txt that lists only Nexus IDs. There is no in-game mods menu. Official docs: installing KCD2 mods does not disable achievements; a package can still change the conditions. Console (PS5 / Xbox) has no official Workshop.

#What KCD2 Mods Can and Cannot Do

KCD2 mods do not appear as a toggle on the title screen. Steam community reports are consistent: you prove a package by the feature it promised, not by a checkbox. Some armour KCD2 mods also need item codes in the console; that is a different tool than the KCD2 commands list, so read the mod page before you type.

Risk rises with what the package edits:

Build KCD2 mods from the top of that table downward. The last package you added is the first one you remove.

Epic and GOG players get the manual path only. Do not hunt a Workshop tab that is not there. Those stores still run KCD2 mods from mods/ if the manifest is valid.

#Install KCD2 Mods from Steam Workshop

Official text: click Subscribe; the game uses those KCD2 mods on the next launch. Before you click, read supported version, required items, last update, and the newest comments. Workshop hosting is not a compatibility stamp.

1. Copy several manual saves plus one save that has never loaded gameplay-changing KCD2 mods.
2. Subscribe to one package. Wait until Steam finishes; a 0-byte Workshop entry is not installed KCD2 mods.
3. Install only dependencies the author names.
4. Launch, load a throwaway save, test the advertised feature, make a new test save, quit cleanly.
5. Write down package, version, and result.

If the Workshop list shows 0 b, a Steam guide (Pilda) and forum threads: unsubscribe, launch the vanilla game, resubscribe, quit, check size again. That is a client download bug, not a broken mod.manifest.

Workshop files live under steamapps/workshop/content/1771300/. You do not unpack those by hand unless an author says so.

#Manual KCD2 Mods and mod.manifest

Official: unpack into mods/ in the game root, and that folder must contain mod.manifest. Some pages nest an extra KCD2/ directory. Use Browse local files and put KCD2 mods next to the real game data, not inside a download wrapper.

⧉KingdomComeDeliverance2/
└── mods/
    └── example_mod/
        ├── mod.manifest
        └── data/

Published game loads packed .pak content. Loose files beyond mod.manifest and mod.cfg are ignored. Author docs win if they document a special case.

The KCD2 code page is item and cheat codes, not folder layout. After a copy, launch once and search kcd.log for [Mod]. Missing line: wrong folder. Rejected line: version, manifest, or order.

Do not keep a Workshop copy and a Nexus copy of the same KCD2 mods package. The loader sees two IDs or one ambiguous folder, and kcd.log becomes guesswork.

#The Vortex File That Hides KCD2 Mods

Official load order: Workshop first (Steam API), then manual mods/ alphabetically. If you create mod_order.txt in mods/, any ID not listed is not loaded, including Workshop KCD2 mods.

That last sentence is the usual “I subscribed and nothing happened” failure. Vortex and some Nexus flows write mod_order.txt with only the folders they manage. Workshop IDs are absent, so official KCD2 mods never start.

• If you do not need a custom order: delete mod_order.txt and relaunch.
• If you do need an order: add every Workshop mod.manifest ID as well as every manual folder. Official: the ID may differ from the folder name.

Mixing Vortex and Workshop without auditing that file is the conflict community threads keep repeating. Third-party managers are allowed by the docs and unsupported when they break. Treat a surprise mod_order.txt as a KCD2 mods outage until you read every line.

#After a Patch: Recover KCD2 Mods

A Warhorse patch can change data that KCD2 mods override. Authors are not on the patch payroll. Steam threads: wait for an update, or play vanilla. Do not strip <supports> from a manifest just to force old KCD2 mods to load; the block may be the only thing keeping a save intact.

1. Copy the save folder and the current list before you touch anything.
2. Disable all KCD2 mods. Keep the backup copies.
3. Verify game files in the client.
4. Reproduce on a clean or disposable save.
5. Re-enable one current package plus its named dependencies.
6. Read kcd.log, test, new save, next package.

If vanilla works and the old save does not, removed KCD2 mods may have left expected quest or item state. Restore the author's migration build or an older backup. Story locks can also be missing DLC ownership; check the KCD2 DLC page before you burn the save.

Source: Deltia’s Gaming

#Safe Layers of KCD2 Mods

Cosmetic and UI KCD2 mods are the stack you can still diagnose at 2 a.m. Overhauls that rewrite combat or economy belong on a separate playthrough with their own saves. Read the vanilla forks in the KCD2 best perks guide before a progression pack decides them for you.

Saving KCD2 mods change how you prove a vanilla quest bug. Turn them off before you file a report. A save-anywhere pack is still KCD2 mods, even if it feels like a setting. Skill-tree packs are still KCD2 mods and should be compared with the unmodified KCD2 skills ranks first.

Some KCD2 mods ask for debug flags or console spawn. Compare the page with documented commands; do not paste a random user.cfg from a year-old video.

Achievements: official line is install does not disable them. A damage or loot pack can still make a trophy meaningless. Use the clean save when you care about the comparison.

Source: PC Gamer

#Mistakes That Break KCD2 Mods

• Treating Workshop as a version guarantee.
• Leaving Vortex mod_order.txt while adding Workshop KCD2 mods.
• Updating ten packages, then guessing which one crashed.
• Dual-installing the same ID from Nexus and Workshop.
• Editing the executable or ripping <supports>.
• Reporting a quest bug without a vanilla reproduce.
• Expecting a PS5 or Xbox copy to grow a mods/ folder.

When KCD2 mods vanish after you “did nothing,” you usually did something: a client update, a Vortex deploy, or a 0-byte subscribe. Log first, folder second, delete last. That sequence recovers more KCD2 mods than a full reinstall.

#KCD2 Mods FAQ

#Do consoles get KCD2 mods?

Not through an official Workshop. Current public docs and store pages describe PC Steam (and a manual folder on other PC stores). Do not wait for a console mods menu that the shipped build does not have.

#Why are my Workshop KCD2 mods subscribed but missing?

Download size first. Then mod_order.txt. Then kcd.log. There is no enable switch on the main menu.

#Where do manual KCD2 mods go?

Game root mods/mod_id/mod.manifest. Unpack the archive. Do not drop a zip on the Data folder.

#Do KCD2 mods turn off achievements?

Official documentation says installing them does not. Gameplay KCD2 mods can still change what the trophy is measuring.

#Can I mix Nexus and Workshop KCD2 mods?

Yes if every ID that should load is either left to the default order or listed in mod_order.txt. Vortex writing that file without Workshop IDs is the usual mix failure.

Install and load-order rules reviewed against the official Deep Silver modding note (updated 14 March 2025) on 1 September 2026. Each package still has its own version line.