7531Leonidas

Take a look at a portion of my display: If I were looking for one(s) that were not working properly, then I would start with the one highlighted, since it didn't get modified when the others above it did at game launch, when listed in descending 'Date Modified' order. In my case, I know that that one, and the others below it, had no changes in settings that would cause them to be modified, or they had been disabled. No real skill needed, just look at the times.

Perhaps a mod not properly installed, is corrupted somehow, or it is missing prerequisite files/mods? Use More Informative Console, run up to it, click on it, and see what it is from, and check some of the other information by mousing over it and using the 'Shift' key.

Making a patch often involves finding and resolving conflicts between mods, and you choosing which entries will 'win' by placing them properly in either an override .esp you make, or editing/drag n drop information to the mod that needs changes to work. While many conflicts can be corrected by adjusting LO, many others cannot, and you sort of have to 'mix and match' by way of the drag n drop, or 'Copy as override into' SSEEdit. Make sure to give the new override .esp a name that will differentiate it as one made by you, so you can adjust/remove it when you update your LO in the future. Maybe even keep some kind of log with the names and which mods/edits were involved.

The screenshot you included looks to me like a standalone LOOT set up to run as a tool in Vortex. Vortex uses its built-in LOOT when you install/deploy mods, or uninstall/disable mods. The messages like you have would be shown on the 'Plugins' tab in Vortex, under the 'Flags' column when you select 'LOOT messages' or 'Dirty' flags. In fact, I THINK that a lot of the information under the 'Flags' column comes from LOOT, in one way or another. As far as the game upgrading when/after you clean the plugins, it shouldn't, as long as you have followed the advice under the thread - and even if you mess up, and the d/l begins, it won't be applied. I did that just a couple of nights ago, clicked on my SKSE loader w/o starting Steam first. I am also staying on 1.6.640 for the time being.

Go to the Skyrim game community, and look on the LE or SE specific forums for information on this. There have been several posts. Two threads that might have some help, take a look: and There might be others.

You asked a question that is the source of a years-long controversy! 1st question, are you using Vortex, or MO2, or something else for your mod manager? If it is Vortex, you should just rely only on its built-in LOOT so its internal conflict resolution stuff works right. 2nd Q - Since you are running an older version of SSEEdit than the latest, are you running a Skyrim version that is also not the latest? Make sure that you have matching versions of SE/AE and SKSE. People fall on both sides of the clean/don't clean topic, sometimes virulently. If you are using/plan to use DynDOLOD 3, it requires cleaned mods (all of them), if I understand correctly. Double-check, but that would take the choice out of your hands. I am currently running cleaned masters (which is still recommended by some old hands), and have a very stable experience, w/the exception of HDT and/or animations. Hopefully you will get more/better input than just me.

I believe that it has to do with preserving the overwritten mod's files as a backup?

If you got the files from Steam, might you have to use the Beth mod manager in the main menu? Vortex might not 'see' some files from Steam, and vice versa. I don't like using the Beth MM and Vortex, it scrambles things. Do you make sure that the Steam files are d/l and installed into Vortex (via the 'Install From File' widget at the top of the mods page)? While there might be other ways to make sure, I would not be familiar with them, since I avoid Steam addons/mods.

You probably need to specify which game you are working with, the version of windows you are using, and exactly what you did to elicit this error message...

I believe that information is simply held in the virtual link (in the mod staging folder?) that enables the particular mod. If you look in the mod staging folder, you can see the mod registration/version info in its name. Hopefully, someone else w/more knowledge can confirm/straighten out this inference.

I am not sure that it can be done for now, as the d/l history is intertwined with the donation points system on the Nexus. Go to the Site support forum ( https://forums.nexusmods.com/forum/117-site-support/ ), or the Vortex Support forum ( https://forums.nexusmods.com/forum/117-site-support/ ) to check. I remember that there was some talk about/a request to be able to do so, but don't remember the particulars. Maybe suggest in feedback a way to 'hide' certain d/l from your personal history, w/o removing them completely from the site?

That is not the SE version of Racemenu ( https://www.nexusmods.com/skyrimspecialedition/mods/19080 ). The SE/AE version of EFM is here ( https://www.nexusmods.com/skyrimspecialedition/mods/35785 ). Apologies if you were referencing LE, I was just focusing on your comment about Skyrim SE/AE in your second post. The SE/AE version(s) all need matching versions of SKSE.

The SKSE folder should already be there, its location can depend on where you got Skyrim from. My Steam install placed that Documents folder under C:\Users\your user(account) name\Documents. The logs should all be in the SKSE folder already, along with other files, just look there.

IMO, the biggest problem w/FSMP-HDT is making sure that the SKSE version is set up properly. I do, however also use CBPC to handle the belly physics, I think. Read up on the things each can do, and do well, so you have less stutter/lag. Also, get the MCM for FSMP, it helps in making the settings make more sense, again - IMO.

@scorrp10 That may be how I got the file in the first place, don't remember.

Me either, it was a fail-safe suggestion. Maybe some kind of trigger for a .bat file that copies/backs up all the .ini files in a folder? I don't know how to do that, either.

IOW, please tell people which game you are commenting on, or asking help for.

It is possible, take a look at the modding.wiki here on the Nexus ( https://modding.wiki/en/skyrim/users/skse-plugins ). It is a listing of which mods are compatible, or have compatible versions, for the various Skyrim SE/AE versions, all the way through 1.6.1170. You might try to make a 'JSsuspect' folder in your SKSE installation, so you can temporarily move the ones that might need updating, if you can't disable them in Vortex or your mod manager. That way, you have not permanently deleted/removed any that still really work. The JS is just a suggestion, your username initials... FYI - go to wherever your ...\Documents\My Games\Skyrim Special Edition\SKSE folder is placed. Make a shortcut to it on your desktop. In that folder is your SKSE_loader.log, skse64.log, and a log for almost every SKSE-based mod in your LO. The skse64.log will show which of those dlls loaded properly, as long as you do not have very many, it shouldn't be hard to spot which one(s) didn't load compared to the dlls you have in your setup. Alternately (and this is what I do), I set the window to display in descending 'Modified By' order, i.e. - most recent at the top. This works best if you set your date in YYYY/MM/DD format, or YYYY/DDD format. Then, all you have to do is scan down the list of your dlls to see which one(s) didn't update its start log in that folder. That could narrow down your search for a problem SKSE mod a lot quicker.

Sorry, didn't notice about the LE situation.

Sometimes, it seems that I have seen that error message runs if you have a mismatch between a Lower version of SKSE and a mod built for a higher version. Which makes it somewhat unhelpful, if true. That .pex file you transferred is a script file, that may be dependent upon an earlier version of SKSE (or vice versa). Check the version of that file in the new Racemenu to see if it is your problem.

WRT COTR - I haven't been tempted, because it has its own race settings, and seriously conflicts w/Left Hand Rings, and maybe Dragonborn Empowered.

Do you use SSEEdit ( https://www.nexusmods.com/skyrimspecialedition/mods/164 )? It has a routine for checking selected mods for conflicts, or even your entire LO. Has a bit of a steep learning curve to understand their notation by color code, you should probably get it and try it, you can set it up as a tool in Vortex. It can help you find the source of some problems, and even patch some. You can do more as you learn.

I can't help with OAR, I haven't changed over yet, was waiting for 1.6.1170+ Beth update to renew/adjust my LO. I really want to get to a working DynDOLOD 3 in that setup.

Use SSEEdit ( https://www.nexusmods.com/skyrimspecialedition/mods/164 ). Not too hard to get started, checking for conflicts and the like, but a lot to learn WRT conflict resolution/patching conflicts. FYI - most conflicts in height maps and water flow do not crash games, but can make for some interesting visual artifacts.

I think that there are one or two on the Nexus, but I don't remember which. I use 'Perks Beyond Reasonable' ( https://www.nexusmods.com/skyrimspecialedition/mods/22015 ), which pretty much allows you to overcharge most perk trees. Goes better with mods that add perks, like Daken's Yummy Dragon Hearts ( https://www.nexusmods.com/skyrimspecialedition/mods/57940 ) and Quests Award Perk Points ( https://www.nexusmods.com/skyrimspecialedition/mods/33081 ). There is also ESO Skyshards on Arthmoor's site AFK Mods. Check them out.