There are two last and very important, specific notes that we’ve saved for this point.
First, the Guide does not support installations of Skyrim that are not using the English Language.
- DarkLadyLexy and the vast majority of her little minions are all native English speakers. That, therefore, is the setup that they use when the update and maintain this Guide.
- While we understand that many of you might speak and play games in your native languages, we don’t have anybody on staff who both knows that language (more likely than not) AND can make and maintain the required changes to all of the patches that the Guide provides to support that language. We simply can’t do it.
- We apologize if this offends, but it is not a matter of “will not”, but “can not”.
This one is important, and will be stated as clearly and simply as possible. We DO NOT and WILL NOT support software piracy in any form, including mod piracy.
- This includes providing links to mod files that have been hidden, deleted, or otherwise completely removed from mod file sites.
- It should be noted that this does NOT include “Archived Files” on the Nexus. There is a legal way to obtain these files (as will be detailed below) and is not piracy. This was determined after discussion with staff members of the Nexus.
- If you are on Lexy’s Discord Server and are found to be using a pirated game, operating system, or any other tool or file, you can expect to be banned from the server by the Moderators or Admins. Illegal activity of any kind will not be encouraged or supported.
- It should also be noted that the Guide cannot be properly installed on a cracked or stolen game or system – almost all pirates that have been caught on the server were caught because of this. DO NOT DO IT.
The Tags shown below will appear with appropriate Mods as you install them. Not all of them require any action on your part – many of them are for informational purposes or to help you locate a particular group of mods quickly if needed. Any action required during the installation will be given when it needs to be performed.
As an example, many mods will have the “LOOT” tag. You do not need to adjust this mod’s LOOT rules until you are directed to do so.
While installing the guide, there are a few things to keep in mind:
- DO NOT try to run the game to “make sure the installation is going well” until directed. Many of the files we install rely on other files that may not yet have been installed. Trust the process. If there are problems at the end, the Staff on the server should be able to help you either correct the errors or at least put you in contact with the right people to get you the help you need.
- For your own sanity, DO NOT run LOOT until you reach The Finishing Line Page portion of the install. You’ll see all kinds of errors on the LOOT UI Screen, and you will completely lose your mind. Trust the process.
- Throughout the Guide, you will find several places where you are instructed to remove files from a mod. Many times, you will see these filenames with a “*” in their names. As an example, you might see “helgen reborn.esp\*.tga”. In such cases, this means deleting ALL FILES that match that pattern (in this case, all files that have the TGA extension in that folder). These instructions will be seen in “SPECIAL INSTRUCTION” headers below the mod information and will appear as follows: Special Instructions.
Depending on the type of file you are downloading, you may treat them differently in how they are installed into Mod Organizer 2. The below instructions are our recommendations for how to handle this, which allow for the greatest possible flexibility and ease of updating. Also, below are some bits of advice for the mod installation process:
- Once you have installed a mod, ACTIVATE THE MOD AND ITS FILES in MO2. Future installations of other mods may rely on that mod being active in both panes of MO2 for its installation to work properly.
- FOR A FILE DESIGNATED AS A MAIN FILE:
- Install as normal. If the mod page has multiple Main Files that you will be installing, each file should be installed AS A SEPARATE MOD (IE, change the mod title name of the second file installed) so that they are considered two different mods by MO2. This allows you to update each file independently of the other instead of downloading and installing all of the files again if only one of them updates.
- FOR A FILE DESIGNATED AS AN UPDATE FILE:
- These files should be installed into the SAME MOD LISTING as its parent mod. This can be done by telling MO2 to “Merge” the files, which will tell MO2 to overwrite the original version with the update, which is exactly what we want to happen.
- FOR A FILE DESIGNATED AS AN OPTIONAL, MISCELLANEOUS or OLD FILE:
- These files should be installed as a SEPARATE MOD in MO2. DO NOT OVERWRITE the original mod files. This is done for the same reasons as the Main Files.
Throughout the guide, you will install several mods with FOMOD Instructions. Updating the FOMOD screenshots is a major pain on the website backend, so replacement screenshots will only be taken when necessary. Cosmetic differences like the Version in the FOMOD being different in screenshots, extra options being available, etc. should be generally ignored. Only select what is selected in the screenshots, and uncheck anything not selected in the screenshots, or not present in the screenshots.
Ancient sweatshirt wisdom tells us that “Change is inevitable (except from a vending machine)”.
Mods are constantly being updated. Bugs get fixed, improvements get made, new features get implemented, new bugs are found, and the process repeats itself all over again. Depending on the development cycle of the guide, it is possible that the mod we list has been updated since the guide was updated, meaning that the version we list in the guide will differ from what is available on the Nexus, making it more difficult to download directly.
Thanks to the Nexus change in policy some time ago, these files can now be found in the Archived Files tab. They do not, however, have a download button associated with them. The files are still available; however, if you know how to get to them. There are several ways to do this, and instructions for how to do this are below.
Option 1: Discord Bot
Thanks to one of the Discord server’s staff members, a bot has been created that can help you quickly locate the version you are seeking.
- If you haven’t already, join the Discord server. Read the server rules, take a look at all the chaos in the channels, and introduce yourself. Once you’ve got a feel for the insane people in charge…
- Go to the #bot-fishing Channel. This channel is specifically for running bot commands, including a few others you might want to use later in the guide install process.
- Type /nexus help, and the bot will walk you through what you need to do.
There are times when the Nexus Bot can’t help or might be very hard to work with. When (If) that happens, go with Option 2.
Option 2: Manual Method:
- If you previously installed this file or still have the original download through MO2, this can be found in the META file in the mod’s install folder or MO2’s download folder, respectively.
- If you don’t have this, then follow the below instructions:
- Go to the Nexus Mod Page for the mod file you are trying to download.
- Go to the “Files” tab.
- Click on the “File Archive” button at the bottom of the page.
Locate the file you need. RIGHT-CLICK on the top of this file, then select INSPECT ELEMENT.
Your browser window will open the Elements pane, and you will see some code. Look for a line that starts similar to:
The number (317360 in this example) would be the FileID of the file you selected.
in the link below, change ONLY the “YourFileIDHere” portion to match the FileID from step 5-6. DO NOT CHANGE the “1704” at the end of the link! This is the identifier for the GAME (Skyrim SE) that the FileID is associated with.
- If you have problems with the above instructions, a picture version of them can be found on Lexy’s Discord, in the #installation-help channel’s pinned posts.
If that STILL doesn’t work…
Option 3: Search your Discord, Luke…
Do a quick search on Discord if you still are having problems – if you can’t get the file, chances are someone else couldn’t either, and you can likely find the link with a quick search or glance through #FAQ. And then, if even after ALL of this you STILL can’t get it, there is always Option 4.
Option 4: Beg and Plead
Give one of the Help-Desk Minions in #installation-help a shout. They can help you out.
A Bethesda Softworks Archive (BSA) file is a compression file type (similar to a ZIP, 7ZIP, or similar file) that Skyrim uses to store assets used by a plugin file. Usually, this includes things like texture files, sound files, scripts, and other similar assets. More times than not, if a Mod Author (MA) packs their assets in a BSA, we leave it alone and allow it to operate as it was designed.
There are, for current Guide purposes, a couple times when we will extract the BSA files:
- The BSA comes with a “Dummy” plugin file. This means that there are no actual records in the plugin file, and that the plugin file exists only so that the BSA will be read by the game. This is completely unnecessary, so we will extract the BSA and delete the plugin in this situation.
- We will be using the plugin as part of a Merge, which will remove the ability of the plugin file to read that BSA, meaning the assets will go unused.
We will be using the BSA Extractor plugin that is included with Mod Organizer 2 to do this. There are two ways to accomplish this.
Option 1: The Normal, Automagical Way
The plugin is enabled by default, but we do want to change one of the plugin settings by doing the following:
- Click the “spanner and screwdriver” icon in the top left corner of MO2.
- Click the Plugins tab.
- Find and select the BSA Extractor plugin.
- On the right side, make sure the only_alternate_source option is set to false.
Anytime a Mod is installed that contains a BSA file, a prompt will appear asking if you wish to extract the BSA file. There are three options – be careful which button you press. For mods that you want extracted (marked with the EXTRACT THE BSA Tag), SELECT YES. Be careful not to turn off the prompt! If you do this, you can re-enable them in the general tab of Settings, by pressing Reset Dialog Choices.
The BSA Extractor prompt will also ask if you want to delete the BSA after extraction – select Yes for this as well.
For all other mods, SELECT NO.
At this point, you will receive a notification during installation for any mod that includes a BSA asking if you want to extract it. If the instructions tell you to do so, click Yes otherwise, click No. With the newest version of MO2, the BSA extractor will also ask if you want to delete the BSA after extracting it say Yes.
Option 2: The Manual Way
If you have turned off the prompt accidentally or for some other reason realize you have not extracted a BSA you need to, you can do it manually as well.
- Pick the “Archive” tab in the MO2 Right Pane.
- Scroll through the list of BSA Archives (they are listed with the plugin file that they are associated with).
- Once you have found the file you are looking to extract, RIGHT-CLICK on the file name and select EXTRACT.
- You will prompted for an extraction location. Find the folder that matches the name of the mod the BSA is associated with.
- The files will be extracted, but the BSA file will still be present. It can be deleted from its location using the normal File Explorer methods.
The original version of Skyrim (Skyrim: LE) used a slightly different version of the plugin files than Skyrim: SE does (Form 43 vs. Form 44). Because the Guide uses a number of mods that were originally designed and released for Skyrim: LE, the plugins will be in this older form. While these files will usually not cause a problem, it is a very simple process to convert the older format to the newer one and make certain of it.
We will be using the Creation Kit to perform this conversion. All mods that require this conversion will have the CONVERT Mod Tag.
1. Convert the Plugin with the Creation Kit
- Verify that the Overwrite Folder is empty. This will always be listed last in the Left Pane of MO2. If any files are present, they can be removed.
- From the Executable Drop-Down menu of MO2, select and run the Creation Kit.
- Once it has loaded, open the File menu and select Data…
- Locate the plugin file to be converted and select “Set as Active File“.
- Click on OK and allow the Creation Kit to finish loading.
- There will be numerous errors shown in a window in the background. These are normal and can be ignored. They will not affect this process.
- Once the load process is complete, select “File” and then “Save“.
- You read that right. As soon as it’s loaded, SAVE IT. This is literally all we need to do to convert the plugin.
- Close the Creation Kit.
The updated version of the plugin should have overwritten the older version. No additional action is required for the conversion. There have been rare reports that the process did not work, but the conversion process can be verified by:
2. Verifying the plugin with SSEEdit
- From the Executable Drop-Down menu of MO2, select and run xEdit.
- When the initial load is complete, RIGHT-CLICK in the window showing the plugin list and choose Select None.
- Locate the converted plugin in the list and DOUBLE-CLICK it. xEdit should begin loading again. Look for the message “Background Loader: finished” to indicate the completion of the loading.
- Verify that the last plugin in the left pane is the one you are verifying. RIGHT-CLICK on this plugin and select Check for errors.
- A message should display that reads “All done!” This indicates a clean plugin that will work.
- If errors are reported, you will need to either correct them or try the plugin conversion a second time before moving to the next step.
- RIGHT-CLICK on the plugin again and select Sort Masters.
- Exit xEDIT. Be sure to save the modified plugin.
- Run the plugin through xEdit Quick Auto Clean.
One last common task that will appear in the Guide for you to work with is running a mod through Cathedral Asset Optimizer (CAO). As mentioned in the Converting Plugins section, some of the mods we use are from Skyrim: LE, and the meshes and textures that go with them do not always play nice with Skyrim: SE. To make sure your game setup doesn’t explode, we’re going to make sure that everything is in order. Mods that require this processing will have the CAO Mod Tag.
- CLOSE MO2. CAO is designed to run OUTSIDE of Mod Organizer. Do not minimize it, CLOSE IT.
- Launch CAO from its executable file in its installation folder.
- Look at the mod’s Special Instructions. It will list a profile type to use in CAO. Ensure you are using the correct profile.
- Click on the Open Directory button. Navigate to the folder containing the mod that requires conversion. Select this folder.
- Click on the Log button. This will show you what CAO will process.
- Click Run.
- When CAO has completed its run, close the program.