Jump to content

Created mod rule for conflict, deployed, but .esp's sorted in reverse order


Norstaera
Go to solution Solved by Norstaera,

Recommended Posts

Which version of Vortex are you on? v1.4.9
What game are you trying to mod with Vortex? Skyrim Special Edition
How many mods do you have installed? 155
What environment are you running Vortex on? Windows 10, x64, 16g

First, I don't know if this is a bug. I only know it isn't what I expected.

2 mods conflicted. In the mod tab, I created a rule for N.Defeat to load after N.Dungeons, which is also what Vortex shows as the suggested order.

I deployed the mods.

I expected the same load order for the plugins as the mod rule. Both .esps are in the default group and there should be no reason at all for this order to be different. There were no error messages and no inline LOOT statements on the plugins page.

 

Vortex1 log, after creating mod rule to resolve the conflict and after deployment

 

Vortex.log, after creating mod rule, deploying, and creating separate plugin rule and redeploying.

 

BTW, I didn't bother providing you with the load order and plugins document for this profile because they haven't updated in 4 days. IMO, they should either be updated every time I hit deploy or I should have a button option in Vortex to update these files. Now they only update if I'm switching profiles.

It would also be helpful if the plugins text showed the load index (0A, 21, 4F, etc.)

If this isn't a bug, then I'd like to know so I remember to check my plugin order every time I deploy mods.

Link to comment
Share on other sites

I have always considered the mods tab to be for sorting mod assets and the plugins tab is for plugins. But I agree that maybe there should be some consistency between the two tabs.

Link to comment
Share on other sites

I have always considered the mods tab to be for sorting mod assets and the plugins tab is for plugins. But I agree that maybe there should be some consistency between the two tabs.

As I said in my post, you can sort both MODS and PLUGINS, according to whichever Column you click the ASCENDING or DESCENDING load order in.

I would NOT want plugins forced to be sorted exactly the same as MODs because it would make absolutely no sense.

 

 

Personally I'm GLAD I can sort the two differently, because the load order positions of Mods and Plugins are independent of each other.

 

Changing the load order of a Mod and having the plugin change it's order too, would be disastrous

 

You can sort mods, ASCENDING or DESCENDING by Mod Name, Installation Time, Category, Endorsed, Install Order, Deploy Order, etc

YOu can sort Plugins, ASCENDING or DESCENDING, by Name, Flags, Load Order, Mod Index, Group, Mod Category, Mod etc...

 

It would be utterly Foolish to force the sorting on the Plugin Page to follow the Mod page.

 

 

Vortex-Mod-Column.jpg

Link to comment
Share on other sites

When I sort the plugins and I'm not trying to find one in particular, I usually sort by the mod index or the load order (aren't they basically the same?).

If I sort by the category headers, that's a visual representation in Vortex, not the game load order. Or am I wrong?

When I am on the mods tab, and hit 'Deploy' that's supposed to sort the mods and how they load in game. Any mod rules I created to resolve conflicts should be taken into account. When I looked at the 'deploy order', the mods in question appeared to be correct based on the mod rule I created.

When I looked at how the plugins were sorted after deployment, their order was the reverse. I opened LOOT and copied the load order and pasted it into notepad for my convenience. Very clearly, despite the mod rule I created to resolve conflicts between the 2 mods, the plugins were loading into the game wrong independently of the mods. Only after I created a separate plugin rule did the mod deployment order and plugin load order match.

Link to comment
Share on other sites

When I sort the plugins and I'm not trying to find one in particular, I usually sort by the mod index or the load order (aren't they basically the same?).

If I sort by the category headers, that's a visual representation in Vortex, not the game load order. Or am I wrong?

When I am on the mods tab, and hit 'Deploy' that's supposed to sort the mods and how they load in game. Any mod rules I created to resolve conflicts should be taken into account. When I looked at the 'deploy order', the mods in question appeared to be correct based on the mod rule I created.

When I looked at how the plugins were sorted after deployment, their order was the reverse. I opened LOOT and copied the load order and pasted it into notepad for my convenience. Very clearly, despite the mod rule I created to resolve conflicts between the 2 mods, the plugins were loading into the game wrong independently of the mods. Only after I created a separate plugin rule did the mod deployment order and plugin load order match.

 

 

You're worrying over nothing.

Stop trying to get the Plugin and Mod order to match, as I said, in Vortex, they will sort IN VORTEX, (NOT THE GAME) by whatever Column head you click on whether Ascending or Descending.

Same with the plugins.

The actual load order however is in the plugins.txt and loadorder.txt

 

Vortex does NOT sort the Load order in your game according to how you have them sorted in Vortex, unless you have Plugins and Mods sorted by Mod Index/Load Order

 

But if you pick sort by Date Installed, and hit Deploy, Vortex does NOT all of a sudden change your load order in the game to a "by date" sorting.

 

You're overthinking it.

The different sorting in Vortex is just to allow easy sorting and selecting of multiple files when doing file operations etc.

 

 

N.defeat, and N.dungeons were the MODS having the conflict, that doesn't mean the PLUGINS have any conflicts.

 

YOu wouldn't be able to get anything done if the same rules you applied to MODS also applied to Plugins, because it would be a never ending pile of unsolvable Conflicts

 

N.Dungeons and N.Defeat had similar files, textures, meshes etc in each MOD that conflicted.

That doesn't mean that the Plugins contain any records that conflict, so there's no reason for MOD rules to apply to Plugins.

 

 

Link to comment
Share on other sites

  • Solution

 

***snip****

N.Dungeons and N.Defeat had similar files, textures, meshes etc in each MOD that conflicted.

That doesn't mean that the Plugins contain any records that conflict, so there's no reason for MOD rules to apply to Plugins.

 

Thank you. This is what I wanted to know.

I already understood what you were telling me about sorting and column headers - I guess I had a case of the famous, or infamous, 'failure to communicate' :).

I had just never seen, or maybe never noticed, a difference in the overall mod deployment order and plugin deployment order before. Since they played better together after I created the plugin rule, I wondered if there was a problem. Glad to know that there isn't.

I appreciate your taking the time to explain. Thanks again.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...