Guide:Wrye Bash: Difference between revisions
From Step Mods | Change The Game
Line 88: | Line 88: | ||
{{Notice Small|The application bar along the bottom of the WB window might show shortcuts to helper applications recognized by WB if those apps are already installed to their default locations.}} | {{Notice Small|The application bar along the bottom of the WB window might show shortcuts to helper applications recognized by WB if those apps are already installed to their default locations.}} | ||
Click the "Installers" tab. This should invoke a pop-up warning to "enable" Installers. If it does, click on | Click the "Installers" tab. This should invoke a pop-up warning to "enable" Installers. If it does, click on "Yes" and it should load very quickly, as there is nothing yet in the package repository. If it does not prompt, right click the header bar of the Installers and make sure "Enabled" is checked. Then select "Full Refresh". | ||
Adding a new package to BAIN is as easy as dropping a zip file into the bash installers directory. A full CRC scan of the package repository (''Bash Installers\'') is initiated every time the installers tab is selected, and any new mods found will be appended in alphabetical order and at the bottom of the load order in the package list. It should be noted that WB recognizes the contents of both extracted folders (called '''projects''') and archives (called '''packages'''); however, it is strongly recommended that installers be kept in archive format as a standard practice, as this is not only a more efficient use of space, but it also prevents WB from calculating a CRC for each file in an unpacked project.Thus, projects can take a long time to scan. The archived package only counts as a single CRC. | |||
= BAIN Installers = | = BAIN Installers = |
Revision as of 01:47, April 4, 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: 1:47:42 4 April 2013 (UTC)