Vortex Dependency Check Issues

[wanton nymph]

In theory it ought to be a good thing but because your existing mods from before the update don't have any dependency links set up Vortex is insufferably awkward to use now

It checks dependencies whenever you install, update, or delete a mod, but that causes a few issues :

1. if you install a mod that needs a dependency you already have installed Vortex doesn't know that, and tries to make you download another copy of the dependency, causing itself to then have mod clashes between the two "versions"

2. same thing when you update a mod

3. if you delete a mod that has a dependency it tries to uninstall the dependency even if there are a ton of other mods that need it

This is all particularly evident with Content Patcher as an example

They need to either add a function that scans all of your existing mod library and puts the dependency links in automatically, or give us the ability to switch off the dependency check and manage it ourselves

The only way around it for now seems to be either :

1. going through your library and manually making the dependency links. I have over 130 mods installed so I am not doing that.

2. skipping all the dependency recommendations when adding or updating a mod and then removing the dependency links to get rid of the constant warning that Vortex gives you.

[desert notch]

I think the first step here is to determine if this is a function of the SDV extension or Vortex itself

I would think if it was general to the entire app we'd hear about it from other communities as well

[desert notch]

Do you have a minimum example of this I can use to replicate the issue?

[echo cliff]

Try the beta version @wanton nymph - this may already be fixed.

[wanton nymph]

Hey sorry I haven't been online much the past couple of days

You unfortunately can't, as far as I can see, replicate it if you didn't have an existing library

Because if you're creating a library anew it will function as intended