Vortex thinks a non-Master is a Master

[tomtheclone]

Presumably, this is related to my earlier post: https://forums.nexusmods.com/index.php?/topic/7534016-vortex-keeps-putting-my-bashed-patch-in-the-middle-of-the-load-order/

 

Vortex version: 0.17.8

 

Game: Skyrim SE

 

Number of mods installed: 52 plugins (not counting the official ones)

 

OS: Windows 7 Pro

 

Problem:

 

For whatever reason, Vortex wants to put my Bashed Patch (in the Dynamic Patch group) before my bashed_patch_patch plugin (which I put in the late fixes and changes group). To "fix" this I made a rule explicitly telling Vortex to place my patch after the bashed patch.

 

I then look a closer look at the error and saw that the problem stemmed from Vortex thinking the plugin was a master. So I open it up in SSEEdit.

 

Indeed, it is not flagged as master. In case it matters, its only flag is ESL. I'd upload the plugin, but its not allowed.

[HadToRegister]

OK, so what's the difference between your Bashed Patch, and your "Bashed_Patch_Patch?

You can't sort ESLs

[rmm200]

ESL files are also known as Light Master files.

This discussion may help you

https://steamcommunity.com/app/489830/discussions/0/3276824488728505237/

[tomtheclone]

OK, so what's the difference between your Bashed Patch, and your "Bashed_Patch_Patch?

You can't sort ESLs

 

The Bashed Patch is what was generated by Wyre Bash. The BPP is a manual patch to clean up the mess that is the auto-generated bashed patch (I merged records where appropriate).

ESL files are also known as Light Master files.

This discussion may help you

https://steamcommunity.com/app/489830/discussions/0/3276824488728505237/

 

I see. Kind of. Can't deal with it right now.

 

Thanks.

[Tannin42]

If the file is named .esl then it's always a master and a light plugin.

If it's named .esp but has the "light" flag set in the header (and not the master flag) then it's not a master.

 

I'm fairly certain that Vortex (recent versions at least) deal with that correctly.

[tomtheclone]

If the file is named .esl then it's always a master and a light plugin.

If it's named .esp but has the "light" flag set in the header (and not the master flag) then it's not a master.

 

I'm fairly certain that Vortex (recent versions at least) deal with that correctly.

It does handle .esp with ESL flags correctly, as well as .esl files with both ESL and ESM flags. However it fails with .esl files with only the ESL flag. Admittedly, .esl files aren't suppose to lack ESM flags, so I can understand Vortex not being set up to handle that case.

 

Please see: https://forums.nexusmods.com/index.php?/topic/7534016-vortex-keeps-putting-my-bashed-patch-in-the-middle-of-the-load-order/ for more info.

 

Don't you just love pathological examples?

[Pickysaurus]

If an ESL without the ESM flag is an invalid plugin then I'm not sure it's really an issue?

[tomtheclone]

If an ESL without the ESM flag is an invalid plugin then I'm not sure it's really an issue?

Which is what I said before. This is a pathological example, but those are interesting for their own reasons. Sure, there is no reason to spend time fixing a bug which only effects idiots, but (and forgive me for sounding presumptuous) sufficiently robust code should be able to handle this. Perhaps this bug might manifest itself later, and this example might be useful. In the meantime, it certainly isn't worth developer time.

[Tannin42]

This is not a bug. If a file has the .esl file extension then it is a master no matter what the flags say.

File extension beats flags. You can't have a .esl file that isn't light or isn't a master. And you can't have a .esm file that isn't a master. The flags are only really relevant for .esp files.

[tomtheclone]

 

If an ESL without the ESM flag is an invalid plugin then I'm not sure it's really an issue?

Which is what I said before. This is a pathological example, but those are interesting for their own reasons. Sure, there is no reason to spend time fixing a bug which only effects idiots, but (and forgive me for sounding presumptuous) sufficiently robust code should be able to handle this. Perhaps this bug might manifest itself later, and this example might be useful. In the meantime, it certainly isn't worth developer time.

 

 

 

This is not a bug. If a file has the .esl file extension then it is a master no matter what the flags say.

File extension beats flags. You can't have a .esl file that isn't light or isn't a master. And you can't have a .esm file that isn't a master. The flags are only really relevant for .esp files.

 

I wasn't referring to the problem stated in the title, but rather that the entire sorting algorithm falls apart. Yes, treating an .esl as a master is the proper behavior. The entire sorting algorithm falling apart is not. Its also not worth anyones times.