A quick word

Warning

Do not skip this page!

Before we get started, we need to have a quick but essential chat.

Your game MAY APPEAR BROKEN, and LOOT will not sort correctly:

  • Until you complete the entire guide.
  • If you add or remove other mods before completing the guide.
  • If you do not carefully read and follow every word of the guide. Do not deviate. Trust the guide!
  • If you are not willing to teach yourself how to use all of the modding tools used in this guide.

If you choose to disregard this warning, you will see many errors in LOOT. You should expect these errors, at least until I tell you to run LOOT, as they are due to how drastically this guide changes the game.

Please, for Talos' sake, read the Nexus description of every mod you install.

Many mods contain multiple parts or several downloads. These individual downloads should be handled according to the following guidelines unless otherwise specified:

  • Files downloaded from the "Main Files" section should be installed as separate mods in MO2.
  • Files downloaded from the "Updates" and "Hotfixes" sections should be merged with their parent mod in MO2. This is accomplished by entering the same name for the update file that you gave its parent, then selecting the Merge option when prompted.
  • Files downloaded from the "Optional Files" and "Miscellaneous Files" sections should be treated as main files and installed as separate mods in MO2.

This guide contains many custom patches. These patches are necessary to make several hundred mods play together nicely. As such, attention to detail is crucial if you want to end up with a properly-working game.

General Utilities

7-Zip

    TOOL

7-Zip is a free, multi-format compression program capable of handling virtually any archive.

Main Files7-Zip for 64-bit Windows x64 (Intel 64 or AMD64)

.NET 5.0 SDK

    TOOL

.NET is a free, cross-platform, open-source developer platform for building many different types of applications. This is required for Synthesis and Scrambled Bugs to function properly.

Main FilesDownload .Net SDK x64

Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022

    TOOL

The Visual C++ Redistributable installs Microsoft C and C++ (MSVC) runtime libraries. These libraries are required by many applications built by using Microsoft C and C++ tools. This is required for Mod Organizer 2 and LOOT to function properly.

Main FilesMicrosoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022 - x86Main FilesMicrosoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022 - x64

Official Bethesda Content

Skyrim Special Edition

   

Steam Overlay

The Steam Overlay is known to cause issues while playing Skyrim Special Edition, and you are advised to disable it; to do this perform the following:

  1. Load Steam.
  2. In the toolbar at the top of the window, click Steam.
  3. In the dropdown menu, click Settings.
  4. Then in the popup box select the In-Game menu item.
  5. Uncheck Enable the Steam overlay while in-game then click OK.

Alternatively, if you would just like to disable the Overlay for Skyrim Special Edition you may:

  1. Load Steam.
  2. Click LIBRARY.
  3. In your games list, look for The Elder Scrolls V: Skyrim Special Edition and right-click on it.
  4. In the dropdown menu, click Properties.
  5. Then, in the popup box, uncheck Enable the Steam Overlay while in-game.

Update Proofing Skyrim

Bethesda regularly (roughly every three months) updates some of the base Skyrim files in support of their Creation Club content. This means that SKSE (and a bunch of mods that use it) will no longer function. In order to prevent STEAM from updating these files, it is required that you make the following selections:

  1. In STEAM, right click on The Elder Scrolls V: Skyrim Special Edition.
  2. In the menu that appears, click on Properties.
  3. In the popup window, select the Updates tab.
  4. In the selection box under "Automatic Updates", select "Only update this game when I launch it".
  5. Close the window.

Despite the wording, no update to the game will occur UNLESS you launch the game via STEAM. Since we will be launching Skyrim via MO2 and the SKSE launcher, no trigger event will occur and your Skyrim install will remain in the same state as it currently is until you force the update yourself.

In the event that it still updates, it is possible to roll back to an earlier version. Rather than detail this procedure, we recommend reading this article for details on how to do so.

Configure Skyrim

Before we can start doing any modding, we need to set up Skyrim Special Edition, so we have a starting base configuration.

Start The Elder Scrolls V: Skyrim Special Edition through the Steam context menu to open the default Skyrim Special Edition launcher.

  1. Click Options.
  2. Click the Ultra button.
  3. Set Aspect Ratio and Resolution in the drop-down box. These should be set to your monitors' optimal resolution.
  4. Set Antialiasing to Off in the drop-down box. This is in preparation for the ENB Install.
  5. Ensure that Windowed Mode is unchecked.
  6. Click the OK button to close and save.
1
2
3
4
5
2

Click the Ultra button.

3

Set the Aspect Ratio and Resolutions to your monitors' optimal settings.

4

Set Antialiasing to Off.

5

Ensure Windowed Mode is unchecked.

Creation Kit

   
Note

If you use Windows Defender Firewall, you may find the CK crashing when trying to launch it for the first time. If this happens, try adding an outbound rule in Windows Defender Firewall.

New to the Creation Kit? There's a great installation video available by Darkfox127!

The Creation Kit is the official Bethesda tool for creating and editing mods. It has been available in one form or another through the release of the last several Fallout and Elder Scrolls games and is invaluable if you have any interest in working with mods for modern Bethesda games.

Beyond allowing users to build their own completely original mods, the Creation Kit (or CK) can tweak and change things throughout both mods and official content in ways not possible through other tools.

Much like with Skyrim itself, the Creation Kit doesn’t ship with a pre-configured .ini, and the “default” configuration generates when the tool runs for the first time.

While you won’t be building new mods in this guide, you will be importing mods originally designed for Skyrim LE, and the Creation Kit will allow you to re-save (and thus, update) them to work with Skyrim SE.

  1. Download and install the Bethesda.net Launcher.
  2. Run the Launcher and sign in (create an account if you don't have one).
  3. In the left pane, expand options to show "All Games" via >>
  4. Select "Creation Kit: Skyrim" and select "Install"
  5. After completion of the installation, click on "Play"
  6. Select "Yes" in the "Script Source Extraction" box
  7. Close the Creation Kit program.

There are a few edits that need to be made before you can use the CK to port mods.

  1. Download the premade CreationKitCustom.ini here
  2. Extract it to Steam\steamapps\common\Skyrim Special Edition.

The custom ini file sets up the CK to allow multiple masters and properly load DLC content.

Note

The scripts archive in the DATA folder can remain in place after the script extraction done during installation. They cause no harm, have no additional affect on the game itself or the Creation Kit, and can be safely ignored.

SSE CreationKit Fixes

    TOOL

Various patches and bug fixes for the Creation Kit to make life easier.

Main FilesCK64Fixes Release 3.2
Special Instructions
  • Manually extract the mod and place in the main Skyrim Special Edition directory.

Page File

  • Press Windows + R on your keyboard and enter sysdm.cpl ,3
  • Under the Performance section, press 'Settings'
  • Go to the Advanced tab at the top, and at the Virtual memory section press 'Change...'
  • Disable 'Automatically manage paging file size for all drives.
  • If you have more than one drive, try enabling it for at least one more drive as a backup (make sure it has a decent bit of free space, like 15GB). Set the size to 'System managed size'.
  • Otherwise, set a custom size for the drive it's currently on and increases the maximum size to be at least 20GB

This is to ensure that proper paging is done. Some SSD drive managers can/used to disable paging on non-system SSD drives to prevent too much writing to occur.

This is no longer relevant for recent SSD drives. Virtual memory paging not only handles RAM to disk paging but also dedicated VRAM (on GPU card) to shared video memory paging (in system RAM)! If paging is disabled on the Skyrim/MO2 drive, and you run out of dedicated video memory you will have random CTDs on region/cell transitions.

Tools

LOOT

    TOOL

LOOT is a utility for load order optimization and is critical for any modded Skyrim run, especially with a list as long as ours.

Note

You will need to run LOOT Once Outside of Mod Organizer 2 and sort your Load Order to ensure the Masterlist updates properly. See Special Instructions below.

Wartortle's tutorial takes you through how to setup the Custom LOOT Groups.

Main FilesLOOT.Installer.exe
Special Instructions
  • LOOT, on first load, has no Masterlist data or default mod groups. (Colored Text indicates the colour of the node (default).
    1. Shut down Mod Organizer 2, if open. (If following the guide for the guide for the first time, MO2 hasn't even been installed yet.)
    2. Run LOOT from its installed location.
    3. Once LOOT has loaded, sort the load order by pressing the icon featuring three lines over each other. This is in the top right corner.
  • The guide requires the addition of new LOOT Mod Groups to properly sort the load order.
    1. Run LOOT (if it's not still loaded from the last step. If you closed it, you can load it through MO2 at this point if desired.)
    2. Locate and click on the Options button in the top right corner (identified by 3 dots over each other).
    3. Open Groups Editor
    4. In the Add New Group box, type Trivial Smelters of Skyrim, then the plus button.
    5. Left-click the Cell Settings node to select it.
    6. Left-click and drag a line from Cell Settings to the Trivial Smelters of Skyrim node that you created. Trivial Smelters of Skyrim should turn green.
    7. Create a new group called MLU Patches
    8. Connect Trivial Smelters of Skyrim to  MLU Patches node that you created. MLU Patches should turn green.
    9. Create a new group called CCOR Patches
    10. Connect MLU Patches to  CCOR Patches node that you created. CCOR Patches Merged should turn green.
    11. Create a new group called CACO Patches
    12. Connect CCOR Patches to  CACO Patches node that you created. CACO Patches should turn green.
    13. Create a new group called Snazzy Patches
    14. Connect CACO Patches to  Snazzy Patches node that you created. Snazzy Patches should turn green.
    15. Create a new group called  Merge Patches
    16. Connect Snazzy Patches to  Merge Patches node that you created. Merge Patches should turn green.
    17. Create a new group called iWant Patches
    18. Connect Merge Patches to iWant Patches node that you created. iWant Patches should turn green.
    19. Connect iWant Patches to Lighting Enhancers iWant Patches should turn grey.
    20.  Create a new group called NPC Retextures
    21. Left-click and drag a line from Khajiit Speak to the NPC Retextures node that you created. NPC Retextures should turn green.
    22. Create a new group called Consistency Patches
    23.  Connect NPC Retextures to Consistency Patches Consistency Patches should turn green.
    24. Create a new group called Conflict Resolution
    25. Connect Consistency Patches to Conflict Resolution Conflict Resolution should turn green.
    26. Connect Conflict Resolution to Leveled List Modifiers Conflict Resolution should turn grey.
    27. Create a new group called Village Mods
    28. Connect Alternate Start to Village Mods, Village Mods should turn green.
    29. Connect Village Mods to Follower Frameworks, Villages Mods should turn grey.
    30. Verify all of the newly added groups are showing as grey. Press Apply to exit this interface.

xEdit

    TOOL

This program is an essential tool that will help with cleaning mods of dirty edits and enable the creation of patches required by this guide.

Notice

xEdit is often used interchangeably with the term SSEEdit, both in this guide and in forums and Discord channels. These are both in reference to the same program: xEdit is the program, with the 'x' replaced with the game it is designed to work with (e.g. SSE for Skyrim Special Edition, FO4 for Fallout 4, etc). For the purposes of this guide, xEdit refers ONLY to the SSE version, SSEEdit.

Main FilesSSEEdit 4.0.3

Mators xEdit Patching Framework

    TOOL

MXPF is an xEdit scripting library that provides a variety of functions for the generation of patches.

Main Filesmxpf.zip
Special Instructions
  • Click on Code then click on Download zip.
  • Once downloaded extract the contents of the Edit Scripts folder in the archive to the Edit Scripts folder found in the SSEEdit main installation folder.

Synthesis

    TOOL

A framework and GUI to construct a single Bethesda game patch from many patcher sources. Designed to allow any program to work as a patcher as long as it conforms to the CLI API.

Main FilesSynthesis.zip

Lexy's LOTD Synthesis Profile for v0.20.4

    TOOL

This mod is a premade profile to use with Synthesis v0.20.4

Main FilesLexy's LOTD Synthesis Profile for v0.20.4
Special Instructions
  • Extract the contents of the archive to where you installed Synthesis.

TES5EditScripts

    TOOL

Bunch of useful xEdit Scripts.

Main FilesTES5EditScripts
Special Instructions
  • Click on Code then click on Download zip.
  • Once downloaded extract the contents of the Edit Scripts folder in the archive to the Edit Scripts folder found in the SSEEdit main installation folder.

WICO cleanup script

    TOOL

This is a script that will help clean up Windsongs Immersive Character Overhaul.

Main FilesHishy_NPC_RecordForwarding.pas
Special Instructions
  • Once downloaded extract the contents of the Hishy_NPC_RecordForwarding.pas-5049-2-5b archive to the Edit Scripts folder found in the SSEEdit main installation folder.

Dark Face Issue Reporter

    TOOL

This is an xEdit script to find "Dark Face Issues" and address them, then create console command batch files for checking in game.

Main FilesDarkFaceIssueReporter
Special Instructions
  • Once downloaded extract the contents of the DarkFaceIssueReporter archive to the Edit Scripts folder found in the SSEEdit main installation folder.

Cathedral Assets Optimizer

    TOOL

Cathedral Assets Optimizer is a tool aiming to automate asset conversion and optimization for Skyrim Special Edition.

Main FilesCathedral Assets Optimizer

Lexys LOTD SE CAO Profiles for v5.3.3

    TOOL

Cathedral Assets Optimizer profiles for Lexy's LOTD Skyrim Special Edition.

Main FilesLexys LOTD SE CAO Profiles for v5.3.3
Special Instructions
  • Once downloaded extract the contents of the Lexys LOTD SE CAO Profiles for v5.3.3 to the profiles folder found in the Cathedral Assets Optimizer main installation folder.

Wrye Bash

    TOOL

The function of this tool is to manage mods and create Bashed Patches. Bashed Patches merge the leveled lists from the installed mods and has some limited functionality to merge mods and tweak game values. For this guide, you will only use the Bashed Patch functionality.

Notice

WINDOWS 10 USERS: Ensure that your O/S has installed the Windows 10 1809 Update or higher. This will ensure that Wrye Bash is able to properly load, as the 1803 update creates a situation where WB attempts to load itself, which it can't because it's already in use.

Notice

WINDOWS 10 USERS: When using Wrye Bash, a 'Docs' folder will be generated and appear in your Overwrite folder. This is not needed for Skyrim to run properly, and can be safely deleted between sessions.

Main FilesWrye Bash 309.1 - Standalone Executable
Special Instructions
  1. Download the file manually.
  2. Extract the contents of the file to a location of your choice. It is advised not to install it into any UAC controlled locations. It CAN be installed into the Skyrim main directory, if you so choose, with no detrimental effects.
  3. WINDOWS 7 USERS: A 'docs' folder needs to be created in Skyrim Special Edition\Data. WIN10 users do not need to follow this step, as it will be auto-created and placed into your Overwrite folder. For additional info, see Notice above.

zEdit

    TOOL

This tool is similar to SSEEdit. It includes zMerge, which is used for merging plugins.

Main FileszEdit_v0.6.6.1_-_Portable_x64.7z

Script Extenders

Skyrim Script Extender

    TOOL

SKSE is absolutely essential. It extends the scripting capacity of the game to allow mods to do things that would not normally be possible in the base Skyrim engine. Many mods depend upon it.

Main FilesCurrent SE build 2.0.20 (runtime 1.5.97)
Special Instructions
  • Install ONLY the following files in the main Skyrim Special Edition directory:
skse64_1_5_97.dll
skse64_loader.exe
skse64_steam_loader.dll

Mod Manager

This guide was written specifically for use with Mod Organizer 2 and its in-built functionality. Any attempts to use alternative mod management systems are unsupported. Some users have had success doing so, but any support will be unofficial and from other users only.

Note

The paid for version of ccleaner is known to break Mod Organizer 2's Virtual Filing System (VFS). Unchecking the 'windows event logs' option under ccleaner's advanced tab will help ensure this doesn't happen. Also make sure the Profile Folder Remains in the same location of Mod Organizer 2 as all the base files.

Mod Organizer 2

    TOOL

This is the tool we'll actually be using to download, install and manage the mods. Don't worry if it looks daunting, we'll set you right shortly.

Main FilesMod Organizer 2

Installing Mod Organizer 2

Warning

Mod Organizer 2 MUST be installed in portable mode. The Script ReLinker functionality of zEdit requires this management method to complete it's work. There are no workarounds for this requirement.

Warning

Please don't put MO2 in either program files or the main Skyrim Directory.

Install Mod Organizer 2:

  1. On the first run of MO2 Windows may give you a warning that Windows Defender doesn't recognise the App and has prevented it from running.
  2. Click More Info and click Run anyway
  3. You may then be presented with a User Account Control warning Click Yes.
  4. You should be able to install MO2 like any normal program.
  5. Pick a location to install MO2 outside of Program Files.
  6. Once installed launch MO2.
  7. At the Create new instance page make sure you select Create a Portable Instance.
  8. In the next pop-up that appears, select Skyrim Special Edition.
Idiot Check

Ensure that you do not move the mods folder out of MO2's install folder at any time. This is needed to ensure that MO2 can see the mods you are about to install.Similarly, do not move the profiles folder out of MO2's install folder at any time. This is needed to ensure that the Script ReLinker functionality of zEdit works as intended.

Configuring Mod Organizer 2

With Mod Organizer 2 now properly installed, there are additional settings that will be required to ensure full integration with the NEXUS and user comfort.

Special Instructions:

Mod Organizer needs to be connected to the NEXUS for account logins and download management.

  1. Full integration with the NEXUS requires that you have a NEXUS account. If you do not have one, you can create one here. This will also be required for large file downloads, and is free of charge (though a free account will also be very limited in bandwidth). A Premium subscription with no bandwidth cap is available. Details can be found on the NEXUS website.
  2. In the toolbar of Mod Organizer 2, locate the 'Settings' button (it will have a spanner and screwdriver icon on it... wrench and screwdriver for you Americans).
  3. At the top of the window that appears, press on the Nexus tab.
  4. Click on the Connect to Nexus button.
  5. A new window will open in your browser, and the Nexus will request permission to link Mod Organizer 2 with your Nexus Account. After allowing this, you can close the browser window.
  6. In the Mod Organizer 2 settings menu, press OK to close the window.

Some users may find the default MO2 theme overly bright or harsh.

  1. In the toolbar of Mod Organizer 2, locate the 'Settings' button (it will have a spanner and screwdriver icon on it... wrench and screwdriver for you Americans).
  2. At the top of the window that appears, press on the Theme tab.
  3. Locate the Style dropdown (possibly with the word "None" in it currently). Any theme may be selected, based on user preference. Most users report the most comfort with the 'dark', 'Paper Dark', or 'vs15 Dark' themes. Note that all FOMOD screenshots in the guide are taken with the vs15 Dark theme.
  4. After selecting a theme, press OK to close the window.

Some settings can be configured to show the user more information at a glance.

  1. In the left pane of Mod Organizer 2, right-click any of the column headers (for example 'Mod Name', 'Conflicts', 'Flags', etc.)
  2. Check 'Content'. This will show graphical representations of certain file types included in a mod. You can mouse over the graphics for an expanded view with a legend.
  3. In the toolbar of Mod Organizer 2, locate the 'Settings' button (it will have a spanner and screwdriver icon on it... wrench and screwdriver for you Americans).
  4. At the top of the window that appears, press on the Workarounds tab.
  5. Under the Options category, check 'Enable archives parsing (experimental)'. While not perfectly accurate yet, this will show conflicts with BSA archives in the Conflicts column of the left pane.
  6. At the top of the window, press on the General tab.
  7. Under the Download List category, check 'Show meta information' and 'Compact list'. Showing meta information will show human readable names of files as well as the file version in the Downloads tab of the right pane. Compact list will get rid of the unnecessary whitespace in the Downloads tab and will fit more files on the screen at once.
  8. Press OK to close the window.
Notice

Depending on your specific download practices, the downloads for the mods can be well over 100 Gb of data. If you have installed MO2 onto a relatively small drive (such as a small SSD), you should consider changing the location of MO2's download storage to a larger location. This can be done by creating a file folder in the desired location, opening the MO2 Settings interface (as above), selecting the Paths tab, and altering the Downloads path to match the newly created file folder.

Base Profile Creation

With Mod Organizer 2 installed and correctly configured, it is time to introduce the creation of Profiles, one of the signature features of Mod Organizer 2. Profiles are used to create mutiple 'versions' of your mod installs, which allows for anything from multiple versions of an install to shorter installs in support of merges (one of the primary things this guide will use it for). This step will familiarize you with the creation of profiles for later in the modding process.

Special Instructions:

Mod Organizer 2 is currently using a "Default" profile. A "Vanilla" profile needs to be created to establish a working game baseline and for troubleshooting purposes.

  1. Locate and press the Configure Profiles button (most MO2 themes show this as an icon that looks like an ID card, but it can vary).
  2. In the Profiles Window, select Create.
  3. In the pop-up, type Vanilla Skyrim SE.
  4. Ensure that the Default Game INI Settings checkbox is unchecked.
  5. Select OK.
  6. Verify that Vanilla Skyrim SE appears in the list on the left.
  7. Verify that the Use profile-specific Save Games is checked.
  8. Verify that the Use profile-specific Game INI Files is checked.
  9. Exit the Profiles Window by pressing Close.
  10. In the Profile dropdown above the mod list (aka "the left pane") select Vanilla Skyrim SE.
  11. Locate and press the Configure Profiles button (most MO2 themes show this as an icon that looks like an ID card, but it can vary).
  12. Click on and highlight the Default profile.
  13. Click on Remove.
  14. In the pop-up that appears, select Yes.
  15. Exit the Profiles Window by pressing Close.
  16. Verify that Vanilla Skyrim SE appears as the selected profile (shown above the the left pane).

Setting up Base Tools for Mod Organizer 2

The last major step is to setup some of the previously installed tools to work from within Mod Organizer. Running these tools via Mod Organizer 2's launcher will allow the other tools to make use of the Virtual File System and see the files from the installed mods as the game, itself, will when it is loaded.

Notice

Some programs that have been installed will be automatically detected by MO2, including SKSE, Skyrim, the Skyrim Launcher, LOOT, and the Creation Kit. These will appear in the MO2 Launcher (just above the right-pane) and are pre-configured.

Special Instructions:

xEdit, Wrye Bash, Synthesis and zEdit need to be set up within Mod Organizer 2.

  1.  Locate and press the Executables button (most MO2 themes show this as an icon that looks like a gear, but can vary).
  2. A pop-up box should appear press the + (Add an executable) button.
  3. In the pop-up box select "Add from file..."
  4. In the Windows folder that opens, navigate to and double-click on SSEEdit.exe in its installed location.
  5. Ensure no optional checkboxes are checked.
  6. Select "Apply" at the bottom right of the pop-up.
  7. Repeat steps 2 through 6, selecting "SSEEdit – Quick Auto Clean.exe" file from the installed location. This second instance will be used only for cleaning the plugin files and will be explained further later in the guide.
  8. In the Argument field of  "SSEEdit – Quick Auto Clean" add -Dontcache
  9. Repeat steps 2 through 5 for Wrye Bash, Synthesis and zEdit selecting the appropriate executable file in each case. No arguments are needed for these entries.
  10. After all the programs have been added, click on the "OK" button on the bottom right of the Modify Executables window.
Notice

xEdit will create a "xEdit Cache" folder in your Overwrite files in MO2. Adding -C:"(Drive letter):\Skyrim SE Tools\SSEEdit\Cache\" (using the appropriate actual folder structure you use) will redirect these files to the xEdit folder you installed earlier. Alternately, you can also make those a separate mod in MO2 and keep it activated... the cache is there to help speed up xEdit load times and has no effect on your game.

Initial Mod Ordering

Mod Organizer 2 will have automatically detected the three official DLC files for Skyrim, but will have them ordered alphabetically, which is not desired. Note also that they will be listed as "Non-MO" under the Category heading - this is an indication that the files are located in the Skyrim base directory. These should be the only files with this listing through the entire guide... if you see it again, you have incorrectly installed a mod.

Special Instructions:

Initial detection of the Skryim DLC will place the assets in an incorrect order. They should be sorted in order of release.

  1. In the left pane, drag-and-drop the three DLC files into the following order (top-to-bottom): Dawnguard, HearthFires, Dragonborn.

The load order of the Skyrim DLC plugins can be confirmed by LOOT.

  1.  From the drop-down Executables list (right-side, above the plugins list), select LOOT.
  2. Press the Run button.
  3. Once LOOT has finished loading, locate the "Sort" button in the top right corner and click on it. Its icon is three horizontal lines above each other.
  4. LOOT will automatically download any updates to its masterlist. It will then compare the files it sees (which is only the DLC at this point) to this masterlist files and sort them into a proper order. Additional messages will be displayed after sorting that indicate that there are ITMs and Deleted References in these files. An explanation of those terms will be given later on in the guide.
  5. Click Apply to accept LOOT's generated load order (if LOOT made any changes). If no changes were made (which happens on occasion), the Apply button may not appear. This is normal, and of no concern.
  6. Close LOOT by using the X button in the top right corner of the LOOT window.

This process has taught you two processes:

  • Loading of LOOT via Mod Organizer. This same process applies to all programs loaded via MO2, and will not be repeated in other steps during the modding installation process. If a tool needs to be loaded in any other fashion, those instructions will be noted when needed.
  • Sorting of a load order using LOOT. This will only be done once more (officially) in the guide, near the end of the process. However, this process is universal to ANY mod list and can be applied in many other circumstances.

The Vanilla Skyrim SE Profile is now properly set up. This profile should be kept for possible troubleshooting purposes, but otherwise left alone.

Creating Legacy Of The Dragonborn: Special Edition Profile

So far we installed and set Mod Organizer 2 up to work with all of the required tools, and to load with a Vanilla profile. You now have the ability to load Skyrim SE with a single click, which can be useful for troubleshooting, but isn't much good for playing a modded game. The next thing to do, then, is to create a new profile where we will install all of the mods.

First, however, a couple things to note.

  • Verify Use profile-specific Game INI Files is checked. When you create a new profile, Mod Organizer creates new copies of the Skyrim.ini and SkyrimPrefs.ini for use by that profile and that profile only. If and when you make changes to these files through MO2, you will be making changes to the profile specific versions of these files, not the ones that are in your Documents directory.
  • Also verify Use profile-specific Save Games is checked on each new profile.

New profile for Lexy’s LOTD:SE

  1. Using the directions provided previously to create the Vanilla Profile, create a new profile with the name "Legacy of the Dragonborn - Special Edition" (or another name of your choosing).
  2. In the left pane, drag-and-drop the three DLC files into the following order (top-to-bottom): Dawnguard, HearthFires, Dragonborn.
Idiot Check

When sorted by priority, from top to bottom, the order of the left pane mods list should be: (0) DLC: Dawnguard, (1) DLC: HearthFires, (2) DLC: Dragonborn; the order of the right pane Plugins tab should be: (0) Skyrim.esm, (1) Update.esm, (2) Dawnguard.esm, (3) HearthFires.esm, (4) Dragonborn.esm

xEdit is not fully configured

From MO2, run SSEEdit and perform the following:

  1. At the popup window click OK to load the selected plugins.
  2. Wait for the plugins to load. You will see the message "Background Loader: finished" when the program is done loading.
  3. Right-click on any plugin in the list on the left side of the screen.
  4. From the popup menu navigate to Other→Options; a new popup box should appear.
  5. Uncheck Simple Records LAND, NAVI, NAVM, CELL, WRLD (requires restart).
  6. Click OK.
  7. Exit SSEEdit.

SKSE is not fully installed

You may recall that in the SKSE installation earlier, we only installed three files directly to the Skyrim main directory. We did not install all of the scripting files. We will be using this to show how to install a mod from an archive, which will be a needed skill for a small number of mods we will be installing later.

  1. Ensure that the newly created "Legacy" profile is selected at the top of the left pane in Mod Organizer 2.
  2. In the MO2 toolbar, locate and click on the "Install a new mod from an archive" button (will look like a file folder in most themes).
  3. In the window that opens, navigate to the location of the SKSE file downloaded earlier. Click on it to highlight it.
  4. Click on Open.
  5. In the next window that appears, replace the text (if any appears - sometimes there isn't any) with SKSE Scripts. This is the name that will appear in the left pane of Mod Organizer 2 after installation.
  6. Another window will appear, as the SKSE archive is not properly set up for an automatic installation. If this is the first time you've seen this window (and we assume it is), MO2 will give you a quick tutorial on how to use this tool. Read it to help with understanding the following instructions. Click on the flashing tutorial to continue.
  7. In the file tree, navigate to and highlight the Data folder inside the archive.
  8. Right-click on Data.
  9. In the right-click menu, select Set Data Directory. The display should change to show only a Scripts folder, which should be checked. A green "Looks good!" will appear at the bottom of the window if you have done this correctly.
  10. Select OK.

A new entry should appear in the left-pane with the name given it above and an empty checkbox next to it. This indicates that it has been installed but not activated. Also note that MO2 does not have a version number or category set for this mod because it doesn't have any Nexus metadata. We will manually input this information in a later step.

SKSE.ini

First we need to confirm that Windows filename extensions are visible.

  1. Open Windows File Explorer.
  2. In the top title bar select the View tab.
  3. Make sure 'File name extensions' is checked.
  4. Close the window.

Before you can edit the SKSE.ini file, you will have to create it.

  1. Right-click SKSE Scripts in the Mod Organizer mod list.
  2. Select Open In Explorer.
  3. Create and enter a folder named SKSE.
  4. Create and open a text file named SKSE.ini.

(This should give you a folder structure of ...\mods\SKSE Scripts\SKSE\SKSE.ini)

Once this file is open to be edited, paste in the following:

[General]
ClearInvalidRegistrations=1

[Display]
iTintTextureResolution=2048

The 'ClearInvalidRegistrations' setting enables self-healing of rogue updating scripts in saves. The 'iTintTextureResolution' setting allows higher resolution textures for warpaints.

Save and close SKSE.ini then exit explorer.

SKSE does not have a version number or category set

  1. Right-click SKSE Scripts in the mod list.
  2. In the right-click menu, select 'Information...'. Alternately, you can also double-click the mod name to achieve this as well.
  3. In the Categories tab, locate and place a checkmark next to 'Utilities'.
  4. In the NEXUS Info tab, set the version number to the installed version of SKSE (as annotated in the SKSE download earlier).
  5. In the NEXUS Info tab, set the Mod ID -1. This tells MO2 that the installed files were not provided by the NEXUS, and will prevent MO2 for searching the NEXUS for data and update information (among other things).
  6. Click Close to save and exit the window.

Notice

In addition to the files installed by a given mod, all file trees will also show a meta.ini file that is added by MO2. This is generated and used by Mod Organizer for its VFS - even if you delete it, the file will be regenerated. It is otherwise safe to ignore.

Notice

Any mod downloaded directly by Mod Organizer 2 from the NEXUS will have one or more of the data fields filled in automatically, based on NEXUS server-provided information (metadata). This data can be changed to suit personal tastes, if desired, with no other effects.

For future reference, version numbers for mods hosted on the NEXUS can be checked for updates. These will then display as:

  • Green for any up-to-date mod.
  • Red for any mod that has a version mis-match. This generally means (but does not always mean) that an update has occurred.
  • White for any mod that is not hosted on the NEXUS.

As noted earlier, the SKSE Scripts are now installed, but are not yet active files, and thus will not be visible to the game on launch.

  1. Activate the SKSE Scripts by checking the box next to its name in the left pane. Nothing will change in the right-pane listing - this is normal and expected.
  2. For future mod installations, it will be assumed that a mod should be activated after installation, and this direction will not be repeated.

The files inside of the SKSE Scripts folder are now visible to the MO2 VFS, and on game launch will act as if they have been placed in the Skyrim/Data folder. File conflicts between mods will be handled by Mod Organizer 2 in order of installation - files installed later will override the files that came before.

Installation Verification:

SKSE is needed to run many mods this guide uses. Proper installation needs to be verified.

    1. Run Skyrim:SE by using the SKSE Executable in MO2.
    2. After the game has loaded into the main menu (listen for the Skyrim Theme to play), open the console with the ~ key (by default). This is the key directly above the TAB key on most keyboards.
    3. In the console that opens, type getskseversion and press enter.
    4. Verify that a new line appears in the console, indicating the version of SKSE you have installed. If there is no output, or a version other than the one you installed appears, reinstall SKSE with the correct files or verify correct installation against the instructions provided above.
    5. Exit Skyrim.
Notice

DO NOT continue past this point unless you are certain that SKSE is correctly installed.

Mod Organizer 2 Plugins

Merge Plugins Hide

   

This is a plugin for Mod Organizer 2 that allows you to hide merged plugins easily.

Main Filesdeorder_plugins-1.1.zip
Special Instructions
  1. Extract the contents of the archive to your Mod Organizer 2 plugins directory.
  2. Load Mod Organizer 2 and press the screwdriver and spanner icon.
  3. Navigate to the Plugins tab.
  4. Scroll down until you find Merge Plugins Hide.
  5. In the right-hand box change hide type to optional.
  6. Click OK.
Merge Plugins Hide is now set up and will move merged plugins to the optional directory within Mod Organizer 2. It can be accessed via the puzzle icon within Mod Organizer 2.
Idiot Check

Make sure the o in optional is lowercase.

Prepare Merge - Mod Organizer 2 Plugin

   

This plugin for Mod Organizer 2 finds and enables the mods containing a selected list of plugins and their required masters. Then it places the selected plugins at the end of the load order. Useful for preparing a merge of plugins with e.g. zMerge.

Main FilesPrepare Merge
Special Instructions
  • Extract the contents of the archive to your Mod Organizer 2 plugins directory.

Cleaning the Bethesda ESMs

We begin the modification process by altering some of the vanilla game files. Bethesda, like a number of modders, have created unintended duplication of records in their DLC files. These records are referred to as Identical to Master records, or ITMs. In most cases, these are not inherently game-breaking, and usually can be ignored if one is playing a mostly vanilla game. For a heavily modified game, however, they can have undesirable effects.

Another issue, and one that is far more serious, are deleted records. These can cause Crash to Desktop (CTD) errors, and should always be cleaned from plugin files.

Both ITMs and UDRs exist in the Bethesda DLC content files, and will need to be cleaned. Please note the process described below is universal to all mods the need cleaning, so will not be repeated for any other mods that require cleaning throughout the guide.

Cleaning Instructions:

Create a backup of the original files.

  1. Navigate to ...\Skyrim Special Edition\Data.
  2. Copy-Paste the following files to your desktop or other readily available location: Update.esm, Dawnguard.esm, HearthFires.esm, and Dragonborn.esm.

The games files contain ITM and UDR records, and require cleaning.

  1. Start Mod Organizer 2, if not already running.
  2. From the drop-down executables menu, select SSEEdit - Quick Auto Clean. Ensure this is the xEdit version with Quick Auto Clean, as this is the one that will handle the removal of ITMs and UDRs.
  3. Press Run.
  4. In the file selection menu that appears, check the box next to Update.esm and no other files. If any additional files need loading, xEdit will automatically load them.
  5. Click OK.
  6. xEdit will now run the cleaning process automatically.
  7. Wait for the process to complete, indicated by the appearance of the message Quick Clean Mode finished.
  8. When the message has appeared, close xEdit by clicking on the X in the title bar of the application ("X-ing out").
  9. Repeat steps 2 through 8 for Dawnguard.esm, Hearthfires.esm and Dragonborn.esm.
Notice

DO NOT ATTEMPT TO CLEAN SKYRIM.ESM. This will result in a corrupted file, as it will be compared to itself and all records would be deleted.

Dawnguard.esm requires manual xEdit cleaning in addition to the Automated cleaning:

  1. From the drop-down executables menu, select SSEEdit. Ensure this is the xEdit version without Quick Auto Clean.
  2. Press Run.
  3. In the plugin selection window, right click.
  4. In the right-click menu, select Select None.
  5. Place a check mark in the box next to Dawnguard.esm.
  6. Select OK. Dawnguard will now be loaded into xEdit, along with any other required files.
  7. After all plugins are fully loaded, click on the "+" next to Dawnguard.esm. Its file tree will expand.
  8. Locate and press the "+" next to Cell. Its sub-records will appear.
  9. Locate and press the "+" next to Block 5. Its sub-records will appear.
  10. Locate and pres the "+" next to Sub-Block 3. Its sub-records will appear.
  11.  Locate and click on 00016BCF. The right pane will now display all records associated with this cell record.
  12. In the right pane, scroll down and locate the XEZN sub-record that refers to RiftenRatwayZone [ECZN:0009FBB9.]
  13. Right click on the above entry under "Dawnguard.esm" select Remove. A window may appear warning you that you are making a change to the file – when able, allow the change. YOU ONLY NEED TO REMOVE THE RiftenRatwayZone [ECZN:0009FBB9.] ENTRY NOT THE ENTIRE RECORD.
  14. Do the same for Block 2 -> Sub-Block 1 -> 0001FA4C  CWGuardTemplates (remove the entire record).
  15. Block 8 -> Sub-Block 1 (remove the entire sub-block).
  16. Close xEdit and save by clicking the "X" in the program's title bar.

Create a new Mod in MO2

With all cleaning now completed, we will make these cleaned files into their own separate modification and restore the original files to the Skyrim directory. This will assist in 'future-proofing' your cleaned files for the inevitable Bethesda CC updates that would overwrite your cleaned files with the original versions.

  1. In your ...\Mod Organizer 2\mods folder, create a new folder called Cleaned Vanilla ESMs.
  2. In the Skyrim\Data folder, Cut and Paste the following files FROM the Skyrim\Data folder TO the Mod Organizer 2\mods\Cleaned Vanilla ESMs folder: Update.esm, Dawnguard.esm, Hearthfires.esm, and Dragonborn.esm.
  3. Cut and Paste the backup files you created earlier into the Skyrim\Data folder.
  4. Start Mod Organizer 2 (if not already active).
  5. A new mod should appear called "Cleaned Vanilla ESMs". If it does not appear, Right-Click -> All Mods -> Refresh.
  6. Activate the new mod.

With this process complete, we are now able to:

  • Run Skyrim through Steam, resulting in a completely vanilla experience.
  • Run Skyrim through MO2's "Vanilla Skyrim" profile using Skyrim in the drop-down, resulting in a completely vanilla experience.
  • Run Skyrim through MO2's "Legacy of the Dragonborn - Special Edition" profile using SKSE in the drop-down, resulting in a SKSE enabled Skyrim using cleaned vanilla assets.

From this point forward, unless otherwise noted, it will be assumed that you will always start Skyrim using the third option.

BethINI

BethINI

    TOOL

This program was created by DoubleYou (The S.T.E.P. resident INI Master). BethINI (pronounced "Bethany") is an attempt to restore decency to the INI configuration files for games created by Bethesda.

Main FilesBethINI Standalone Version
Special Instructions
  1. Close MO2 if open. MO2 must be closed or BethINI changes won't take effect!
  2. Run BethINI.exe outside of MO2.
  3. A popup window asking you to select your game will appear if running BethINI for the first time. Select game: Skyrim Special Edition.
  4. Under the Setup tab:
    1. Mod Organizer Path: Navigate to ModOrganizer.exe in your Mod Organizer folder.
    2. INI Path: Choose your Lexy's LotD profile from the dropdown.
  5. BethINI will restart. A popup asking about Modify Custom INIs will pop up, click No.
  6. Under the Basic tab:
    1. Click the DEFAULT button. This will refresh your INI files to the default settings for your system, with minimal tweaks.
    2. Click the HIGH preset.
    3. Make sure the BethINI Presets option is checked.
    4. Make sure Recommended Tweaks is checked.
    5. Make sure Windowed Mode is checked.
    6. Make sure Borderless is checked.
    7. Make sure FXAA is Unchecked.
    8. Make sure Antialiasing is set to NONE.
    9. Make sure VSync is unchecked.
    10. Make sure Lock Frame Rate is unchecked.
  7. Under the General tab:
    1. Make sure Intro Logos is unchecked.
    2. Make sure Post-Load Update Time is 2000
  8. Under the Gameplay tab:
    1. Make sure Over-Encumbered Reminder is set to 60
    2. Make sure NPC Use Ammo is checked.
    3. Make sure 1st Person Arrow Tilt-up Angle is 0.7
    4. Make sure 3rd Person Arrow Tilt-up Angle is 0.7
    5. Make sure 1st Person Bolt Tilt-up Angle is 0.7
  9. Under the Interface tab:
    1. Make sure the Bethesda Modding Platform is unchecked.
    2. Make sure Mouse Settings → Lock Sensitivity is 0.0125
  10. Under the Detail tab:
    1. Make sure Reflect Sky is checked.
    2. Make sure Field of View is set to 85.00
    3. Make sure Particles is set to 2000
    4. Make sure Depth of Field is checked.
    5. Make sure Lens Flare is unchecked.
    6. Make sure Shadow Resolution is set to 2048
    7. Make sure Shadow Bias is set to 0.47
    8. Make sure Sun-Shadow Transition is Unchecked.
    9. Make sure Ambient Occlusion is Unchecked.
  11. Under the View Distance tab:
    1. Make sure Grass Fade is set to 18000
  12. Under the Visuals tab:
    1. Make sure Grass Density is set to 60
    2. Make sure Grass Diversity is set to 15
    3. Make sure Improved Shader is unchecked.
  13. Under the Basic Tab, click the Save and Exit button.

Post BethINI Tweaks

While BethINI does handle the vast majority of the tweaks needed to the INI files, a few need to be changed manually. This will be done via MO2's INI Editor. To access the viewer, click on the Tools icon in MO2's toolbar, then select the INI Editor. Once open, make the following changes (if the option does not appear, add it):

Notice

The Skyrim.ini and SkyrimPrefs.ini files can be edited using the ini editor built into MO2. From the toolbar, click the Tools icon, then select INI Editor.

Skyrim.ini

[SaveGame]
bAllowScriptedAutosave=0
bAllowScriptedForceSave=0
bDisableAutoSave=1

SkyrimPrefs.ini


[Display]
bSAOEnable=0

[Main]
bSaveOnPause=0
bSaveOnRest=0
bSaveOnTravel=0
bSaveOnWait=0

Due to the heavily modded nature of this guide, it is advised to have autosaves turned off and to create fresh new saves every time and not overwrite old pre-existing saves.

SkyrimCustom.ini

SkyrimCustom.ini is created by BethINI and can be used to overwrite settings placed in Skyrim.ini. For the purposes of this guide, we will use a blank copy of this file. In the INI Editor delete any lines in the file. Click save and close the window.

NPC Chooser

NPC Plugin Chooser

    TOOL

This is a utility that is meant to help solve one of the long-standing frustrations of the game: how to mix and match NPC appearance mods that overlap.

Note

Make sure to Install NPC- NPC Plugin Chooser outside of the main Skyrim and Mod Organizer 2 mods folders.

Update FilesPre-Release
Special Instructions
  • Once Downloaded add NPC-Plugin-Chooser.exe as an executable in MO2.

Lexys NPC Chooser settings json

    TOOL
Note

When editing the settings.json file make sure you have double slashes.

This is a premade settings.json file for NPC Plugin Chooser.

Main FilesLexys NPC Chooser settings json
Special Instructions
  1. Navigate to NPC- NPC Plugin Chooser\Data and replace the settings.json file with the one I provide in this archive.
  2. Open the settings.json and edit the following:
  • "GameDataPath": "",
  • "MO2DataPath": "Drive letter:\\Replace with your MO2 location\\mods",
  • "AssetOutputDirectory": "Drive letter:\\Replace with your MO2 location\\mods\\NPC Appearance Output",

xLODGEN

xLODGen

    TOOL

This is a utility used to generate LOD meshes and textures "exactly" like the CK.

Note

Make sure to Install xLODGEN outside of the main Skyrim and Mod Organizer 2 mods folders.

Main FilesxLODGen-84
Special Instructions
  1. Download the main xLODGen-84 archive.
  2. Extract the contents to a new folder called xLODGEN but DO NOT PUT THE FOLDER INSIDE the main Skyrim Special Edition OR Mod Organizer 2 folder.
  3. Create a folder called SSELODGen_Output At the ROOT of a drive.
  4. Once the above is done, open Mod Organizer 2 and add xLODGenx64.exe as an executable.
  5. In the Arguments field enter -sse -o:"Drive Letter:\SSELODGen_Output"

DynDOLOD

DynDOLOD Standalone 3.00

    TOOL

This is a utility used to create a mod based on the load order, which adds custom, distant LOD for objects to Skyrim.

Miscellaneous FilesDynDOLOD 3.00
Special Instructions
  1. Download the archive file.
  2. Extract the contents to a new folder called DynDOLOD Special Edition.
  3. Once the above is done, open Mod Organizer 2 and add TexGenx64 and DynDOLODx64 as executables.
  4. In the Arguments field, enter -sse for each executable.
Enable Expert Mode in DynDOLOD:
  1. Navigate to ...\DynDOLOD Special Edition\Edit\Scripts\DynDOLOD\ and open DynDOLOD_SSE.ini in Notepad.
  2. In Line 8, set  Expert=1.
  3. Save and exit.

zMerge Setup

In this section you will set up zMerge so that you can create merged mods later on.

  1. Open zEdit and select zMerge from the drop-down menu.
  2. Press Start Session.
  3. Click on the cog in the upper-right corner and a new popup box should appear.
  4. Navigate to Integration Settings.
  5. Under Mod Manager select Mod Organizer 2.
  6. Under MO2 Instance select Portable.
  7. Under Mod manager path, fill in the file path to your main Mod Organizer 2 folder.
  8. Under Mod manager mods path, fill in the file path to your Mod Organizer 2 mods folder.
  9. Navigate to Merge Settings.
  10. Under Merge output path fill in the file path to where your Mod Organizer 2 mods folder is.
  11. Uncheck Disable plugins.
  12. Navigate to Archive Creation Settings.
  13. Under Advanced change Minimum files per archive to 999999.
  14. Under Advanced make sure Create texture archives is unchecked.
  15. Click OK.
  16. You can now close zMerge.

Check these pictures on how to set up zMerge if you're having trouble.

ENB Series

ENB Series Binaries

    ENB

This is a graphics modification library designed to allow gamers to configure their games to their liking.

Main FilesENBSeries v0.465 for TES Skyrim SE
Special Instructions
  1. At the bottom of the page, click the link for the specified version.
  2. At the bottom of the new page, click the download link.
  3. When the file has downloaded, open the Wrapper Version folder enclosed in the archive and extract ONLY the files d3d11.dll and d3dcompiler_46e.dll.
  4. Place the d3d11.dll and d3dcompiler_46e.dll into the main Skyrim Special Edition directory.

ENB PRESET

Ljoss ENB for Cathedral weather - Night Eye - Real time snow cover - Performance friendly

    ENB
Main FilesLjoss V10.03
Special Instructions
  • Install Ljoss into MO2 using the FOMOD then copy-paste all installed files to the Main Skyrim Directory.

Post ENB ini Tweaks

Once Ljoss is installed change the following, if the value doesn't exist add them:

Skyrim.ini

[Display]
fGlobalBloomThresholdBoost=5.0000
fSAOBias=0.5000
fSAOExpFactor=0.220
fSAOIntensity=12.0000
fSAORadius=850.0000
fSAOValueDiffFactor=0.3000

Skyrimprefs.ini

[Display]
bDrawLandShadows=1
bEnableImprovedSnow=0
bFXAAEnabled=0 - (You can set to 1 if you prefer, but choose only TAA or FXAA. Keep to 0 for guide-default SMAA from Ljoss ENB.)
bIBLFEnable=0
bIndEnable=0
bSAO_CS_Enable=0
bSAOEnable=0
bShadowsOnGrass=1
bTreesReceiveShadows=1
bUse64bitsHDRRenderTarget=1
bUseTAA=0 - (You can set to 1 if you prefer, but choose only TAA or FXAA. Keep to 0 for guide-default SMAA from Ljoss ENB.)
bVolumetricLightingEnable=1
fGamma=1.0000
iVolumetricLightingQuality=2

Setting up HDMI Full Range:

A special step is required for users that connect their GPU and monitor via an HDMI cable.

For Nvidia users:
Go to your Nvidia Control Panel (right click on your desktop).
Then go to "change resolution" and find "Output Dynamic Range" and change it to "Full". (If it is greyed out press "Use NVIDIA color settings" first.)

For AMD users:
If you're using a AMD/Radeon graphics card you need to do a similar tweak, but you have to change the display pixel format instead. This can be done by selecting "RGB 4:4:4 Pixel Format PC Standard (Full RGB)" instead of the default "RGB 4:4:4 Pixel Format Studio (Limited RGB)" inside of AMD Catalyst.

Antivirus and Windows Defender

Antivirus software and Windows Defender are known to interfere with the tools from the guide. It is strongly advised to add folder and process exclusions for all tools and MO2. It is also advised to add a file type exclusion for .nif.

How to add a process exclusion to Window Defender:

      1. Search for Virus & Threat Protection
      2. Under Virus & Threat Protection Settings click Manage Settings.
      3. Under Exclusions, click Add and Remove Exclusions.
      4. Click the Add An Exclusion button.
      5. From the drop-down menu click Process
      6. In the popup window under Enter Process name add the file path to the .exe you wish to exclude.
      7. For example, DynDOLODx64 on my system would be:J:\Skyrim Special Edition Tools\DynDOLOD Alpha 39\DynDOLODx64.exe
    1. Run through steps 4-6 for DynDOLODx64.exe, TexGenx64.exe, LODGenx64.exe, and Cathedral_Assets_Optimizer.exe. Do the same for the copies of Texconvx64.exe in your ...\DynDOLOD\Edit Scripts and ...\xLODGen\Edit Scripts folders.
    2. Add a folder exclusion for your MO2 folder and your Tools folder(s). It's the same steps as above, but choose 'Folder' instead of 'Process'.
    3. Add a file type exclusion for .nif