Follow the system setup guide. The system setup guide ensures that all game files are fresh and prompts you to create a basic modding folder structure to install tools into. This guide uses the folder structure from the system setup guide in its instructions. Users that deviates from the system setup guide needs to be aware of this and adjust the instructions accordingly to their installation and modding paths.
Folder structure
c:\
└── Modding\
│
└── Tools\
...Steam\
│
└──steamapps\
│
└──common\
│
└──Skyrim Special Edition\
│
└──Data\
Common folders referred to in this guide
After following the system setup guide you will have a clean installation of Skyrim and the following tools installed and configured:
When you install DynDOLOD, choose DynDOLOD 3.00. None of the main files are needed at this point.
Complete the system setup by installing the following tools:
The Creation Kit is needed to convert plugins made for Skyrim to work with Skyrim Special Edition. The conversion is very simple and basically just means to open a plugin in the creation kit and re-save it. The link above goes to the Bethesda Launcher install file. Installation of the Creation Kit will be done using the Bethesda Launcher.
Create a new text file in the main game folder and name it CreationKitCustom.ini. Paste the following into the file:
[Audio]
bEnableAudio=1
[Grass]
bAllowCreateGrass=1
bAllowLoadGrass=0
[General]
bAllowMultipleMasterFiles=1
bAllowMultipleMasterLoads=1
[MESSAGES]
bBlockMessageBoxes=1
[Archive]
SResourceArchiveList2=Skyrim - Voices_en0.bsa, Skyrim - Textures0.bsa, Skyrim - Textures1.bsa, Skyrim - Textures2.bsa, Skyrim - Textures3.bsa, Skyrim - Textures4.bsa, Skyrim - Textures5.bsa, Skyrim - Textures6.bsa, Skyrim - Textures7.bsa, Skyrim - Textures8.bsa, Skyrim - Patch.bsa, Dawnguard.bsa, Hearthfires.bsa, Dragonborn.bsa
Download and extract the contents to the main game folder.
Install vc_redist.x86.exe and vc_redist.x64.exe.
This is a script for SSEEdit. Unzip the archive and place the content in the SSEEdit script folder (i.e. ..Modding/Tools/xEdit/Scripts/).
To prevent output files generated by tools ending up in Mod Organizer’s overwrite folder, thus mixing with other files you might want to keep track of, it is advised to create empty mod listings in Mod Organizer for these types of files.
Create a separator to keep things tidy:
Create the output data folders:
Repeat the steps, creating the following mod listings:
Some tools can be set to output data to these mod listings while other tools output data will have to be manually moved after each run. The tools that can output data directly into the output folders will be configured to do so in the next section.
All tools except BethINI should be launched through Mod Organizer. Mod Organizer may have auto-detected some tools but you need to confirm this and manually add the rest of the tools.
Instructions to add tools as executables
Repeat the steps for the executables listed below, filling in the appropriate data. The titles are suggestions. Users that deviate from the recommended install paths need to adjust the arguments accordingly.
Tools
Note that you need to check that the paths in the given arguments are valid for your install paths.
BethINI needs to be run for the current profile in Mord Organizer and ran to establish the INI’s before beginning the mod installations.
Close Mod Organizer and run BethINI if it isn’t open already.
Use the following settings:
Basic tab
In the presets section:
Use the following settings:
View Distance tab
Custom Tab
On the Basic tab, click the Save and Exit button.