trying to understand how the profiles work with Vortex

[Forestwolf17]

Scenario: I have two versions of the same mod (slightly different) which both are managed by Vortex. Next step: I create  a cloned profile. Now my question is if I remove (utilizing 'remove related') one of these versions completely in the cloned profile will this particular version still be available for the old/original profile?

N.b.: I#m not talking about disabling a mod but removing/deleting all the the related files.

Thank you for your feedback! :)

[7531Leonidas]

AFAIK, if you completely remove the mod, it will be unavailable for ALL profiles, at least that is how it worked early in my experience w/Vortex.  You simply disable any mods that you do not want to take effect in that particular profile.

[ChemBoy1]

Vortex uses shared downloads (archives) and mod staging folders (installed mods) for all profiles for a game, currently. This means that when you change a mod version in one profile, that change would be reflected in other profiles as well.

 

@Forestwolf17 To answer your question - Removing a mod would remove it from both profiles, not just the active one. 

It would be a great update to Vortex if they could add a feature to make a separate staging folder so that if a profile uses a different version of a mod, it would install that version to a staging folder only for the selected profile, rather than all profiles. 

 

For example, if you were managing Fallout 4 and wanted to have a profile for old-gen and one for Next-gen, this would not really be possible with the current functioning because the staging folders are not separated. That use case is not practical anyway, but illustrates the point. 

[Forestwolf17]

@753Leonidas1 & ChemBoy1: Thank you very much for your responses! That clarifies the situation. (Also, I agree that would be a great added feature for vortex to have separate staging folders for the individual profiles)