Jump to content

Recommended Posts

MCM is bugging out and won't save my preferences now that I've recently breach the 255 LO limit. I looked up toots on Bash Patches and installed Wrye. After many videos, pictorial pdfs, and the main webpage readme for WB I can't find a toot on what the next steps are after successfully creating a bash patch. Do I manually deactivate the merged mods? What if I install new ones, do I rebuild the same patch or make another one and put it beneath the first in the load order? I wish I knew what to do. I can hear my synapsis popping.

Link to comment

If you change your load order by removing plugins in the middle of a game it may cause you issues later, especially if one of them is a dependency for another mod.  Best is to make your bashed patch at the beginning of your game and delete the plugins then.

 

What I usually do when merging mods (before starting a new game) is to make my merge or bashed patch, then deactivate the plugin (esp file) in the right pane (using MO2) but leave the mod itself activated in the left pane in case there are meshes/texture/something else that the patch still needs.  Not sure if that's proper or not, but it works.

 

If you add mods and make a new bashed patch, first make sure you reactivate the mods you merged and de-activated the plugins for.  Then make your new bashed patch.  Then de-activate (but not delete) the plugins that were merged (again).  After activating your new bashed patch, delete the old one.

Link to comment

In Zmerge one can include resources, likes meshes, textures.

Then you don't even need the mod activated on left side. 

Can be deleted.

 

mid game I would not recommend a new bash, even not a new sorting with loot.

Better place the mods below the bash. 

References might change and ctd the old saves.

Better way to stay below limit is esp-fe most of the mods, like clothing, followers and so on.

 

Link to comment
  • 4 months later...

Sorry I just saw this. I was playing Valheim back in February.

 

You can have more than one Bashed Patch in the same load order. That's why the functionality to build another BP is in there. 

 

The easy way to get around 255 masters in the BP is to split your patchers out.

The technique I use is to run half the patchers in one patch, and the other half in the other.

 

Here's an image of how you'd do it:

2030189866_Bash-splitpatchesupbypatchers.png.f8ff11d31c65d246fec61f8d4de3b47b.png

 

 Build your first Bashed patch with only the patchers in the Green box checked then create a second Bashed Patch (right click -> Files -> New Bashed Patch) with only the patchers in the blue box checked.

 

Since most mods won't have records covered by all the patchers,  you should have way less than 255 plugin masters per Bashed Patch.

 

Even if you do manage to hit two BPs with 255 masters you can keep going and keep splitting like so.

 

Bash-multiple-patches.jpg.e74b22308ee71f18a8b60814d008b9b9.jpg

 

Hope this helps.

 

 

 

 

 

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. For more information, see our Privacy Policy & Terms of Use