Automatically setting rules in response to another rule being set

[Keksalot]

On Skyrim SE when I set a rule between two mods, Vortex then sets other rules for other mods preventing me from establishing the correct load order I need. For example if I set Majestic Mountains Main to load before Majestic Mountains 2.72 (an update) it then sets rules for Majestic Mountains to load before Noble Skyrim and Velanimus Grass Overhaul for no apparent reason. In those two cases the load order is correct, but there are other situations where it has not been correct and the only way around it seems to be to change the order in which I set rules. In any case I have not yet found a path through this maze that has allowed me to get the load order I actually want.

[Keksalot]

I had to uninstall ALL mods and go through them installing one at a time again setting rules as I went. That was the only way to stop it from trying to set arbitrary rules that made no sense. By doing this I was able to get the correct load order. Had I not done so Vortex would have forced me to run a bad load order. Not sure what you guys were going for with this function, or if it is a bug. It would make sense for certain mods with dependencies to automatically have load rules similar to their parent but it does not always seem to do this. Most of the time the rules it sets are for mods that are not related to the rule being set by the user.

 

Another example would be Vortex attempting to set a rule between Ember (a fire lighting mod) and RLO (An interior lighting mod) when the user is setting a rule between a pair of weapon texture mods. That can't be intended.

[HadToRegister]

I had to uninstall ALL mods and go through them installing one at a time again setting rules as I went. That was the only way to stop it from trying to set arbitrary rules that made no sense. By doing this I was able to get the correct load order. Had I not done so Vortex would have forced me to run a bad load order. Not sure what you guys were going for with this function, or if it is a bug. It would make sense for certain mods with dependencies to automatically have load rules similar to their parent but it does not always seem to do this. Most of the time the rules it sets are for mods that are not related to the rule being set by the user.

 

Another example would be Vortex attempting to set a rule between Ember (a fire lighting mod) and RLO (An interior lighting mod) when the user is setting a rule between a pair of weapon texture mods. That can't be intended.

 

 

It doesn't set Arbitrary Rules.

 

Were you following a Load Order guide and forcing Vortex/Loot to load AGAINST what Vortex/Loot set?

Because so far, you're the only ONE who has claimed something like this.

[Keksalot]

 

I had to uninstall ALL mods and go through them installing one at a time again setting rules as I went. That was the only way to stop it from trying to set arbitrary rules that made no sense. By doing this I was able to get the correct load order. Had I not done so Vortex would have forced me to run a bad load order. Not sure what you guys were going for with this function, or if it is a bug. It would make sense for certain mods with dependencies to automatically have load rules similar to their parent but it does not always seem to do this. Most of the time the rules it sets are for mods that are not related to the rule being set by the user.

 

Another example would be Vortex attempting to set a rule between Ember (a fire lighting mod) and RLO (An interior lighting mod) when the user is setting a rule between a pair of weapon texture mods. That can't be intended.

 

 

It doesn't set Arbitrary Rules.

 

Were you following a Load Order guide and forcing Vortex/Loot to load AGAINST what Vortex/Loot set?

Because so far, you're the only ONE who has claimed something like this.

 

 

 

No, I was forming a load order based on my preference regarding what textures/lights will be used vs those that will be not. Such as overriding SMIM with another mod for example. When I do this with several other mods installed that currently do not have rules set, it will frequently set another rule somewhere else for another mod that it does not allow me to override. I found that If I install the mods in the exact order in which I intend to load them, setting their rules as I go that it was no longer an issue (since there was no opportunity for Vortex to set rules other than for that specific mod).

 

I'll take a screenshot next time I'm in a situation where it happens since you don't seem to believe me :tongue:

 

Edit: Snipped out some redundant details. Short story is that it isn't always just 'random' mods being moved around, but I verified with a fresh (no rules set) attempt that it was happening anyway. So no load order conflict.

[BigBizkit]

Vortex will set the "mirror" rules to avoid confusion, for example:

 

If you set Mod A to load before Mod B

 

...then Vortex will automatically set Mod B to load after Mod A

 

That's only logical. I get that it can get way more involved when you have loads of mods, and you might even run into cyclic rules, but that's not because of Vortex setting the mirror rules.

 

If you want help debugging your setup we would need pictures.