A quick word
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.
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:
- Load Steam.
- In the toolbar at the top of the window, click Steam.
- In the dropdown menu, click Settings.
- Then in the popup box select the In-Game menu item.
- 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:
- Load Steam.
- Click LIBRARY.
- In your games list, look for The Elder Scrolls V: Skyrim Special Edition and right-click on it.
- In the dropdown menu, click Properties.
- 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:
- In STEAM, right click on The Elder Scrolls V: Skyrim Special Edition.
- In the menu that appears, click on Properties.
- In the popup window, select the Updates tab.
- In the selection box under "Automatic Updates", select "Only update this game when I launch it".
- 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.
- Click Options.
- Click the Ultra button.
- Set Aspect Ratio and Resolution in the drop-down box. These should be set to your monitors' optimal resolution.
- Set Antialiasing to Off in the drop-down box. This is in preparation for the ENB Install.
- Ensure that Windowed Mode is unchecked.
- Click the OK button to close and save.

Click the Ultra button.
Set the Aspect Ratio and Resolutions to your monitors' optimal settings.
Set Antialiasing to Off.
Ensure Windowed Mode is unchecked.
Creation Kit
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.
- Download and install the Bethesda.net Launcher.
- Run the Launcher and sign in (create an account if you don't have one).
- In the left pane, expand options to show "All Games" via >>
- Select "Creation Kit: Skyrim" and select "Install"
- After completion of the installation, click on "Play"
- Select "Yes" in the "Script Source Extraction" box
- Close the Creation Kit program.
There are a few edits that need to be made before you can use the CK to port mods.
- Download the premade CreationKitCustom.ini here
- 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.
Tools
7-Zip
LOOT
LOOT is a utility for load order optimization and is critical for any modded Skyrim run, especially with a list as long as ours.
FOMOD Instructions - Loot Configuration
- LOOT, on first load, has no Masterlist data or default mod groups. (Colored Text indicates the colour of the node (default).
- Shut down Mod Organizer 2, if open.
- Run LOOT from its installed location.
- 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.
-
- 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.)
- Locate and click on the Options button in the top right corner (identified by 3 dots over each other).
- Open Groups Editor
- In the Add New Group box, type Trivial Smelters of Skyrim, then the plus button.
- Left-click the Late Loaders node to select it.
- Left-click and drag a line from Late Loaders to the Trivial Smelters of Skyrim node that you created. Trivial Smelters of Skyrim should turn green.
- Create a new group called MLU Patches
- Connect Trivial Smelters of Skyrim to MLU Patches node that you created. MLU Patches should turn green.
- Create a new group called Merge Patches
- Connect MLU Patches to Merge Patches node that you created. Merge Patches should turn green.
- Create a new group called iWant Patches
- Connect Merge Patches to iWant Patches node that you created. iWant Patches should turn green.
- Create a new group called NPC Retextures
- Connect iWant Patches to NPC Retextures NPC Retextures should turn green.
- Create a new group called Consistency Patches
- Connect NPC Retextures to Consistency Patches Consistency Patches should turn green.
- Create a new group called Conflict Resolution
- Connect Consistency Patches to Conflict Resolution Conflict Resolution should turn green.
- Connect Conflict Resolution to Leveled List Modifiers Conflict Resolution should turn grey.
- Create a new group called Arthmoor's Villages
- Connect Low Priority Overrides to Arthmoor's Villages Arthmoor's Villages should turn green.
- Connect Arthmoor's Villages to High Priority Overrides Arthmoor's Villages should turn grey.
- Verify all of the newly added groups are showing as grey. Press Apply to exit this interface.
xEdit
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.
- Right-click on any plugin.
- From the popup menu navigate, to Other→Options; a new popup box should appear.
- Uncheck Simple Records LAND, NAVI, NAVM, CELL, WRLD (requires restart).
- Click OK.
- Exit SSEEdit.
Mators xEdit Patching Framework
MXPF is an xEdit scripting library that provides a variety of functions for the generation of patches.
- 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.
TES5EditScripts
Bunch of useful xEdit Scripts.
- 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
This is a script that will help clean up Windsongs Immersive Character Overhaul.
- 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.
Cathedral Assets Optimizer
Cathedral Assets Optimizer is a tool aiming to automate asset conversion and optimization for Skyrim Special Edition.
- Download these premade profiles.
- Extract the contents to your Cathedral Assets Optimizer/Profiles directory.
Wrye Bash
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.
- Download the file manually.
- 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.
- 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.
Script Extenders
Skyrim Script Extender
SKSE is absolutely essential. It extends the scripting capacity of the game to allow mods to do things that would not normally be doable in the base Skyrim Engine. Many Mods depend upon it.
- Install ONLY the following files in the main Skyrim Special Edition directory:
skse64_1_5_97.dll skse64_loader.exe skse64_steam_loader.dll
zEdit Modules
zEdit allows for the application of patches to large portions of the game in a single location, without having to run individual xEdit scripts in multiple sessions of xEdit. The following modules are installed now, but will not be used until the Finishing Line portion of the guide. Again, pay attention to the special installation instructions, as failure to install them correctly will mean they are not available when they are needed.
Experience Mod zEdit Patcher
This mod adds compatibility to Experience so the kills function will work on all NPCs.
- Extract into the modules subdirectory of zEdit.
UPF No Dragon LODs Patcher
This mod applies the No Dragon LODs effect.
- Extract into the modules subdirectory of zEdit.
UPF Khajiit Ears Show Patcher
This mod will allow all Khajiit to show their ears when wearing helmets.
- Extract into the modules subdirectory of zEdit.
Microsoft Visual C++ Redistributable
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.
Installing Mod Organizer 2
Install Mod Organizer 2:
- On first run of MO2 Windows may give you a warning that Windows Defender doesn't recgonise the App and has prevented it from running.
- Click More info and click Run anyway
- You may then be presented with a User Account Control warning Clcik Yes.
- You should be able to install MO2 like any normal program.
- Pick a location to install MO2 outside of Program Files.
- Once install launch MO2.
- at Create new insance page make sure you select Create a Portable Insance.
- In the next pop-up that appears, select Skyrim Special Edition.
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.
- 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.
- 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).
- At the top of the window that appears, press on the Nexus tab.
- Click on the Connect to Nexus button.
- 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.
- In the Mod Organizer 2 settings menu, press OK.
Some users may find the default MO2 theme overly bright or harsh.
- 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).
- At the top of the window that appears, press on the General tab (if not already selected).
- In the upper right corner of the Settings window, locate the Theme 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' or 'Paper Dark' themes.
- After selecting a theme, press OK to close the window.
- In the pop-up window that appears, allow Mod Organizer 2 to restart to apply the theme change.
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.
- Locate and press the Configure Profiles button (most MO2 themes show this as an icon that looks like an ID card, but can vary).
- In the Profiles Window, select Create.
- In the pop-up, type Vanilla Skyrim SE.
- Ensure that the Default Game INI Settings checkbox is unchecked.
- Select OK.
- Verify that Vanilla Skyrim SE appears in the list on the left.
- Verify that the Use profile-specific Save Games is checked.
- Verify that the Use profile-specific Game INI Files is checked.
- Click on and highlight the Default profile.
- Click on Remove.
- In the pop-up that appears, select Yes.
- Exit the Profiles Window by pressing Close.
- Verify that Vanilla Skyrim SE appears as the selected profile (shown above the mod list aka "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.
Special Instructions:
xEdit, Wrye Bash, and zEdit need to be setup with Mod Organizer 2.
- Locate and press the Executables button (most MO2 themes show this as an icon that looks like a gear, but can vary).
- A Pop-up box should appear press the + (Add an executable) button.
- In the Pop-up box select "Add from file.."
- In the Windows folder that opens, navigate to and double-click on SSEEdit.exe in its installed location.
- Ensure no optional checkboxes are checked.
- Select "apply" at the bottom right of the pop-up.
- 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 of plugin files, and will be explained further later in the guide.
- In the Argument field of "SSEEdit – Quick Auto Clean" add -Dontcache
- Repeat steps 2 through 5 for Wrye Bash and zEdit, selecting the appropriate executable file in each case. No arguments are needed for these entries.
- After all programs have been added, click on "Okay" on the bottom right of the Modify Executable window.
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 Skryim DLC will place them in an incorrect order.
- In the left pane, drag-and-drop the three DLC files into the following order (top-to-bottom): Dawnguard, HearthFires, Dragonborn.
The loading order of Skyrim DLC is incorrect and needs to be correctly sorted.
- From the drop-down Executables list (right-side, above the plugins list), select LOOT.
- Press the Run button.
- 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.
- 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. See the notice below for an explanation of these two terms.
- Click Apply to accept LOOT's generated load order. If no changes were made (which happens on occasion), the Apply button may not appear. This is normal, and of no concern.
- 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 few things to note.
- 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 profile specific save game is checked on each new profile.
- 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.
New profile for Lexy’s LOTD:SE
- 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).
SKSE is not fully installed.
- Ensure that the newly created "Legacy" profile is selected at the top of the left pane in Mod Organizer 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).
- In the window that opens, navigate to the location of the SKSE file downloaded earlier. Click on it to highlight it.
- Click on Open.
- 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.
- 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.
- In the file tree, navigate to and highlight the Data folder inside the archive.
- Right-click on Data.
- 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.
- 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 - neither are required, but if you wish to fill these in, you can do so.
SKSE does not have a version number or category set.
- Right-click SKSE Scripts (or as appropriate).
- In the right-click menu, select Information.... Alternately, you can also double-click the mod name to achieve this as well.
- In the Categories tab, locate and place a checkmark next to Utilities.
- In the NEXUS Info tab, set the version number to the installed version of SKSE (as annotated in the SKSE download earlier).
- 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).
- Click Close to save and exit the window.
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.
- 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.
- 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.
-
- Run Skyrim:SE by using the SKSE Executable in MO2.
- 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.
- In the console that opens, type getskseversion and press enter.
- 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.
- Exit Skyrim.
Mod Organizer 2 Plugins
Merge Plugins Hide
This is a plugin for Mod Organizer 2 that allows you to hide merged plugins easily.
- Extract the contents of the archive to your Mod Organizer 2 plugins directory.
- Load Mod Organizer 2 and press the screwdriver and spanner icon.
- Navigate to the Plugins tab.
- Scroll down until you find Merge Plugins Hide.
- In the right-hand box change hide type to optional.
- Click OK.
Clean 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. Note that the below process is universal to this process, and will not be repeated for other mods that require cleaning.
Cleaning Instructions:
Create a backup of the original files.
- Navigate to ...\Skyrim Special Edition\Data.
- 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.
- Start Mod Organizer 2, if not already running.
- 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.
- Press Run.
- 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.
- Click OK.
- xEdit will now run the cleaning process automatically.
- Wait for the process to complete, indicated by the appearance of the message Quick Clean Mode finished.
- When the message has appeared, close xEdit by clicking on the X in the title bar of the application ("X-ing out").
- Repeat steps 2 through 8 for Dawnguard.esm, Hearthfires.esm and Dragonborn.esm.
Dawnguard.esm requires manual xEdit cleaning in addition to the Automated cleaning:
- From the drop-down executables menu, select SSEEdit. Ensure this is the xEdit version without Quick Auto Clean.
- Press Run.
- In the plugin selection window, right click.
- In the right-click menu, select Select None.
- Place a check mark in the box next to Dawnguard.esm.
- Select OK. Dawnguard will now be loaded into xEdit, along with any other required files.
- After all plugins are fully loaded, click on the "+" next to Dawnguard.esm. Its file tree will expand.
- Locate and press the "+" next to Cell. Its sub-records will appear.
- Locate and press the "+" next to Block 5. Its sub-records will appear.
- Locate and pres the "+" next to Sub-Block 3. Its sub-records will appear.
- Locate and click on 00016BCF. The right pane will now display all records associated with this cell record.
- In the right pane, scroll down and locate the XEZN sub-record that refers to RiftenRatwayZone [ECZN:0009FBB9.]
- Right click on the above record in the "Dawnguard.esm" column and select Remove. A window may appear warning you that you are making a change to the file – when able, allow the change.
- Do the same for Block 2 -> Sub-Block 1 -> 0001FA4C CWGuardTempates (the entire record).
- Block 8 -> Sub-Block 1 (the entire sub-block).
- 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.
- In your ...Mod Organizer 2\mods folder, create a new folder called Cleaned Vanilla ESMs.
- In the Skryim\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.
- Cut and Paste the backup files you created earlier into the Skyrim\data folder.
- Start Mod Organizer 2 (if not already active).
- A new mod should appear called "Cleaned Vanilla ESMs". If it does not appear, Right-Click -> All Mods -> Refresh.
- 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
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.
- Run BethINI.exe outside of MO2 and make sure MO2 is closed or changes won't take effect!
- Under the Setup tab:
- Select the profile you wish to use via the INI Path setting.
- Make sure the Modify Custom INIs option is unchecked.
- Under the Basic tab:
- Click the DEFAULT button. This will refresh your INI files to the default settings for your system, with minimal tweaks.
- Click the HIGH preset.
- Make sure the BethINI Presets option is checked.
- Make sure Recommended Tweaks is checked.
- Make sure Windowed Mode is checked.
- Make sure Borderless is checked.
- Make sure FXAA is Unchecked.
- Make sure Antialiasing is set to NONE.
- Make sure VSync is unchecked.
- Make sure Lock Frame Rate is unchecked.
- Under the General tab:
- Make sure Intro Logos is unchecked.
- Make sure Post-Load Update Time is 2000
- Under the Gameplay tab:
- Make sure Over-Encumbered Reminder is set to 60
- Make sure NPC Use Ammo is checked.
- Make sure 1st Person Arrow Tilt-up Angle is 0.7
- Make sure 3rd Person Arrow Tilt-up Angle is 0.7
- Make sure 1st Person Bolt Tilt-up Angle is 0.7
- Under the Interface tab:
- Make sure Bethesda Modding Platform is unchecked.
- Make sure Mouse Settings → Lock Sensitivity is 0.0125
- Under the Detail tab:
- Make sure Field of View is set to 85.00
- Make sure Particles is set to 2000
- Make sure Depth of Field is checked.
- Make sure Lens Flare is unchecked.
- Make sure Reflect Sky is checked.
- Make sure Ambient Occlusion is Unchecked.
- Make sure Shadow Resolution is set to 2048
- Make sure Shadow Bias is set to 0.47
- Make sure Sun-Shadow Transition is Unchecked.
- Under the View Distance tab:
- Make sure Grass Fade is set to 18000
- Under the Visuals tab:
- Make sure Grass Density is set to 60
- Make sure Grass Diversity is set to 15
- Make sure Improved Shader is unchecked.
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):
Skyrim.ini
[SaveGame] bDisableAutoSave=1 bAllowScriptedForceSave=0 bAllowScriptedAutosave=0
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 placed in the Legacy Of The Dragonborn - Special Edition profile that you will use to actually play the game.
SKSE.ini
Before you can edit the SKSE.ini file, you will have to create it.
- Right-click SKSE Scripts in the Mod Organizer mod list.
- Select Open In Explorer.
- Create and enter a folder named SKSE.
- Create and open a text file named SKSE.ini. Make sure you are showing hidden file extensions.
Once this file is open to be edited, paste in the following:
[General] ClearInvalidRegistrations=1 [Display] iTintTextureResolution=2048
This enables self-healing of rogue updating scripts in saves.
Save and close SKSE.ini then exit explorer.
xLODGEN
xLODGEN
This is a utility used to generate LOD meshes and textures "exactly" like the CK.
- Download the main xLODGen-71 archive.
- 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.
- Create a folder called SSELODGen_Output At the ROOT of a drive.
- Once the above is done, open Mod Organizer 2 and add xLODGenx64.exe as an executable.
- In the Arguments field enter -sse -o:"Drive Letter:\SSELODGen_Output"
DynDOLOD
DynDOLOD Standalone
This is a utility used to create a mod based on the load order, which adds custom, distant LOD for objects to Skyrim.
- Download the archive file.
- Extract the contents to a new folder called DynDOLOD Special Edition.
- Once the above is done, open Mod Organizer 2 and add TexGenx64 and DynDOLODx64 as executables.
- In the Arguments field, enter -sse for each executable.
zMerge Setup
In this section you will set up zMerge so that you can create merged mods later on.
- Open zEdit and select zMerge from the drop-down menu.
- Press Start Session.
- Click on the cog in the upper-right corner and a new popup box should appear.
- Navigate to Integration Settings.
- Under Mod Manager select Mod Organizer 2.
- Under MO2 Instance select Portable.
- Under Mod manager path, fill in the file path to your main Mod Organizer 2 folder.
- Under Mod manager mods path, fill in the file path to your Mod Organizer 2 mods folder.
- Navigate to Merge Settings.
- Under Merge output path fill in the file path to where your Mod Organizer 2 mods folder is.
- Uncheck Disable plugins.
- Navigate to Archive Creation Settings.
- Under Advanced change Minimum files per archive to 999999.
- Under Advanced make sure Create texture archives is unchecked.
- Click OK.
- You can now close zMerge.
Check these pictures on how to set up zMerge if you're having trouble.
ENB Series
ENB Series Binaries
This is a graphics modification library designed to allow gamers to configure their games to their liking.
- At the bottom of the page, click the link for the specified version.
- At the bottom of the new page, click the download link.
- 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.
- Place the d3d11.dll and d3dcompiler_46e.dll into the main Skyrim Special Edition directory.
ENB PRESET
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] bEnableImprovedSnow=0 fGamma=1.0000 bFXAAEnabled=0 - (you can keep to 1 if you prefer, choose only TAA or FXAA) bUseTAA=0 - (you can keep to 1 if you prefers, choose only TAA or FXAA) bIBLFEnable=0 bIndEnable=0 bSAO_CS_Enable=0 bSAOEnable=0 bTreesReceiveShadows=1 bDrawLandShadows=1 bShadowsOnGrass=1 bUse64bitsHDRRenderTarget=1 bVolumetricLightingEnable=1 iVolumetricLightingQuality=2
Setting up HDMI Full Range:
A Special Step is required for users that connect their GPU and Monitor Via a 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 grayed 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 the AMD Catalyst.