BlueGunk Posted December 14, 2020 Share Posted December 14, 2020 When I run SSEEdit, I get a warning about Mod Groups being invalid.Now, I have never made any Mod Groups. I have my usual pile of dodgy mods, Looted, and Bashed, but I have never made groupings for them. :huh: Here's a picture: https://i.postimg.cc/c1FsrnQG/SSEEdit-Groups.jpg Please can a Guru explain why I am seeing this error, and if there is anything I can do to fix it? Many thanks! Link to comment Share on other sites More sharing options...
BlueGunk Posted December 18, 2020 Author Share Posted December 18, 2020 No-one???? Link to comment Share on other sites More sharing options...
iSkylight Posted December 18, 2020 Share Posted December 18, 2020 Hi, BlueGunk. I've been modding off and on since about 2 months after Skyrim's release, but with many pauses throughout the years. I can attempt to help you, but I'm no expert. Things are changing all the time, so I am learning every time I return to Skyrim. As far as I know, the ModGroup thing is just a way to help reduce "conflict noise." It is to say "Mod groups is a feature used to state that it is considered normal/intended that two or more plugins have conflicts." Your ModGroup "AOS ISC USSEP" isn't one I have seen before. Even if you didn't set it up manually, you can still edit it yourself.The ModGroups are ignored if all of the necessary plugins are not loaded for that session, too. In this case, your plugins seem to be present, but they are not being identified with the appropriate CRC32s. What you can try to do is Right-click a mod that is in the target ModGroup and then click "Update CRC in ModGroups." Select the appropriate mods and go on through the process. This will update the CRC32 values for the mods within the selected ModGroup.Someone please correct me if I am wrong, as well. I like to learn.Anyway, let me know if this has helped you. Link to comment Share on other sites More sharing options...
nt5raham Posted December 18, 2020 Share Posted December 18, 2020 @iSkylight, you're right on target as far as I know. Mod groups do not have to be created by the user. For instance, USSEP has its own mod group. It is known to conflict with some of the core plugins because, well, that is what USSEP is for. So it has its own mod group so the user doesn't have to see the "conflict noise" as you put it (good description!). IOW, "Those conflicts are known and are supposed to be there, so don't worry about them. We'll take them out of view so you can concentrate on what needs to be resolved." There are some other well-developed plugins that come with their own mod group, like Legacy of the Dragonborn. I'm guessing that AOS ISC USSEP is for Audio Overhaul Skyrim / Immersive Sounds Compendium / Unofficial Skyrim Special Edition Patch. It is just telling you that conflicts between these three plugins are expected and acceptable. I also agree that it is probably a simple matter of updating the CRC 32s. The procedure you outlined looks spot on. As a matter of practice, when doing this procedure I normally "select all" because I've never had a situation where I didn't want to update CRC 32s. However, I don't know why the CRC 32s would be invalid to begin with, because that normally happens when one of the plugins in the group has been modified. @BlueGunk, have you modified any of those plugins directly rather than creating a patch? Or, it may have been modified due to an update. Another thing that may cause a mod group to be invalid is if that mod group specifies a particular load order, and the load order has been altered. That is to say, "Conflicts between these plugins are OK as long as and only if they are loaded in this order." The way to correct that would be to change your load order to match the load order of the mod group (it is there for a reason). You can always right click on any plugin, choose Edit Modgroup, select the mod group in question, and then just look without changing anything. It will tell you the specifics, like if load order is ignored or not, etc. Edit: Confirmed, AOS ISC USSEP mod group has only two plugins, USSEP and AOS_ISC_Integration.esp, and it is load order specific. USSEP must load first, and AOS_ISC_Integreation.esp is expected to overwrite USSEP. If either plugin has been modified or is disabled, or if the load order has been changed, then the mod group will fail to load and will generate an error message. I see from your screenshot that AOS USSEP is also invalid. It has only two plugins, USSEP and AOS, and it is also load order specific. And Cutting Room Floor is also invalid, though I have changed that mod group quite a bit on my system so I can't tell you about its original state. Link to comment Share on other sites More sharing options...
BlueGunk Posted December 19, 2020 Author Share Posted December 19, 2020 Very many thanks to you both for the clear and thorough information! I really appreciate it, and now I can understand what I need to do. THANK YOU! :thumbsup: And Kudos to you both for the help. Link to comment Share on other sites More sharing options...
nt5raham Posted December 19, 2020 Share Posted December 19, 2020 Glad we could help! Link to comment Share on other sites More sharing options...
Recommended Posts