Witcher 3 Mod Load Order and Compatibility Guide for the Remastered (5.0)

Bundle files are the first mechanism. When two mods ship the same bundle file, such as a UI layout, a HUD element, a font, or a texture pack, the game picks one, and the decider is the mods folder plus mods.settings in Documents, The Witcher

3. A mod manager writes that file, or you can write it by hand. Script Merger cannot help here: bundles are not scripts, and no merge can reconcile two different versions of the same interface file.

Scripts are the second mechanism. When several script mods change the same game scripts, Script Merger builds merged versions that carry the compatible changes from each mod, and the merged files live in mod0000_MergedFiles. The merge order inside the tool is where you resolve what the tool flags, and deleting that folder before a rebuild is how you stop stale merges from haunting a new stack. The third mechanism is annotation stacking: mods built with REDkit-style annotations, such as Ink and Iron's scripts, add their behavior on top of the game and of each other without touching the same lines, so they stack without a merge at all.

Rule one: dependencies first. If a mod lists a requirement, that requirement must load before anything that uses it. Ink and Iron's UI module needs its Fonts module; the Fonts module goes first, and the same logic applies to every framework a mod names. A missing dependency is the most common silent failure, because the game loads without it and the dependent mod simply does nothing.

Rule two: author notes beat habit. When a mod's own page names a position, that position is part of the mod's requirements, not a suggestion. Slots Slots Slots is the working example: its page says to give it priority over Smooth UI Remastered in mods.settings, and skipping that step breaks its page indicator. If two authors give conflicting instructions, one of them has to lose, and that is a reason to drop one mod rather than force both.

Rule three: winner-last for scripts, winner-only for bundles. For scripts, the mod that loads later wins the contested lines after merging, so the change you care about most should be the last one that touches those lines. For bundles there is no merging at all: the priority winner takes the whole file, and everything the loser changed in that file is gone. That asymmetry is why a UI mod losing priority looks so dramatic, while a script mod losing priority looks like a single feature quietly missing.

Rule four: one UI overhaul, always. Two interface overhauls cannot coexist, because both replace the same interface files and no merge exists for bundles. The same rule covers HUD mods and font mods that replace whole files. Pick one, and treat any second UI mod as a replacement candidate, not an addition.

This stack uses only mods with verified 5.0 evidence from our best-mods list, and it makes exactly one priority decision by hand. Install in this order, run Script Merger after the script mods, and test on a copy of your save before you commit to the stack.

Notice what is not in the stack. Friendly HUD is not here, because Ink and Iron already fills the UI slot; if you prefer Friendly HUD, swap it in and drop Ink and Iron entirely, keeping its Fonts module out too. Smooth UI is not here either; if you add it, the one hand-set priority is Slots over Smooth UI in mods.settings. Everything else in the stack needs no priority decision, because annotation stacking and own-script mods do not fight over files.

Start with Workshop subscriptions: if the game worked before and broke after a reinstall, old subscriptions are the prime suspect, and the fix is unsubscribe, delete the mods folder, and verify files. Next check priority: if one mod's changes are silently missing, open mods.settings and look for the file they fight over. Then check merges: if the break followed an update or a removal, delete mod0000_MergedFiles and rebuild. Test each step on a copy of your save, and change one thing at a time, or you will not know which fix worked.

When the game patches, the same diagnosis repeats with one extra rule: nothing from the old version is trusted until its author updates it. Our 5.0 compatibility guide explains the five-step check for any mod after a patch, and the Remastered Modathon running until November 30, 2026 is a good moment to expect updates to land. Until an update lands, run the game without that mod rather than with a broken one.

No hard number was verified for the Remastered in this research, and no limit is claimed here. The practical limit is conflicts: each added mod adds a chance of a script or bundle collision, so grow a stack in small batches and test each batch, rather than counting mods.

Not verified on 5.0. The Ink and Iron page itself says the alphabetical convention is a Witcher 3 convention not verified on 5.0, so use mods.settings priority as the reliable lever and treat folder renaming as a rule to test in game, not a guarantee.

Because the merged files were built from the old set. Delete mod0000_MergedFiles and rebuild the merge from only the mods still installed, then test on a save copy. Keeping an old merge alongside a new one creates duplicate scripts and more conflicts.

No. The Remastered rebuilt systems that the Next-Gen order assumed, including the skill tree, and mods that were stable on 4.0x may not even load on 5.0. Rebuild the stack from mods with 5.0 evidence, and use the four rules above rather than an old list.