Guide:Wrye Bash: Difference between revisions
From Step Mods | Change The Game
Line 154: | Line 154: | ||
At this point, the mod packages are ready to install. Begin by confirming that no unexpected or undesirable conflicts exist. Before doing this, it will be useful to 'hide' the packages that should not or cannot be installed. 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 undesirable conflicts exist. Before doing this, it will be useful to 'hide' the packages that should not or cannot be installed. 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. | ||
# Right click on one of the selected packages and select | # Right click on one of the selected packages and select {{Fc|#e6b69e|"Hide"}} from the context menu (confirm when prompted; see '''Figure 11''').{{clear|left}} | ||
[[File:WB_Figure12.jpg|thumb|left|200px|'''Figure 12:''' Show inactive conflicts]] | [[File:WB_Figure12.jpg|thumb|left|200px|'''Figure 12:''' Show inactive conflicts]] | ||
[[File:WB_Figure13.jpg|thumb|right|200px|'''Figure 13:''' View conflicts]] | [[File:WB_Figure13.jpg|thumb|right|200px|'''Figure 13:''' View conflicts]] | ||
::::::::::: Select one of the installers, and examine the package details in the upper right frame of the BAIN window. | ::::::::::: Select one of the installers, and examine the package details in the upper right frame of the BAIN window. | ||
:::::::::::* The '''[General]''' tab gives an overview of the files recognized in the package as well as some useful statistics. | :::::::::::* The {{Fc|#e6b69e|'''[General]'''}} tab gives an overview of the files recognized in the package as well as some useful statistics. | ||
:::::::::::* The '''[Matched]''' tab should be empty, and will only list files with paths if there is a currently-installed file in the Data directory identical to any of the files that BAIN recognizes in the selected package. | :::::::::::* The {{Fc|#e6b69e|'''[Matched]'''}} tab should be empty, and will only list files with paths if there is a currently-installed file in the Data directory identical to any of the files that BAIN recognizes in the selected package. | ||
:::::::::::* The '''[Missing]''' tab should list all files in the package, since it is the exact reciprocal of the [Matched] tab. | :::::::::::* The {{Fc|#e6b69e|'''[Missing]'''}} tab should list all files in the package, since it is the exact reciprocal of the [Matched] tab. | ||
:::::::::::* The '''[Conflicts]''' tab is of special interest, because it will reveal actual conflicts OR potential conflicts according to a setting in BAIN’s main context menu. If | :::::::::::* The {{Fc|#e6b69e|'''[Conflicts]'''}} tab is of special interest, because it will reveal actual conflicts OR potential conflicts according to a setting in BAIN’s main context menu. If {{Fc|#e6b69e|"Show Inactive Conflicts"}} is unchecked, the {{Fc|#e6b69e|'''[Conflicts]'''}} tab should be empty, so ensure that this setting is ticked to reveal potential conflicts ('''Figure 12'''), as no packages have been installed to this point. | ||
:::::::::::** Files and package | :::::::::::** Files and package {{Fc|#e6b69e|"Order"}} numbers that will be overwritten will be listed first under the "=Lower===" heading, and those that will overwrite the currently-selected mod will be listed under the "=Higher===" heading ('''Figure 13'''). In-game, assets listed under "=Higher===" will appear in game, so verify that the conflicts will resolve as desired. | ||
:::::::::::** '''[Underridden]''' and '''[Dirty]''' tabs list assets in the currently-selected installer that are not installed due to being either superseded by the assets of a mod installed upstream or due to a file mismatch for some other reason (e.g., if the file has been altered after installation), respectively. Both should always be empty. | :::::::::::** {{Fc|#e6b69e|'''[Underridden]'''}} and {{Fc|#e6b69e|'''[Dirty]'''}} tabs list assets in the currently-selected installer that are not installed due to being either superseded by the assets of a mod installed upstream or due to a file mismatch for some other reason (e.g., if the file has been altered after installation), respectively. Both should always be empty. | ||
:::::::::::** The '''[Skipped]''' tab lists any files/folders that are not recognized by BAIN as "install-able". For some cases, this can be rectified by ticking | :::::::::::** The {{Fc|#e6b69e|'''[Skipped]'''}} tab lists any files/folders that are not recognized by BAIN as "install-able". For some cases, this can be rectified by ticking {{Fc|#e6b69e|"Has Extra Directories"}} in BAIN's main context menu. If not, the file will need to be restructured within the installer if it should be installed. | ||
:::::::::::** Check to be certain that any packages that have a white box preceding the package name have sub-packages selected as indicated in the middle frame on the right side of BAIN. Likewise, be certain that all necessary ESP/M Filters are also selected. | :::::::::::** Check to be certain that any packages that have a white box preceding the package name have sub-packages selected as indicated in the middle frame on the right side of BAIN. Likewise, be certain that all necessary ESP/M Filters are also selected. | ||
:::::::::::** Once all packages have been verified and all necessary or optional adjustments made to the instllers, ALL packages may be selected at once and installed by right clicking one of the selected packages and clicking on | :::::::::::** Once all packages have been verified and all necessary or optional adjustments made to the instllers, ALL packages may be selected at once and installed by right clicking one of the selected packages and clicking on {{Fc|#e6b69e|"Install"}}. This can also by done for each individual package and in any order, since the hierarchy has already been defined. Depending on computer hardware, this process could take only a minute or more than 10 minutes. | ||
:::::::::::** Uninstallation is done in the same manner as installation, and all of the same rules apply. | :::::::::::** Uninstallation is done in the same manner as installation, and all of the same rules apply. | ||
:::::::::::** Once installed, the boxes preceding package names will be either yellow or green, and each will have a '+' symbol, which indicates that the package is installed. Yellow means that the package has some file installed, but others have been overwritten by higher-order packages. Green means that all files of the package are installed without any overrides ('''Figure 14'''). | :::::::::::** Once installed, the boxes preceding package names will be either yellow or green, and each will have a '+' symbol, which indicates that the package is installed. Yellow means that the package has some file installed, but others have been overwritten by higher-order packages. Green means that all files of the package are installed without any overrides ('''Figure 14'''). | ||
[[File:WB_Figure14.jpg|thumb|left|200px|'''Figure 14:''' Installed mods & Overwrites: before install]][[File:WB_Figure15.jpg|thumb|right|200px|'''Figure 15:''' Installed mods & Overwrites: after install]] | [[File:WB_Figure14.jpg|thumb|left|200px|'''Figure 14:''' Installed mods & Overwrites: before install]][[File:WB_Figure15.jpg|thumb|right|200px|'''Figure 15:''' Installed mods & Overwrites: after install]] | ||
::::::::::: Infrequently, packages that are highlighted in yellow or orange have not been installed according to the defined heirarchy. This can easily be corrected by right clicking on the package and selecting | ::::::::::: Infrequently, packages that are highlighted in yellow or orange have not been installed according to the defined heirarchy. This can easily be corrected by right clicking on the package and selecting {{Fc|#e6b69e|"Install Missing""}}. Afterwards, right click the package again and click {{Fc|#e6b69e|"Anneal"}} or {{Fc|#e6b69e|"Anneal All"}} to tell BAIN to consider all packages in the install list. The {{Fc|#e6b69e|"Anneal"}} function simply tells BAIN to refresh its assessment of the defined install hierarchy and reapply those rules to correct any unintended conflicts. It never hurts to use this function frequently, and {{Fc|#e6b69e|"Auto Anneal"}} should always be ticked in BAIN’s main context menu to honor the install hierarchy. | ||
::::::::::: Be strategic about the order in which things are installed and uninstalled, as any yellow-boxed package with a '+' symbol in it will need to be re-accessed by BAIN in order to install assets from higher-order mods that may be removed. If the overwritten package is very large (and 'solid'), it will significantly delay the uninstall of a conflicting downstream package being removed, regardless of the size of the package being removed. Even if the package being removed is being updated, then a lot of time can be saved by first positioning and ''installing'' the update, thus effectively 'blocking' the large, overwritten file from being accessed, since it will no longer be required for conflict resolution. | ::::::::::: Be strategic about the order in which things are installed and uninstalled, as any yellow-boxed package with a '+' symbol in it will need to be re-accessed by BAIN in order to install assets from higher-order mods that may be removed. If the overwritten package is very large (and 'solid'), it will significantly delay the uninstall of a conflicting downstream package being removed, regardless of the size of the package being removed. Even if the package being removed is being updated, then a lot of time can be saved by first positioning and ''installing'' the update, thus effectively 'blocking' the large, overwritten file from being accessed, since it will no longer be required for conflict resolution. | ||
::::::::::: Use the approach described thus far for setting up BAIN installers and installing the rest of STEP. | ::::::::::: Use the approach described thus far for setting up BAIN installers and installing the rest of STEP. |
Revision as of 16:38, May 3, 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: 16:38:04 3 May 2013 (UTC)
GUIDE FORUM THREAD Template:Notice