This may be a blasphemous question round these parts but are there other tools that do a similar job to Wrye Bash? I have never managed to use Wrye bash properly. I have always found it too complcated and difficult to use. Most of the features of Wrye bash I don't need but I would like something that helps mods works together better. Crucially I want something that is easier to use than WB. I do use BOSS for what it's worth. Thanks for comments.

http://tesnexus.com/downloads/file.php?id=35230

But if you *really* insist on not using Wrye Bash (despite the fact that this means certain awesome mods will ebout of bounds, installation and uninstallation will be far worse to deal with, and the more mods you add/adjust/subtract, the worse things will get on top of that)...

There's this: http://tesnexus.com/downloads/file.php?id=2097

Or, my preference, if you're going to use that type of thing for organising mods: http://tesnexus.com/downloads/file.php?id=32277

Hope that helps!

You could try OBMM, but I honestly don`t recommend it, because once you get used to Wrye Bash and its unique features you won`t think about returning to any other mod manager and believe me I was overwhelmed and frightened off by the possibilities of Wrye Bash too for quite some time. Sure you can use OBMM if you only have a dozen non-conflicting mods, but as your mod setup gets bigger and more complicated you will be happy having Wrye Bash. I would suggest to read the comprehensive WB pictorial guide by alt3rnity. I started with those guides.

Not using Wrye Bash is not a problem as long as you accept two things:

1. There are some mods you can't use.

2. You have to limit the type and number of mods you use.

Learning the intricacies of mod conflicts is arguably harder than using Wrye Bash (and reading the BOSS report).

I wholeheartedly recommend using Wrye Bash. Just yesterday I finished moving all my mods over from OBMM to BAIN and I couldn't be happier.

OBMM = Flying blind. After being burned by OBMM (I had mod resource files overwritten causing CTDs and OBMM couldn'tt help me know what was going on) I decided to just move to BAIN.

BAIN is simpler to use than OBMM. OBMM just gives the illusion of simplicity. With BAIN I know exactly how my mod files are being used thanks to its extremely powerful Install Order feature, I can configure which mod overwrites what and I don't ever have to, for example, uninstall a mod because it needed to overwrite another mod's files.

Example:

Animated Window Lighting System requires that you have Qarl's Texture Pack 3 installed so it can overwrite some of its files. If you install AWLS and then decide to try out QTP3, with OBMM you have to uninstall QTP3 and then install AWLS.

With BAIN you just put QTP3 to be "lower" than AWLS in the BAIN Installation Order and you install it. And if BAIN complains about any files being mismatched afterwards for AWLS for example you can simply right-click on AWLS and select Anneal. Done. Problem solved.

Breton Paladin already linked the Wrye Bash Pictorial Guide which is a great tutorial but theres also the Wrye Bash website itself that you can use as a reference along with the Pictorial guide.

So you have your tutorial and your reference. If you stick with it, it'll pay off. The earlier you start with BAIN the less mods you have to eventually transfer over to BAIN if/when OBMM finally bites you in the ass.

(Tutorial) Wrye Bash Pictorial Guide: http://tesnexus.com/downloads/file.php?id=35230
(Reference) Wrye Bash website http://wryemusings.com/Wrye%20Bash.html

Oh and like Wetblanket said, some mods _require_ Wrye Bash's Bashed Patch feature to even work (like the best weather mod out right now All Natural). All the more reason to stick with Bash...

OK thanks for the advice and links. I was hoping there was a simpler more convenient alternative to Wrye but I guess not. I will see how far I get with Wrye bash.

Don't worry about using all the functions at first. Just get comfortable running WB and using it to activate your mods. You can still use OBMM to install them if you prefer. You may not even need a Bash Patch until your mod list grows a bit. If you run All Natural, you will need a Bash Patch, but AN has instructions for building the patch.

Just keep at it. It's not that complicated once you've played with it for a while. Bash is the only thing that will get mods that modify the same leveled list entries, for example, to work together instead of overriding one another. Not to mention it's required for stuff like All Natural, and I wouldn't ever play without All Natural it's so great.

Also, I use both OBMM and Bash. I sort mods with OBMM as well as use a couple omods, and then use Bash mostly to import and merge mods into my Bashed Patch. You don't have to use Bash to sort and activate mods if you don't want to, but there are some things that you can only do with Bash.

For installation, you can use OBMM. For some of the utility functions (ABomb counter reset, potion reweighing, spell deletion and some others), there are alternatives. For things like making an extensive load order work properly, there's no alternative. For using mods like All Natural or Item Interchange, there's no alternative. For having all the numerous functions in a single "box", there's no alternative.

Vac

Speaking as someone who wasn't a fan of Wyre Bash..found it to be nothing more then a headache and I stayed away from it as much as I could each & every time I could..I freaking hated the thing.

However it was mostly due to all you had to do to get it running. Install this do that..man it was hell. But it wasn't the program it was me. When I finally found the Optional files section of wyre bash on the nexus & found a version where you didn't have to do much installing other then copy files into their respective folders..well my life has gotten alot simpler.

So now like most others I praise the Bash!

Being serious thou..check http://tesnexus.com/downloads/file.php?id=22368l

& dl the 1 under Optional files. Trust me..it's as painless as it can get.

Uh... it's not at all complicated, even without resorting to a standalone version.

You install the Wrye Python package from that link. Then you install the Wrye Bash package from that link.

Done.