Merged and bashed patches

Post » Fri Sep 27, 2013 6:16 pm

I thought I have a decent understanding but I am starting to read posts that caused me to pause...do I really know what I thought do? For those with better undertanding...please correct me or I will lose my mind...

Wrye Bash created Bash Patches is for

+ ESM / ESP resource and conflict management (I treat them as indexing in database terms)

+ Global setting (e.g., timescale and arrow recovery rate) changes

+ Content tagging that helps with resource / conflict management

+ (limited) plugin merging into Bash patches

+ Level lists merging

- not used for compatibility patch creation

- not suited for esm / esp content merging (e.g., merging multiple weapon mods into one)

TES5Edit created Merged Patches

+ Conflict resolution and content merge (e.g., merging esp with NPC face record with esp with NPC quest records)

+ creation of compatibility patch (e.g., "Copy as override info" command)

...can someone with deeper understanding tell us when to use Bash Patches and when to create TES5Edit patches?

Thanks in advance

User avatar
Kate Norris
 
Posts: 3373
Joined: Mon Nov 27, 2006 6:12 pm

Post » Fri Sep 27, 2013 11:56 am

I only use one, the Bashed Patch. For me, I prefer that I can use just one patch. I also don't have a ton of mods, so more mods could drive a need for both patches. I can merge face and NPC mods with the Bashed Patch. I have never needed a compatibility patch, other than ones provided by the mod authors.

You can always try one or the other or both on a test save and see what gives you the mod mix operation that you want and the best stability. Note, a screwed up patch won't even let the game launch, so the worst problems are quickly discovered.

You also need to be real careful as to what you add to each patch if you use both of them as they can do the same things and I am not sure about all the weirdness that would introduce.

User avatar
Jessie Rae Brouillette
 
Posts: 3469
Joined: Mon Dec 11, 2006 9:50 am

Post » Fri Sep 27, 2013 2:05 pm

You have down pat, though I'm sure there are more uses in each tool.

FYI - I'm pretty sure the limited mod merging feature of BASH applies ONLY to mods that change ONLY game settings (GMST).

Edit: added "I'm pretty sure" above.

User avatar
michael flanigan
 
Posts: 3449
Joined: Thu Jun 14, 2007 2:33 pm

Post » Fri Sep 27, 2013 8:52 am

Does a bashed patch merge formlists, say, llike adding custom voicetypes to a vanilla NPC Voicetypes Formlist used by shared responses?

Say I add my new voicetypes to the vanilla formlist.

another mod author does the same for their mod to the same vanilla modlist.

Will a bashed patch merge the formlist entries so my custom voicetypes and the other author's custom voicetypes are all now in the [formerly] vanilla voicetype formlist?

User avatar
CHARLODDE
 
Posts: 3408
Joined: Mon Apr 23, 2007 5:33 pm

Post » Fri Sep 27, 2013 4:56 am

@PetPet - I think you've got the basic ideas down. The only thing that I'd add is that AFAIK, Bash is better for dealing with leveled lists, because a lot of it's early functionality (previous games) was focused on that.

The TES5Edit merge option is kind of a happy coincidence. TES5Edit wasn't intended for that, but it just happens that it can do it pretty well (and people have jumped in to focus on and improve that feature).

I'd say that a Bashed Patch is a requirement for any large-ish load order, while a TES5Edit merged patch can help to improve stability or (with careful editing and some risk) entirely merge plugins together.

I have patches from both apps, and it's been working great for me.

User avatar
LittleMiss
 
Posts: 3412
Joined: Wed Nov 29, 2006 6:22 am


Return to V - Skyrim