![]() ![]() 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. ![]() 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |