Question About File Conflicts

[QuenIgni47]

Hey there. So, I just have a quick question about how Vortex manages file conflicts in Skyrim SE. Let's say that I have two mods (let's call them Blue Mod & Orange Mod) that only change some textures (no plugin files), and both of those mods have 20 specific texture files that are in conflict. If I select Blue Mod to win the conflict, does that mean the ENTIRETY of Blue Mod will deploy after Orange Mod? Or does it just mean that Blue Mod will be the one to deploy those 20 specific texture files into the Data folder?

 

The reason I ask is because I have a lot of mods that affect things like textures and meshes, and they have a lot of conflicts with each other (and I'd rather not comb through hundreds of individual files), so I just wanna make sure that I have the right idea about how Vortex is managing these conflicts.

[HadToRegister]

Hey there. So, I just have a quick question about how Vortex manages file conflicts in Skyrim SE. Let's say that I have two mods (let's call them Blue Mod & Orange Mod) that only change some textures (no plugin files), and both of those mods have 20 specific texture files that are in conflict. If I select Blue Mod to win the conflict, does that mean the ENTIRETY of Blue Mod will deploy after Orange Mod? Or does it just mean that Blue Mod will be the one to deploy those 20 specific texture files into the Data folder?

 

The reason I ask is because I have a lot of mods that affect things like textures and meshes, and they have a lot of conflicts with each other (and I'd rather not comb through hundreds of individual files), so I just wanna make sure that I have the right idea about how Vortex is managing these conflicts.

 

 

Vortex works like any other mod manager, it can't overwrite files from one mod if the files don't exist in the other mod.

It only overwrites files that named the same in both mods.

 

Example: Blue Mod and and Orange Mod have conflicts.

 

If you tell Blue Mod to LOAD BEFORE Orange Mod, then Orange Mod overwrites whatever files that Blue and Orange Mod have in common.

 

If you tell Blue Mod to LOAD AFTER Orange Mod, then Blue Mod overwrites whatever files that Blue and Orange Mod have in common.

 

EXAMPLE: Blue has 500 Files, Orange has 500 Files, Vortex sees there's a Conflict between 67 files.

Depending on what you tell vortex to do, LOAD BEFORE or LOAD AFTER, Vortex will only Overwrite those 67 files, because of the conflict.

Everything else will go through.

 

And of course, you can apply the same two scenarios to "If you tell Orange Mod to LOAD BEFORE" etc...it's the exact same thing

 

So yea, if Blue and Orange Mod have hundreds of the same files, and you want Blue to overwrite hundreds of the same files that the Orange mod has, you might also want to ask "Why exactly am I using Blue and Orange Mod together if I want Blue to completely overwrite all of Orange mod's files"?

 

 

 

[Tannin42]

As HTR said, the load after/before rules simply affect the order in which mods are put into the game directory with later mods overwriting only the conflicting files from mods previously loaded. All non-conflicting files are unaffected.

 

If you need more fine-grained control you _can_ right-click any mod and click "Manage File Conflicts" where you can override the order for single files.