-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metadata for Chidren of The North #2959
Comments
Children of the North has both RS Children plugins as masters, so it will be sorted after them by default. The only patch on the RSC page is the Bruma one which doesn't conflict with CotN, & the USSEP & AI Overhaul "patches" on CotN's page are just alternate versions of the plugin with appropriate masters as well. Are there any patches in particular that CotN needs to sort after that LOOT isn't sorting correctly? |
Sorry, I forgot to mention that some of these were other mods. Loot put CotN's esp higher than these: RS Children Patch Compendium (https://www.nexusmods.com/skyrimspecialedition/mods/13409) https://www.nexusmods.com/skyrimspecialedition/mods/118629 I don't use "RSChildren + AI Overhaul Patch.esp", "RSChildren-Patch-base-SD.esp" or "RSChildren-Patch-IWI-SD.esp" at the same time. Isolated, all three ended up lower that CotN. |
I don't understand what the point is of using any of those plugins with CotN. The AI Overhaul version of CotN already makes them compatible, so loading those patches are completely redundant when loaded before CotN, & loading them after undoes CotN's changes as I'm sure you're already aware. As for the IWI patch, that just resolves conflicts between IWI & RS Children, so loading it before CotN will also make it completely redundant. At that point, you need to just make your own patch between IWI & CotN (or just use a Bashed Patch, IWI already has the appropriate tags to do this automatically). |
Children of the North should load after RSChildren and most of its default patches, such as patches for AI Overhaul and USSEP
The text was updated successfully, but these errors were encountered: