Jump to content

non-nexus mods "removed" when uninstalled


injaku

Recommended Posts

That does not match the behavior that I have seen with nexus and many non-nexus mods. I am not talking about "removing" the mod, but "uninstalling" it. Removing the mod uninstalls it, removes the mod from Votrex's mod list (de-indexes it), and removes the file from Vortex's download folder. Uninstalling the mod, removes the decompressed files, keeps the mod file in the vortex download directory, and keeps the mod in the mod list (thus allowing a reinstall and rerun of setup). In all cases with a nexus mod, and many non-nexus, mods this is the expected behavior.

 

The bug I am talking about is different. A uninstall removes the decompresses files, keeps the mod file in the vortex's directory (thus the need to remove the mod file before you can re-add it), but removes it from the mod list and appears to de-index it. Since the mod file remains in vortex's downloads folder it should still maintain the index.

 

I experimented with copying the file to Vortex's download folder before drag-dropping it from there. Vortex detected it as a duplicate, presented the option to replace (which deleted the file and added nothing), or adding it as alternative version, which created two copies of the file.

Link to comment
Share on other sites

I have tested it with a 400+ mod and clean profile.

 

- drag drop the SexLabArousedSSELosse-29.7z to Vorte's "Drop File(s)" area

--- interestingly this does not add it to the mod list if you don't auto-install, but you will see a "File imported" message with the option to "install".

- "installing" the mod will add it to the list

--- you can now enable/disable the mod without effecting the list

- "uninstalling" the mod will remove it from the list, but keep the file in the downloads directory

 

Vortex 1.6.14

- electron 19.1.1

- node 16.14.2

- chrome 102.0.5005.167

Link to comment
Share on other sites

I have tested it with a 400+ mod and clean profile.

 

- drag drop the SexLabArousedSSELosse-29.7z to Vorte's "Drop File(s)" area

--- interestingly this does not add it to the mod list if you don't auto-install, but you will see a "File imported" message with the option to "install".

- "installing" the mod will add it to the list

--- you can now enable/disable the mod without effecting the list

- "uninstalling" the mod will remove it from the list, but keep the file in the downloads directory

 

Vortex 1.6.14

- electron 19.1.1

- node 16.14.2

- chrome 102.0.5005.167

 

That sounds like it's working correctly, if you select "Remove archive" when removing the mod you will also delete the file from the downloads folder.

 

If you don't want the file copied into the downloads folder when you install it, there's a setting for that. Settings -> Download -> Copy Files with using "Install from File".

 

What was the expected result in this scenario?

Link to comment
Share on other sites

First I wish to apologies for the snakiness of this response. I don't know how to make it less snarky without being as specific. I do appreciate your attention to this issue.

This can not be the "correct" behavior, since this is not how Vortrex treats any of nexus's mods. If it was the correct behavior then listing "uninstalled" status mods should always return an empty list. This is not the case, look at the screen capture of the Vortex mod list. It is not empty. Vortex tracks mods in an "uninstalled yet not removed" status.

 

uninstalled-but-not-removed.png

https://ibb.co/j8F9FYY

The "uninstalled and not removed" status serve two primary functions:
- it reduce the size of mod on disk without the need to track the file outside vortex, or download the file again
- it provides a method to tell Vortex to reinstall, ie rerun the FOMOD, if the user wishes to change the set of install options. without the need to re-add it to vortex

The current behavior silently drops the uninstalled mod from the mod list, but leaves the file on disk. This leaves the user with the impression that the file has been removed, while in fact it remains in the download directory taking up space.

Consider two mods that both apply patches if the other is detected as deployed. First the user installs and deploys A, which does not apply B's patch. Then installs and deploys B, which add's A's patch. The user uninstalls, reinstalls, and deploys A to get its B's patch. I know of at least mods that have this behavior (luckily Vortex does not silently remove either from its mod list or this process would be much more annoying).

What was the expected result in this scenario?

Clicking on the "uninstall" option on the left (not the remove option on the right) should:
- remove the unbundled files from the deploy directory
- flag the mod as 'uninstalled' in the mod list
- NOT remove the mod from the mod list (like it does for all nexus mods ie the correct/expected behavior)

Link to comment
Share on other sites

Yes. I want it to copy the mod's file to download. That is not the bug. The bug is that it treats the mod differently and silently from other mods.

Vortex should treat the SexLabArousdSSELoose-29.7z file the same way it treats all the other files. Uninstalling the other files, does not drop them from the mod list. Removing the mod drops them from the mod list.

Uninstall != Removed for all nexus mods., so this is the behavior the user expects for all mods.

 

JK-kept-Sex-Lab-dropped.png

https://ibb.co/d5qPVDT

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...