Vortex 1.13.6 mod updates automatically uninstalling previous versions

[ThisUsernameIs2long]

Game is Skyrim SE. I don't know if this is intended behavior. Previously, you had the option to install mod updates as variants. I no longer have this option. Previous mod versions are now automatically uninstalled without my consent, which is very undesirable considering I tend to make personal edits to most of my installed mods and I want to be able to switch between versions in order to compare them. Not only that, but updating mods now completely overwrites all files in the staging folder instead of creating a new one. Assorted Mesh Fixes is currently on version 0.126, yet the staging folder is still for the old version 0.120. Perhaps I accidentally messed with the wrong setting? I don't know, hoping for a fix.

[ChemBoy1]

When you update a mod, the old version of the mod is Uninstalled. That is how it has always worked. The archive is still there, though, so you can rollback to an earlier version.

If you are making edits to mods, you should install them as a separate, customized mod in your mod list so that an update does not remove those customized files from the staging folder. 

I have noticed that recently, Vortex does not always recognize a new version as the same mod. This can happen if the mod author changes the file name, but sometimes it happens even without that change. 

 

[7531Leonidas]

8 minutes ago, ChemBoy1 said:

Vortex does not always recognize a new version as the same mod. This can happen if the mod author changes the file name

And it happens when the MA changes the file without changing the version number.

[ThisUsernameIs2long]

5 hours ago, ChemBoy1 said:

When you update a mod, the old version of the mod is Uninstalled. That is how it has always worked.

Incorrect. Before you had the option to replace the mod or install as variant, like you do when reinstalling a mod. Choosing to install as variant simply disabled the old version instead of outright uninstalling it. Please read my post carefully. My issue is not Vortex failing to recognize a new version as the same mod. My issue is Vortex actually recognizing a new version as the same mod but automatically overwriting everything in the staging folder WITHOUT giving me the option to install it as a variant like it should.

Edited Tuesday at 10:50 PM by ThisUsernameIs2long

[ChemBoy1]

33 minutes ago, ThisUsernameIs2long said:

Incorrect. Before you had the option to replace the mod or install as variant, like you do when reinstalling a mod. Choosing to install as variant simply disabled the old version instead of outright uninstalling it. Please read my post carefully. My issue is not Vortex failing to recognize a new version as the same mod. My issue is Vortex actually recognizing a new version as the same mod but automatically overwriting everything in the staging folder WITHOUT giving me the option to install it as a variant like it should.

You did not read my comment carefully. If you want to modify files, install as a separate mod. Not that hard. 

Using the mod update function has always uninstalled the old versions and installs the new one as a variant. It does not present the dialogue. It automatically installs mod versions as variants if they have the same fileName. 

The way to get the "Install Options" dialogue below that you are talking about is to install the mod again with the same fileName and version (from Nexus or manually).

Probably what you are thinking of is the popup that asked if you want to update only the current Profile or all profiles. That popup no longer occurs if you only have one profile for the game. https://github.com/Nexus-Mods/Vortex/pull/16468

Please know what you are talking about before you start calling others incorrect. If the fileName is different than the old version, it will not present the dialogue. 

The Vortex application is open-source. You can go read exactly how it works. You can even do a PR to change it if you think it should do something different. https://github.com/Nexus-Mods/Vortex

 

[ThisUsernameIs2long]

21 minutes ago, ChemBoy1 said:

You did not read my comment carefully. If you want to modify files, install as a separate mod. Not that hard.

Irrelevant to the discussion at hand. This is not what my issue is about.

Anyway, thanks for at least giving a solution. So it's the intended behavior. Good. I'll trust you on that. We can consider this problem solved.

[ChemBoy1]

49 minutes ago, ThisUsernameIs2long said:

Irrelevant to the discussion at hand. This is not what my issue is about.

Anyway, thanks for at least giving a solution. So it's the intended behavior. Good. I'll trust you on that. We can consider this problem solved.

It is most definitely relevant. Your customized mod will be overwritten on an update unless you make a separate mod with the customized files. That is the way to solve your issue.

[ThisUsernameIs2long]

My issue is specifically mods being overwritten without my permission at all, regardless if they are edited by me or not. I do not care that I may lose edits on a mod update. I care that this is suddenly happening now despite it never happening before. Anyway, this discussion is not productive. You say this behavior is intended. Fine. Now I'll just have to work around it. Let's please not continue this any further. Thank you.

Edited Wednesday at 01:13 AM by ThisUsernameIs2long