Potential mod order problem and the guided fix

[dreadflopp]

I know we are not supposed to care about the "potential mod order problem" warning in MO since the install order in STEP is fine and the warning can be ignored. My concern is that I actually want to use this feature and as a pack author of MMO I have many mods not in STEP installed. I have other packs installed too and want to maintain compatibility with these. I therefore have lots of mods installed and many mod order warnings. I think it would be nice to be able to use this feature to find real install order/mod order problems that I may have.

Since STEP now uses LOOT, the load order is more dynamic and it is not possible to have all STEP mods organised in such a way that these warnings disappear for all users when packs/custom mods are installed. My suggestion is this: couldn't we hide the conflicting files from the mods that gives a "false" warning or from mods where the install order is critical, and thus making them install order independent. By doing this we can get rid of the warnings users shouldn't care about and pack authors/users with more custom installs can find actual mod order problems.

 

[DoubleYou]

That's a rather complicated fix, and the problem I would see is, what if a user decides to use the mod with the hidden file independent of the one we use for the file?

 

And also, most of the time, you can't do that, as there are actually no conflicting files at all. The MO detection merely looks for a scripts folder, not an actual script file.

[dreadflopp]

It's a little complicated that's true. And it could lead to problems when removing mods that had files another mod was dependent on. Since there are no actual file conflicts this isn't a solution anyway.