In The Witcher 3: Wild Hunt (including the 2022 next-gen update), “loot merge” is not a built-in game feature—it refers to community-made mods that combine multiple inventory, loot, or level-scaling mods into one package, or that merge the loot tables of different DLCs and mods to prevent conflicts. If you’re looking to merge your own modded loot files, you’ll need a tool like Script Merger or the WolvenKit, not a game setting.
Background: Why Loot Conflicts Happen
The Witcher 3’s modding scene is vast, and many popular mods alter the same game files—especially those related to loot, item stats, and merchant inventories. When two mods both modify the same XML or script file (e.g., items.xml or def_item_*.xml), the game engine can only load one version, causing one mod’s changes to silently override the other. This is the core problem that “loot merge” tools solve: they combine those overlapping files into a single, unified version that preserves the changes from both mods.
How Loot Merging Works in Practice
Merging loot files isn’t a one-click operation. The standard workflow involves:
- Identifying conflicting files – Tools like Script Merger scan your
modsfolder and list all files that are modified by more than one mod. - Choosing which changes to keep – For loot mods, you often need to decide whether to keep the item’s base stats from one mod and the added items from another.
- Generating a merged file – The tool creates a new mod (e.g.,
mod0000_MergedFiles) that contains the combined data, and you enable it in your load order.
For example, if you have a mod that adds new swords and another that rebalances all silver swords, a merge would let you keep both the new swords and the rebalanced stats, instead of losing one set of changes.
Tools You Can Use for Merging
The most common tools are:
- Script Merger – Primarily for scripts, but it can also handle certain XML files. It’s the go-to for most players.
- WolvenKit – A more advanced mod editor that can merge complex file types, including loot tables and item definitions. It’s steeper learning curve but more powerful.
- Manual merging – For simple conflicts, you can edit the XML files yourself with a text editor, but this is error-prone and not recommended for beginners.
None of these are official CD Projekt Red tools; they’re community creations, but they’re widely used and generally safe when used correctly.
How to Choose the Right Merge Approach
Your approach depends on the mods you’re using:
- If the mods affect different items (e.g., one adds a new armor set, another changes a different armor set), there’s usually no conflict—no merge needed.
- If they affect the same items but in different ways (e.g., one changes price, another changes weight), you can often merge by combining the specific fields.
- If they affect the same items in the same way (e.g., both change the damage of the same sword), you must choose which mod’s value to keep—merging isn’t possible.
Always read the mod descriptions: many authors already provide compatible versions or patches, which is simpler than merging.
Common Problems and How to Avoid Them
Merging loot files can introduce issues:
- Redundant entries – If two mods add the same item, you might end up with duplicate IDs, causing crashes or missing textures.
- Load order issues – The merged mod must load after the originals. In the Witcher 3, mods load alphabetically, so name your merged mod with a prefix like
mod0000_to ensure it loads first (or last, depending on the tool’s instructions). - Save game corruption – If you remove a merged mod after loading a save, the game may crash because the save references items that no longer exist. Always back up your saves before merging.
If you encounter crashes after merging, disable the merged mod and test each original mod individually to isolate the issue.
Loot Merge vs. Other Mods: What’s the Difference?
Loot merging is often confused with two other things:
- Loot overhaul mods – These are single mods that change the entire loot system (e.g., “Better Loot” or “Loot Everything”). They don’t require merging unless you stack them with other mods.
- Level scaling mods – These adjust enemy and item levels. They may conflict with loot mods because they both affect item stats. Merging can combine them, but it’s trickier because the scaling logic is in scripts.
The key difference: merging is a technical process to make other mods work together, not a gameplay feature.
Costs and Safety Considerations
Merging is free—all tools are open-source. The main cost is time and potential frustration. Safety-wise, always:
- Back up your
modsfolder and your save files. - Use the latest version of the merging tool.
- Follow the tool’s documentation—each has its own quirks.
- Test the game after merging, preferably with a new game or a save before the affected area.
There’s no official support from CD Projekt Red, so if something breaks, you’re on your own—but the modding community is active and helpful on forums like Nexus Mods.
Alternatives to Manual Merging
If merging sounds too technical, consider:
- Use mods that are already compatible – Many popular loot mods are designed to work together and state so on their pages.
- Use a mod manager – Tools like Vortex or The Witcher 3 Mod Manager can automate some conflict resolution, but they don’t fully merge files—they only manage load order.
- Stick to one comprehensive loot mod – Instead of combining several, pick one that does everything you want (e.g., “W3EE” or “Enhanced Edition” overhauls).
These alternatives are simpler but less flexible.
Frequently Asked Questions
Can I merge loot mods without a PC? (Console players)
No. Modding and merging are only available on PC. Console versions of Witcher 3 don’t support mods, so you can’t use loot merge mods there.
Will merging loot mods break my save game?
It can, if you remove the merged mod after loading a save. Always keep the merged mod installed, and back up your saves before making changes. It’s also safer to start a new game after major merges.
What’s the difference between Script Merger and WolvenKit?
Script Merger is simpler and handles most script conflicts automatically. WolvenKit is a full mod editor that can merge more complex file types, including loot tables, but requires more manual work. For loot merging, WolvenKit is often necessary if Script Merger fails.
Do I need to merge if I only use one loot mod?
No. Merging is only needed when two or more mods modify the same files. If you use a single loot mod, you can just install it normally.
Can I merge mods that add new items with mods that change existing items?
Yes, that’s a common scenario. The merge combines the new item additions with the stat changes, as long as there’s no direct conflict on the same item ID. Tools like WolvenKit can handle this.
What if the merge tool says “cannot merge”?
This usually means the mods modify the same lines in a way that can’t be combined automatically. You’ll need to either choose one mod over the other, or manually edit the files—which is advanced and not recommended unless you know XML.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Turn Off Backup Encryption in iTunes?
- Campus Tech Innovation Hubs: What They Are
- Poco C51 Airtel Prepaid Locked Variant India?
- Jenkins vs GitHub Actions: Which CI/CD Fits Your Team?
- Shared VPS Hosting: Is It Better?
- Disk Defrag Pro: What It Does and Whether You Need It