Patches or alternate mod options flagged as needing an update?

[zarantha]

Is there a way to have Vortex check the version for the file name of what you downloaded (patch version or alternate download version) instead of just the main file when checking for an update?

 

Couple of examples:

 

JK's Skyrim and Holiday patch for JK's. Both JK and the Holiday patch for JK are up to date. JK's Skyrim is 1.2, JK's Skyrim SE Holidays Patch is 1, both are downloaded from JK's Skyrim mod page. But because JK's is version 1.2, the Holiday patch is also flagged as needing to be updated even when the current version for the patch is 1.

 

Holidays itself is flagged as needing an update even though I am using the SKSE version (2.20A1) and not the main version. The version that I am using is current. This is even weirder, because the main Holidays version is 2.14. Vortex is not recognizing that 2.20A1 > 2.14. (This might just be a quirk of how Vortex recognizes version numbers, I think I recall reading something about that.)

[Tannin42]

It would help if you posted links to the mods you're talking about.

 

But in general, Vortex tracks each file individually, the "Mod version" as shown at the top of the mod page is ignored.

 

It's a bit hard to talk about this being precise, you download a "file" from nexus and install it as a "mod" inside vortex.

One "Mod" on Nexus can contain multiple files (like the main file and patch in your case), so you can have multiple "mods" inside vortex that correspond to different files of the same mod on nexus.

 

Now, again, Vortex tracks updates for each of it's mods individually so it needs to figure out if that file has been updated, it's not enough to know that the mod on nexus has a higher version number or that there is a new file because Vortex still wouldn't know if that new file is an update of the file you've downloaded.

 

Mod authors can provide that information, when you upload a file to nexus you have a dropdown box to specify "this file is a new version of file x". If the author did, Vortex can reliably figure out if it's an update you need.

Otherwise Vortex needs to rely on heuristics, like "the file I've installed was a "main" file, now it's an "old" file and there is a single main file now". In this case Vortex should determine that that is an update.

Still, depending on how the author manages its files it may not be obvious to vortex that a new file is an update to a file it downloaded previously.

 

And all this is under the assumption that your mod inside vortex has "Nexus" as the mod source and the proper mod id. Otherwise Vortex doesn't even know what mod that is.

[zarantha]

Thank you for the explanation. Based on that, I'd expect the heuristics to pick it up, but it could also be how the author uploaded them.

 

JK's Skyrim

https://www.nexusmods.com/skyrimspecialedition/mods/6289?tab=files

 

I have JK's Skyrim all in one and JK's Skyrim SE Holidays Patch from the miscellaneous files.

Vortex screenshot: https://www.dropbox.com/s/sj88p2l9zhmglfk/jk_skyrim_example.jpg?dl=0

 

Holidays

https://www.nexusmods.com/skyrimspecialedition/mods/1533?tab=files

 

I have Holidays v2_20 Alpha 1 from the miscellaneous

Vortex screenshot: https://www.dropbox.com/s/9nsq390plkqed7c/holidays_example.jpg?dl=0

 

I looked through my mods again, and I do have some mods that don't flag different versions for updates, so it's not all mods. Here's some 'working' ones, if you need them for comparison.

 

Skyrim Alchemy and Food Overhaul (SAFO) - assets and core files are different versions, and assets is not flagged for an update.

https://www.nexusmods.com/skyrimspecialedition/mods/12343?tab=files

 

Legacy of the Dragonborn SSE - has a main and an update file, the update is installed separately. The main file does not show as needing an update. For the times when there's no update file, just the main file, I usually know this one needs an update because the patches file shows it is downrev.

https://www.nexusmods.com/skyrimspecialedition/mods/11802?tab=files

[arcum42]

It's probably also worth mentioning that it seems to flag mods as needing an update if the mod has been deleted or hidden. It'd be nice to have a separate flag for that situation.

 

An example would be this mod here, which was recently deleted:

https://www.nexusmods.com/fallout4/mods/26493

 

It'd also be nice if there was a way to group all the mods with the same nexus id together, regardless of how they are sorted, to make it easier to find all the patches that go with a mod, but that's probably a different subject.

 

--arcum42