Guide:Wrye Bash: Difference between revisions
From Step Mods | Change The Game
Line 91: | Line 91: | ||
= Using Wrye Bash = | = Using Wrye Bash = | ||
WB's two main uses are found under the Installers Tab where resides "BAIN" (BAsh INstaller) and the Mods Tab where mods can be managed using many various tools including the "Bashed Patch". The Bashed Patch takes elements from various mods and puts them into one plugin, which resolves many mod conflicts. Think of mods as a series of transparent films containing layers of a complex graphic. When laid atop one another, each layer adds to the final composite. Redundancies and conflicting components are effectively merged into an overall mean that is a composite mod called the Bashed Patch. This allows otherwise incompatible plugins to coexist, and many mods are completely merged into the composite, thus effectively circumventing the 255 plugin limit, since byte references to completely mergeable mods are no longer required. BOSS is still required to maintain load order, and it can be launched BOSS directly from WB. | |||
BAIN informs the user of potential resource conflicts ''prior'' to installation and provides details concerning the conflicting resources, mods involved and the order numbers of the involved mods. This allows one to customize mod installation order to achieve the desired result. Perhaps even more importantly, BAIN keeps track of the mod-specific resource hierarchy, allowing simple installation and uninstallation of any combination of mod packages at any point in the installation hierarchy. This means that if a mod installed after a previously-installed conflicting mod is removed, then the assets from the overwritten mod will be re-installed automatically by default (this is the "Anneal" functionality of BAIN). | |||
== Launch Wrye Bash for the First Time == | == Launch Wrye Bash for the First Time == | ||
Line 100: | Line 104: | ||
Click the "Installers" tab, this might invoke a pop-up warning, if it does click on ‘Yes’ and it should load very quickly, as there is nothing yet in the package repository. 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 to 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 for some reason, it takes WB significantly longer to scan a given project than it does its corresponding package. | Click the "Installers" tab, this might invoke a pop-up warning, if it does click on ‘Yes’ and it should load very quickly, as there is nothing yet in the package repository. 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 to 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 for some reason, it takes WB significantly longer to scan a given project than it does its corresponding package. | ||
= BAIN Installers = | = BAIN Installers = |
Revision as of 05:58, June 7, 2012
Template:Notice 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:58:49 7 June 2012 (UTC)
Installing & Maintaining S.T.E.P Using Wrye Bash