Python HTML NSIS Other
Latest commit 7ac0dbd Jun 7, 2017 @Utumno Utumno Random readme edits and other nitpick/small fixups:
- Dropping archive name from conflicts project:
Lead to very long directory names:
Anyway the package files are included in the project so we can guess the
package name.
- No tooltip on installers comments, see:
- stray import sys from 928b478

- Wrye Bash Monitor External Installation How-To and other RRE:


Some wrapping, trim trailing and edits by me and alt3rn1ty - see

Tried to keep the best - ugh - next time first one wins.

- Mopy/bash/bosh/ frozen set for type warn.

Disable autoghosting pop up for games other than oblivion. See around:
for a discussion. Autoghosting must be disabled for all games but TESIV,
lots of work there.

Mopy/bash/basher/ Add busy cursor to save settings
Mopy/bash/basher/ some wrapping and making message game
Mopy/bash/basher/ dropping hardcoded Oblivion
string, we still need to replace TES4LodGen with a per game string.

Mopy/bash/bosh/ minimal edits -> this file needs serious work.
I wrapped a bit, squashed couple formatting warns, pruned couple 'name'
attribute (yak!) but remains a fact that this code needs be split into
a and a SaveFile hierarchy be built, using the headers from Used also some iterators instead of for loops. Less than
WIP - #349

Mopy/bash/ don't ask user confirmation for creating dirs

Fix for Bash now asking confirmation for creating dirs, introduced in
aa11399 - I had tested but missed it
somehow. See:

The value of FOF_NOCONFIRMMKDIR I took directly from printing it on
import - see:

Mopy/bash/ Fixes for unneded error thrown in testUac (yak) - see:
Closes #387

Mopy/bash/game/fallout4/ F4SE names confirmed ok by

Wrye Bash


Wrye Bash is a mod management utility for Oblivion and Skyrim with a rich set of features. This is a fork of the Wrye Bash related code from the SVN 3177 trunk revision. We are in the process of refactoring the code to eventually support more games, offering the same feature set for all of them. Please read the Contributing section below if interested in contributing.

Supported Games

Here is a list of supported games with the minimal patch version that Bash was tested on (previous versions or latest versions may or may not work):

  • Oblivion (patch 1.2.0416)
  • Skyrim (patch
  • Fallout 4 (patch
  • Skyrim Special Edition (patch


Docs are included in the download but we are setting them up also online here.


  • Short version: just use the installer, and install everything to their default locations.
  • Long version: see the General Readme for information, and the Advanced Readme for even more details.

To run Wrye Bash from the latest dev code (download from here) you need:

NB: the 32-bit versions are required even if you are on a 64-bit operating system.

Refer to the readmes for detailed instructions. In short:

  1. Install one of the supported games (Oblivion, Skyrim).
  2. Install Python and plugins above.
  3. Extract the downloaded Wrye Bash archive into your game folder.
  4. Run Wrye Bash by double-clicking "Wrye Bash Launcher.pyw" in the new Mopy folder.


Wrye Bash 306 runs on WINE - with some hiccups. In short:

  1. Do not use the installer - instead wine-install the python prerequisites above, then unzip/clone the python version in your game folder
  2. Edit Mopy/bash/ - add canVista = False just above the def setUAC(button_,uac=True): so it becomes
canVista = False
def setUAC(button_,uac=True):
  1. Run Bash as wine python /path/to/Mopy/Wrye Bash Launcher.pyw

For details see our wiki article. Wine issue: #240

Questions ? Feedback ?

We are currently monitoring this thread at the SSE forums, for all supported games - or alternatively this thread, at AFK mods. Please be sure to ask there first before reporting an issue here. If asking for help please provide the info detailed in our Reporting a bug wiki page. In particular it is essential you produce a bashbugdump.log.

Latest betas

In the second post of the Oblivion thread there are links to latest python and standalone (exe) builds. Be sure to check those out for bleeding edge bugfixes and enhancements. Feedback appreciated!


To contribute to the code, fork the repo and set your fork up as detailed in [git] Syncing a Fork with the main repository. A good starting point is the currently worked on issues (see also issue 200 for some refactoring tasks we need help with). The recommended way to code for Bash is Pycharm (set up instructions). Please also read at least:

When ready do not issue a pull request - contact instead a member of the team in the relevant issue and let them review. Then those branches can be pulled from your fork and integrated with upstream. Once this is done a couple times you get write rights.

Main Branches

  • dev: the main development branch - approved commits end up here. Do not directly push to this branch - push to your branches and contact someone from the owners team in the relevant issue.
  • master: the production branch, contains stable releases. Use it only as reference.
  • utumno-wip: bleeding edge dev branch. Do have a look if interested in contributing or testing very latest features/fixes.