The Worst thing about Vortex (which is pretty okay otherwise)

[Onikobe]

hi,

please for the love of all that's holy fix the behaviour described below:

Vortex doesn't deploy files while a modding tool is running, which is fine, BUT it doesn't keep the function you wanted it to do (un-)installing a mod) on hold, but pretends it did what you wanted it to do (deploys files, icon of mod status changed to enabled/uninstalled),

so a mod might appear installed or uninstalled, but the files were never copied or removed, so you end up with missing necessary files or with leftover files which can cripple your installation without you being aware that these files are still there.

Vortex should only give out the warning, without doing anything else, apart from unflagging a mod to enabled/uninstalled status again, whichever the status was before the user clicked the button and doing a checkup of the deployed files.

Seriously, this can totally **** with your install, especially the files not being removed.

Also this can happen if you closed a tool just beforehand, but Vortex didn't get the memo yet, still thinking the tool were running.

[HadToRegister]

So, you want Vortex to keep track of files you already have open and are editing/or not editing, in another application, and it doesn't keep uninstall information that you may or may not have changed while you've tried to tell vortex to install/uninstall/deploy a mod you may or may not be editing, installing, uninstalling at the time?

Did I get that right?

 

 

I use stuff like Xedit all the time on my installed load order, because I usually edit every ESP in my load order with script, instead of using "Patches", and I make my own "weightless" patches, that only use ONE esp, rather than Dozens etc.

So, would you give a detailed example of what you're trying to do, I'm trying to figure out what your problem might be, because it could be something I could help you with

[Onikobe]

 

So, you want Vortex to keep track of files you already have open and are editing/or not editing, in another application, and it doesn't keep uninstall information that you may or may not have changed while you've tried to tell vortex to install/uninstall/deploy a mod you may or may not be editing, installing, uninstalling at the time?

Did I get that right?

 

 

I use stuff like Xedit all the time on my installed load order, because I usually edit every ESP in my load order with script, instead of using "Patches", and I make my own "weightless" patches, that only use ONE esp, rather than Dozens etc.

So, would you give a detailed example of what you're trying to do, I'm trying to figure out what your problem might be, because it could be something I could help you with

 

I want Vortex to give out a message that Files can't be deployed because another tool is running and then to change the enabled/uninstalled button back to how it was before the user clicked it and to perform a deployment check the next time the user wants to install/uninstall a mod. Nothing else, o need for Vortex keeping track of files currently being edited.

Usually it's not even that i'm editing a file, more likely I just forgot to close Loot or Wrye Bash (which I only use for a quick checkup of form types anyways) or I already did mand saved my errors in xEdit, but didn't close the app.

I try to explain it with a fictional example.

I got Wrye Bash open.
I'm trying to uninstall a mod, because the mod installs a file (DialogueMenu.swf) which conflicts with a file I want the game to use, which is in an archive (ba/bsa).

Vortex tells me that it can't deploy files whil a tool (wrye bash) is running. I close Wrye Bash, Vortex does it's deployment stuff, the mod i wanted to uninstall is flagged as uninstalled, BUT the files which were installed by that mod earlier, are still in the Data folder and aren't deleted, so of course the mod I wanted to use still doesn't work. also Vortex doesn't have info about the (not)deleted files anymore, so it doesn't recognise them as edited or anything when doing another deployment check.

Now I got a bunch of files in my data folder messing with at least on other mod and no deployment info for those files.
To remedy this, i would have to install the mod i wanted removed again, then uninstall it a second time or remove them manually, by checking the contents of an archive of the mod.

Now, I know what to do about it now, but it took me a while to realise what's happening there and I don't want to know what other installs/uninstalls are botched because of this and for new or casual users this is can into a nightmare easily, since they usually don't have the capabilities to pin down problems with mods.

[JoshQuake]

I agree 100%. When you enable/disable/install/uninstall a mod and it isn't able to, it still changes the button state so it looks like it worked even though nothing was actually changed.

[AugustaCalidia]

@Onikobe

 

If you think there should be a feature in Vortex that addresses your problem, then use Vortex feedback to tell the developers about it.