Guide:Wrye Bash: Difference between revisions
From Step Mods | Change The Game
Line 191: | Line 191: | ||
{{Notice Small|If the "BAIN" tag is placed after the package ID# when renaming a package, the '''[Open at]''' option in the right-click menu will break. The '''[Open at]''' option allows one to open the package's corresponding Nexus page in the default browser.}} | {{Notice Small|If the "BAIN" tag is placed after the package ID# when renaming a package, the '''[Open at]''' option in the right-click menu will break. The '''[Open at]''' option allows one to open the package's corresponding Nexus page in the default browser.}} | ||
<span style="color:#005AE0">'''SIDEBAR: BAIN package restructure'''</span> | <div style="margin:100;"><span style="color:#005AE0">'''SIDEBAR: BAIN package restructure'''</span> | ||
---- | |||
<ins>'''EXAMPLE - Simple-package repack: ''1-(CORE!)Accingite Vos - HQ Shields-225-1.'''''</ins> | <ins>'''EXAMPLE - Simple-package repack: ''1-(CORE!)Accingite Vos - HQ Shields-225-1.'''''</ins> | ||
Rearrange the project (<span style="color:#3F48CC">'''blue'''</span> outline) into a ‘simple’ structure that BAIN will recognize (<span style="color:#22B14C">'''green'''</span> outline). In this case, ... | Rearrange the project (<span style="color:#3F48CC">'''blue'''</span> outline) into a ‘simple’ structure that BAIN will recognize (<span style="color:#22B14C">'''green'''</span> outline). In this case, ... | ||
Line 228: | Line 228: | ||
*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. | ||
</div> | |||
= Ex: Create BCF = | = Ex: Create BCF = |
Revision as of 05:32, January 23, 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: 5:32:11 23 January 2013 (UTC)