Check for Update generates error message when mod is no longer available from Nexusmods

[Guest deleted34304850]

I transitioned from NMM to Vortex a while back, and it's gone perfectly, however, I have one question for you, which is this;

 

I have a mod that is installed locally on my system. It used to be available on Nexusmods, but has since been removed by the author. I installed it, using Vortex, from my local archive.

As the mod is no longer available on Nexusmods, if I run Check for Updates for my mods, this mod will flag up a red warning, indicating that Check for Updates could not complete successfully, as this mod cannot be found.

 

Is there a way that I can flag this mod within Vortex, that would remove it from being included in the Check for Updates script, so that the Check for Updates will run, but not provoke the error message, for something that Vortex cannot resolve, due to the fact that the mod is no longer available for download?

 

Thanks for any advice offered.

[Guest deleted34304850]

.... and I answered my own question.

 

All I needed to do was ensure that the source of the file in the mod's metadata is not set to Nexusmods, and instead, contains no value. This will allow the check for updates to go about its business, and ignore this mod.

Little things like this make Vortex an intriguing and comprehensive mod manager. Kudos to you guys behind this program. It works!

[HadToRegister]

The other problem is there's a TON of Dead Links for the older games, such as Fallout 3, Fallout: New Vegas, because they weren't switched over to the new format, so a link like this: http://www.fallout3nexus.com/downloads/file.php?id=7875 will bring you to the main Nexus Page instead of the Mod page, but this one will https://www.nexusmods.com/fallout3/mods/7875 bring you to the actual mod page.

There's thousands of them out there like this, and I wish they'd fix them