updating/replacing a mod in my load order is now convaluted

[Guest deleted34304850]

.

[GladiusVictorius]

To avoid this i uninstall always first the Old Mod version and after i install the new Version.But you are right Vortex ask sometimes to much.I have that many times with translation Mods.Vortex say me i have then a Conflict and i have to make Load rules what is stupid as the Translation Mods get install last and have to overwrite the other Mod and not to Conflict with it.

[BigBizkit]

I can only reproduce parts of this.

 

When I update a mod and pick "replace" I am getting an "External Changes" prompt like you do (which should not be the case and I told the devs about it).

 

However, I cannot reproduce what you are suggesting: a new version being installed next to the old version (which gets disabled).

 

What are the mods in question?

 

edit: It sounds more like you might have selected "Install" instead of "Replace". Because when you do that, you will likely get a "this mod is redundant" message, seeing how you just installed the same mod (but with a newer version) again. And that would also explain why you end up with one old and one new version, with the former being disabled.

[HadToRegister]

I just did this the other day as well, so now I don't bother using the UPDATE feature in Vortex, and instead download the updated mod, uninstall the old mod and install the update in it's place.

What I've seen happen to other users is, they download a Mod that contains an ESP and BSA or Loose Files, then they later UPDATE from Vortex, and the UPDATE consists only of the updated ESP, so they tell Vortex to Update, and now Vortex sees that "Original Mod.esp" is overwritten by "Updated Mod.esp", so they pick Remove "Original Mod.Esp, and Vortex UNINSTALLS the ENTIRE MOD, BSA, Loose Files and All, leaving just the "Updated Mod.esp", which is now left without the BSA or Loose Files, so the mod doesn't work.

[Guest deleted34304850]

.