Right-click on one of the mods and click "Apply Script".Ħ. Hold control and click on each of the mods you want to merge so they're highlighted.ĥ.
See the FAQįor more information on errors and how to fix them.Ĥ. Use "Check For errors" on files to be merged and fix any errors 圎dit finds. Run 圎dit through Mod Organizer and load the mods you want to merge.ģ. Make sure the plugins create the desired behavior in the game before merging.Ģ. Set up the plugins you plan on merging so they're all in adjacent load order slots. In any case, this is a side project, so I don't know that I'll get to doing anything with it really any time soon.This is taken from page for Merge Plugins 圎dit Script by matortheeternal -, which is what I use (there is a newer merge mod out that replaces this one: Merge Plugins by Mator - )ġ. I totally understand! Mostly I'm an algorithms guy, so I was more going to see if there was anything I could do to improve the performance of some of the operations, or even improve some of the capabilities around searching. I'm just using MO as an example I'm not saying you are doing anything wrong by compiling 圎dit or checking things out.
Mod Organizer changes how things are done through its DLL files so the compatibility comes from that program not ours. There is no compiler directive to add "Mod organizer" support in the Embarcadero compiler. Mod Organizer support is one of them and they don't understand why it appears that there is no support. Thanks for trying things request features that are not needed sometimes. If you have added something you like and we have not included the addition because it more or less goes against program functionality, like the MO Overwrite folder, I would appreciate it if that was not done and no binaries are released. If the consensus is that you feel it's a benefit but Zilav, Hlp, or myself object to that then I would appreciate it if that would be the end of the discussion. If you have something you can submit that is actually a feature or addition that can be used we are happy to discuss including it.
I do know that this is essentially what modgroups have been designed for (so I do get that the answer might just be a straight "No, not possible, rely on mod groups"), but sadly they're nowhere near as convenient as I'd like them to request features that are not needed sometimes. Right now there is no difference between a regular conflict between two independant mods, and "chained conflicts" between an intermediate master and its child plugin.
If value A is at 1 in Skyrim.esm, 2 in Update.esm, and 3 in MyMod.esp, (MyMod.esp having both Skyrim and Update as masters) then the record in Update.esm would have this new status and color.Īlternatively, an option to have those cases displayed as "master" (even if the record isn't defined directly in it, they're still in a "it make sense that I am being overriden") could do the trick. Would it be possible to have another status (and thus font color) for records / sub-records which are "Conflict looser, but the conflict winner have me as a master". Sorry for making such a big a request kindof out of nowhere but.