Guide:Wrye Bash: Difference between revisions
From Step Mods | Change The Game
No edit summary |
|||
Line 142: | Line 142: | ||
|} | |} | ||
= | = Example: Package Restructure = | ||
== BAIN-Repack Unrecognized Packages == | == BAIN-Repack Unrecognized Packages == | ||
Line 195: | Line 195: | ||
*Delete the remaining project, but '''DO NOT DELETE''' the original three SRO packages! | *Delete the remaining project, but '''DO NOT DELETE''' the original three SRO packages! | ||
Repeat this process for all remaining projects that need BAIN re-packing, TheCompiler’s advice modifications or whatever makes sense beyond that. This process is tedious, but it forces the mod user to become intimately familiar with a given mod, which will be useful later on. | Repeat this process for all remaining projects that need BAIN re-packing, TheCompiler’s advice modifications or whatever makes sense beyond that. This process is tedious, but it forces the mod user to become intimately familiar with a given mod, which will be useful later on. | ||
= Example: Create BCF = | |||
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) exists, it is quite simple to create a BCF to make the task fast and easy for other downstream users. | |||
{{Note|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|<span style="font-size:110%">'''Figure 9:''' Selecting source files for creating a BCF.</span>]] | |||
*In BAIN, select the file or files that were used as the source(s) of the resulting BAIN file, and right click to bring up the context menu (see '''Figure 9'''). Select '''[Conversions]''' > '''[Create]'''. | |||
*Select the resulting BAIN package when prompted. Using the SRO example described previously ... | |||
*Select “OK” to the following pop-ups. | |||
[[File:Figure10_BCF2.jpg|thumb|left|450px|<span style="font-size:110%">'''Figure 10:''' Create BCF dialogue (Pt 1).</span>]] | |||
{{clear}} | {{clear}} | ||
- | [[File:Figure11_BCF3.jpg|thumb|left|450px|<span style="font-size:110%">'''Figure 11:''' Create BCF dialogue (Pt 2).</span>]] | ||
-- | *The results will be summarized, and the new BCF will be created in Bash Installers/Converters/. | ||
*To apply a converter, simply select and right click all of the input files, select [Conversions] > [Apply] and choose the BCF of interest. Given that the source package contents (file CRCs and structure) are as expected by the BCF, the BAIN will be converted automatically, with the defined file name. This process is agnostic of the input file names per se. | |||
*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 ... | |||
= BAIN - Installing Mods = | = BAIN - Installing Mods = |
Revision as of 18:09, June 4, 2012
Template:TOC left A simplified guide to using Wrye Bash to maintain a modded S.T.E.P. setup -- by z929669 & S.T.E.P. Team
- Updated: 18:09:10 4 June 2012 (UTC)
Installing & Maintaining S.T.E.P Using Wrye Bash