GUIDE Wrye Bash Guide

[z929669]

The Beta Wrye Bash Guide to STEP Installation is available

on THE WIKI

 

Based on the advice I received from users here, I will be asking TC to host on his site if he wishes. I will also host right here on the STEP wiki site when final. It is not yet final, but I will make it so once we have a fully compatible BOSS-Wrye Bash implementation to support Skyrim v1.5.

[peppergomez]

Thanks for the tip

[peppergomez]

That didn't seem to work. All those mods are still listed after the Bashed Patch in the Mods load order.

 

I noticed that I got Python Mergability messages that some aren't mergable:

 

ORM-Avak.esp:

- Unsupported types: NPC__, OFTF, TXST. New records in blocks: ARMA, ARMO

 

Manny Lantern Caretakers.esp:

Has BSA archive.

Unsupported types: CELL, NAVI, NPC___, OTFT, PACK, QUST, SCEN, SPEL, WRLD

 

MORE SALT PLEASE:

--Dragonborn addon esp.:

Unsupported types: CONT

 

MVABasic.esp:

Unsupported types: NPC___, WRLD

 

(same for MVARorikstead)

 

MVALVERSTEAD.esp:

Unsupported types:WRLD

 

NonEssentialChildren:

Unsupported Types: FURN, KYWD, QUST, RACE

 

 

 

 

 

 

Traps Make Noise was marked as mergable, so I have no idea why it's still appearing after the Bashed Patch. The order of the mods in Wrye Bash Mods column is signicfant I assume, with Bashed Patch needed to come last?

 

Any assistance with the above issues would be much appreciated. Thanks.

[Kelmych]

If the Bashed Patch is active and Traps Make Noise has a checkmark, click the checkbox and the checkmark should change to a plus sign (indicating that is merged). Typically the Skyrim Wrye Bash can't merge any mods that it doesn't automatically detect as mergeable.

 

To answer another question, when a BCF runs there is always an error message even when it successfully runs :facepalm:.

[peppergomez]

Thanks. Sadly the Traps Make Noise doesn't change to a plus sign when I click it. Just toggles the check on or off.

 

Edit- OK, think I figured it out. I unchecked/rechecked it AFTER rebuilding the patch, and the + appeared beside Traps Make Noise.

 

so for the other mods, is there a way I can force them to stay in a particular order? What I've been doing is simply moving the bashed patch to the end of the mod list. But those other non-merged mods are still at the end of the list before the bashed patch, putting them out of the correct order.

[Kelmych]

You can either manually change the load order or use BOSS Userlist Manager to create new load order rules that BOSS will use; you will see this discussed in Skyrim Revisited

[peppergomez]

Thanks a lot. I used Skyrim Revisited to guide me through the BOSS Userlist Manager steps necessary. In a few cases the steps differed since a couple of the mods needed to go after different mods than described in the Skyrim Revisited page.

[daybreakarief]

hi, i recently updated my skyrim and becouse i use wyre bash, i dont know which mod to update.. does wyre bash have the mod version feature ?. or i have to check manually?.

[Kelmych]

You need to check manually; WB doesn't keep track of mod versions. One way to do this is to click the Modified column in the Installers tab to show which mods were recently added, then install the appropriate set of recently installed mods and uninstall the old versions. You can use the MoveTo command, or drag and drop if you first click the Order column, to put the newly installed mod in the correct installation order.

[peppergomez]

I notice that Elven Weapons for Silence in Wrye Bash if red, indicating some or all of the files in the package are not installed as configured. 

 

In the Conflicts tab and there are a number of files, with =Lower====== being the heading at the top, and ==44=== HRDLC Optimzed.rar being the heading closer toward the bottom.

 

In the Missing tab ther is one file: textures\weapons\battleaxe\~pse8E74.tmp

 

There are also a number of Skipped (Dir) files (NIF and DDS).

 

There are multiple subfolders in the original RAR file for the mod- Data, fomod, Options. Does Wrye Bash know to skip the fomod and Options folders, and only draw from the Data folder?

 

And is the red color indicating that Wrye Bash is aware of these folders and the fact that it's not installing files from them?

 

I ask because the only other red Installers in Wrye Bash are HRDLC Optimzed.rar and STD.rar and I am assuming they are red because some of the files in their subfolders are intentionally being skipped.

[Fazel]

Hi

I'm sorry but i don't understand the "groups of mods" stated in the wyre bash guide.

Maybe it's a dated information?

In the STEP guide it's stated that you have to install the mods using the order in which they are presented, but it's not the same order you can see in Figure 8.

Have I to use the tabs as group (like Fixes, Interface etc) and so give the mods that order?

 

Thz for the help^^ and sorry for the english :S

[Kelmych]

I notice that Elven Weapons for Silence in Wrye Bash if red, indicating some or all of the files in the package are not installed as configured. 

 

In the Conflicts tab and there are a number of files, with =Lower====== being the heading at the top, and ==44=== HRDLC Optimzed.rar being the heading closer toward the bottom.

 

In the Missing tab ther is one file: textures\weapons\battleaxe\~pse8E74.tmp

 

There are also a number of Skipped (Dir) files (NIF and DDS).

 

There are multiple subfolders in the original RAR file for the mod- Data, fomod, Options. Does Wrye Bash know to skip the fomod and Options folders, and only draw from the Data folder?

 

And is the red color indicating that Wrye Bash is aware of these folders and the fact that it's not installing files from them?

 

I ask because the only other red Installers in Wrye Bash are HRDLC Optimzed.rar and STD.rar and I am assuming they are red because some of the files in their subfolders are intentionally being skipped.

Clicking on the "?" icon at the bottom of Wrye Bash brings up the WB General readme file in a browser window. If you go to a little above the bottom of the page you can select the Advanced Readme; this has descriptions for the contents of each of the tabs (e.g., Missing, Skipped) in the installer window. These are also described in the STEP WB guide.

 

The Advanced Readme also has a difficult to understand discussion of files and folders WB reads or ignores.

 

If an Installation tab checkbox is red then at least one associated file in the Data directory was changed by a user after WB installed the mod, and the change was not done using WB. WB doesn't know whether this is proper or not. An example is when a mod has an ini file that a user can edit; if the user edits it the associated WB checkbox turns red.

[Kelmych]

Hi

I'm sorry but i don't understand the "groups of mods" stated in the wyre bash guide.

Maybe it's a dated information?

In the STEP guide it's stated that you have to install the mods using the order in which they are presented, but it's not the same order you can see in Figure 8.

Have I to use the tabs as group (like Fixes, Interface etc) and so give the mods that order?

 

Thz for the help^^ and sorry for the english :S

In the BAIN Installers tab of the guide, step 6 of ""Obtain the Mods" includes renaming the mods so the mod name starts with associated STEP guide section identifier. A single group of mods is all the mods that are part of one section of the STEP guide (e.g., Fixes), and if you follow the Wrye Bash guide approach all mods in that section of the STEP guide should be renamed to have the section identifier at the beginning of the mod name (e.g., the mod name would start with "D_" if the mod is in the Fixes section (2D)). When Figure 8 was created the STEP guide sections had different identifiers than they do now. We need to replace Figure 8 with an example that uses the current identifiers.

 

The most important thing is to assign the Wrye Bash Installation order number in such a way that when you click the Order column in the Installation Tab the mods are ordered in the same sequence as they are in the STEP guide.

[z929669]

I'll see about updating the figs, but they will always be outdated, so maybe a not about this in the guide is warranted.

[Fazel]

In the BAIN Installers tab of the guide, step 6 of ""Obtain the Mods" includes renaming the mods so the mod name starts with associated STEP guide section identifier. A single group of mods is all the mods that are part of one section of the STEP guide (e.g., Fixes), and if you follow the Wrye Bash guide approach all mods in that section of the STEP guide should be renamed to have the section identifier at the beginning of the mod name (e.g., the mod name would start with "D_" if the mod is in the Fixes section (2D)). When Figure 8 was created the STEP guide sections had different identifiers than they do now. We need to replace Figure 8 with an example that uses the current identifiers.

 

The most important thing is to assign the Wrye Bash Installation order number in such a way that when you click the Order column in the Installation Tab the mods are ordered in the same sequence as they are in the STEP guide.

Thz for the answer^^

The problem now is that Wyre Bash do not understand that 10 is after 9 xD

There is a way to make it understand that? Until now i forced the mod order manually so that the tenth file of section D (i renamed it D10-etc) is after the ninth one (D9-etc) instead of after the first one.

[bitdman]

 

 

The most important thing is to assign the Wrye Bash Installation order number in such a way that when you click the Order column in the Installation Tab the mods are ordered in the same sequence as they are in the STEP guide.

Doesn't BOSS Already do this?