Hitting The Books

Post-install instructions for completing a mod list.

In order to prevent every mod guide presented on this site from becoming too long, this is the catch-all post to cover everything you should do after downloading the final mod and running LOOT one more time. So far, it only includes instructions for using Wyre Bash to create a Bashed Patch, but as more complex mod guides are posted, Hitting The Books will start to cover more complex post-install processes, including DynDOLOD and Merge Plugins.

Wyre Bash

The Wyre Bash tool can be used as a mod manager of its own, but for the purposes of this guide, it is solely used to create a Bashed Patch. This patch, which comes at the end of a mod list, merges various things from plugins – chiefly leveled lists. This means that you can use multiple mods that change the same levelled lists, and still see the actors/items from every mod.

Run Wyre Bash through Mod Organizer. If you have not yet set up Wyre Bash, please see Before The Storm for instructions on how to do so.

Make sure you are in the ‘mods’ tab at the top. You should see a list of all your installed .esp files. Scroll to the bottom, right click on ‘Bashed Patch, 0.esp’, and select ‘rebuild patch’. If a window appears asking you to deactivate some mods prior to patching, click OK. This will merge several .esp files into the Bashed Patch, reducing your .esp count.

Open the ‘tweak settings’ menu if you would like – I generally recommend setting the timescale of the game to 12, by right clicking ‘timescale’, selecting 12 from the list, and checking the box next to it. Leave everything else – the ‘automatic’ box should be checked in the ‘leveled lists’ screen. Click Build Patch. Let Wyre Bash do its work, then click OK on the report screen, and yes to activate the Bashed Patch.

The Bashed Patch is now active in your load order, but the .esp file is contained within Mod Organizer’s overwrite folder. To keep your folders clean, and to allow for easy switching between mod profiles (files in the overwrite are not unique to a profile – leaving something in overwrite for one profile will mean the same files appear in another), scroll to the bottom of Mod Organizer and right click on the red ‘overwrite’ mod. Select create mod, and give it a suitable name – ‘Dragon Rising Bashed Patch’, for example. Activate this new mod, and place it just below the last mod in your list. Now, the Bashed Patch functions as a normal mod, and can be activated and deactivated at will.

You should rebuild your Bashed Patch every time you add new mods to your game, and it will almost always be at the very bottom of your load order. It’s an important step – don’t forget it!

 

17 thoughts on “Hitting The Books

  1. When I try to build a bashed patch it wants to create a new docs folder. I allow it, but the html and the txt versions of the mod cannot be moved, because they are already occupied by another program, which is weird.

    Liked by 1 person

    1. This puzzled me in the past, then I figured out what was happening. If you are using Mod Organizer (faithfully following this guide) do the following:
      1 – In your overwrite folder, you will find an empty doc folder created by Wrye Bash. If you have not done so already, right click on overwrite and tell it to create a new mod and name it whatever you like.
      2 – In the Skyrim SE data folder you will find the Bashed Patch. Put it into your new mod.
      3 – In your Saved Games \ Skyrim Special Edition folder you will find the two Bashed Patch files, one a txt and one an html. Put those two files into the empty Doc folder that Wyre Bash makes.
      4 – Make sure you check the box to activate your new mod. Going forward you will not get the error.

      Like

    1. I haven’t worked with Mator Smash nearly enough to feel comfortable recommending it yet. Maybe in the future!

      Like

  2. Hi,
    Great guide!
    Helped me to get started on modding SSE.
    All 100 plus mods stable and working.
    No CTD’s. I needed some advice from you.
    Which landscape and flora mods would you recommend along with this setup.
    I believe my system has good enough power to handle it
    I7-4790K stock
    16gb ddr3
    GTX 1060 6gb

    Like

    1. Skyrim Flora Overhaul is the obvious recommendation, but I prefer a slightly different setup. I like Vanilla Vegetation Overhaul, and Simply Bigger Trees. You can swap out VVO for Verdant or Veydosebrom and use HQ Tree Bark for the trees, if you want to really max out the visuals.

      Like

    1. A DynDOLOD guide will be added to Hitting The Books when the first of my new packs, The Winds Of Change, is published. The Winds Of Change will definitely need DynDOLOD, but it might not need Merge Plugins. I haven’t decided yet. If I do decide to use it, expect instructions for it to be added at the same time.

      Like

  3. Hey there. Great guide but I’ve hit a hiccup.

    I’m trying to open Wrye Bash through MO and it won’t open. I’ve set it up just like every other program but it just refuses to work. Below is a full breakdown of what happens.

    1. Modify Executables: Binary: xxx\Mod Tools\Mopy\Wrye Bash.exe ; Start in: xxx\Mod Tools\Mopy
    2. Launching Wrye Bash from MO: MO locks and says WryeBash.exe ; unlocks without opening Wrye Bash
    3. Launching Wrye Bash through the file explorer brings up a window that says “Move File” and asks if I want to Move and Replace, Don’t Move, or Move and Keep Both Files for a file called _tempfile.tmp
    a. Each one has a different directory. The Move and Replace leads to my C: while the Don’t move leads to my Games drive in Steam\steamapps\common\Skyrim Special Edition\Data

    I’m completely at a loss. I’ve tried to remove and reinstall Wrye Bash both through the standalone executable and the installer and nothing seems to work.

    Like

    1. There’s a new version of MO2 available on the Nexus. This was an issue that several devs worked very hard on and works perfectly well.

      Like

  4. I have followed this guide to the letter but the game crashes at startup when the bashed patch is activated. When the bashed patch is inactive the game runs. This is so for both Dragon Rising and Blood’s Honour. Any idea’s?

    Like

Leave a comment