DoubleYou

I cannot guarantee you will have no issues, but you might slide by ok. Please post your skyrim.ini file. (Puzzle, INI Editor, Skyrim.ini, copy and paste).

In the STEP Guide you will see the DLC mentioned in section 2.D Fixes. In the table it says "Detailed instructions available." Click that. You can just verify cache to get the original update.esm back.

AND you don't have to manually create the file structure for the SDO patch version, which only contains the file.

My guess is you are not posting the correct error message. You probably have an old version of SKSE installed in MO, and that is why you are getting an error. It probably is saying that the scripts are the incorrect version.

Papyrus ini settings being invalid and install location of SKSE have absolutely no correlation, so I have absolutely no idea what you are trying to say. The error regarding incorrect ini settings happens when you modify the Papyrus section of the skyrim.ini using the bad tweaks that are all over the Internet, or using blindly someone else's ini settings that they recommend to you. We only support installation of SKSE as outlined here when using Mod Organizer. If you decide to do it some other way, you do so at your own risk.

It actually will not matter, Tech, if they merged the patch, as the file will simply be provided by SkyFalls. Indeed, it's the exact same file, so no change necessary. It just is simpler to install the SkyFalls patch version.

You installed the wrong options (specifically the Explosive Bolts Visualized by Madcat221 option). Reinstall and make sure you use the Closer Quivers and Default Quiver option for Explosive Bolts Visualized by Madcat221.

You're right. With the change, SDO should be moved up in priority above Skyfalls and SkyMills. /fixed.

This mod has been moved in priority above SkyFalls and SkyMills in the STEP Guide to accommodate the update of aforementioned mod that provides the SDO patch file.

https://issue.tannin.eu/tbg/modorganizer/issues/777

That happened to me once too. I don't know what causes it. Doesn't happen all the time at least.

Simply put, you would have to be an advanced user to use LOOT with SR:LE and be 100% sure it was working correctly.

You can't, and you shouldn't. You should only add LOOT rules where the LOOT algorithm fails to correctly determine the correct load order.

Verify the bug and verify the fix and then we should be good.

Does Wrye Bash support OMODs?

I would disagree that this should have been apart of 2.2.9, as it had a few issues, causing ctd. Since these are supposed to be fixed, perhaps, but we like to test things first. Would you mind testing it?

I know. I just needed to add them all before I start the triggers. I need to design a layout before I create the fully functioning mechanism.

This is starting to get complex... https://wiki.step-project.com/User:DoubleYou/testpack/modlist#Examples It's a rendition of a mod entry with expandable instructions.

I'm going to guess that at some point you ticked the "Hide Inactive ESPs/ESMs" Workaround in Settings > Workarounds.

My idea is if we solve incompatibilities between mods instead of between packs, we'll get a lot farther ahead, as those fixes could be applied across all packs that used those two mods.

https://wiki.step-project.com/Project_talk:Data_Dictionary#Pack-Specific_Mod-Level_Install_Notes You'll see a bunch of bullets.

Please indicate the archive where this is the case, as I think it is more likely that you are now installing a corrupted archive, which will cause problems. It is possible, however, that the mod author zipped a file in using an incompatible method, for which that would be the proper method for resolution.

True, but some find it convenient to keep all the apps in one place.

Unless you're on Windows 8, that should be true.

Was there something preventing the other one from being added as a MO exe? I'm tracking it now, as it looks good. I don't use ENB manager. I just have a keen understanding of what I got in my base skyrim folder, but this does look handy.