Guide:Wrye Bash: Difference between revisions
From Step Mods | Change The Game
No edit summary |
|||
Line 85: | Line 85: | ||
#Download [http://skyrim.nexusmods.com/downloads/file.php?id=8221 Script Dragon from the Nexus]. | #Download [http://skyrim.nexusmods.com/downloads/file.php?id=8221 Script Dragon from the Nexus]. | ||
#From the archive, drop ''bin\dinput8.dll'' and ''bin\ScriptDragon.dll'' into the ''skyrim\'' directory. | #From the archive, drop ''bin\dinput8.dll'' and ''bin\ScriptDragon.dll'' into the ''skyrim\'' directory. | ||
=== Launch Wrye Bash for the First Time === | === Launch Wrye Bash for the First Time === | ||
Line 97: | Line 95: | ||
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 & Package Interpretation | = BAIN - Introduction = | ||
== BAIN Installers & Package Interpretation == | |||
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. 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. The following examples illustrate BAIN package interpretation and allude to some effective packing methods. |
Revision as of 17:13, 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: 17:13:18 4 June 2012 (UTC)
Installing & Maintaining S.T.E.P Using Wrye Bash