How to download compatability patches with mod organizer

When you look at the conflicts you have a few choices. Quickest is to pick one mod to be the "winner" usually by re-ordering your lists although there are more advanced mechanisms too. That's the most common decision because many conflicts will be things like a mod replacing an original Bethesda texture with something better. Another choice is to go look for compatibility patches. If there's no compatibility patch, another choice is to follow the ordering recommendations of the LOOT tool - but be aware that MO is one of the few tools that would allow the "loose" textures and scripts and other files to be in a different order than the LOOT driven plugin list of esps and esms.

And do what you're already doing - start with S. And lastly - For stability, try to avoid removing or even upgrading stuff during a play-through. If you do, follow the "clean save" procedure on the S.

Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. How do you manage the compatibility between mods in Skyrim? Ask Question.

Asked 5 years, 3 months ago. Active 5 years, 3 months ago. Viewed 16k times. Improve this question. You kind of need to do it manually in TES5Edit. You can create your own compatibility patches.

Mod Organizer lets you detect conflicts in other files. That just leaves script conflicts, and I did manage to make a fairly stable mod setup though. I was wondering if there were kind of automated solutions or practices for those who haven't dig into the internals like me much like how LOOT worked, Skyrim mod community has always amazed me in such ways. Yes, there is still far too much manual work to do when applying mods. Really short version: read all the guides on STEP.

But there are so many other cool mods out there Show 1 more comment. Active Oldest Votes. If it's a patch to resolve a conflict between 2 mods, you install it and load it after both mods. For a normal DSR mesh pack it can be installed anywhere as it just adds meshes and not replace any.

For an "On Back" mesh pack you want to load them after said mods since they also remove the rings of the normal sword sheath. Then we should probably add a new section to STEP at the end for mods that require patching like ear and fnis. That would probably reduce some of the problems people have.

It would be really helpful if the STEP guide was more specific about this, because I totally messed things up during my first install using 2. I just never overwrite a mod with a patch, I always install those separately so I can easily go back to "vanilla" version of a mod anytime I like. It's also very helpful to have them in separate directories to be able to just uncheck them for different profiles without having to reinstall the whole mod.

Being able to uncheck Requiem patches, SkyRe patches, Civil War Overhaul patches etc lets me jump between different configurations and with the local save options, saved game sets very quickly.

You need to be a member in order to leave a comment. Sign up for a new account in our community. It's easy! Already have an account? Sign in here. By using this site, you agree to our Terms of Use. Search In. Sign in to follow this Followers 0.

Installing patches for mods Asked by Octopuss. Question Octopuss Posted January 23, Share this post Link to post Share on other sites. Recommended Posts. Aiyen 0. Where and when, exactly, are the various mod compatibility patches supposed to be installed? My gut feeling says that patches would need to go AFTER a mod that causes an incompatibility issue with a mod earlier in the load order, but this would also necessitate rather convoluted install instructions and I don't see anything to suggest that..

For example, if following the STEP 2. D - Dual Sheath Redux" main mod, am I supposed to hold on to adding its aMidianborn patch after I've actually installed "2. Just wondering where the patch file s needs to reside when the complete STEP install is finished. You can throw those into DSR with the merge function. There are certain patches like the STEP patches which are the very first mods listed. In that light, it's delightfully misleading to have STEP Patches listed in the very first category, when they are, in fact, installed very last.

Or at least put there once most everything else is done. I design user manuals for a living and could try to improve the wording in certain pieces of the STEP guide, if you guys feel like it's needed. It could use some clarifications and polish along the way, IMHO. You need to be a member in order to leave a comment. Sign up for a new account in our community.