Jump to content


Wrye Bash question

  • Please log in to reply
1 reply to this topic

#1 InsaneShad0w92



  • Members
  • 6 posts

Posted 11 September 2018 - 10:04 AM

Is there a way to ensure that bashed patch doesn't include plugins that are disabled prior to building the patch? On SE bashed patch I ended up having several duplicate MCM menus, like a matter of time as bashed patch required that as a master but it was also in a merge. 

  • 0

#2 Shadriss


    High King

  • Members
  • PipPipPipPipPipPipPipPipPipPipPipPip
  • 1,123 posts

Posted 11 September 2018 - 06:14 PM

To make sure I understand:


1) Merged plugins, one of which contained a mod with an MCM.

2) Turned off esp in the right pane, then ran WB.

3) Created Bashed Patch, which then merged in and now requires the mod that you previously merged.


If the above is what you meant, then here's what you do:


1) After merging, double click the mod containing the esp you want to avoid merging into Bash.

2) Go to the Optional ESP tab at the top.

3) Move the ESP file from Active to Optional. This will remove the esp file from the RIght Pane (and your load order entirely).

4) Run WB and rebuild your Bash. Problem should no longer exist.


This is one of a couple ways to do it, but the primary thing here is to completely remove the offending ESPs from showing AT ALL in the right pane - to my knowledge there is no way to prevent disabled esps from being analyzed by WB... only ways to keep them from appearing in the Right Pane instead.

  • 0

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users