Complex situation surrounding the Great Requiem Load Order.
Complex situation surrounding the Great Requiem Load Order.
While adjusting Skyrim for the eighth time, I encountered a new error. After setting up a fresh game, everything worked smoothly until loading began. A message from Requiem indicated either a load sequence problem or an unpatched mod introducing races. Since I don’t rely on race modifications, I suspect the order of loading matters. When running LOOT, I manually ordered the masters, mods, and patches correctly. This resolved the race issue but introduced another problem: weapons displayed vanilla damage instead of the values set by Requiem. It likely stemmed from a mod conflicting with what Requiem altered (as noted in the popup). I confirmed all patched mods, and I gave up using TES5EDIT as it didn’t provide the needed details.
Nexus mod manager is what I’m familiar with. I tried it in my previous modded configuration, but it didn’t perform well. It had many bugs, downloads via NMM stopped mid-process, and some external files wouldn’t run even after several fixes. Overall, it was a hassle to set up and use.
I noticed the issue with downloads, but that's the main concern. You should be able to download and install them yourself—it might seem like a mod conflict. MO mentions this situation. With NMM you'll need to make an educated guess. If you have any race mods, consider disabling them. Generally, Skyrim modding is about trial and error.
I don’t have any race mods, so I’ll try using Mod Organizer. It seems unlikely to succeed because the installer uses a different method than NMM and might not recognize everything installed by NMM. Updated: After turning on all plugins through MO, it detected no conflicts.
I tried to fix it but didn’t succeed. I thought updating the post would help, so I used tes5edit to locate the problem and resolved the bad mod. It looks like there was an unpatched mod in my load order. I had a patch installed, but it seemed faulty. I then downloaded another patch from Nexus, and everything worked again.