Vortex and optional file versions question!

[Sable17]

You guys remember this about Nexus Mod Manager: If you had a main file and 3 patches from that same mod page, NMM would only look for the main file version.

 

So it would look like:

ModName Main file - 5.0

ModName Light Mod Patch - 2.3 :excl:

ModName Floor Patch - 1.3 :excl:

ModName ArbitraryCouldHaveBeenMerged Patch - 1.1 :excl:

 

Where the little :excl: would indicate that it wasn't the most "recent" file version because the main file was higher. I hope I'm making sense.

 

Anyway, apparently Vortex is all fancy and can detect individual files under the same mod. Super cool. But...

 

I got used to the NMM days and I like to keep my patches as the same version number of the main file. It's easier for me to remember that the patch has been looked at by me, even if I didn't have a "real" update for it and merely changed the file version on Nexus without uploading a new version. It's pretty much just a habit now.

 

Back to Vortex. I've had a few comments from users that Vortex is telling them that the patches aren't the most recent versions of themselves:

 

 

Vortex is confused by the optional file versions. The version says 5.3, but the file versions are lower (5.1 for CRF for example). This causes vortex to keep saying the file has a newer version. Updating the version without uploading a new file causes this. Only way to increase the version correctly on nexus, is to also (re)upload the file and replace the older version.

 

While I get that the way I do it is dumb, this seems like a flaw in the system. Why would it be good to add undue stress on the Nexus servers just to reupload the same file so that Vortex doesn't get confused? And why does the ability to change the file version manually still exist if it causes issues with the official Nexus mod manager?

 

Is it just me? Is there something that could change about the system?