You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bandolier for NPC's FOMOD has a couple of issues. For one, you can't select both the WACCF patch & WACCF, WiC, & CoS patch even though the latter is missing conflict resolution from the former. We also state that the former is a requirement of the latter, so this leads to confusion. CCOR also has an official patch for Bandolier that serves much of the same purpose as this mod, so they should be marked as incompatible. The CCOR patch should probably be preferred if CCOR is installed; this would also resolve an issue where some of the patches depend on 1nivWICSkyCloaksPatch.esp even though we state that it's already in 1nivWICCloaks_COS_CCOR_Patch.esp (although alreadyInOrFixedByX might be more appropriate since it's not entirely included, but the authors claim it isn't necessary with their patch). More investigation & consideration is required.
The text was updated successfully, but these errors were encountered:
Ref link, Discord
Bandolier for NPC's FOMOD has a couple of issues. For one, you can't select both the WACCF patch & WACCF, WiC, & CoS patch even though the latter is missing conflict resolution from the former. We also state that the former is a requirement of the latter, so this leads to confusion. CCOR also has an official patch for Bandolier that serves much of the same purpose as this mod, so they should be marked as incompatible. The CCOR patch should probably be preferred if CCOR is installed; this would also resolve an issue where some of the patches depend on
1nivWICSkyCloaksPatch.esp
even though we state that it's already in1nivWICCloaks_COS_CCOR_Patch.esp
(althoughalreadyInOrFixedByX
might be more appropriate since it's not entirely included, but the authors claim it isn't necessary with their patch). More investigation & consideration is required.The text was updated successfully, but these errors were encountered: