Skip to content

Issues i have dealt with with vortex v1.16.2 #20133

@g7755726

Description

@g7755726

Your Nexus Mods username
g7755725

There is an issue that affects every user that uses vortex in some way (mo2 users are probably fine)

so I'm going to detail everything I have experienced and others can feel free to add on this for issues you encountered if you did update in the comments

1). Collections are essentially broken not on the collection side but on Nexus Mods side if you attempt to download collection that has external mods included for "Direct Downloads" vortex will straight up break and doesn't matter if the source it's downloading from is valid or not vortex broke something and now going to have to fix it and yet till to this day it's not fixed some will be able to download them but vortex will straight up give your the middle finger and not install it and only way to get collections to work is downgrading to v1.15.2 or earlier.

2). This affects all collection maintainers if your collection has mods configured settings for many mods the setting is called "Same Installer settings" and then you want to update your collection so you download your collection then proceed to clone it you will notice some mods that have fomod will say fresh install instead of same installer options thus having to go back and and check if the mod has fomod installer options and change the settings.

Sometimes during install it will bug out and ask the user to set up the mod before it installs this accidentally having a user select wrong options and break their game entirely if not selected correctly. the maintainer has pre selected to ensure things work.

3). When a mod or a collection receives a update vortex has a new bug that will literally prevent the mod to update and instantly faill to install, it doesn't matter if the mod is fine or not this is a vortex issue and the team at nexus mods need to fix.

4). Vortex has introduced a new bug that causes mods and vortex to detect masters, witch means even if you have the mod it's telling you do not have and you infact do, it doesn't care it will ask you to download it again and when you do vortex will tell you that you already have it installed and only way to fix it is by force installing it and uninstall the one you have just installed not the one you had already installed just to get vortex to register you have the masters.

5). You currently see collections you DID NOT curate, this means you have the ability to see collections others have made download them and not sure if you can but possibly wreak havoc on another persons collection without them knowing unless they check themselves when it was lat.updated (if you see this bug please do not alter or mess with other users creations because you wouldn't want the same thing happening to your especially taking hour's to rest, curate and build those collections) oh there's a chance that you can only see a limited amount of collections.you created too.

5). if you end up downgrading (do a clean downgrade not a dirty downgrade), most things will work with the occasional missing master stuff but you can't create, clone or view your collections on an older version of VMM you must be on the latest up to do anything with your collections, though you can download existing collections that are already live via nexus mods

6). Updating collection which I forgot to mention will uninstall external mods automatically without even to bother to ask you to review what mods to remove or keep which I hate cause I only remove mods that have been removed from a collective specifically and keep ones that doesn't need to be uninstalled even when those mods do not have updates to them!

I also forgot mention that even if the maintainer of said collection set to same config there a big chance during users installation it won't respect that setting and ask the user what they have installed and setup.
Expected behavior
A clear and concise description of what you expected to happen.

Platform (please complete the following information):

  • OS: Windows 11 Pro x64 25H2
  • Vortex Version 1.16.2

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions