Skyrim Initial Setup (GOG) An infernalryan Skyrim Modding Guide
Overview This guide will provide instructions for the initial setup of Skyrim, including installation, downgrading to a previous (more supported) version, and preventing automatic updates. I will also cover how to bring the most recent game files (e.g. 'masters') and Creation Club content over to a downgraded build, as well as essential mod installations, whether you choose to use a Wabbajack mod pack, prefer the manual approach, or a combination of both. These steps may vary slightly from those you may have seen before, but they will provide arguably the best possible initial setup to support your modding journey.
This guide is for SSE/AE for GOG. For the Steam version of this guide, click here. For the Skyrim VR version of this guide, click here.
While every attempt was made to keep this guide short and to the point, I have added additional context to some of the steps where I felt appropriate, and there may be information, and/or steps/sections which may not apply to your specific case. This has resulted in the guide growing larger than anticipated, but do not be overwhelmed! I have added spoiler tags where possible, and steps that may not apply have been noted and can be skipped entirely.
Guide Contents:
Install Skyrim (and/or update to latest version) and prevent updates
Prepare Creation Club content files and set them aside
(Optional) Perform a downgrade by downloading and installing your preferred version
Final setup including Mod Manager selection and installation of updated masters, CC content, and/or other essential and optional mods
Run the game and verify SKSE is running
Further reading including compatibility notes and other helpful information
Soft copy is also available for download from the files tab. Please consider ENDORSING if you found this guide helpful!
In this guide, there are several references to your ' <Skyrim game folder>' as well as your Skyrim ' /Data' folder. These folders refer to your specific Skyrim installation folder and its /Data folder inside. For example, if you install Skyrim into the C:\Games\GOG folder, your <Skyrim game folder> would refer to C:\Games\GOG\Skyrim Anniversary Edition, and the /Data folder would refer to C:\Games\GOG\Skyrim Anniversary Edition\Data (NOTE – your folders may look slightly different).
In GOG Galaxy, if you have enabled integration with Steam and/or Epic Games, and also own Skyrim on one of those platforms, you may have issues performing any Skyrim game related operations described in this guide (such as installing, downgrading, etc). This is because the integration system is buggy and only one "instance" of each game can be present (even if you own it on more than one platform), which may prevent you from installing the GOG version of the game. The recommendation here is to disable the integration(s) for these platforms altogether.
1 Install Skyrim First things first, Skyrim needs to be installed. By default, GOG Galaxy installs all games into C:\Program Files (x86)\GOG Galaxy\Games. DO NOT DO THIS! If Skyrim is currently installed here, you will have to move it.
IMPORTANT NOTE – Never install Skyrim into the C:\Program Files (x86) or C:\Program Files folders! Many mods and plugins cannot function when games are installed here and/or may cause crashes as they are system protected folders. Skyrim must be moved from here to prevent these issues.
1.1 Install latest version Although it seems counter-intuitive to "downgrading", we must first install/update Skyrim to the latest version (1.6.1179 at the time of writing this guide) for some files and assets to be used later. Follow only one of the two options and their associated step(s) below (expand their respective 'Spoiler' tag).
1.1.1 Option 1: New installation For new installations, follow the steps below to perform the install using the GOG Galaxy application. While it is possible to install this manually via the offline backup game installers from GOG, using that method will not allow for actions such as downgrading, which this guide takes full advantage of to provide the most compatible version(s) of Skyrim for modding. This guide does not provide support for installations performed in that way.
Spoiler:
Show
In GOG Galaxy, select your Skyrim game.
Click the 'Install' button at the top of the window.
On the installation screen, be sure your 'Install to' field points to a folder outside of Program Files.
Uncheck the 'Keep this game up to date automatically' button.
Click 'Install'.
1.1.2 Option 2: Existing installation For existing installations, there are a couple of steps you want to complete before proceeding.
Spoiler:
Show
1.1.2.1 Purge mods (Vortex) Skip to section 1.1.2.2 if you have never previously used Vortex Mod Manager, otherwise, if it is still installed, you will need to check to ensure the program does not have any mods deployed to the GOG Skyrim folder. If it does, this could cause Vortex to complain that changes were made outside of the program the next time you open it, requiring you to manually resolve each issue. Note – this is NOT the same as trying to manage separate instances of Vortex for Steam and GOG. This is specifically pertaining to whether or not you have previously managed Skyrim for GOG with Vortex in the past.
Open Vortex.
Ensure Skyrim SSE is the active managed game – This is found under the 'Games' tab. If it is not, hover over the Skyrim Special Edition game and click the 'Activate' button.
Navigate to the 'Mods' tab.
Click the 'Purge Mods' link in the top toolbar.
Spoiler:
Show
If you are still having issues, or receive an error that indicates issues already existed prior to starting this guide, you may simply need to stop managing the game via Vortex. Do this by navigating to the 'Games' tab, clicking the 3 vertical dots on the Skyrim Special Edition game, and selecting 'Stop Managing'. If you are STILL having issues, you may simply need to uninstall Vortex altogether.
1.1.2.2 Move Skyrim out of Program Files folder Skip to section 1.1.2.3 if Skyrim is not installed here, otherwise, you will need to move it (you don't need to perform a complete uninstall). To do this perform the following:
Close GOG Galaxy.
Move your Skyrim GOG installation folder to the desired destination (alternatively, you can use cut and paste).
When files are done moving, open GOG Galaxy.
Select your Skyrim game.
From the 'More' menu (next to 'Install'), select 'Manage installation > Import folder'.
In the 'Select a directory to import' folder selection dialog, browse to the new location of your installation folder and click 'Select Folder'.
You're done!
1.1.2.3 Delete existing files
Open your root <Skyrim game folder> (this can be done via the 'More' menu > 'Manage installation' > 'Show folder' selection.
Delete all files and folders in here. This will ensure any renamed files, custom .dlls, etc., from previous modding activities which may affect the game and/or its ability to open on the current version are removed, and all files are 100% reset back to stock.
1.2 Configure installation The steps below will ensure the latest version is selected and available DLC is downloaded.
In GOG Galaxy, select your Skyrim game.
From the 'More' menu (next to 'Install'), select 'Manage installation > Configure…'.
On the dialog that opens, under the 'Installation' tab, be sure 'Auto-updates' is unchecked, and select the latest version (0.1.3905696 at the time of writing this guide, which is actually version 1.6.1179). NOTE - As of 2024, Version 1.6.659 is no longer available for download/downgrade on GOG. The image below is for reference only.
Click the 'DLC' tab.
Ensure the 'The Elder Scrolls V: Skyrim Anniversary Upgrade' option is checked, if available (requires the Anniversary Upgrade purchase). Even if you have zero intention whatsoever of using this CC content now, I recommend downloading these and managing the files with your Mod Manager of choice in case you change your mind later.
Click 'OK'.
1.3 Verify files Skip to section 2 if you performed a clean install and Skyrim was NOT previously installed, otherwise, we need to ensure files are redownloaded if your previous version did not change.
In GOG Galaxy, select your Skyrim game.
From the 'More' menu (next to 'Play'), select 'Manage installation > Verify / Repair'.
Wait for the game to complete verification, it will show an 'Updating X%' indicator in the top of the window. Hovering over this will show the status.
2 Prepare Creation Club content Since Creation Club mods are technically officially packaged/endorsed Bethesda mods, they will pre-install themselves directly in the Skyrim /Data folder. This makes them unmanageable from Mod Managers. We will change that.
Spoiler:
Show
The Anniversary Edition was released in November of 2021, and as a free upgrade to existing Skyrim Special Edition owners, it provides 4 DLC mods (Survival Mode, Saints and Seducers, Rare Curios, and Fishing). Additionally, it has an optional paid DLC upgrade (referred to as the Anniversary Upgrade) which contains 70 community mods. The Anniversary Upgrade is purchasable on its own, or together with Skyrim Special Edition in a bundle called "The Elder Scrolls V: Skyrim Anniversary Edition". When referring to the 'Anniversary Upgrade', I am referring to this paid DLC content, regardless of how it was purchased.
2.1 Move Creation Club content files These are the free and paid Creation Club files that we will be saving for later. If you purchased the Anniversary Upgrade, these files should have already been downloaded in our previous section 1.2 as part of our installation configuration steps.
Open your Skyrim /Data folder.
Create a folder inside /Data called 'CC Content'.
Move all ccXXXsse0XX-filename.xxx files (.bsa, .esl, .esm) inside /Data into this new 'CC Content' folder (example: ccBGSSSE001-Fish.bsa)
The folder should now contain all 4 free DLC mods (.esm, .esl, and .bsa) as well all mods contained in the Anniversary Upgrade (if applicable).
3 (Optional) Perform a downgrade Skip to section 4 if you do NOT want to perform a downgrade (and just want to stick with current version 1.6.1179), otherwise proceed. "Downgrading" refers to the process of reverting the Skyrim game version to an earlier one. This was once common practice, particularly when many mods had not yet been updated to support newer game versions, but given the current level of mod support for the latest version, downgrading is now less necessary.
As of 2024, 1.6.659 is no longer available for download/downgrade on GOG. This includes download of offline backup game installers, making this version officially no longer supported by GOG. Since version 0.0.3895161 was erroneous (due to game version number), downgrade is currently not possible for the GOG version of Skyrim. This section will remain in this guide for reference purposes in the event downgrading becomes possible again, but for now, skip to section 4.
Refer to the list below for information on the most commonly referenced versions of Skyrim to further help you decide on a preferred version. Note that when following this guide we will be using newest game masters and CC content ("best of both worlds"), so preference should come down to whether or not there are any specific user mod(s) that are incompatible with your selected version. Check out the amazing SKSE Plugin Status list for plugin compatibility with the version of Skyrim you want to run – for GOG, compatibility should be at or near 100% similar to versions 1.6.640 (GOG 1.6.659) and 1.6.1170 (GOG 1.6.1179).
Skyrim version list:
Spoiler:
Show
1.6.659.0.8 (1.6.659) (AE Pre-Creations) Released 09/28/2022 – This is the GOG equivalent of version 1.6.640. This is the final 'stable' release of AE prior to the Creations update. It had the most time to bake and receive new mods/mod updates, so is the current de-facto recommended AE version. This version is no longer available on GOG.
0.0.3895161 (1.6.1170) (erroneous) Released 01/15/2024, this is equivalent to version 1.6.1170, but was later replaced with 0.1.3905696 (1.6.1179) to give the GOG version its own unique version number. You can safely ignore this version.
0.1.3905696 (1.6.1179) (AE Post-Creations) Released 01/26/2024 – This is the GOG equivalent of version 1.6.1170 (1.6.1130 or equivalent was skipped). This version introduced the Creations update for GOG. It also fixed some bugs in master files, but you don't need this game version to use them (we saved the masters earlier). 1.6.1179 is the current version as of the writing of this guide. It is still relatively new and generally NOT recommended unless you are specifically interested in the Creations themselves. There are currently many outstanding bugs with mods that have not been made compatible with these versions.
Downgrade instructions (Reference only - Currently not possible) Expand the 'Spoiler' tag below for downgrade instructions. GOG downgrades are extremely simple to perform.
Spoiler:
Show
3.1 Prepare master game files Whether you plan to run version 1.6.659 or a more recent version of Skyrim, you will want to use the latest game files (.esm, .esl, .bsa) to ensure maximum compatibility with newer mods (i.e., "best of both worlds"). These are essentially mod files themselves, so even older versions of Skyrim have no issues running them (there is a small–but extremely important–exception with the plugin version which we will get to in section 4 (Final setup) below), so no matter which version of Skyrim you ultimately choose, we will want to save these files for later.
Spoiler:
Show
While more prominent for earlier versions of Skyrim which are not available to GOG, some popular mods require these updated files due to referencing records only found in newer versions of them (and not the 1.5.97 versions, for example), which could cause issues and/or CTDs if they are not found. Two such examples of popular mods doing this are JK's Castle Dour and JK's Sinderion's Field Laboratory, which both use a record from a recent version of update.esm which does not exist in the 1.5.97 files, making the mods incompatible with a base 1.5.97 install. To get around this, we will later copy these updated master files into our Mod Manager along with applicable AE Creation Club content. This also makes compatibility with mods such as USSEP much easier. This is what is effectively known as the "best of both worlds" (using an older Skyrim game version with the latest master files + CC content). This is still an important consideration for GOG versions.
3.1.1 Move master files
Open your Skyrim /Data folder.
Create a folder inside /Data called 'Skyrim Updated Masters'
Move the following files in the /Data folder into this new 'Skyrim Updated Masters' folder.
_ResourcePack.bsa
_ResourcePack.esl
Dawnguard.esm
Dragonborn.esm
HearthFires.esm
Skyrim - Animations.bsa
Skyrim - Interface.bsa
Skyrim - Meshes0.bsa
Skyrim - Meshes1.bsa
Skyrim - Misc.bsa
Skyrim - Shaders.bsa
Skyrim - Sounds.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 - Voices_en0.bsa
Skyrim.esm
Update.esm
Move any applicable additional language voice packs into this folder as well from the below list, otherwise, leave them be.
Skyrim - Voices_de0.bsa (German)
Skyrim - Voices_es0.bsa (Spanish)
Skyrim - Voices_fr0.bsa (French)
Skyrim - Voices_it0.bsa (Italian)
Skyrim - Voices_ja0.bsa (Japanese)
Skyrim - Voices_pl0.bsa (Polish)
Skyrim - Voices_ru0.bsa (Russian)
NOTE – There are files intentionally left out the lists above, so leave those in /Data.
3.2 Delete existing Skyrim game files Before downloading, the first step is to remove (most of) the files from the main game folder. This is because that version is still the current version, and we need to replace it with our preferred downgraded version.
Open the main <Skyrim game folder>.
Open the /Data folder.
Delete all files and folders EXCEPT the following folders we created earlier:
/Skyrim Updated Masters
/CC Content
Go back to the main <Skyrim game folder>.
Delete all files and folders EXCEPT the /Data folder (which should only contain the two folders above).
3.3 Download and install files The Skyrim game version is selected from the installation configuration menu within GOG. This process is outlined below.
In GOG Galaxy, select your Skyrim game.
From the 'More' menu (next to 'Install'), select 'Manage installation > Configure…'.
On the dialog that opens, under the 'Installation' tab, select your preferred version. You may have to click the 'Show more versions' text to expand the list. NOTE - As of 2024, Version 1.6.659 is no longer available for download/downgrade on GOG. The image below is for reference only.
In the 'DLC' tab, uncheck 'The Elder Scrolls V: Skyrim Anniversary Upgrade' if you purchased the Anniversary Upgrade and it was previously checked (we already set this content aside so don't need to redownload it).
Click 'OK'.
Your selected version will download.
3.4 Remove (re-)downloaded CC content When the downgrade/rollback is performed, all free Creation Club content will be redownloaded (as well as paid CC content if you did not uncheck the option in the previous step). We will need to delete these files since we will be managing this content via our Mod Manager using the files we already backed up.
Open the /Data folder.
Delete all ccXXXsse0XX-filename.xxx files (.bsa, .esl, .esm) inside this folder (example: ccBGSSSE001-Fish.bsa)
4 Final setup Your Skyrim game folder is now ready, but before you start modding, you will need to install and/or verify the following essential mods with your Mod Manager. See below.
IMPORTANT NOTE – Whether you plan to use a pre-built Wabbajack mod pack, manually download and install mods, or a combination of both, to ensure maximum compatibility with newer mods, you will need to download and install the Backported Extended ESL Support plugin. Failure to install this and/or lack of inclusion in your Wabbajack mod pack WILL RESULT IN A CTD at game launch. DO NOT SKIP THIS. These steps are found later in this section.
4.1 Install Mod Manager Skip to section 4.2 if you intend to use a Wabbajack mod pack since this will typically come pre-built with a portable version of Mod Organizer 2 (so this decision will have been made for you). For everyone else, the two options are Vortex and Mod Organizer 2. Nexus Mod Manager (NMM) has been sunset and is no longer supported, so do NOT attempt to use that with modern Skyrim modding. If you need help deciding between Vortex and MO2, there are several threads on this on the internet. Personally, I prefer MO2, and believe that what appears initially to be a steeper learning curve inevitably reveals itself to be a bit more intuitive overall, especially for larger mod lists, with the main benefit being you can keep your /Data folder (and root folders with Root Builder) completely free of files and/or links. Ultimately this is up to you, and my guides will support both applications. Install your Mod Manager of preference and then proceed.
Spoiler:
Show
Your Nexus account should be connected to your installed Mod Manager. Additionally, all steps below assume Nexus downloads (nxm links) have been associated with the program so that mods are automatically downloaded to the proper folder when using the 'Mod Manager Download' buttons on nexusmods.com. This should be automatic following installation, but if this association changes, MO2 will ask at startup, and Vortex will reclaim this automatically. Follow your chosen Mod Manager's installation guide for more information on either topic above.
4.1.1 Install Root Builder for MO2 Skip to section 4.2 if NOT using MO2. Unlike Vortex, MO2 does not have the native ability to manage files in the <Skyrim game folder>, only the /Data folder. This functionality is provided by the Root Builder plugin, allowing you to leave the entire <Skyrim game folder> in "pristine, vanilla condition!", and the steps to set it up are quite simple. All the remaining steps for MO2 in this guide assume this is installed. Follow the instructions below by expanding the 'Spoiler' tag.
Spoiler:
Show
Download the latest version from the main mod page 'FILES' tab – ensure you click the 'MANUAL DOWNLOAD' link (this will not install with your Mod Manager).
When completed, open this file from your web browser downloads folder (it is a .zip file).
Extract the contents of the file into the /plugins folder of your MO2 folder. For example, if you installed MO2 into 'C:\Modding\MO2', extract this to 'C:\Modding\MO2\plugins'.
If done correctly, you should now have a 'rootbuilder' folder inside of /plugins (example: 'C:\Modding\MO2\plugins\rootbuilder').
Close MO2 if it is open.
Re-open MO2.
Verify this is installed correctly by navigating to the 'Tools > Tool Plugins' menu of the main menu bar. You should now see a 'Root Builder' entry.
You are done!
4.2 Install core mods Before you start adding your own mods to your mod list, you will want to set up core mods which will serve as the foundation for any future mods added. For Wabbajack, this is an entire mod list which you can later build off of, whereas if you are looking to create your mod list manually from scratch, there are several mods which should be installed first. Follow only one of the two options and their associated step(s) below (expand their respective 'Spoiler' tag).
4.2.1 Option 1: Wabbajack mod pack If using Wabbajack, simply download the Wabbajack modlist file, open it with Wabbajack for download, and follow any specific instructions on the mod pack page to configure. Be sure the mod pack is compatible with your selected game version. Skip to section 4.3 when done.
4.2.2 Option 2: Custom mod list Follow the instructions below to download the listed mods for the specific version(s) of Skyrim you are running. Only the recommended game versions are listed here, so you will have to visit the main mod page for versions not listed to download, if applicable.
Spoiler:
Show
4.2.2.1 Skyrim Script Extender (SKSE) SKSE is installed differently depending on the Mod Manager chosen. In general, we are doing the same thing for each: downloading, enabling, and then telling the Mod Manager to launch Skyrim with the SKSE launcher when we run the game. Follow only one of the two options based on your Mod Manager of choice (expand their respective 'Spoiler' tag).
Click the 'Start Download' button on the following page after clicking the link above to download into your Mod Manager.
This will automatically install and enable SKSE. In addition, it will also automatically set the primary launch tool as SKSE.
Restart Vortex (exit and re-open). This will remove the notification that SKSE is not installed and the visual bug that does not show SKSE as the primary launch tool.
Deploy mods by clicking the 'Deploy Mods' button in the main toolbar at the top of the application.
Click the 'Start Download' button on the following page after clicking the link above to download into your Mod Manager.
Double-click the file in the 'Downloads' tab in MO2 to install – When installing, you will be informed that ' The content of <data> does not look valid.'.
If the tutorial pops up, feel free to read through this if this is your first time or just exit by clicking the 'Exit Tutorial' box.
In the 'Install Mods' dialog, expand both the ' skse64_x_xx_xx' and ' Data' folders, then right-click the ' Data' folder and select 'Create directory…'.
Name the directory 'root' (without quotes).
Drag the ' skse64_x_x_xx.dll' and ' skse64_loader.exe' files into the ' root' folder you just created.
Next, right-click the ' Data' folder and select 'Set as <data> directory'.
Your 'Install Mods' window should now look something like this (with ' root' expanded)
Click the 'OK' button.
Enable the mod by clicking the checkbox to the left of the mod name in the mod list on the left side of the main MO2 window.
Next, click the executables dropdown (next to the 'Run' button), which by default should either say 'Skyrim Special Edition', and select '<Edit...>'.
On the dialog that opens, if this list on the left already contains an entry for 'SKSE' (or similar, which it may by default), you can optionally change the name to something like 'Play Game (SKSE)'. Ensure both the 'Force load libraries (*)' and 'Use application's icon for desktop shortcuts' checkboxes are selected, click 'OK'. and Skip to section 4.2.2.2.
If the entry does not exist, click the '+' icon on the left and select 'Add empty…' (we have to do this because the SKSE loader file does not exist in your game folder, instead it is managed by Root Builder).
For 'Title', give this a name like 'Play Game (SKSE)'.
Click the '...' button in the 'Start in' row and select your root <Skyrim game folder>.
In the 'Binary' field, use this same path followed by ' \skse64_loader.exe', for example, ' C:\Games\GOG\Skyrim Anniversary Edition\skse64_loader.exe'.
Select both the 'Force load libraries (*)' and 'Use application's icon for desktop shortcuts' checkboxes.
Optionally, click the green 'up' arrow in the left list to bring this entry to the top.
Your screen should look something like this (with your actual paths).
Click 'OK'.
4.2.2.2 Address Library This process is the same for both Vortex and MO2, and should download automatically into your Mod Manager.
Download the latest version of ' All in one Address Library (Anniversary Edition)' from the main mod page 'FILES' tab using the 'MOD MANAGER DOWNLOAD' button. This should be the second file on the page and is for all versions of 1.6.
Install and enable the mod (Vortex should do both automatically, but confirm).
Deploy mods (Vortex only).
4.2.2.3 SSE Engine Fixes Skip to section 4.3 if you do not wish to install this. While not required, this mod fixes a lot of game bugs and additionally allows achievements when mods are enabled, which most people want. This mod is installed differently depending on the Mod Manager chosen. Follow only one of the two options based on your Mod Manager of choice (expand their respective 'Spoiler' tag).
Click the 'Start Download' button on the following page after clicking the link above to download into your Mod Manager.
Enable the mod if it does not do so automatically.
Download part 2 – All versions (this is NOT a Mod Manager download)
Click the 'Start Download' button on the following page after clicking the link above to download into your download folder
Open your web browser downloads folder.
Drag the ' (Part 2) Engine Fixes - skse64 Preloader and TBB Lib-xxxxx.7z' file into the 'Drop File(s)' section of Vortex, which is found at the bottom of the 'Mods' tab.
Enable the mod if it does not do so automatically.
Double-click the ' (Part 2) Engine Fixes - skse64 Preloader and TBB Lib' entry in the list to open its properties panel.
Under the 'Mod Type' dropdown, select 'Engine Injector' – This will install the mod into the root <Skyrim game folder> (instead of the /Data folder).
Click the 'Start Download' button on the following page after clicking the link above to download into your Mod Manager.
Double-click the file in the 'Downloads' tab in MO2 to install.
Enable the mod by clicking the checkbox to the left of the mod name in the mod list on the left side of the MO2 window.
Download part 2 – All versions (this is NOT a Mod Manager download)
Click the 'Start Download' button on the following page after clicking the link above to download into your download folder
Open your web browser downloads folder.
Drag the ' (Part 2) Engine Fixes - skse64 Preloader and TBB Lib-xxxxx.7z' file into the 'Downloads' tab of MO2, which is on the right side of the main MO2 window.
Double-click the file in the 'Downloads' tab in MO2 to install – When installing, you will be informed that ' The content of <data> does not look valid.'.
Right-click the '<data>' folder and select 'Create Directory…'.
Name the directory 'root' (without quotes).
Drag the ' d3dx9_42.dll', ' tbb.dll', and ' tbbmalloc.dll' files into the ' root' folder you just created.
Your 'Install Mods' window should now look something like this (with ' root' expanded).
Click the 'OK' button.
Click the 'Ignore' button on the prompt that comes up (don't worry, this will work).
Enable the mod by clicking the checkbox to the left of the mod name in the mod list on the left side of the main MO2 window.
Finally, right-click the mod name in the mod list and select 'Ignore missing data' – Since we are using Root Builder, and no ' Data' folder was set during install, MO2 will complain about this, even though it is configured properly. Performing this step will fix that.
4.3 Install Backported Extended ESL Support If you have downgraded to a game version lower/older than 1.6.1130, you must install this mod (or ensure your Wabbajack mod pack has it installed, if you went that route) otherwise you will suffer an immediate CTD when launching the game.
Download the latest version from the main mod page 'FILES' tab using the 'MOD MANAGER DOWNLOAD' button. Be sure to press any 'DOWNLOAD' buttons on the following page if the mod does not start downloading automatically.
For Wabbajack users, if you receive an error in your Mod Manager indicating the file already exists when downloading, you can safely assume this is already installed and can skip (re-)installing this mod. Skip to section 4.4.
For everyone else, Install and enable this mod.
Deploy mods (Vortex only).
4.4 Install prepared masters Skip to section 4.5 if you did not perform a downgrade, otherwise, in these next steps we will be adding the masters and CC content that we prepared earlier. Follow only one of the two options based on your Mod Manager of choice (expand their respective 'Spoiler' tag).
4.4.1 Option 1: Vortex
Spoiler:
Show
Open your game folder by clicking the 'Open…' button in the main application taskbar, and select 'Open Game Folder'.
When inside the main <Skyrim game folder>, open the /Data folder. In addition to other files, you should see the following folder we created earlier:
/Skyrim Updated Masters
Drag the ' Skyrim Updated Masters' folder into the 'Drop File(s)' section of Vortex, which is found at the bottom of the 'Mods' tab. This may take several minutes to fully import as the file size for this folder is quite large. Watch the notification area in the top right of Vortex to see when completed. Since the mod contains multiple plugins, when asked whether you'd like to enable these, select 'Enable all'.
This will create a mod for the dragged folder and add it to your list. Additionally, this appends a .7z extension to your mod name and actually creates an archive (which we will delete later).
Double-click the ' Skyrim Updated Masters' entry in the list to open its properties panel.
Remove the '.7z' from the name and/or rename it entirely (based on your preference) and change the 'Source' to 'User-Generated' (to get rid of the warning icon).
If you want to to delete the .7z files automatically generated when dragging and dropping these folders (they are not required and are needlessly taking up space), navigate to ' %appdata%\Vortex\downloads\skyrimse' (without quotes – you can paste this in an explorer window, the Windows Win+R Run dialog, or the start menu search bar) and delete the following file:
Skyrim Updated Masters.7z
Skip to section 4.5 when done.
4.4.2 Option 2: Mod Organizer 2
Spoiler:
Show
From the folder dropdown icon at the top right of the mod list window within MO2 (next to the 'wrench' dropdown), select 'Open Mods folder'.
Move this folder aside for a moment.
From the same folder dropdown icon in MO2 select 'Open Game Folder'.
When inside the main game folder, open the /Data folder. In addition to other files, you should see the following folder we created earlier:
/Skyrim Updated Masters
MOVE the above folder into the mods folder we opened in the previous step.
When finished, select MO2 to ensure it is the active window and hit the 'F5' button on your keyboard. This will refresh the application and display our new folder added at the bottom of the mod list on the left.
Enable the mod by clicking the checkbox to the left of the mod name in the mod list on the left side of the main MO2 window.
Feel free to move the mod higher in the list to better organize it with your other mods. There should not be any mods overwriting any of the files in this mod, so just ensure it is below the 'DLC: Dawnguard' entry at the top of the mod list.
4.5 Install prepared Creation Club content Next we will be adding the Creation Club content that we prepared earlier. There are several options on how to perform this listed below in the order of most to least recommended. Follow only one of the options and their associated step(s) below, based on your preference (expand their respective 'Spoiler' tag).
IMPORTANT NOTE – If using Wabbajack, determining what Creation Club content to bring over will depend 100% on the requirements of the mod pack itself. Since I cannot account for all possibilities, be sure to enable ONLY the content which the Wabbajack pack requires in the steps below.
Spoiler:
Show
If Creation Club files are left in the Skyrim /Data folder, they cannot be enabled or disabled with your Mod Manager at all. Even if you copy the files directly into a "mod" that can be managed by your Mod Manager, many (but not all) of the Creation Club mods cannot simply be toggled on and off in the plugin list for some reason. Mod Organizer 2 can get around this by allowing you to 'hide' and 'unhide' files themselves in the mod's 'Filetree' list, but Vortex has no native ability to do so. This requires Vortex users to either delete files which cannot be toggled off or manually copy each mod to its own respective mod entry in the 'Mods' tab. There are 70 Anniversary Upgrade mods alone, so this is both tedious and even confusing given it must be done by filename, which may not be intuitive. It is for this reason that following the steps in this section is (highly) recommended. The final option below will allow you to keep these mods unmanaged, if desired.
4.5.1 Option 1: Curation Club plugin (MO2 only) The Curation Club plugin will separate all Creation Club content into their own individual mods within MO2 automatically with a single click so that you can easily toggle them on or off, depending on preference. This option is for MO2 users only since it is a plugin specifically for that application. NOTE – This plugin requires MO2 version 2.5 or greater so will not work on version 2.4.4 or below.
Spoiler:
Show
4.5.1.1 Install Curation Club for MO2 Skip to section 4.5.1.2 if the Curation Club plugin is already installed, otherwise, proceed with the steps below.
Download the latest version from the main mod page 'FILES' tab – ensure you click the 'MANUAL DOWNLOAD' link (this will not install with your Mod Manager).
NOTE – Ignore the message on the mod page stating the plugin does not work, I have tested this prior to posting instructions.
When completed, open this file from your web browser downloads folder (it is a .zip file).
Extract the contents of the file into the /plugins folder of your MO2 folder. For example, if you installed MO2 into ' C:\Modding\MO2', extract this to ' C:\Modding\MO2\plugins'.
If done correctly, you should now have a ' curationclub' folder inside of /plugins (example: ' C:\Modding\MO2\plugins\curationclub').
Close MO2 if it is open.
Re-open MO2.
Verify this is installed correctly by navigating to the 'Tools > Tool Plugins' menu of the main menu bar (you can also click the "puzzle" icon in the main icon bar). You should now see a 'Curation Club' entry.
You are done!
4.5.1.2 Run Curation Club
Open the Skyrim /Data folder.
Open the ' CC Content' folder inside.
MOVE all files in this folder back to the Skyrim /Data folder (cut and paste may be easier).
DELETE the ' CC Content' folder when finished.
Click the 'Curation Club' entry from the 'Tools > Tool Plugins' menu of the main menu bar (you can also click the "puzzle" icon in the main icon bar).
The following window should be shown:
NOTE – There are no manifest files for GOG so the ‘Root Builder Support’ option can be ignored altogether.
Click the 'OK' button. It may appear the program is frozen but give it a few seconds to complete.
You should now see individual entries in your mod list for all 4 free DLC mods as well all mods contained in the Anniversary Upgrade (if applicable).
These can be moved higher in your mod list in MO2 to organize them better with your other mods.
Optionally, you can organize these with separators. For example:
Creation Club Content - Free DLC
Creation Club - Fishing
Creation Club - Rare Curios
Creation Club - Saints & Seducers
Creation Club - Survival Mode
Creation Club Content - Anniversary Upgrade
All other CC mods
Enable any/all of these mods that you would like to use by clicking the checkbox to the left of the mod name in the mod list on the left side of the main MO2 window.
4.5.2 Option 2: AE Creation Club File Organizer This is a PowerShell script that I wrote which provides the exact same functionality as the Curation Club plugin, but does not require MO2 (which means Vortex users can also use it). It works on a file and folder level (rather than a mod level within your Mod Manager), so should never break as a result of future Mod Manager and/or Skyrim game updates.
Spoiler:
Show
4.5.2.1 Download and install scripts
Download the latest version from the main mod page 'FILES' tab – ensure you click the 'MANUAL DOWNLOAD' link (this will not install with your Mod Manager).
NOTE – Ignore the Installation and Usage instructions on the page as we are covering those here.
Extract the files to your Skyrim /Data folder.
4.5.2.2 Open PowerShell and run the script In order to execute the script, we have to launch PowerShell a certain way to ensure we bypass the system's execution policy (otherwise the script will not run). This will affect the current instance only, so when PowerShell is closed, the current system policy will be reinforced again.
Open your Skyrim /Data folder (the scripts should already be in here).
Click on the address bar at the top. This will highlight the location (yours may be different).
With the folder highlighted, type ' powershell -ExecutionPolicy Bypass' to replace the text and hit enter.
This will open PowerShell directly in this folder.
Type the following and hit enter:
.\ae_creation_club_file_organizer.ps1
NOTE – you can simply type 'ae' and then press the 'TAB' key until the .ps1 file above is shown.
You will be prompted with this screen:
If you are OK to proceed, type 'Y' (or just hit 'Enter'). This will start processing the files.
If you are using Steam, and the Anniversary Upgrade manifest files are detected, you will be prompted with the following:
Enter your preferred selection from the list of options. This will determine your mod folder setup depending on the Mod Manager you are using. Once you enter your selection, the script will continue to process.
When finished, the script should show the following (your output may differ slightly depending on the number of files moved and/or manifest file selection):
Close PowerShell.
Open the Skyrim ' .\Data\CC Content' folder that was just created. You should now see a list of applicable folders for the mods detected by the script (see example image below):
Keep this folder open and move it aside for a moment.
4.5.2.3 Import mods into Mod Manager The next step is to import these folders into your Mod Manager. Follow only one of the two options based on your Mod Manager of choice (expand their respective 'Spoiler' tag).
4.5.2.3.1 Option 1: Vortex
Spoiler:
Show
Open your mod staging folder by clicking the 'Open…' button in the main application taskbar, and select 'Open Mod Staging Folder'.
From the ' CC Content' folder we set aside in the previous section, COPY (or MOVE) ALL folders into the mod staging folder.
Note – Do NOT drag these files/folders into the "Drop File(s)" section of the Vortex application as this could modify our intentional file structure of the mods in a way that makes them unusable (this is the case when opting to manage the .manifest files). Additionally, dragging a folder into Vortex also automatically creates a .7z file which unnecessarily takes up space.
Close Vortex.
Re-open Vortex.
When opening, you will be prompted with the following message (example image below, your prompt may differ depending on the name of your mods):
Click the 'Apply Changes' button.
In the 'Mod Name' field of the mod list, type 'Creation Club'. This should filter your list to show the mods we just imported (they are all currently disabled).
Double-click the first entry in the list to open its properties panel and make the following updates.
IMPORTANT – If manifest files were found when running the script and you selected option 2 (Manage them with Vortex), you MUST change the 'Mod Type' in the properties list to 'Engine Injector'. This will ensure the mod is installed in your main Skyrim game folder, rather than the /Data folder, otherwise, these mods will not load properly.
Optionally change the 'Source' to 'User-Generated' (to get rid of the warning icon in the list).
Repeat this process of updating properties for ALL files you imported. Don't worry, although tedious, you only have to do this once. If you are not managing manifest files you can effectively skip the above step entirely as long as you don't mind seeing the warning icon.
Enable any/all of your preferred CC mods in Vortex.
If you were previously managing any Creation Club content with Vortex, disable and/or delete those mod(s) now since the process we performed will completely replace the old mod(s) (assuming they were included for processing with the script).
You can now delete the ' CC Content' folder from your Skyrim /Data folder. If you moved the files in the previous section, the folder should be empty. If you copied all files (rather than moving them), you can optionally keep this folder as a backup for all of your CC content.
Skip to section 4.6 when done.
4.5.2.3.2 Option 2: Mod Organizer 2
Spoiler:
Show
From the folder dropdown icon at the top right of the mod list window within MO2 (next to the 'wrench' dropdown), select 'Open Mods folder'.
From the ' CC Content' folder we set aside in the previous section, COPY (or MOVE) ALL folders into the mods folder.
When finished, select MO2 to ensure it is the active window and hit the 'F5' button on your keyboard. This will refresh the application and display our new folders added at the bottom of the mod list on the left.
Feel free to move the mods higher in the list to better organize with your other mods. There shouldn't be any other mods conflicting if you did not have these files previously.
Optionally, you can organize these with separators. For example:
Creation Club Content - Free DLC
Creation Club - Fishing
Creation Club - Rare Curios
Creation Club - Saints & Seducers
Creation Club - Survival Mode
Creation Club Content - Anniversary Upgrade
All other CC mods
Enable any/all of your preferred CC mods by clicking the checkbox to the left of the mod name in the mod list on the left side of the main MO2 window.
If you were previously managing any Creation Club content with MO2, disable and/or delete those mod(s) now since the process we performed will completely replace the old mod(s) (assuming they were included for processing with the script).
You can now delete the ' CC Content' folder from your Skyrim /Data folder. If you moved the files in the previous section, the folder should be empty. If you copied all files (rather than moving them), you can optionally keep this folder as a backup for all of your CC content.
Skip to section 4.6 when done.
4.5.3 Option 3: Anniversary Edition Content Picker mod This mod provides an easy-to-use FOMOD installer with names and descriptions for each Creation Club mod, allowing you to easily decide which mod(s) you want to actually install and use. The only downside here is that you cannot simply enable and disable mods at will, you have to re-run the installer to select which content you’d like. This comes with a little bit less granularity than the above options, and also requires an additional 3.5GB of space (with all Anniversary Upgrade content) since a copy of the files also needs to remain in the.zip file/installer so that the reinstall can be re-run at another time. That said, if you have the space, the inline descriptions can be of huge benefit when selecting which content to enable.
Spoiler:
Show
4.5.3.1 Prepare mod installation files This mod is special in that you need to unpack it, add files to it, then repack it before it can be installed. The steps below provide instructions for this process.
Download the latest version of 'Anniversary Edition Content Picker' from the main mod page 'FILES' tab – ensure you click the 'MANUAL DOWNLOAD' link (this will not install with your Mod Manager).
Extract the files to a temporary location (e.g., ' C:\temp').
MOVE the ' CC Content' folder from the steps above to this temporary folder. The folder should already contain its own ' CC Content' folder, so you are just adding your files to it.
Select all 3 folders within the temporary folder. These folders are:
CC Content
fomod
Images
With the folders selected, re-compress into a .zip file.
This can be done using a 3rd party tool (such as 7zip, Winrar, etc.) or by the 'Send to > Compressed (zipped) folder' option in the default Windows right-click context menu. Be sure to (re-)name the file ' Anniversary Edition Content Picker.zip'.
Move this folder aside for a moment.
4.5.3.2 Install the mod Follow only one of the two options based on your Mod Manager of choice (expand their respective 'Spoiler' tag).
4.5.3.2.1 Option 1: Vortex
Spoiler:
Show
Drag the ' Anniversary Edition Content Picker.zip' file from the above temporary folder into the 'Drop File(s)' section of Vortex, which is found at the bottom of the 'Mods' tab. NOTE – This may take several minutes to fully import as the file size for this mod is quite large.
The FOMOD installer should automatically open when the file is done importing.
Proceed through the FOMOD installer and select all of the content you wish to use.
When completed, double-click the 'Anniversary Edition Content Picker.zip' entry in the list to open its properties panel.
Remove the '.zip' from the name and change the 'Source' to 'User-Generated' (to get rid of the warning icon).
Ensure the mod is enabled (Vortex should auto-enable this after installation).
You can now completely remove the temporary folder you created earlier (e.g., ' C:\temp').
NOTE – You can always reinstall this mod if your requirements change at any time by right-clicking the mod in the mod list, and selecting 'Reinstall' to re-run the FOMOD installer and re-select which CC content you wish to enable/disable, so your current selections are not permanent.
Skip to section 4.6 when done.
4.5.3.2.2 Option 2: Mod Organizer 2
Spoiler:
Show
Drag the ' Anniversary Edition Content Picker.zip' file from the above temporary folder into the 'Downloads' tab on the right side of the main MO2 window. NOTE – This may take a minute to copy as the file size for this mod is quite large.
Double-click the file in the 'Downloads' tab in MO2 to install. The FOMOD installer should open.
Proceed through the FOMOD installer and select all of the content you wish to use.
When done, it may take a minute to extract/copy all of the selected mod files.
Enable the mod by clicking the checkbox to the left of the mod name in the mod list on the left side of the MO2 window.
You can now completely remove the temporary folder you created earlier (e.g., ' C:\temp').
NOTE – You can always reinstall this mod if your requirements change at any time by right-clicking the mod in the mod list, and selecting 'Reinstall Mod' to re-run the FOMOD installer and re-select which CC content you wish to enable/disable, so your current selections are not permanent.
Be sure you do NOT delete the ' Anniversary Edition Content Picker.zip' file from the 'Downloads' tab of the main MO2 window, otherwise you won't be able to perform the reinstall later.
Skip to section 4.6 when done.
4.5.4 Option 4: Do not manage with Mod Manager If you do not wish to manage these files with your Mod Manager (and keep them all enabled), follow the steps below. You can always choose to perform one of the other options above at a later time.
Spoiler:
Show
Open the Skyrim /Data folder.
Open the ' CC Content' folder inside.
MOVE all files in this folder back to the Skyrim /Data folder (cut and paste may be easier).
DELETE the ' CC Content' folder when finished.
4.6 Installing Unofficial Patches The following patches are recommended due to the number of mods which also require them as masters, however, these require some consideration depending on the game version and/or CC content options you have chosen above. If you decide to install these, follow the steps below.
4.6.1 Unofficial Skyrim Special Edition Patch (USSEP) Skip to section 4.6.2 if using a Wabbajack mod pack as the proper version should have already been included in your mod pack. For everyone else, see below for download links for your specific setup requirements.
Spoiler:
Show
The issue with this mod is that only the latest version is available on the mod page on Nexus at any given time. While this is fine for us since we have carried over the updated master files (which the latest version of the mod requires), the problem occurs if you have disabled ANY of the 4 free AE Creation Club DLC content (since this mod requires those 4 mods as masters). If you have done this, you CAN NOT use the latest version, and instead need to use version 4.2.5b, which was the last version released which does not require these DLC as masters.
If Survival mode, Fishing, Rare Curios, AND Saints & Seducers are ALL enabled, download the latest version from the main mod page 'FILES' tab. Be sure to press any 'DOWNLOAD' buttons on the following page if the mod does not start downloading automatically. Our updated masters ensure the patches in this mod are all valid for us, despite the game version requirements listed.
4.6.2 Unofficial Creation Club Patches Skip to section 4.7 if you do NOT own the Anniversary Upgrade, or are using a Wabbajack mod pack, as the proper version(s) should have already been included, if applicable. For everyone else, see below for download links for your specific setup requirements.
Spoiler:
Show
This mod fixes many bugs with the Anniversary Upgrade Creation Club content, and has a few other mods which use it as masters. The issue is that as of version 7.8, this mod has converted to an all-in-one model (single plugin). If you have disabled ANY of the Anniversary Upgrade CC content, using the all-in-one version will result in missing master(s), and likely CTDs. To get around this, you will need to instead download version 7.7, which has a FOMOD installer allowing you to select individual plugins for each CC content mod, enabling fixes for only the mods you have installed. The downside to this is that version 7.7 will receive no further updates from the mod author.
If you did NOT disable any AE CC content (all mods enabled) – Download the latest version from the main mod page 'FILES' tab using the 'MOD MANAGER DOWNLOAD' button. Be sure to press any 'DOWNLOAD' buttons on the following page if the mod does not start downloading automatically.
If you DID disable some CC content, Download this version instead (7.7) – This version contains multiple plugins and a FOMOD installer to select which patches to apply.
4.7 Additional Mods The mods below are recommended but optional, and should all simply need to be downloaded via Mod Manager links and installed/activated unless otherwise noted. This is by no means an extensive list, but those listed are typically seen as 'essential' mods and/or bug fixes. Be sure to check the mod requirements before downloading and installing, and install their prerequisite(s) where applicable. Some of these may or may not be included with all Wabbajack packs.
Achievements Mods Enabler – Not required since SSE Engine Fixes has been updated for GOG 1.6.1179 and above. Still listed for those that do not wish to use Engine Fixes. Does not require xSHADOWMANx’s Dll Loader since SKSE is installed.
SkyUI – Elegant, PC-friendly interface mod with many advanced features. There are other alternatives out there (such as Dear Diary and Nordic UI to name a couple) but SkyUI provides the most compatibility with other mods out of the box.
Quest Journal Fix for SkyUI (1.6.1179+ only) – Fixes the issue with GOG 1.6.1179 and above that prevents the difficulty setting from saving in the SkyUI menu. Includes patches for many other UI mods as well.
TrueHUD – HUD additions, including customizable actor info bars, boss bars, player widget, and recent loot log. Be sure to check mod requirements.
True Directional Movement – Overhauls the third person gameplay similarly to modern action RPGs. Move and attack in any direction. Includes a custom target lock component and an animated target reticle widget, target headtracking, projectile aim support during target lock, mount support and more! Be sure to check mod requirements.
Improved Camera – Improved Camera enables the 1st person body and allows for typically forced 3rd person animations also to be played in 1st person.
Scrambled Bugs – A collection of engine bug fixes and patches.
Dual Casting Fix – Fixes a vanilla bug which causes the game to treat dual cast spells as if they were single cast. Requires Visual C++ Redistributable.
BethINI Pie – This is a tool, rather than a mod, that makes editing INI configuration files simple via a graphical user interface. In particular you can apply recommended "Tweaks" which can in some cases drastically improve game performance. SPECIAL NOTE – if using MO2, special action is required. You will need to add this as an executable in a similar fashion that we did in section 4.2.2.1.2 with SKSE, and launch it from within MO2 itself. This will ensure that even if the 'Use profile-specific Game INI Files' option is checked under your current profile, you are modifying the correct .ini file.
4.8 Download latest Microsoft Visual C++ Redistributable Many mods (including SSE Engine Fixes, which we installed earlier) require this, so you will want to ensure you have the latest redistributable installed. This is a windows installer so is not something even a Wabbajack install can provide for you automatically.
At the time of writing this guide, the current redistributable is for 'Visual Studio 2015, 2017, 2019, and 2022'.
Scroll down to the 'Latest Microsoft Visual C++ Redistributable Version' section, and follow the link for your specific version – This is likely the x64 build.
Download and install.
5 Run the game! After all of this prep work, you're finally ready to test launching the game from your Mod Manager. We will launch the game and verify SKSE is working.
5.1 Launch Skyrim Note that when using Mod Managers, you MUST launch the game via their respective SKSE loader location. This is how you will launch the game each and every time you wish to play (with mods). Follow only one of the two options based on your Mod Manager of choice (expand their respective 'Spoiler' tag).
5.1.1 Option 1: Vortex
Spoiler:
Show
Open Vortex if it is not already open.
Deploy mods (if any changes have been made since the last time you performed this).
Launch the game via the 'play' button icon in the main SSE graphic at the top of the Vortex Application.
Skip to section 5.2 when done.
5.1.2 Option 2: Mod Organizer 2
Spoiler:
Show
Open MO2 if it is not already open.
Select the SKSE executable you set up in previous steps (or that came with your Wabbajack installation) from the executables dropdown list. Example:
Click the 'Run' button.
5.2 Verify SKSE is running Once in the game, you will need to make sure SKSE is loaded properly. If it is not, you will need to revisit the steps above to ensure you are launching with the SKSE launcher, and additionally review steps in section 4.2.2.1.2 for MO2 users to ensure folders have been set up correctly for Root Builder. Follow the steps below.
At the Skyrim main menu (or in-game if you've started or loaded a game), press the tilde ('~') key to open the console – This key is typically directly to the left of the '1' key, although this may be missing on custom/small form-factor keyboards and accessible only with a function key combination – See your specific keyboard documentation for more info).
With the console open, type 'getskseversion' (without quotes) and press <Enter>.
This should show the SKSE version number if you've done everything correctly up to this point.
NOTE - REMEMBER THIS VERSION OF SKSE! While this should be visible in your Mod Manager (under the 'Version' column), this is the version which may be referred to by other mods when noting their compatibility (example, "Compatible with SKSE 2.0.20"). You don't have to commit this to memory, just remember where to find it before grabbing additional mods which require SKSE to prevent crashes.
Exit the console by pressing the tilde ('~') key again, and quit Skyrim. If you are stuck in the opening carriage ride (and cannot open the main menu), you can open the console again and type 'qqq' (without quotes) and press <Enter> to exit the game.
Skyrim is now ready for modding!
6 Further reading See below for some last minute information and recommendations before proceeding with your modding setup.
6.1 Compatibility and troubleshooting I have created a separate guide on compatibility and troubleshooting which covers many topics to help you prevent, identify, and fix common problems. I recommend reading this at some point to gain a better understanding of possible issues you may encounter through the course of your playthrough.
6.2 Have fun! Lastly, be sure to have fun! Many people consider modding Skyrim a game in itself, and spend more time modding Skyrim than playing Skyrim. Just remember that many countless hours have been put into creating the mods you are downloading, so taking a second to ENDORSE those mods really goes a long way. You can do this easily within your Mod Manager with selected mods (via a 'thumbs up' icon in Vortex, or by right-clicking and selecting 'Endorse' in MO2).
6.3 Other Guides See my guides page on Nexus for other helpful Skyrim modding guides.
6.4 Changelog See below for changes made to this document.
Version 1.17.10 (01/28/2025)
Updated section 3 and some image text descriptions with modified version/downgrade information since downgrading is no longer possible
Updated section 3.1.1 to also include _ResourcePack.bsa and _ResourcePack.esl for consistency with other guides, even though downgrade is no longer possible, since updated versions of USSEP and LOTD now require this (thanks @davemcknz, @Schinkennudel, and @ddsonic28 for bringing this to my attention)
Version 1.13.2 (04/27/2024)
Fixed section 4.5.1.2 subtext which affected Nexus article only
Version 1.10.5 (04/24/2024)
Added list of all options into each applicable section for soft copy version for easier navigation as there are no spoiler tags available for use
Rewrote Creation Club content sections to be more streamlined and included additional content picker options
Updated Vortex images
Other minor corrections and formatting changes
Version 1.9.3.2 (04/13/2024)
Fixed version number in .pdf footers
Version 1.9.2 (04/11/2024)
Updated info surrounded SSE Engine Fixes since this mod has been updated to work with versions 1.6.1179 and above.
Version 1.6.4 (04/04/2024)
Revamped guide to better explain and support 1.6.1179+ versions by making downgrade optional, reorganizing sections to accommodate, and providing additional disclaimer information
Slightly increased default font size for article readability
Other minor corrections and formatting changes
Added changelog
Version 1.5 (03/20/2024)
Initial release
Please leave a comment with any issues or suggestions!
Guide updates required: Below are some items that will require guide updates. I am listing them here for reference and will remove them when the guide is updated.
Downgrading
GOG no longer supports downgrade to 1.6.659 through the GOG Galaxy application or the offline installers found on the website. If you already have this version, you can continue using it, but users will no longer be able to use this version moving forward. - Updated in version 1.17.10
Popular Mod Updates
USSEP and LOTD now require _ResourcePack.esl and _Resourcepack.bsa master files. If you intend on using either of these mods and are downgrading, you will need to also ensure you keep these files when following the process to upgrade Skyrim game masters. Thanks @davemcknz, @Schinkennudel, and @ddsonic28 for this info. - Updated in version 1.17.10
Mod versions
Since it's been asked multiple times, I will add additional notes to the initial setup guides for those users that have downgraded on what versions of mods are supported. For example, all creation kits should be fine (if masters are updated), but SKSE mods will need to stick with the specific game version.
Please let me know in comments below if there are any other updates that are required.
So far, this is extremely helpful. I'm at the point of downgrading to 1.6.640 - but my configure pane in GoG does not have any versions but 0.1.3905696 and 0.0.3895161 and also does not have an option for "Show more versions". So I'm rather at a standstill - and having got this far, being on limited data since I have only satellite for connection, I'm unsure just what I should do at this point.
I hope you can help me get unconfused!
[Oh, I did check to see if GoG Galaxy had had an update I didn't know about; unfortunately, no - so I'm on the latest current version.]
Apologies as I posted this under main page comments. I have a guide update coming - recently (last month) GOG removed older versions so downgrading is no longer possible. If you currently a downgraded version, you won't be forced to upgrade, however, new users are stuck with 1.6.1179. I will sticky that in this thread until the guide update is done.
Ah, I see! Makes sense then. Well.... since that's the case, I'll just go back to square one! That didn't even occur to me. I'll wait for the new guide, thanks!
To be clear, the update to the guide would (among other unrelated things) simply remove the section for picking what version you want. Just use 0.1.3905696 (which is game version 1.6.1179) and proceed. If you want to use a different version (like 1.6.640 which was previously available) you will unfortunately have to use the Steam version, which is a totally separate license/key than GOG.
I very much enjoyed following this guide, simple to follow and informative. I'm already tracking the main page for updates, which I'm also looking forward to. Thank you!
100% true, however, Vortex and MO2 are far more popular than Wrye Bash, likely because they're arguably easier to use are generally more preferred for their modern, user-friendly interfaces. I've used Wrye Bash before and is by far my (personal) least favorite mod manager. I still use it for bashed patches, though. I was actually considering including steps for WB in my guides but I wanted to prioritize getting information out rather than having to (re-)train myself how to use the program.
I followed your instructions to the letter. I got to the stage where you say to run SKSE and I did so. But nothing happened. Thinking back to the first time I modded Fallout 4, I ran the game through GOG first, quit the game and tried again. And it worked.
Sort of.
Spoiler:
Show
MCM Helper is required by TrueHUD in your list of recommended mods. Have I perhaps installed the wrong version?
And then there is this:
Spoiler:
Show
Any thoughts as to what I may have done to cause this?
Your guide is fantastic and endorsed. These issues have most likely arisen due to my own stupidity, but any insights you could provide would be greatly appreciated.
First question is what version of Skyrim are you are running? 1.6.659 or 1.6.1179? If you are running 1.6.659 but are using 1.6.1179 masters (as recommended in the guide), then you can ignore the LOOT message (that is likely going off of your game version, but the mod itself relies on the .esm masters from 1.6.1179 which you should be using if you followed the guide).
Also, same question for SKSE -- if it is complaining about game version you may be using a mismatched version of the plugin for GOG, just make sure you have the right plugin for the version you are using. These are outlined in step 4.2.2.1.1:
I have actually managed to get it working and I figured LOOT was just crying about the about the version, even though I am using the downgraded version with the 1.6.1179 masters.
I accidentally skipped over the Backported Extended ESL support. When I went through that bit it seemed to resolve my issues.
I do have a question though. If I am using 1.6.659, but I am using the masters from 1.6.1179 does that mean I could theoretically use mods for either version?
As an example, I am trying install PapyrisUtil SE and I am using the GOG version but Vortex states it is incompatible with the current version of the game. Am I out of luck or am I doing something wrong?
Modding Skyrim seems a bit more complicated than Fallout 4, which is the game that really got me into the modding scene.
You can use ANY creation kit mods (.esm/.esp/.esl) when you do the "best of both worlds" downgrade, etc., but .dll type plugins (SKSE, for example) are all based on the game executable version of the game. This means if you are using 1.6.659 you can ONLY use .dll type plugins compatible with this version.
FYI there is a version of PapyrisUtil SE for the version of GOG you are using in the 'OLD FILES' section. Version 4.4 for GOG:
FOR THE GOG VERSION OF SKYRIM ONLY
Version 4.4 for SKSE 2.2.3, Skyrim 1.6.659(GOG) , & Address Library
An amazing guide, easy to follow, simple to use. However, I am currently at stage 4.5.2 and I seem to have run into an issue I can't seem to solve.
I followed the instruction as written regarding powershell, but it doesn't seem to have converted all of the files? The guide states that after Powershell is run, all I should be left with in my CC Content folder is mod folders and I did indeed have four folders. Fishing, Rare Curios, Saints and Seducers and Survival.
But I still have a lot of "loose" files left in my folder with names like "Wraithguard", "BeAFarmer" and "BA_Orcish" all with either the .esl, .esm or .bsa suffix.
Am I being incredibly dense and missing something or might I have encountered a separate issue?
PS I bought my Skyrim Anniversary Edition today from GOG.
EDIT: I attempted method 4.5.3 but Vortex is giving me an "Installer reported errors" message. I'm at a loss...
can you paste the output of the powershell script? if you run the revert script file it will put files back into their normal locations, then re-run the standard script and paste the output in a reply here. i wrote that script so should be able to troubleshoot.
First of all, thanks for the detailed howto, it is much appreciated.
However, the GOG version with MO2 and downgrade does not work: the skse64loader can not find the "bink2w64.dll" nor the "Galaxy64.dll". (I click manually to root build, then run skseloader, when I click MO2's play, it simply doesn't do anything apparently.) I have neither of those dlls: the first is Steam-related, the second is issued by GOG as I guess.
Can you help, and/or elaborate on the article? :)
Which is amazing, but still: I did everything according to that, but no success...
I click manually to root build, then run skseloader, when I click MO2's play, it simply doesn't do anything apparently
I'm not sure what you mean. The bink2w64.dll is not a Steam-related file, it is a Skyrim required file. I verified this process before publishing. Just want to make sure you didn't stray from the guide in some way.
So basically I have followed every step thorougly: installed the newest version of Anniversary Edition (which lists as Special Edition in GOG Galaxy, but I am not going into that), then moved the data / CC elements, then downgraded the game, at last copied back the contents to where it was needed. Installed and set everything according to as stated, following your doc bit-by-bit, it was really straightforward almost everywhere.
I have not seeny any bink2w64.dll anywhere (just wondering: doesn't it needs to start the game at least once to be generated..? But .dll-s are not "generated" by the game itself imo, but who knows, it was a long time ago...).
I have searched the entire c:\ and h:\ drive, but no success. H: is a separate drive where only Skyrim + MO2 are installed to separate dirs, c: is the default Windows system drive. MO2 is installed as portable, with separate .ini and save files.
I have now repaired the GOG installation, and magically, the two missing .dlls reappeared in the game dir. After first run, they have relocated into the MO2/overwrite dir. So the game basically runs now.
Unfortunately I am struggling with .ini files now: after the recommended Bethini mod install, I have chosen the default profile's .ini location in MO2, but nothing seems to work: the .ini files are generated from somewhere else. Could you please elaborate on how did you installed the Bethini Pie within MO2? I think the root cause lies somewhere here.
Update: sorted out the .ini issue. It is a fix, not a permanent solution: after Bethini Pie tweaks, simply copy-paste to the .ini editor the Bethini results to the appropriate files under MO2.
Thanks for the feedback. I will update the guide to instruct everyone perform a verification/repair after "downgrade" just in case this happens to others. I had this previously for all users and during a clean-up of the guides I now only instruct users that previously had an install to do it.
Regarding Bethini PIE (and any app run w/in MO2 for that matter), it has to be setup as an 'executable' within MO2, and launched from within there. This will build the VFS with all of your files/mods and configs before launching the application and save the files in the appropriate places. If you try to just launch Bethini PIE from its own .exe itself (outside of MO2), it will save the files directly to your "Documents\My Games\Skyrim Special Edition" folder, which won't work correctly if you have the option in your MO2 profile to 'Use profile-specific game INI files' enabled. It sounds like you just copied the contents of the files from this location to your own profiles INI files by way of the ini editor plugin. This is fine as well but adds an additional step.
Hope this helps, and thanks again for the feedback.
I thank you for your article, it was a great help to (re)start modding.
Bethini: I have started from the MO2 as well, but it still asked for the original skyrim.ini location as well for the location of the game root dir.
My choices were for the skyrim.ini location: - Documents\My Games\Skyrim Special Edition - Documents\My Games\Skyrim Special Edition GOG (there were files as well) - MO2\profiles\default - MO2\overwrite (there were .ini files too at the first install attempt) Choices of the game root dir: - where it was actually installed - MO2\plugins\data\RootBuilder\HgameSkyrim_Anniversary_Edition\1_6_659_0\Backup
And all of the variations of the two above, but none of them helped, just the way as I described. Also in the Bethini description says if you use it with MO2, then it doesn't matter if you choose the Documents\My Games\Skyrim Special Edition location, MO2 will detect it, and will use it. But noooo. :)
Thats why I have asked how do you run it from MO2. I have simply added a new executable from file, checked the "force load libraries" checkbox (tried without it as well). It still asked for the .ini and game root locations, tried there all the above variations too, but still no luck. Have tried to run Bethini standalone, still not working. Only with the manual copy-paste method.
I am almost certain that when you run any executable within MO2 and have the 'profile specific game INI files' option checked, it will build the VFS to place all files in their standard locations. So in this case, just select the standard INI location "Documents\My Games\Skyrim Special Edition". By the time Bethini PIE launches from the MO2 executable, your profile specific INI files will have been "virtually" copied to that location and when the program closes it will update them back to the profile specific location MO2 is managing. This is how Skyrim itself is able to read the settings files -- MO2 is not telling Skyrim to read the files from a new location.
I will update my guides to be more clear on where to select the files from.
29 comments
Below are some items that will require guide updates. I am listing them here for reference and will remove them when the guide is updated.
Downgrading
GOG no longer supports downgrade to 1.6.659 through the GOG Galaxy application or the offline installers found on the website. If you already have this version, you can continue using it, but users will no longer be able to use this version moving forward.- Updated in version 1.17.10Popular Mod Updates
USSEP and LOTD now require _ResourcePack.esl and _Resourcepack.bsa master files. If you intend on using either of these mods and are downgrading, you will need to also ensure you keep these files when following the process to upgrade Skyrim game masters. Thanks @davemcknz, @Schinkennudel, and @ddsonic28 for this info.- Updated in version 1.17.10Mod versions
Please let me know in comments below if there are any other updates that are required.
I hope you can help me get unconfused!
[Oh, I did check to see if GoG Galaxy had had an update I didn't know about; unfortunately, no - so I'm on the latest current version.]
Apologies as I posted this under main page comments. I have a guide update coming - recently (last month) GOG removed older versions so downgrading is no longer possible. If you currently a downgraded version, you won't be forced to upgrade, however, new users are stuck with 1.6.1179. I will sticky that in this thread until the guide update is done.
Thank you!
I've been trying different solutions for hours but following this guide from a clean slate finally got things working!
I followed your instructions to the letter. I got to the stage where you say to run SKSE and I did so. But nothing happened. Thinking back to the first time I modded Fallout 4, I ran the game through GOG first, quit the game and tried again. And it worked.
Sort of.
MCM Helper is required by TrueHUD in your list of recommended mods. Have I perhaps installed the wrong version?
And then there is this:
Any thoughts as to what I may have done to cause this?
Your guide is fantastic and endorsed. These issues have most likely arisen due to my own stupidity, but any insights you could provide would be greatly appreciated.
Many thanks.
Also, same question for SKSE -- if it is complaining about game version you may be using a mismatched version of the plugin for GOG, just make sure you have the right plugin for the version you are using. These are outlined in step 4.2.2.1.1:
I have actually managed to get it working and I figured LOOT was just crying about the about the version, even though I am using the downgraded version with the 1.6.1179 masters.
I accidentally skipped over the Backported Extended ESL support. When I went through that bit it seemed to resolve my issues.
I do have a question though. If I am using 1.6.659, but I am using the masters from 1.6.1179 does that mean I could theoretically use mods for either version?
As an example, I am trying install PapyrisUtil SE and I am using the GOG version but Vortex states it is incompatible with the current version of the game. Am I out of luck or am I doing something wrong?
Modding Skyrim seems a bit more complicated than Fallout 4, which is the game that really got me into the modding scene.
FYI there is a version of PapyrisUtil SE for the version of GOG you are using in the 'OLD FILES' section. Version 4.4 for GOG:
An amazing guide, easy to follow, simple to use. However, I am currently at stage 4.5.2 and I seem to have run into an issue I can't seem to solve.
I followed the instruction as written regarding powershell, but it doesn't seem to have converted all of the files? The guide states that after Powershell is run, all I should be left with in my CC Content folder is mod folders and I did indeed have four folders. Fishing, Rare Curios, Saints and Seducers and Survival.
But I still have a lot of "loose" files left in my folder with names like "Wraithguard", "BeAFarmer" and "BA_Orcish" all with either the .esl, .esm or .bsa suffix.
Am I being incredibly dense and missing something or might I have encountered a separate issue?
PS I bought my Skyrim Anniversary Edition today from GOG.
EDIT: I attempted method 4.5.3 but Vortex is giving me an "Installer reported errors" message. I'm at a loss...
Interestingly, it seems to have reverted more than it originally converted. I'm going to attempt to repeat the process. I shall post my results.
EDIT: I am scratching my head in bewilderment. I repeated the process of converting the files and it seems to have done all of them this time.
I am totally at a loss as to what I did wrong last night, but thank you for your help!
First of all, thanks for the detailed howto, it is much appreciated.
However, the GOG version with MO2 and downgrade does not work: the skse64loader can not find the "bink2w64.dll" nor the "Galaxy64.dll".
(I click manually to root build, then run skseloader, when I click MO2's play, it simply doesn't do anything apparently.)
I have neither of those dlls: the first is Steam-related, the second is issued by GOG as I guess.
Can you help, and/or elaborate on the article? :)
Which is amazing, but still: I did everything according to that, but no success...
Best,
B
I'm not sure what you mean. The bink2w64.dll is not a Steam-related file, it is a Skyrim required file. I verified this process before publishing. Just want to make sure you didn't stray from the guide in some way.
Installed and set everything according to as stated, following your doc bit-by-bit, it was really straightforward almost everywhere.
I have not seeny any bink2w64.dll anywhere (just wondering: doesn't it needs to start the game at least once to be generated..? But .dll-s are not "generated" by the game itself imo, but who knows, it was a long time ago...).
I have searched the entire c:\ and h:\ drive, but no success. H: is a separate drive where only Skyrim + MO2 are installed to separate dirs, c: is the default Windows system drive.
MO2 is installed as portable, with separate .ini and save files.
I have now repaired the GOG installation, and magically, the two missing .dlls reappeared in the game dir.
After first run, they have relocated into the MO2/overwrite dir.
So the game basically runs now.
Unfortunately I am struggling with .ini files now: after the recommended Bethini mod install, I have chosen the default profile's .ini location in MO2, but nothing seems to work: the .ini files are generated from somewhere else.
Could you please elaborate on how did you installed the Bethini Pie within MO2? I think the root cause lies somewhere here.
Update: sorted out the .ini issue.
It is a fix, not a permanent solution: after Bethini Pie tweaks, simply copy-paste to the .ini editor the Bethini results to the appropriate files under MO2.
Regarding Bethini PIE (and any app run w/in MO2 for that matter), it has to be setup as an 'executable' within MO2, and launched from within there. This will build the VFS with all of your files/mods and configs before launching the application and save the files in the appropriate places. If you try to just launch Bethini PIE from its own .exe itself (outside of MO2), it will save the files directly to your "Documents\My Games\Skyrim Special Edition" folder, which won't work correctly if you have the option in your MO2 profile to 'Use profile-specific game INI files' enabled. It sounds like you just copied the contents of the files from this location to your own profiles INI files by way of the ini editor plugin. This is fine as well but adds an additional step.
Hope this helps, and thanks again for the feedback.
Bethini: I have started from the MO2 as well, but it still asked for the original skyrim.ini location as well for the location of the game root dir.
My choices were for the skyrim.ini location:
- Documents\My Games\Skyrim Special Edition
- Documents\My Games\Skyrim Special Edition GOG (there were files as well)
- MO2\profiles\default
- MO2\overwrite (there were .ini files too at the first install attempt)
Choices of the game root dir:
- where it was actually installed
- MO2\plugins\data\RootBuilder\HgameSkyrim_Anniversary_Edition\1_6_659_0\Backup
And all of the variations of the two above, but none of them helped, just the way as I described.
Also in the Bethini description says if you use it with MO2, then it doesn't matter if you choose the Documents\My Games\Skyrim Special Edition location, MO2 will detect it, and will use it. But noooo. :)
Thats why I have asked how do you run it from MO2. I have simply added a new executable from file, checked the "force load libraries" checkbox (tried without it as well). It still asked for the .ini and game root locations, tried there all the above variations too, but still no luck.
Have tried to run Bethini standalone, still not working.
Only with the manual copy-paste method.
And thank you again for the answers and for the detailed guide.
Here, this one is on me. ;)
I will update my guides to be more clear on where to select the files from.