To Everyone whose mods use .esp files marked as masters

[BlazeStryker]

Have you ever known someone whose load order only goes to EE but can't get a bashed patch or even a CRC calculation from Wrye Bash?

 

You might...

 

You see, Wrye Bash simply does not care if an ESP file is actually a master or a light master like the Creation engine or the mod managers do. It lists them as esp files.

 

To Wrye Bash, my aforementioned list is actually well past FF, even if the Nexus and the game itself disagrees.

 

Barring a long needed overhaul of how Bash handles file formats (and, God help us, actually becoming capable of merging Fallout 4 mod files) the only sane solution is making those mods "marked as masters" into actual .esl or .esm format.

 

It's what it is.

[WHITELION1284]

Honestly I, for one, am so tired of Wrye Bashe's BS. It has several uses but it is so finicky, so counterintuitive and expects everybody to jump through it's hoops and use it's flags that, honestly? It's more trouble than it's worth.

[pra]

ESL-tagged ESPs seem to be a good solution for small mods, especially settlement mods: they contain less than 2k forms, and must be able to be loaded after ESPs.

If some tool doesn't actually support them, tough luck. The most I'd do here is put a notice on the mod description page that the mod is not compatible with the tool in question.

 

And, you'd probably be better off removing the ESM or ESL flag from the file than actually renaming it, if it bothers you. Not only is the filename important to some mods (any mod with SMM support, for example), true ESLs will always lose any mod conflict. And, especially in the case of settlement mods, you want them to win. And, settlement-related again: ESLs cannot break a cell's previs.

 

In general, if Wrye Bash doesn't get updated, you'd be better off switching to some other tool. Maybe there is an xEdit script which can do whatever you use WB for. xEdit has full ESL support.