Guide:Wrye Bash: Difference between revisions
From Step Mods | Change The Game
No edit summary |
|||
Line 190: | Line 190: | ||
*Optionally, it is recommended that any ReadMe files present be named accordingly and placed into a folder named "Docs" created beside each of the "Textures" folders within each sub-project. | *Optionally, it is recommended that any ReadMe files present be named accordingly and placed into a folder named "Docs" created beside each of the "Textures" folders within each sub-project. | ||
*The result is a complex BAIN package for SRO that includes all options for maximum customization. Archive the project into an aptly-named package and move to ''Bash Installers\''. | *The result is a complex BAIN package for SRO that includes all options for maximum customization. Archive the project into an aptly-named package and move to ''Bash Installers\''. | ||
[[File:FigureSB15.jpg|frame| | [[File:FigureSB15.jpg|frame|right]] | ||
*Delete the remaining project, but '''DO NOT DELETE''' the original three SRO packages! | *Delete the remaining project, but '''DO NOT DELETE''' the original three SRO packages! | ||
Repeat this process for all remaining projects that need BAIN re-packing, TheCompiler’s advice modifications or whatever makes sense beyond that. This process is tedious, but it forces the mod user to become intimately familiar with a given mod, which will be useful later on. | Repeat this process for all remaining projects that need BAIN re-packing, TheCompiler’s advice modifications or whatever makes sense beyond that. This process is tedious, but it forces the mod user to become intimately familiar with a given mod, which will be useful later on. |
Revision as of 18:03, 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: 18:03:37 4 June 2012 (UTC)
Installing & Maintaining S.T.E.P Using Wrye Bash