Picky, Found a small issue with this. Game is Fallout 4, the mod that is being flagged as requiring an update is Darker Nights. https://www.nexusmods.com/fallout4/mods/191
Mod has not been updated since 2018. Now, my Vortex is showing that this mod requires an update because Vortex believes that its version is 0.0.0-. I do not know where Vortex is getting this value from, it's nothing I've added so I suspect its bad data on the back end.
The issue with this extension is because Vortex thinks this mod requires a full update, there is no option on right clicking the mod to ignore this update. The ignore update is only presented if there are several files available to download as part of the mod.
Is it possible to add the ignore update option even if Vortex is telling me that a full update is available and should be downloaded?
I can provide any other information you need to show this issue - let me know. If I can help, I will.
Hmm, that seems to be an odd bug in Vortex's update checker. If you want to temporarily make the change to the extension yourself, open the index.js in your %appdata%\vortex\plugins\ folder (the subfolder for this extension) and in index.js change the lines that say this:
This will bypass the "modHasUpdate" filter for showing the icon in the context menu and show it on everything. This might cause a crash if you use it on a downloaded mod that you have not yet installed though.
After making the change, save the file and restart Vortex.
There is a different way to edit the file but it's a little more complex.
I installed this extension and it works brilliantly - however - after shutting down my system, I turned everything on again this morning, fired up Vortex and ran the usual check for updates. The process worked fine, BUT - mods that I'd previously marked as "ignore update" were once again flagged as requires update. Is that expected behaviour from the extension, or is the flag on the mod supposed to remain 'permanent'?
This doesn't seem to work with mods that have false update flags, which is what I mainly wanted to use it for. Any idea why?
By false update flags, I mean that I'll be using say version 2.0 of a mod, 2.0 will be listed as the latest version on the mod's Nexus page, but Vortex will still flag it as having an update available when I run "check for updates."
Ignore Update is not available in the menu when I right click on such mods.
The option doesn't show when the "latest version" and "current version" are the same. You can try reinstalling that mod from the right-click menu to see if that helps?
Did you try doing it from the multiple select option? Click one that already has an update. Then control and click the one you're having problems with. The toolbar at the bottom has a batch option to remove updates
31 comments
Is there any way to make this permanent for a mod? with an option to "unhide" updates?
edit: nevermind, found it.
I cnnot make this extension to work.
i installed, and restarted Vortex
Enabled
But is not showing on my mods...
any fix?
Image
Found a small issue with this.
Game is Fallout 4, the mod that is being flagged as requiring an update is Darker Nights. https://www.nexusmods.com/fallout4/mods/191
Mod has not been updated since 2018. Now, my Vortex is showing that this mod requires an update because Vortex believes that its version is 0.0.0-. I do not know where Vortex is getting this value from, it's nothing I've added so I suspect its bad data on the back end.
The issue with this extension is because Vortex thinks this mod requires a full update, there is no option on right clicking the mod to ignore this update. The ignore update is only presented if there are several files available to download as part of the mod.
Is it possible to add the ignore update option even if Vortex is telling me that a full update is available and should be downloaded?
I can provide any other information you need to show this issue - let me know. If I can help, I will.
context.registerAction('mods-multirow-actions', 100, 'hide', {}, t('Ignore Updates', { ns: NAMESPACE }), ignoreUpdate, modHasUpdate);
context.registerAction('mods-action-icons', 100, 'hide', {}, t('Ignore Update', { ns: NAMESPACE }), ignoreUpdate, modHasUpdate);
into this:
context.registerAction('mods-multirow-actions', 100, 'hide', {}, t('Ignore Updates', { ns: NAMESPACE }), ignoreUpdate, () => true);
context.registerAction('mods-action-icons', 100, 'hide', {}, t('Ignore Update', { ns: NAMESPACE }), ignoreUpdate, () => true);
This will bypass the "modHasUpdate" filter for showing the icon in the context menu and show it on everything. This might cause a crash if you use it on a downloaded mod that you have not yet installed though.
After making the change, save the file and restart Vortex.
There is a different way to edit the file but it's a little more complex.
Would you like me to report this to the vortex devs?
Is that expected behaviour from the extension, or is the flag on the mod supposed to remain 'permanent'?
Actually one of the things I would have liked to see implemented in Vortex when I send the survey. . . Picky listens to me ?
Thanks Picky!
Very much appreciated. . . now, about the other things on my wish list . . .
By false update flags, I mean that I'll be using say version 2.0 of a mod, 2.0 will be listed as the latest version on the mod's Nexus page, but Vortex will still flag it as having an update available when I run "check for updates."
Ignore Update is not available in the menu when I right click on such mods.
But great extension. Hope you make more.
Thank you and Endorsed!