Troubleshooting guide
How to Fix Skyrim Mod Conflicts
Sooner or later, every modded Skyrim save hits the same wall: an NPC is wearing the wrong outfit, a quest won't trigger, or the game just crashes near a specific cell. Nine times out of ten, that's not a "broken mod" — it's two mods fighting over the same record. Here's how to actually find that fight and end it.
What a "Mod Conflict" Actually Is
A mod conflict isn't a special category of bug — it's just two or more mods editing the same piece of data and the game only being able to keep one version. Skyrim's engine doesn't merge changes automatically. If Mod A changes an NPC's outfit and Mod B changes that same NPC's outfit, whichever mod is lower in your load order wins, completely, and the other mod's change is simply gone like it was never installed.
That's the whole mechanism behind almost every "why isn't my mod working" question you'll see on r/skyrimmods. It's rarely that a mod is broken. It's that something loaded after it quietly overwrote the part you cared about. Once you understand that, troubleshooting stops being guesswork and becomes a process: find the shared record, decide which mod should actually win, and either reorder your load order or build a patch that keeps both changes.
This guide assumes you already know the basics of installing mods and reading a load order. If you're newer to modding, start with how to install Skyrim mods and our load order guide, then come back here once you're running enough mods that they're starting to step on each other.
The good news is that conflicts scale predictably with mod count. A 15-mod list is unlikely to need any of this. A 100+ mod list with multiple combat, magic, and NPC overhauls absolutely will, and that's normal — it doesn't mean you've done something wrong, it just means your load order has reached the point where two well-made mods are reasonably trying to control the same thing. The fix is the same either way: find the overlap, decide who should win, and apply the right tool from the list below.
Every conflict example below is pulled from real ScrollForge mod guides, not hypotheticals.
The 5 Types of Conflicts You'll Actually Run Into
Not every conflict needs the same fix. Knowing which type you're dealing with tells you which tool to reach for.
Record overwrites
Two mods edit the same record — an NPC, a weapon stat, a cell — and whichever loads last wins completely. This is the most common conflict type and the one xEdit is built to show you directly.
Leveled list conflicts
Item and loot mods both add entries to the same leveled lists. Without a merge, only one mod's additions actually show up in the world — the classic Heavy Armory / Immersive Weapons situation below.
Script conflicts
Two mods attach Papyrus scripts to the same event or object. These rarely show up in xEdit at all — they surface as stutter, broken quest triggers, or crashes, and need a Papyrus log or crash log to actually pin down.
Missing or wrong masters
A mod depends on a DLC, another mod, or a specific mod version you don't have active. This usually causes an instant crash to desktop on launch rather than a subtle in-game glitch.
Texture and mesh conflicts
Two mods both replace the same texture or mesh file, but with different versions — for example two armor retextures fighting over the same vanilla armor model. Your mod manager loads whichever one is installed later (or higher in the left-pane priority order in Vortex / MO2), so the loser simply never shows up in-game, with no error message at all.
Now that you know what you're looking for, here's how to actually find it.
How to Diagnose a Conflict
Don't start by uninstalling mods at random — that's how you lose a save's worth of progress trying to find a problem that takes ten minutes to actually identify with the right tool.
1. Run LOOT first, every time
LOOT won't fix a conflict, but it sorts your load order against community-maintained rules and flags known incompatibilities with a warning message. If LOOT is already telling you two mods conflict, you've just skipped the hardest part of diagnosis. See our load order guide if you haven't run it before.
2. Open your load order in xEdit (SSEEdit)
Load your full plugin list into SSEEdit and right-click any plugin to run "Apply Filter for Conflict Loser/Winner Records." It color-codes every record two or more active mods are both touching — green means no conflict, orange/red means a real overwrite worth checking. This is the single most useful tool for record-level and leveled-list conflicts.
3. Read the crash log, not the crash
If you're crashing rather than just seeing a glitch, install Crash Logger SSE or Trainwreck before doing anything else. The log it generates names the specific plugin and function involved in the crash, which turns "something is wrong somewhere" into "this exact mod, this exact line."
4. Isolate with a clean test if all else fails
Disable everything except the two mods you suspect, load a fresh save in an interior cell, and see if the problem reproduces. It's slower than xEdit, but it's the only reliable method for script-based conflicts that don't show up as record overwrites at all.
Step-by-Step: Actually Fixing It
Once you know what's conflicting, the fix is almost always one of these four, roughly in order of how often you'll need them.
-
1
Check for an official patch first. Many popular mods already publish compatibility patches for common conflicts — the mod's Nexus page and its "Articles" tab are the first place to check before building anything yourself.
-
2
Reorder your load order, if one mod should simply win. If a patch mod exists specifically to override another mod's changes, it needs to load after the mods it's patching — this is the one case where moving a plugin lower genuinely is the fix.
-
3
Build a bashed or smashed patch for leveled list conflicts. Wrye Bash's bashed patch (or zEdit/Smash's smashed patch) merges leveled lists from multiple mods so all of them show up instead of just whichever loaded last. This is the right tool for loot, weapon, and NPC-spawn conflicts specifically.
-
4
Hand-build a compatibility patch in xEdit for everything else. For a record both mods need to keep parts of, you can manually copy the relevant fields into a small empty patch plugin loaded after both. This takes longer but works for conflicts no community patch covers yet.
4 Real Conflicts We've Actually Documented
These aren't hypothetical examples — they're real compatibility notes from across our Skyrim mod guides, with the actual fix for each.
Inigo + Nether's Follower Framework (NFF) — Don't Import Inigo
Inigo is a fully voiced custom follower with his own dedicated AI and dialogue scripts, and his own author specifically lists him on NFF's do-not-import exception list. Importing him into NFF anyway can break his unique quest dialogue and commentary system, which is the entire reason most players install him in the first place.
The fix: run Inigo standalone alongside NFF rather than importing him — NFF manages your other followers fine without needing every custom follower funneled through it. See the full breakdown on our best Skyrim NPC mods guide.
Open Cities Skyrim — Needs Separate Editions of City-Editing Mods
Open Cities Skyrim removes the loading-screen walls around cities by merging them into the main worldspace, which means any mod that edits a city as its own interior cell — including Relationship Dialogue Overhaul's city-specific dialogue and Populated Cities Towns Villages's NPC additions — needs an Open Cities-specific edition or patch to place its changes correctly.
The fix: check the mod's Nexus page for an "Open Cities patch" or "OCS edition" before installing alongside it, rather than assuming the standard version will just work. Covered in more depth on our NPC mods guide.
Mysticism vs. Odin — Two Foundations, Pick One
Mysticism - A Magic Overhaul and Odin - Skyrim Magic Overhaul both rework the same set of vanilla spells from different design philosophies. Running both means whichever loads last simply overwrites the other's balance changes on every shared spell — you don't get "the best of both," you just get the second mod's version with the first mod wasted.
The fix: there isn't a patch for this one — pick Mysticism or Odin as your vanilla-spell foundation and build from there with Apocalypse or Triumvirate, which are both designed to layer on top of either. Full detail on our best Skyrim magic mods guide.
Heavy Armory + Immersive Weapons — Classic Leveled List Conflict
Both mods add a large number of new weapons into the same vanilla leveled lists so they show up as loot and on enemies. Without intervention, only one mod's weapons actually get distributed into the world — not because either mod is broken, but because the last one loaded simply owns those shared lists.
The fix: this is a textbook bashed (or smashed) patch case. Building one merges both mods' leveled list additions so you actually see weapons from both showing up in the world. Full setup notes are on our best Skyrim weapon mods guide.
Mistakes That Cause Conflicts in the First Place
Installing two mods that do the same job. Two combat overhauls, two magic foundation mods, two city-population mods — if they're solving the same problem, they're going to fight over the same records. Pick one per category instead of stacking them and hoping.
Ignoring LOOT warnings because the game still launches. A warning doesn't always mean an instant crash — sometimes it means a quiet, hours-later problem like a quest that silently fails to trigger. Read every LOOT message, not just the ones marked critical.
Updating one mod in a pair without checking the other. A mod update can change which records it touches, which can re-introduce a conflict that was already patched. If you update Heavy Armory or Immersive Weapons individually, rebuild your bashed patch afterward rather than assuming the old one still applies.
Never running a bashed/smashed patch at all. If you're running more than two or three mods that touch leveled lists — weapons, armor, loot, NPC spawns — and you've never built one, you're very likely already missing content from one of them without realizing it.
Assuming "compatible" means "stacks perfectly." A mod page saying it's compatible with another mod usually means it won't crash your game, not that both mods' full content will show up side by side. Heavy Armory and Immersive Weapons are a good example — they're compatible in the sense that nothing breaks, but you still need a patch to actually see weapons from both in the world.
When Two Mods Just Don't Belong Together
Not every conflict has a patch waiting to be built. Mysticism and Odin are the clearest example — they're not buggy together, they're just two complete answers to the same question, and combining them doesn't combine their strengths. The honest fix in cases like that is choosing one, not spending an evening trying to force compatibility that was never the goal.
A good rule of thumb: if a conflict is between two mods that fundamentally redesign the same system from different philosophies, that's a "pick one" situation. If it's between two mods that each add separate content into a shared list — weapons, loot, followers — that's almost always a "patch it" situation. Knowing which category you're in before you start saves a lot of wasted troubleshooting time.
Frequently Asked Questions
How do I know if two Skyrim mods are conflicting?
The most reliable way is to open your load order in xEdit (SSEEdit) and run a conflict check, which color-codes any record two or more mods are both editing. In-game symptoms — missing dialogue, floating items, NPCs with the wrong outfit, broken quest triggers, or crashes near a specific location — are also strong hints, but xEdit is what actually confirms it instead of guessing.
Does LOOT fix mod conflicts automatically?
No. LOOT only sorts your load order into a sensible order based on community-maintained masterlist rules and warns you about known issues — it doesn't merge content or resolve which mod wins a shared record. Load order can reduce the impact of a conflict by controlling which mod loads last, but an actual fix usually still needs a patch.
What's the difference between a bashed patch and a smashed patch?
A bashed patch is built by Wrye Bash and is mainly aimed at merging leveled lists (loot, NPC spawns, enchanted gear pools) so multiple mods that add items to the same lists all show up instead of one overwriting the other. A smashed patch, built by Smash, does something similar but with a more modern, flexible merge engine that handles a wider range of record types. For most leveled-list conflicts — like Heavy Armory and Immersive Weapons both adding to the same loot pools — either tool solves the problem; Wrye Bash is the more established, beginner-friendly option.
Can I just put one mod lower in my load order to fix a conflict?
Sometimes, but it's a blunt tool. Moving a mod lower makes it win any shared record over mods loaded earlier, which can fix one conflict while silently breaking another change that mod was supposed to keep. Load order is the right fix when one mod is genuinely meant to override another (a patch is supposed to load after the mods it patches), but it's the wrong fix for two mods that both want to meaningfully edit the same content — that needs an actual patch, not just reordering.
Why did my game start crashing after I installed a new mod?
The most common causes are a missing master file (the new mod depends on a mod or DLC you don't have active), two scripted mods fighting over the same hooked event, or a texture/mesh conflict where two mods replace the same model with incompatible versions. Install Crash Logger SSE or Trainwreck before you keep playing — the crash log will usually name the exact plugin involved, which turns a guessing game into a five-minute fix.
Is it ever okay to just not fix a conflict?
Yes, if the conflict is cosmetic and you can live with it — like a minor texture seam — it's reasonable to leave it alone rather than spend an hour patching something you'll barely notice in motion. But conflicts that affect quest scripts, NPC AI packages, or save stability are worth fixing properly, because they tend to get worse the longer a save runs, not better.
Want a setup that avoids these conflicts from the start?
Our AI Mod Builder puts together pre-checked mod combinations by style and focus, so you spend less time patching and more time playing.