Guide:Wrye Bash: Difference between revisions
From Step Mods | Change The Game
Line 129: | Line 129: | ||
== Package Structure & Interpretation == | == Package Structure & Interpretation == | ||
[[File:Figure3_BAINFirst.jpg|thumb|right|475px|'''Figure 3:''' Introduction to BAIN. (L to R) {{Fc|#ED1C24|'''Package Details'''}}, {{Fc|# | [[File:Figure3_BAINFirst.jpg|thumb|right|475px|'''Figure 3:''' Introduction to BAIN. (L to R) {{Fc|#ED1C24|'''Package Details'''}}, {{Fc|#4F58DC|'''Sub-Packages/Plugins'''}}, {{Fc|#22B14C|'''Comments'''}}]] | ||
The installers tab contains the package-management interface. Package management is a VERY important aspect of WB, and standards of Wrye '''BA'''sh '''IN'''staller (aka BAIN package or archive) structure represent the foundation of effectively using BAIN. Unfortunately, not all mod authors pack their mods in a BAIN-ready format, so it is important to understand how to convert to the proper structure. The good news is that BAIN has some flexibility, and usually can translate archives correctly. Packages preceded by a red (simple package), white (complex package) or gray (unrecognized) box are NOT installed (installed packages will have a plus [+] symbol inside the box). Before proceeding further, all packages must be made recognizeable to BAIN (i.e., gray boxes and text must be eliminated). The following examples illustrate BAIN package interpretation and allude to some effective packing methods. | The installers tab contains the package-management interface. Package management is a VERY important aspect of WB, and standards of Wrye '''BA'''sh '''IN'''staller (aka BAIN package or archive) structure represent the foundation of effectively using BAIN. Unfortunately, not all mod authors pack their mods in a BAIN-ready format, so it is important to understand how to convert to the proper structure. The good news is that BAIN has some flexibility, and usually can translate archives correctly. Packages preceded by a red (simple package), white (complex package) or gray (unrecognized) box are NOT installed (installed packages will have a plus [+] symbol inside the box). Before proceeding further, all packages must be made recognizeable to BAIN (i.e., gray boxes and text must be eliminated). The following examples illustrate BAIN package interpretation and allude to some effective packing methods. | ||
*Clicking on an archive will bring up details about the package in the upper right frame ( | *Clicking on an archive will bring up details about the package in the upper right frame ({{Fc|#ED1C24|'''red'''}} outline), as well as any sub-packages or plugins if present just below that ({{Fc|#4F58DC|'''blue'''}} outline), followed by a convenient area to type in some comments about the package (Fc|#22B14C|'''green'''}} outline). | ||
*A closer look at the package details of example packages 1-4 depicted in the package list of '''Figure 3''' reveals further detail: | *A closer look at the package details of example packages 1-4 depicted in the package list of '''Figure 3''' reveals further detail: | ||
*Plugin filters and sub-packages can be seen just beneath the package details viewer (see | *Plugin filters and sub-packages can be seen just beneath the package details viewer (see {{Fc|#4F58DC|'''blue'''}} outline in '''Figure 3'''). Any BAIN-ready package selected that contains an ESM or ESP will list them under '''[Esp/m Filter]'''. Complex BAIN packages will also list the folder names alphanumerically under '''[Sup-Packages]'''. Details in '''Figure 6''' reference the '''Ex 1''' and '''Ex 5''' as in '''Figures 4 & 5'''. | ||
{{Notice Small|In working with installer packages, it is useful to extract and repack large packages (i.e., > 500 MB packed) into non-solid archives. This format sacrifices a bit of compression ratio as a trade-off for a significant increase in extraction/compression speed, which can take a while for large packages containing many small files backed into a solid compression "block".}} | {{Notice Small|In working with installer packages, it is useful to extract and repack large packages (i.e., > 500 MB packed) into non-solid archives. This format sacrifices a bit of compression ratio as a trade-off for a significant increase in extraction/compression speed, which can take a while for large packages containing many small files backed into a solid compression "block".}} | ||
Revision as of 05:40, January 23, 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: 5:40:39 23 January 2013 (UTC)