I have yet to experiment with that enough to figure it out! One assumes it has something to do with horses, but "mount" can have more than one meaning.
If you put this ESP before the Bashed Patch, then any Race record changes in the patch will overwrite your ESP. I would recommend placing it after the Bashed Patch and tell people not to select your ESP when building the Bashed Patch. Also, tell them not to carry over any changes from the Bashed Patch. Instead, from the mod ESPs.
Does Wrye Bash itself insert RACE record changes on its own into the Bashed Patch? I was under the impression it was just merging things from previous mods that it was capable of merging (plus injecting things you might specify in its settings, like the encumbrance multiplier, timescale, cell respawn time, max. resistance, etc. In Skyrim, none of these appear to pertain to races, though I think they did in the xEdit for Morrowind and maybe Oblivion).
Looking in my own BP, it contains zero RACE records. So, is there an actual issue, or just a theoretical one? I'm not entirely certain what the BP is capable of merging and "absorbing" into itself. Maybe it sometimes does have RACE records. Does yours? Why would WB not take this ESP as "the winner" in the mod list up until the BP, and use what it says when building the BP?
If people are merging mods with the bashed patch (which they shouldn't these days with Mator's merge plugins & zEdit tools) then there might be conflicts in the BP, but otherwise, there shouldn't be.
That said, I would stick with Merge Plugins Script, not the stand-alone Merge Plugins application. Unless it's changed its behavior semi-recently, it appears to "merge down" instead of up. That is, if your load order has A, then B, then C, and you're merging B and C, it'll change IDs of B to fit into C instead of the other way around. I've had poor results from the app version, especially when adding something into an ongoing game, but virtually never a problem with the script version (once I learned how to use it really well). MO users should probably hunt down the MO-patched version of it; it's in the Merge Plugins Script forum page somewhere). I think the issue it addresses is uncommon, but common enough to bother patching, though I forget the specifics. Something to do with paths that MO uses.
Merge Plugins script and standalone are deprecated and replaced with the zMerge module of zEdit. Issues should be reported on the github or Mator's discord server.
Thanks for this. I have only been modding for a year and a bit so while I know some stuff I have lots of holes in my knowledge. I use a smashed patch, should I load this after that? And for lord of LA, why not let wrye bash merge stuff I only use wrye bash for the merge and tweaks and let Mator Smash deal with the rest. Then of course I use xedit
The other thread about this here seems to suggest that putting it after the bashed/smashed patch is fool-proof, though most people shouldn't have an issue if they use it immediately before the BP/SP. I use it afterward, because I want absolute certainty about what the final race records look like. I found all kinds of mods doing stupid stuff like reverting Nord back to 2011 original, pre-Update.esm defaults, just to make a goofy hair color playable (and FIVE more mods after that one doing exactly the same thing, for another hair color, or eyes no one would really want to use, etc.). And another undoing everything Dawnguard does with vampires. And one clobbering half the stuff done by that Dragon Priests overhaul. And another reverting my own Bosmer height fix. And ... By the time the game started, virtually nothing was left of USLeEP's corrections, either. After I built my own end-of-load patch, it occurred to me that (as long as it contains no mod races) it would be useful for anyone skilled with TES5Edit.
cool I am really looking foreward to seeing myself how much gets changed. I am finally getting a much better handle on using xedit and knowing what I am changing. I would classify myself as an advanced novice when it comes to Xedit, and it has been a holy crap learning experience. I have allowed a lot of stuff to change USLEEP when I edit my patch, should I be looking more critically at that? Good Suggestions are always welcome.
Wrye Bash merges things it shouldn't, just that it can. It doesn't adapt scripts for the merged mods, doesn't rename assets if needed, causes problems with DynDOLOD, etc. It's a very, very poor man's merge plugins/zmerge.
If you're using mator smash you probably don't need a based patch at all. Just set everything to smash.all and press go. Then fix the smashed patch in xEdit.
However, this probably isn't the best place to discuss all that. I'd recommend r/skyrimmods on Reddit and/or its discord server.
Give Feedback
15 comments
Looking in my own BP, it contains zero RACE records. So, is there an actual issue, or just a theoretical one? I'm not entirely certain what the BP is capable of merging and "absorbing" into itself. Maybe it sometimes does have RACE records. Does yours? Why would WB not take this ESP as "the winner" in the mod list up until the BP, and use what it says when building the BP?
And for lord of LA, why not let wrye bash merge stuff I only use wrye bash for the merge and tweaks and let Mator Smash deal with the rest. Then of course I use xedit
If you're using mator smash you probably don't need a based patch at all. Just set everything to smash.all and press go. Then fix the smashed patch in xEdit.
However, this probably isn't the best place to discuss all that. I'd recommend r/skyrimmods on Reddit and/or its discord server.