How to add bash tags to a mod w/o Wrye Bash?

[7531Leonidas]

I am currently running a mod list of over 2000 mods (a lot of graphics mods are in there), and the latest version of WB started bashing things it had not on the previous version I had.  I currently have eight mods that need to have records placed in the bashed patch (I make all such adjustments in SSEEdit) that are not picked up as masters for the bashed patch.  When I add the records, SSEEdit requires me to add each one as a master to the bpatch.  I run WB as a tool in Vortex.

1.  Am I right that I will need to add bash tags to the eight mods to be able to manipulate/add their records to the bashed patch?

2.  How do I use SSEEdit to add bash tags to the eight laggards?  (I have the list of tags for Skyrim from the adv. bash readme.)

I got very upset when I found out that editing the bashed patch w/these eight in xEdit caused the patch to no longer recognize almost all of my edits, due to the reordering of masters.  That's about 1-1/2 hours plus of work.  A real catch-22.

Thanks, all!

[IsharaMeradin]

If you run WB as a tool in Vortex, you can still add the bash tags there.  You should also be able to look at any plugin with bash tags in the description field and edit the description field of your plugin to be the same way (with relevant tags of course).  

If you are manually editing the bashed patch to include other records, those plugins will need to be added as master files, but they won't need to have a bash tag added to them.  Only reason to add bash tags is to ensure that certain data is carried over into the bashed patch.  And if you do add bash tags, the bashed patch will need to be rebuilt to ensure that the tags work correctly and that will wipe any manual edits already done.

Consider doing a separate patch for your eight mods and putting bash tags on that patch only.  At least this way if the bashed patch doesn't pull it over correctly, you can remove the override records from the bashed patch and let your patch handle the records instead.

[7531Leonidas]

Thanks, IsharaMeradin.  I am a bit confused, b/c upon further inspection, now that I know where to look, at least two of my eight have bash tags, but are not included as masters in my bashed patch.  I guess that my question should rather be "How do I change/add which mods are used as masters by WB in the forging of a bashed patch?"  I had come to believe that bash tags were needed to do so, but those two have confused me a bit.  Maybe they are missing a tag for the info I want/need to be included?

[radiusrsatti]

Masters are only added if the plugin in question adds new records generated in that plugin. IE, if the record originates in Skyrim.esm, only Skyrim.esm is added as master, or if the record originates in KSHairs.esp, KSHairs.esp is added as master. Any changes to existing records, say in a plugin that only edits food restoration values, the edits will be forwarded to the patch, but only the originating plugin (such as Skyrim.esm) will be added as Master because no new records were added or referenced by the food plugin.

Bashing is good for a cursory patch, but it only covers a few record types. If you would like to do a more comprehensive Bashing, for ALL record types, you should look into Mator Smash, which I think makes bash tags irrelevant, but will require manual editing to ensure your desired values (if multiple plugins edit same records) are forwarded correctly. IE, my setup of almost 3k mods requires 21 Smash Patches to cover every record edit in my load order (due to 255 Master limit per plugin). With a 255 master limit, and because WB only creates 1 plugin for multiple record types, Wrye Bash may not cover all conflicted plugins. To my knowledge, it does not create multiple patches.

 

 

 

Edited 6 hours ago by radiusrsatti