Start up your game and look for problems.

Avoid mods that look like they edit the same thing, and avoid running more than one overhaul mod at a time unless you can find a compatibility patch or a statement that they're compatible without one. Try to choose mods that you think will work well together. This should give you a stable game, if you're happy with their choice of mods. So you would follow the STEP guide and never deviate from it. Use someone else's mod listĪs you mentioned, you could run a list of mods provided by someone else, in the order they specify, using their patches. You can then either remove conflicting mods or learn how to make your own compatibility patch. Basically: it's not too terribly difficult to identify mods that might conflict. Is there a way to manage this task? Should I really build a database of mod pairs for every possible patches? This becomes even worse when realizing that some of the patches are provided only within FOMOD installers, not even mentioned on the mod pages at all. Similar thing happens when removing a mod. When installing an additional mod X, it is quite easy to overlook a patch between X and any of existing mods, unless it is provided on X's mod page. Unfortunately, when editing an existing mod list, it doesn't work because most patches are provided from only one of the mod pages. If I target a perfectly pre-arranged mod list (such as STEP) and install them one-by-one from the beginning, it is possible to grab all of those patches by carefully navigating each of mod pages. Now let's get to the modder's perspective. To handle those side effects, lots of them are providing compatibility patches for other common mods. In Skyrim, there are lots of mods that influence other mods' functionality.

How to use tes5edit to find conflicts