Guide:Wrye Bash

Installing & Maintaining S.T.E.P Using Wrye Bash

By z929669 & the S.T.E.P Team

---

Wrye Nomenclature

Wrye was a prominent TES (The Elder Scrolls) enthusiast, modder and developer that created Wrye Bash as a tool to help other modders deal with the idiosyncrasies of modding for Oblivion (TES4). Wrye also later created an implementation that he called Wrye ‘Mash’ for Morrowind (TES3). Wrye Smash is simply Wrye ‘Bash’ implemented for Skyrim (TES5), so it is Wrye Bash. For the sake of brevity and consistency, this guide will henceforth refer to Wrye Bash as ‘WB,’ and its analogues will likewise be referred to as ‘WS’ and ‘WM’ for Wrye Smash and Wrye Mash, respectively.

Purpose of This Guide

This guide assumes that the reader has reviewed the most updated, relevant documentation available for the WB program. If that is not the case, the authors strongly encourage a review of that documentation. Understanding--in a basic sense--what WB does and why it is useful are important concepts providing a context necessary for the reader to maximize the benefit of using this guide with respect to a fresh install of the most current major STEP (Skyrim Total Enhancement Project) release. Additionally, the guide will be modified and updated to reflect ongoing changes in each forthcoming major release of STEP. The novice WB user will likely find substantial value in following the guide as an actual working example of several sound techniques for implementing WB; nevertheless, much of the material covered in the following pages will be best understood with a baseline level of experience that exceeds “null” by at least a small margin, please familiarize yourself with the program before getting started.

Background - Basic Modding Principles

As with all TES games, modding Skyrim--in the most raw sense--can be accomplished by simply placing compatible files within the Steam/SteamApps/common/skyrim/Data directory (henceforth, referred to as “Data directory”). These files usually come packaged as a “mod” in an archive that facilitates simple decompression into the Data directory. Due to the vast number of mods and their incredible variety, the task of manual extraction and installation is a tedious process with lots of potential for error. Furthermore, it is difficult to “undo” what has been done, since it is difficult to keep track of the source of each file as the number of mods and files in the Data directory increases.

One must take care to read each mod’s documentation to understand exactly what it does and how it does in in at least a very general sense. Why? Because it is important to create a customized Skyrim that suits the tastes of the individual modder. Strictly defined, two mods are compatible if they do not attempt to alter the same game variable. Likewise, two mods that affect the same game variable are strictly defined as incompatible, which is more often termed a conflict. Said variable could be a mesh or a texture as well as a plugin or INI file. Even a game setting affected by a plugin while also being altered by an INI setting or a configuration script represents a conflict. Under the strict definitions of mod compatibility and conflict, many mods are incompatible and thus, have conflicts.

Fortunately, this is usually not really a problem, because most of the time, a conflict is inherently resolved by one mod “winning;” that is, one mod overwrites or overrides the other. For example, two particular versions of a texture file could attempt to occupy the same logical space in the Data/textures directory, in which case the second texture to be written to that space during installation will naturally overwrite the first; however, if one of those texture copies resides in a compressed BSA while the other exists as a “loose file,” then neither will physically overwrite the other upon installation, but rather one will override the other in-game upon execution of Skyrim.

The STEP Solution

One can spend hundreds of hours just searching for mods before actually getting down to the business of installing them. As mods increase in number and complexity and mod creators produce more and more mods that alter game play, interface and settings, the probability of game-crashing conflicts increases. The STEP project takes care of the heavy lifting associated with sifting through thousands of mods and selecting the ones that significantly enhance and improve the vanilla experience without detracting from it with as little cost as possible in terms of performance. Users are able to follow TheCompiler’s detailed, step-by-STEP manual-installation instructions and be confident that all components have been individually and communally tested and the results verified. STEP also facilitates customization by providing details of changes affected by each mod so that the user can choose to omit or change the order of STEP’s’. This cuts down on a vast amount of time and headache dealing with sampling, testing, troubleshooting, etc.

Limitations of STEP

Regardless of the huge time savings, efficiency boost and piece of mind that STEP offers, it is still a large manual process with many, well … steps. It can therefore take a while, and problems can and will occur for many users with increasing frequency as mod numbers and complexity increase, so STEP will only go so far to reduce the job of maintaining a viable setup with each new mod or mod update. In order to allow better scalability of STEP as it evolves, it is necessary to simplify and condense the procedure into more manageable components. Mod organizers in general help in this regard by keeping track of files installed and package installation order. In particular WB enables the most configurable interface for mod management, and is thus the recommended choice for installing, configuring and maintaining the STEP setup with each new alteration in the mod configuration.

Install BOSS

Get BOSS from the Nexus and install according the the instructions provided. You will be launching BOSS from Wrye Bash’s interface going forward (WB-BOSS v2.0+ integration is still pending at the time of this writing).� Install SKSE & Script Dragon

Download the current release build of SKSE. Drop all loose files into skyrim/ (but leave the ‘src’ directory behind) Create a text file using Notepad or any other simple text editor and paste the following two lines: [Interface] EnableContainerCategorization=1 Under the Data directory, create a folder called ‘SKSE’, save the file as ‘skse.ini’ and drop it into skyrim/Data/SKSE Download Script Dragon from the Nexus. 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 using the Start Menu shortcut, and WB will open to the Mods Tab, which is where plugins (ESMs & ESPs) are managed. Upon launch, WB creates Skyrim Mods/ beside skyrim/. This is the directory under which WB will look for mod packages among other things; therefore, mod packages should be moved or downloaded directly to:

Wrye Bash as a Tool for Maintaining STEP

WB is not just simply a mod organizer but much, much more. Like other mod organizers, WB keeps track of mod packages as well as file sources and installation priority; however, WB goes far beyond this, as will be demonstrated throughout the rest of the guide. Set Up Skyrim & Supporting Software

Establish a Clean Skyrim Install

Figure 1: These are the only files that should appear in skyrim/

A clean Skyrim install establishes a baseline from which to begin the STEP installation procedure. The simplest way to ensure a clean Skyrim install is to delete all loose files (not directories) from the skyrim/ directory (parent to Data directory), followed by cleaning out all files and directories from the Data directory (see Figure 1).

Once complete, open the Steam Libraries view, right click on Skyrim and select [Properties]. Click on the [LOCAL FILES] tab, then click on [VERIFY INTEGRITY OF GAME CACHE...]. This will restore any missing files whilst avoiding the time-consuming and redundant download of the large files listed above. If ther is any uncertainty, uninstall and then reinstall Skyrim from scratch to this point.

Install File-Compression Software

Almost any file-compression software can be used to view the contents of packages. 7-zip is favored by the authors, because it can produce dramatically smaller files than the other formats and it recognizes virtually every compression format. It's also free, open-source, and supports most of the other common formats.

Install & Configure Wrye Bash

Download the Wrye Bash installer as well as the Game Definitions under [updates]. Click the tracker (the small binoculars icon near the bottom of the header) while you are there to keep track of updates. To keep thing simple, just run the installer and select only [Skyrim] as well as the [Wrye Bash [Standalone]] check boxes. Other options exist, but please avoid them at this time unless the reader is willing to support related issues on his/her own. Ensure that the path points to the correct location of your sykrim/ directory and proceed.

1. Navigate to the skyrim/Mopy/ directory.
2. IMPORTANT: Merge the contents of the ‘Game Definitions’ archive into this location. (This will place files called 'skyrim.py' and ‘Oblivion.py’ into skyrim/Mopy/bash/).
3. Copy then rename the file 'bash_default.ini' to 'bash.ini,' and place this alongside the former. This INI lets you define many useful things including where Wrye looks for installers. (Be certain to global replace the ‘/Oblivion’ directory references to ‘/Skyrim’ and DO NOT simply do a global replace of ‘Oblivion’ with ‘Skyrim’ or you will break the INI, since certain variable names must remain unchanged even in Skyrim: e.g., ‘sOblivion=’).
4. Lastly, go to skyrim/Mopy/templates/ and move 'Bashed Patch, Skyrim.esp' into your Data directory.