Striker879

I normally download the latest masterlist from the BOSS Masterlist page when I notice an update has been released. There are instructions somewhere back in the mod comments on that page concerning how to get the masterlist updating to work automatically but I had no luck getting it to work myself. Manually updating the masterlst really isn't a big deal for me (a simple download to a folder, extract and then copy/paste ... took me as long to describe here as it takes to accomplish). I can't tell you anything about LOOT. I use BOSS because BOSS was the tool to use before LOOT, and mhahn123 is maintaining it so it is again the tool to use for Oblivion in my opinion. I know I have seen enough LOOT users with problems that were resolved by switching to BOSS to keep me firmly in the BOSS camp. I can't say much about your parsing errors either. Perhaps try asking in the BOSS Masterlist mod comments. Can't say if it is or isn't related to a "superpak" problem. I know I have seen it reported that often superpaks have edited ESPs that don't work properly. I couldn't say if that is the case here as you won't see me within a mile of a superpak download. Probably the best place to get support for a superpak is where ever you downloaded it (I know ... good luck with that ... another reason to learn how to mod rather than look for some "easy" route).

In my opinion BOSS is the tool to use for Oblivion load order management. If you run into a mod (usually a fairly new mod) that isn't on the masterlist you can set up a user rule for it and report it to mhahn123 in the mod comments here and it will be added to the masterlist.

If the race isn't HGEC compatible then HGEC won't work with it. Check your race mod for recommended clothing/armor replacer.

So what armor/clothing replacer are you using?

Download the OMOD file to a folder. Double left mouse click on it and OBMM will open ... if OBMM doesn't open you haven't installed OBMM correctly.

Should be OK if you use the EVE armor/clothing replacer ... vanilla clothing/armor will display different anomolies for different races and different clothing/armor worn. HGEC and vanilla don't use the same body texture mapping at all and are not compatible with one another. You want HGEC, you need to go all in HGEC.

OMOD Ready isn't the same as a premade OMOD. OMOD Ready means the files and folders are arranged in a manner that OBMM can understand, but doesn't necessarily mean there is a script to walk you through the installation. You will notice those downloads I recommended download with the file extension OMOD, and OBMM will start and run the installation script no matter where you have them downloaded on your computer when you doube click on te downloaded file (even downloaded to your desktop, though that is not a location I recommend). I doubt that the other HGEC download has an equipment replacer (sounds like the old original HGEC download to me, that was somewhat recently updated to include a NMM option). Like I said, if you don't mind mismatched body textures while wearing vanilla clothing/armor then go with one of the old outdated HGEC downloads that doesn't include everything, otherwise go with EVE.

Use EVE HGEC Eyecandy Variants Expansion for females and RobertMaleBodyReplacerV5 for males. Both come with an option to download as a premade OMOD (top listed download for EVE, fourth down from the top in Roberts male) and will walk you through the selection process. Install the included armor/clothing replacer that comes with each unless you prefer to see weird stuff on exposed skin areas (see the thread started in this section by trrrf for an example of not using the armor/clothing replacer).

What body mods are you using? Is your character male or female? - Edit - Look here for more info and links.

The authors of EVE marked those ESPs with a No Merge bash tag, instructing Wrye Bash to not deactivate the ESPs and merge their contents into the bashed patch, but instead to leave the ESPs active and then Wrye Bash will merge some of the ESP records into the bashed patch (same as any other mod that has stuff that can be merged into the bashed patch but not deactivated). Wrye Bash believes that all of the changes made by those ESPs can be safely merged into the bashed patch and the ESPs deactivated so it gives you the report. The only compelling reason to do that is to save ESP slots for other mods (but deactivating them won't be enough if you are at the ESP limit ... they will need to be ghosted as well). Bottom line ... follow the mod author's advice unless you are pushing the 255 ESP limit. The only thing I know about "superpaks" is I see plenty of advice from knowledgeable people who say to avoid them. I am far too pick and choosey to use anybody else's "use all these mods" advice/superpak. I use exactly the mods I have researched and chosen, and only those mods.

There is a tremendous amount of info to get your head around when you start out. It took me quite a while to piece it all together ... you are well on your way.

Nothing jumps out at me in your load order, but I'm far from being an expert on load order and conflicts (which is why I use BOSS before I bash).

One of the reasons I've resisted using Pluggy and any Pluggy dependant mods is it's reputation.

Yup ... the inside the sewer exit save should be free of all mods except those you would "never play without". My own has only OBSE installed along with Blockhead and OCO v2. Any new character I create from that save can use a completely different load order than my current character without using any tricks to "clean" the save. Your outside the sewer save is the one you use to test mods (often my testing sessions are long enough that I will make further saves, and those saves will then become dependant on the current load order while I build my base load order). Once you get your load order to your liking you can either continue your character from one of those subsequent saves or use the outside the sewer save and delete/archive your testing saves ... all depends on what stuff you did while testing, and whether or not you want that in your save line.

The way the Installers tab works is quite similar to load order ... Wrye keeps track of what files all mods listed in the Installer tab install, and when two or more mods install files to exactly the same folder path and same file name (i.e. an overwrite) the mods involved that are lower in the Installers tab list than the other "conflicting" mods will "win" the conflict. Another way to think of it is Wrye Bash installs the mods from the top of the list down to the bottom, so the lowest on the list wins all conflicts. You can drag mods higher or lower on the list and see how their new position changes what is reported as far as overwrites. Sometimes the overwrites aren't a probem (mod A overwrites mod B's files with ones that are identical) and other times you will need a certain mod to "win". Anneal is for when you decide to uninstall a mod that was involved in an overwrite battle. If it wasn't a "winner" in any battles it won't make a difference if you anneal or not (the winner's files will still be there). However if the mod you uninstall was one of the "winners" what anneal will do is put back the lowest listed "loser's" files (so if Mod A, mod B and mod C all changed the same file and they were listed from top to bottom in the Installers tab mod A then mod B and then mod C, mod C would win ... if you then uninstall mod C anneal will replace mod C's file with the one from mod B and mod A will still be the "loser"). Mods overwriting other mod's files isn't super common except in certain classes of mods. The ones I call "replacer mods" is one of the spots you will find overwrites commonly reported (there can only be a single replacement for the vanilla female iron cuirass for example and it will need to be in exactly Data\meshes\armor\iron\f\cuirass.nif ... if ten mods in your load order all want to change it only the one lowest in the Installers tab list will be displayed in game). If you only installed a single mod that wanted to change the female iron cuirass no overwrite would be reported.

If you ever get to zero crashes you will join a club that currently has zero members.

Here's another tip ... make a save right before you exit the tutorial dungeon (where you can see the sewer exit in the distance but before you get the character finalization menus). Exit the sewers and make another save (not overwriting the first ... and never use quicksave, it's a known corrupter of save games). The before the sewer exit save will come in handy when/if you decide to start a new character but don't want to redo the tutorial. The outside the sewer exit save is for testing mods, and can be used to continue your character after you finish getting your base mods installed. A good habit to get into is never overwriting saves. It gives you a fall back position when you wind up with a save that gets all bunched up and won't load anymore (simply revert to your newest good save). Either delete old saves or archive them in another folder when your save folder starts getting full (100 or more, mine will sometimes get 400 or 500 saves before it gets archived).

What are you using to sort your load order? Right off the bat two things pop out at me ... Maskars Oblivion Overhaul.esp should be below your bashed patch plus 1em_Vilja_OCOV2_By_jet4571.esp should be below Oblivion_Character_Overhaul.esp (as well as below 1em_Vilja.esp, which it is). I recommend BOSS to sort load orders for Oblivion. Are you actually using the bashed patch? I ask because as far as I know MOO won't work properly when loaded above the bashed patch as once you build the bashed patch with it above then all of MOO's leveled lists don't work.

There we go ... and the old dog learned a new trick to boot.

Make sure you close Wrye Bash completely and then restart it after you have installed BOSS. The Run BOSS button should be in the row of icons that starts from the very bottom left corner of the Wrye Bash window. You could also try right mouse clicking in that area and see if BOSS gets listed in that right click menu ... if it's there but doesn't have a tick mark beside it you shoud be able to just click on it to get it ticked (though I don't remember needing to do anything like that ... maybe because I'm still running WinXP and so don't have anything interfering with me using my machine).

And yes, you will activate the bashed patch after building it ... I think Wrye Bash will even prompt you to activate it.

Having some mods already installed shouldn't affect getting BOSS to show up in Wrye Bash ... you could have a whole bunch of mods instaled before installing BOSS and it would be OK. Just work on finding out if BOSS will run from the desktop and then Wrye Bash will find it.

Unfortunately all I have until I return home is an Android tablet ... my gaming machine is about 9 hours drive away from where I'll be the rest of the summer. It's been quite a while since I installed BOSS myself, but wasn't there an EXE file you could run to install it? If I remember correctly after I installed it Wrye Bash found it automatically and displayed the BOSS button. Could be you need to run BOSS once from either the desktop or Start menu ... I seem to remember something about chosing which games it would run for (though in my case I only have Oblivion so it was a short list).

I wouldn't suggest installing a bunch of mods before running BOSS and building your bashed patch. The best way is to add a single mod, run BOSS and rebuild the bashed patch and then test thoroughly in the game. That way you will know how each mod you add affects how the game runs, and if you run into something that causes problems it will be trivial to figure out where to start troubleshooting. If you add a dozen mods and then your game runs like crap or crashes it will be much much harder to figure out which mod was the culprit.

Here's an explanation of what the bashed patch is. What Wrye Bash does when it builds/rebuilds your bashed patch is it resolves all of the conflicts between the different mods in your load order. It uses something called bashed tags (most commonly added by mod authors to tell WB what to do, but you can add bashed tags yourself) and load order to determine which changes from which mods will "win" those conflicts. There are many mods that simply won't work (or work correctly) without a bashed patch. The bashed patch is then put at or very near the bottom of your load order so that the combined changes it contains will "win" in the load order. Some mods will require to be placed below the bashed patch to work (e.g. Maskar's Oblivion Overhaul), but in general your bashed patch will be right at the bottom of your load order.