How do I force Vortex to recognize a variant/verison of a mod instead of making multiple rows for the same mod?

[ScotteiIsTakenWhoaWhy]

Let me use AAF for Fallout 4 as the example. I have four versions of AAF -- 78b, 121b, 139b, and 154b. That's four different rows on Vortex, ie, four different "mods" even though they're just versions of the same mod. I know Vortex can support versioning for some mods if they support a certain format but some mod authors just don't follow the x.x.x format and likely never will. How can I force Vortex to recognize versions, preferably keeping the metadata in the process? Just assigning version numbers myself to follow the x.x.x format doesn't work.

 

To be clear my beef is with organization, not activation -- I use profiles already to manage activation of different versions. I just want one row per mod in my mods list.

[HadToRegister]

What's AAF?

Use the name of the mod rather than the Acronym, not everybody has memorized them

[Guest deleted34304850]

while its not ideal, you could filter on enabled/disabled in your mod list, so if you have four versions of a mod in your mod manager, only one of them is going to be enabled/active in your mod list for that profile, and that should give you what you want?

[Pickysaurus]

As you point out, auto group requires the author to use a recognisable pattern to their versions. I believe it's controlled by mods having the same file name and mod id. I'm not sure editing this info manually will cause the groups to form though