Vortex mod overwriting issue - is this intended? - as if so, is a major flaw.

[Tetrol88]

Added a replacer mod "B" to my mod list that overwrites another NPC replacer "A" - fully intending to edit it to replace other NPCs. Have done this dozens of times while using MO2. Did so, the four other npcs now use the meshes and textures perfectly. Trouble is, when I first found one of the initial npcs she had the classic dark face of a mesh/texture mismatch. Went to replacer "A" to trace the nifs and dds paths - to find that Vortex has copied the NIF from "B" into mod "A" ie it has overwritten the data in mod "A" . This is a disaster as I have already done this process on about 6 - 7 other replacers.

What dropkick thought this was a good idea? If it is intended to ensure that there are no accidental overwrites in future - it is like causing a train wreck to prevent a car crash. 

[showler]

You'll need to be more clear.

Vortex doesn't change install locations, and only shows conflicts if two mods are installing identically named files to the same location.  And then all it does is pick which of the two files to put in your game directory.

[Zanderat]

Vortex allows you choose individual files within mods, not just the entire of mod A overwriting mod B.   Dark face shouldn't be an issue if done correctly.  Here is a screenshot of what I mean.   As you can see, I can choose one of four different meshes for that facegen file from 4 different mods without affecting the rest of either mod.