Vortex: Load before vs load after

[Violence]

 

Apologies for quoting you directly, but could you tell me exactly which of the two files is the actual load order for Vortex? There are two in AppData/Roaming/Vortex/Skyrim/Profiles. One is LoadOrder and the other is PlugIn, and they look almost completely identical.

Then, supposing I arrange things as I want manually(So for example the exact way I had my load order in NMM in a text file), how do I prevent Vortex from changing anything I do there? Turn off auto sort in the UI?

Setting rules within Vortex itself seems extremely tedious and time consuming to me, not to mention a bit confusing. For example, if I had A.ESM and B.ESM, and want B to be prevalent over A, do I set it so B "Load After" A? Same for ESP, if I have X.ESP and Y.ESP and want X to be prevalent over Y, then X "Load After" Y?

I ask specifically, because I remember that ESM work exactly the opposite as ESP, so the ESM highest on a list is the prevalent one... So doesn't that reverse the meaning of "Load After"? As said, confusing.

Criticism follows, don't take me wrong but.. If I try to do any of this within Vortex, I have to work without visual clues, since I see nothing visibly reflecting what I do. With NMM I could see the list of my ESPs and their order, simple and easy.

Hey in any case, I would appreciate any information!! Thanks!

[divotdog]

load after to overwrite. so if you want mod A to be the dominate file then load it after mod B

[Violence]

load after to overwrite. so if you want mod A to be the dominate file then load it after mod B

Thank you for the information, could you also tell me if this is universally true for both ESM and ESP? As an example which I mentioned earlier, in NMM it worked the other way around- You had to put the mod you wanted to dominate above of the others, instead of below like you would do with ESP. So in Vortex, does that translate into putting the mod that should dominate, to "Load Before"?

 

I hope my question makes sense!

[AugustaCalidia]

Criticism follows, don't take me wrong but.. If I try to do any of this within Vortex, I have to work without visual clues, since I see nothing visibly reflecting what I do. With NMM I could see the list of my ESPs and their order, simple and easy

 

 

If your game uses plugins, then open the Vortex plugins page. There you'll find all the information you want and more.

[AugustaCalidia]

 

load after to overwrite. so if you want mod A to be the dominate file then load it after mod B

Thank you for the information, could you also tell me if this is universally true for both ESM and ESP? As an example which I mentioned earlier, in NMM it worked the other way around- You had to put the mod you wanted to dominate above of the others, instead of below like you would do with ESP. So in Vortex, does that translate into putting the mod that should dominate, to "Load Before"?

 

I hope my question makes sense!

 

 

In Bethesda games it's universally the case that the "load after" .esp and/or mod wins. That is true for Vortex, for NMM, and every other mod manager that I know of.

[HadToRegister]

 

load after to overwrite. so if you want mod A to be the dominate file then load it after mod B

Thank you for the information, could you also tell me if this is universally true for both ESM and ESP? As an example which I mentioned earlier, in NMM it worked the other way around- You had to put the mod you wanted to dominate above of the others, instead of below like you would do with ESP. So in Vortex, does that translate into putting the mod that should dominate, to "Load Before"?

 

I hope my question makes sense!

 

 

 

The main focus of Vortex is more about loading Textures, meshes, and BSA BA2 properly, so let Vortex manage the ESPs, and ESMS and only do something about them if Vortex tells you there's a problem/conflict

There's no need to micromanage your plugins like you had to do with NMM

 

Same with the MOD part of the Mod, the textures, meshes etc, only fix things if Vortex complains about them by reporting a conflict.

[Violence]

 

Criticism follows, don't take me wrong but.. If I try to do any of this within Vortex, I have to work without visual clues, since I see nothing visibly reflecting what I do. With NMM I could see the list of my ESPs and their order, simple and easy

 

 

If your game uses plugins, then open the Vortex plugins page. There you'll find all the information you want and more.

 

I get that, but... "One is LoadOrder and the other is PlugIn, and they look almost completely identical" as I described. Of course my game uses them, but which one is the actual load order is what I'm asking. Thank you.

[Violence]

 

 

load after to overwrite. so if you want mod A to be the dominate file then load it after mod B

Thank you for the information, could you also tell me if this is universally true for both ESM and ESP? As an example which I mentioned earlier, in NMM it worked the other way around- You had to put the mod you wanted to dominate above of the others, instead of below like you would do with ESP. So in Vortex, does that translate into putting the mod that should dominate, to "Load Before"?

 

I hope my question makes sense!

 

 

In Bethesda games it's universally the case that the "load after" .esp and/or mod wins. That is true for Vortex, for NMM, and every other mod manager that I know of.

 

I mean, yes, but you do know that for example in NMM the ESMs that come before, win? So I was wondering if that is the case for Vortex, so in essence if for ESMs I should pick load before, to give them higher priority over other ESM... Hey, maybe I am not phrasing it right, I don't know, English is not my primary. Sorry.

[Violence]

 

 

load after to overwrite. so if you want mod A to be the dominate file then load it after mod B

Thank you for the information, could you also tell me if this is universally true for both ESM and ESP? As an example which I mentioned earlier, in NMM it worked the other way around- You had to put the mod you wanted to dominate above of the others, instead of below like you would do with ESP. So in Vortex, does that translate into putting the mod that should dominate, to "Load Before"?

 

I hope my question makes sense!

 

 

 

The main focus of Vortex is more about loading Textures, meshes, and BSA BA2 properly, so let Vortex manage the ESPs, and ESMS and only do something about them if Vortex tells you there's a problem/conflict

There's no need to micromanage your plugins like you had to do with NMM

 

Same with the MOD part of the Mod, the textures, meshes etc, only fix things if Vortex complains about them by reporting a conflict.

 

I would gladly let it handle ESP/ESM except it doesn't do so properly, I need certain things it insists should not be low my order, to actually be low. And I know that is the case because I've had this set up and I've used those particular mods. It does place Realistic Water Two to the bottom as it should, same for DSR, but I have others which Vortex insists shouldn't be too low. And some ESMs that need to take priority over others, don't. So Vortex's auto sorting is quite good but not good enough for me.

 

TLDR me asking for a way to manually set my load order, and you telling me I shouldn't do it, is not exactly a conversation pertaining to the matter ;3 But you're right that in terms of textures especially, it handles things nicely and obviously I do let it do its thing and it works. But that's not the question here.

[Guest deleted34304850]

if you have an esm that should be loaded before a certain other one - just make a load before, or load after rule. takes seconds and once set is done. i should add - you can only load before/load after another esm - dont try that for an esm/esp/esl combo thats gonna be painful

Edited May 11, 2020 by 1ae0bfb8