Explicit Update Function Needed

[Vyxenne]

I have not found an actual "Update" installation option so far in Vortex. I found "Replace" but that one worries me greatly since it does not explicitly say what that means and I fear that it just means "overwrite" which falls far short of what is needed.

 

Currently when I want to update a mod, I am doing the following individual Vortex functions:

1. Remove the currently-installed mod completely
2. (Tap my toe impatiently as Vortex relentlessly and unstoppably "deploys" all of my mods despite the fact that if it would just wait 10 effing seconds there is something else I would like to do before it deploys)
3. Install the Update archive (7z, rar, zip, etc.) as a new mod, thereby losing my ini's and any saved data
4. (Tap my toe impatiently as Vortex deploys my 200+ mods again, mostly duplicating the useless deployment it just finished doing)

I would love it if "Update Existing Mod" was an explicit option when I have downloaded a new version of an existing mod, and that this new option would allow me to incorporate #1, #3 and #4 above with a single click, skipping the premature deployment at #2.

 

When I have brought this up in conversation elsewhere, someone always asks "well why not just install the updated archive and authorize overwrites/overrides?" Seemingly a logical question, but not so fast...

 

1. The files don't always match up, so overwriting/overriding does not always do the trick. Examples that really happened lately:

• Flower Girls plugin extension changed from esp to esm, so simple "overwrite" would leave both plugins installed and enabled
• SKSE Script count went from 63 to 81 in one update, then back down to 63 for the next (or similar numbers). If we just used Overwrite on the 2nd update, it leaves 18 orphan scripts still installed. (Many users did exactly this- go read the SkyUI forum)

2. The relentless, interminable, unstoppable, uncancellable "deploy all 200++ mods every time we detect a hiccup anywhere on your entire continent" is the bane of my Vortex existence. Surely there must be some way to cancel or abort this abominable seeming-overkill.

 

With a dedicated "Update" function that checks the existing mod's files against the Update's files for "orphans" and deletes them, then allows the update to overwrite the name-matching files, all of the above issues would be addressed including the execrable (seemingly-over)-deployment.