Guide:Wrye Bash: Difference between revisions
From Step Mods | Change The Game
No edit summary |
No edit summary |
||
Line 220: | Line 220: | ||
</div> | </div> | ||
= Ex: Create | = Ex: Create & Use BCFs = | ||
== BAIN "Package" Conversion Files == | == BAIN "Package" Conversion Files == | ||
BCFs (BAIN Conversion Files) are very useful compressed instruction scripts that tell BAIN how to create BAIN-ready installers from BAIN-incompatible packages. Given that both source file(s) and converted BAIN version(s) exist, it is quite simple to create a BCF to make the task fast and easy for other downstream users. | |||
BCFs (BAIN Conversion Files) are very useful compressed instruction scripts that tell BAIN how to create BAIN-ready installers from BAIN-incompatible packages. Given that both source file(s) and converted BAIN version(s) | |||
{{Notice Small|A BCF requires the exact same input file that was used to generate the BCF itself in order to be used again to repeat the process. Therefore, it is mostly useful to mod creators or just plain considerate people ;)}} | {{Notice Small|A BCF requires the exact same input file that was used to generate the BCF itself in order to be used again to repeat the process. Therefore, it is mostly useful to mod creators or just plain considerate people ;)}} | ||
[[File:Figure9_BCF1.jpg|thumb|right|450px|'''Figure 9:''' Selecting source files for creating a BCF.]] | [[File:Figure9_BCF1.jpg|thumb|right|450px|'''Figure 9:''' Selecting source files for creating a BCF.]] | ||
Line 237: | Line 235: | ||
*Once a BCF is created, there is less value to retaining the original non-BAIN source packages. It is recommended that these be separated from the actual installers by selecting each source package, right click, select [Move To], and enter in a -1. This will move them to the bottom of the installation list when packages are later sorted by [Order]. … More on this later in the guide ... | *Once a BCF is created, there is less value to retaining the original non-BAIN source packages. It is recommended that these be separated from the actual installers by selecting each source package, right click, select [Move To], and enter in a -1. This will move them to the bottom of the installation list when packages are later sorted by [Order]. … More on this later in the guide ... | ||
{{Sidebox|right|width=500|Applying a BCF| | |||
Drop the mod into Bash Installers\ and the BCF.7z into Bash Installers\Bain Converters\Start WB and go to the Installers Tab (BAIN)Right-click on the mod (most likely at bottom of list)Select "Conversions" > "Apply" > BCF.7zGive the output BAIN package a name (accept the default)Right-click the new package (most likely at bottom of list)Select "Wizard", and follow the instructions | |||
}} | |||
= BAIN - Installing Mods = | = BAIN - Installing Mods = | ||
== Package Order == | == Package Order == | ||
[[File:Figure7_BAINHeaders.jpg|thumb|right|450px|'''Figure 7:''' BAIN column headers.]] | [[File:Figure7_BAINHeaders.jpg|thumb|right|450px|'''Figure 7:''' BAIN column headers.]] | ||
Line 252: | Line 251: | ||
{{clear}} | {{clear}} | ||
=== Set the Installation Order === | === Set the Installation Order === | ||
Because installation order is critical to get the results expected in game, the packages must be ordered properly according to install order such that the desired assets overwrite their conflicting assets. This is done by sorting BAIN installers by the '''[Order]''' field. BAIN will handle every aspect of the hierarchy according to the preset install order, regardless of what packages are installed, saving the user a huge management headache and allowing the user to easily install/uninstall alternate conflicting assets. | Because installation order is critical to get the results expected in game, the packages must be ordered properly according to install order such that the desired assets overwrite their conflicting assets. This is done by sorting BAIN installers by the '''[Order]''' field. BAIN will handle every aspect of the hierarchy according to the preset install order, regardless of what packages are installed, saving the user a huge management headache and allowing the user to easily install/uninstall alternate conflicting assets. | ||
Line 267: | Line 265: | ||
== Package Installation == | == Package Installation == | ||
At this point, the mod packages are ready to install. Begin by confirming that no unexpected or undesireable conflicts exist. Before doing this, it will be useful to 'hide' the original installers that were previously converted to BAIN format. Doing so prevents these packages from being included in the conflicts viewer. | At this point, the mod packages are ready to install. Begin by confirming that no unexpected or undesireable conflicts exist. Before doing this, it will be useful to 'hide' the original installers that were previously converted to BAIN format. Doing so prevents these packages from being included in the conflicts viewer. | ||
*Select all of the obsolete packages, which should now be listed at the very end of the BAIN package list after the "==Last==" marker. | *Select all of the obsolete packages, which should now be listed at the very end of the BAIN package list after the "==Last==" marker. | ||
Line 302: | Line 299: | ||
== Using the WB Mods Tab == | == Using the WB Mods Tab == | ||
=== Setting the load order of the plugins === | === Setting the load order of the plugins === | ||
Now that the installation is finished and verifiable, move to the Mods tab to begin ordering your plugins according to the latest BOSS masterlist. No need to tick the plugins via the 'Data Files' menu via the Skyrim Launcher. WB will take care of that right here, simply tick every box, then click on the BOSS icon at the bottom left of the WB window. This will execute boss and potentially give you some recommendations or warnings and perhaps suggestions for 'Bash Tags' or that a mod can be marked as mergeable. For now, I will stop right here, as the complexities of plugin management are not relevant at this stage of STEP. The same is true for INI Edits and Saves tabs. I will cover those once I get feedback as to the format and usefulness of what I have discussed thus far. | Now that the installation is finished and verifiable, move to the Mods tab to begin ordering your plugins according to the latest BOSS masterlist. No need to tick the plugins via the 'Data Files' menu via the Skyrim Launcher. WB will take care of that right here, simply tick every box, then click on the BOSS icon at the bottom left of the WB window. This will execute boss and potentially give you some recommendations or warnings and perhaps suggestions for 'Bash Tags' or that a mod can be marked as mergeable. For now, I will stop right here, as the complexities of plugin management are not relevant at this stage of STEP. The same is true for INI Edits and Saves tabs. I will cover those once I get feedback as to the format and usefulness of what I have discussed thus far. | ||
=== INI Tweaks === | === INI Tweaks === | ||
Nothing interesting here right now ... | Nothing interesting here right now ... | ||
Line 314: | Line 308: | ||
= Official Documentation = | = Official Documentation = | ||
The following documents are updates to the original WB documentation and will be updated with each official WB release moving forward. These guides will also support Skyrim users. All maintained by WrinklyNinja and the [http://sourceforge.net/projects/oblivionworks/ OblivionWorks Developers]. Current and future releases of WB will include this documentation. | The following documents are updates to the original WB documentation and will be updated with each official WB release moving forward. These guides will also support Skyrim users. All maintained by WrinklyNinja and the [http://sourceforge.net/projects/oblivionworks/ OblivionWorks Developers]. Current and future releases of WB will include this documentation. | ||
Revision as of 02:12, February 22, 2013
A simplified guide to using Wrye Bash to maintain a modded S.T.E.P. setup -- by z929669 & S.T.E.P. Team
- Updated: 2:12:29 22 February 2013 (UTC)