BSA versus loose file conflicts

[khumak]

I'm guessing my tendency to always use the BSA version of any mod I see rather than the loose files edition when possible has enabled me to avoid this issue until now but is there a way to get SE to give loose files the same priority as BSAs and actually use the load order they're in instead of always giving preference to loose files?

[Akzyra]

How? The game can't know what ESM/ESM the loose files belong to. With BSA it can.

 

Maybe package loose files?

 

Or extract the files from the BSA you want to win the conflict and copy them over the loose files replacing them.

Easier if you use Mod Organizer as you can create your own mod - lets say 'BSA Override' - where all those files are put into, and loaded last.

[khumak]

Ahh that makes sense.  I guess that's why I see so many people wanting to extract loose files from their BSAs.  Thanks.  Will have to look into how to package loose files into a BSA one of these days I guess.

[Akzyra]

A small note: as a BSA needs a mod with the same to be loaded, you can either create a empty esp,

or name the BSA the same as one of the last mods in your loadorder which doesn't have one.

 

Bashed Patch, MatorSmash Patches, SUM Patches, ...