GENERAL NOTE ABOUT GAME VERSIONS

Skyrim SE = 1.5.97

Skyrim AE = 1.6.x, even if you don't have the Anniversary DLC content.

You need to get mods that match your game version. On AE, check the mod page to find out if the mod is compatible with AE. If not, check the Requirements section on the nexus page in the "Mods that require this file". Look for NG or AE versions of the mods.

IF NONE EXIST: DON'T PERSTER THE AUTHOR FOR AN UPDATE, IT IS POINTLESS AND COUNTER PRODUCTIVE!

As of 26/03/2023, the only valid choices for game versions are:

Skyrim SE 1.5.97

This still remains the most supported version, safest from further updates by bethesda breaking everything again

• SKSE version: 2.0.20
• DAR version: 1.1.0 (in old files)
• Address Library version: 2.0

Skyrim AE 1.6.353

Most supported AE version

• SKSE version: 2.1.5
• DAR version: 1.1.2 (in old files)
• Address Library version: 8.0

Skyrim AE 1.6.640

It's getting there, most mods are getting ported now to it.

• SKSE version: 2.2.3
• DAR version: 1.1.3 (latest)
• Address Library version: 8.0

GENERAL TROUBLESHOOTING TIP

Clear the Nemesis cache and run Nemesis again. The cache location is dependent on your mod manager.

MO2:

If you set it up properly with a dedicated mod to receive the Nemesis output, it will be in your Nemesis Output mod.

If setup incorrectly, I would recommend following every step of the How to setup Nemesis properly in MO2 page. If you somehow refuse to do that, it's in your Overwrite, Nemesis_engine/cache.

Vortex

Check your Skyrim Data folder, it will be in Nemesis_engine/cache.

Nemesis ERROR(6002)

Method #1: If when you run Nemesis, you get an error message mentioning 6002 error, the issue is likely due to your antivirus being overzealous. Add the nemesis patcher to your antivirus’ exclusions. If it is already there, try deleting the rule and adding it again.

If it doesn’t work, try disabling your antivirus temporarily to see if the issue is solved.

Method #2: Run Nemesis in compatibility mode

1. Close Nemesis Engine completely.
2. Navigate to your Nemesis Engine executable file.
3. Right click > Properties
4. Go to the Compatibility tab
5. Run this program in compatibility mode for Windows 7 or 8. Save and close the window
6. Run Nemesis again

T-posing ingame

This is most often due to a missing requirement, more often than not Dynamic Animation Replacer.

I've done everything correctly and I still T-pose ingame (MO2 specific)

Possible cause: Path too long

It may be because the path to your Nemesis executable is too long. This unfortunately is a Windows limitation, and if you left the default base folder for MO2 (in your AppData), the path will be very long. Try to find out the length of the path to the Nemesis executable: just copy it from the configuration window, paste it in Notepad++ or Word for example, you can then find out how many characters the path is. If it is close to 200 characters, you will have issues generating the behaviour files with Nemesis. The solution here is simple: you have to shorten the path to Nemesis. You can do this 2 ways:

• Rename the "Project New Reign - Nemesis Unlimited Behavior Engine" mod in MO2 to something shorter (simply "Nemesis" for example). This should be good enough in most cases...
• Move the MO2 base folder closer to the root of the drive. This is a little more complex, but still quite easy to do.

0. For safety: make a backup of your modlist and load order by clicking the respective backup buttons:

1. Go to your MO2 settings, in the Paths tab

IMPORTANT: OPEN THAT PATH AND KEEP THE EXPLORER WINDOW OPEN!!!

2. Change it to something simpler, for example like this:

IMPORTANT: you'll probably have to create that folder in your drive. Do that before clicking OK.

3. Click OK and close MO2.

4. Cut the following 5 folders from the explorer window you still have open from step 1:

5. Paste the 5 folders into the new directory you created

6. Re-open MO2. Everything should be as it was.