TESEDIT vs WYRE BASH

[BooneoftheWasteland]

So I'm back to a game of Oblivion round 3 after a year of FO3 round 4. However this time around with FO3 l braved the world of FO3Edit and, I feel, made a pretty stable, and covered my best gaming options, game by making deep copy override patches to get things like Project Beauty to work and some other conflicts I drag'n'dropped to the patch.

 

Well back to OB and I'm running FCOM overhauls and using all the usual suspects like obse obmm, pluggys etc and now including BOSS and with BOSS it's the first time using. Then I remembered Edit and forgot that OB has one too, well became quite comfortable with it's use with my last run with FO3 and just downloaded it for OB last night.

 

I'm still adding mods and I haven't left the prison part yet, usually after that I load weather and other world improvements. Anyhow things are running and 'feeling' stable but then I thought about taking a look into TESedit and I was a little surprised by the amount of conflicts. For the most part it's overrides without conflict, purple text on yellow backgrounds, but there were quite a few red conflicts, and in some cases the bashed patch, I feel, selected the wrong options i.e and Oblivion.esm script over a OOO script.

 

So being a newb at this, I'm pretty perplexed at what may be left out of the game I'm playing through bash. If I download all the mods I want to use, would it be best to create patches through edit drag and drop? Or put all faith into Wyre Bash?

 

Any thoughts?

[Tomlong54210]

You just do not know how to use Wrye Bash yet. Oblivion scripts would when, if you have a mod merged that loads after OOO and contains the Oblivion scripts. TES4Edit and Wrye Bash serve very different purposes.

 

 

Edit: I suggest reading through Bash's ReadMe to learn more. If you are a "hands on" kind of person, you should try deselecting mods in certain section to see how the contents of the bashed patch are affected. Whenever you check the bashed patches changes in TES4Edit, you should load the plugins that have changes merged or imported into it; otherwise, unless you are familiar with its rules, you will not know why it contains certain version of records instead of others. You are just analyzing it the "wrong" way.

 

Rebuild FCOM Bashed Patch <-- guidelines

[David Brasher]

I am more of an empiricist. I have seen so many bizarre things. So many illogical glitches that break all the rules. Some experts are good at reading the reports and thinking about mod interrelations and utility program usage, but they can still slip up. I recommend just installing your mods one at a time with several hours of play-testing between mod installations. Then when your game glitches (which it eventually will) you can blame the last mod you installed, and feel fairly confident that you are blaming the correct culprit.

[BooneoftheWasteland]

Yeah I don't know Bash well, heck I don't know FO3edit well either lol even though I've put hours working with it. That's a great link. I'll take a look.

---------------------

I sort of install mods piece meal but rarely play for hours in-between, it's usually limited.

[Tomlong54210]

Yeah I don't know Bash well, heck I don't know FO3edit well either lol even though I've put hours working with it. That's a great link. I'll take a look.

 

I sort of do mods piece meal but rarely play for hours in-between, it's usually limited.

 

No worries. It is nice to know that you actually investigate your LO that thoroughly, and there are exceptions among the bashed patch importing rules, etc. Ask for clarification when you need it. (Most of the complicated importing is related to cosmetic mods.)

 

 

Edit: wording