Contradictory mod rules without error warnings

[tomtheclone]

There are no 'contradicting rules' made by Vortex in this situation, if there were, the rules would be in italics (example below, 2 rules built into Vortex, and one rule I made myself) and you wouldn't be able to change them.

The fact that you could change them to get a working load order shows there's no bug, a bug would be that Vortex is insisting the mod and plugins be loaded in a certain order and you couldn't change it.

 

What you did was completely run-of-the-mill Standard operating procedure.

 

 

 

 

 

 

You seem to still be insisting that I'm talking about plugins. That screenshot is about plugin rules.

 

Also, I'm not talking about built in rules. I'm talking about the rules Vortex generates in response to other rules. In the conflicts resolution selector, if setting one override implies another, you get a lock next to that rule. I set a rule involving CBBE and Botox. Vortex then made a made for Botox and CBBE which was in conflict with the rule I set. I did not set two rules. I couldn't have set two rules since the drop down would have been greyed out. If I COULD have set two contradictory rules, that itself would have been a bug.

[Rattledagger]

 

In the first photo, you'll see that CBBE is suppose to load before Botox. In the second, Botox is suppose to load before CBBE.

 

You tested it? As in you had contradictory rules as well?

 

Look more closely at the pictures.

 

 

Was sure you've posted 3 pictures, but taking a closer look the first I detected as two pictures is only a single picture so not surprisingly I didn't see the problem here.

 

For the mods I tested on all my rules are consistent, meaning if A is loaded after B on mods-tab (similar to first picture) the same is true when looks on mod A, while if looks on mod B (the locked one) it shows B is loaded before A.

 

So, not sure why you're getting a different result for some of the locked mods.

 

Only thing I can guess is, since I'm using the test-branch v0.17.10 it's possible something has changed between versions, despite I can't really find anything relevant in the change-log.

 

BTW, going by your two pictures, for the actual rule it's the same rule in both pictures, it's only the "locked" rule not used for anything besides showing the current assignment that is wrong.