I updated Vortex recently and I recently got more than like 900+ Loot Messages that are completely useless.

[red48dude]

The error for the 900+ mods I got for seemingly no reason aside from Vortex just unassigning the default group on update is as follows: 

No LOOT metadata could be found for this plugin. this is usually fine, but you may have to assign it a different Group to help LOOT sort this correctly.

Why is this happening now right after I update vortex. Why does this even count as a Loot Message and why did it unassign the group default and now give me an error for Loot Message even though it is already set to "default" which isn't actually a default group. Now I can't even read actual real Loot Messages which usually exist to help, and it's buried under like 900 plugins. 
What even happened??? Why can't I select all (CTRL+A) and set each to the default group?? According to some other users, apparently my mod list is too long even though I just made it shorter by getting rid of mods. What the hell is actually going on??? 

[imprimis432]

Same issue, I am noticing this could also be potentially causing issues with auto sorting, somebody more familiar with LOOT and ordering may be able to confirm this, I'm guessing because it doesn't recognise the metadata that it is unable to know how to auto sort the load order.

"Why not just ignore it?" just incase anybody has this thought, the problem is when trying to find out which mods are missing compatibility patches I like to filter to "LOOT Message" in the flag category drop down, this helps filter down to only plugins that require my attention, with this bug it means all of the mods with the message

Quote

No LOOT metadata could be found for this plugin, This is usually fine but you may have to assign it a different Group to help sort it correctly.

message are showing up and as the message seems to confirm my autosort problem I think this needs addressing rather asap please.

 

Further info in this thread

 

[Nagev]

Hi there - we're still investigating any potential issues with Vortex's LOOT sorting mechanism as part of the 1.12.0 release; but the metadata message is 100% not tied to any sorting issues.

I do agree that the inability to filter by _relevant_ LOOT messages is annoying and this will be fixed in a hotfix later today.

[imprimis432]

Glad to hear it, good to know my explanation of the convenient way to filter down to plugins that have LOOT warnings that are useful was understood, didn't know quite how to describe it.
The choice to simply turn off the message from occurring (ignore no metadata for sorting warning) or a way to 'add all to custom group' in a one click fix would be useful.

I'm more relieved now knowing this is purely just a cosmetic thing, I was panicking thinking all those mods had somehow been corrupted.

I'm assuming these mods that have this warning are find to be left as is and require no user side fixing.

[red48dude]

4 minutes ago, imprimis432 said:

Glad to hear it, good to know my explanation of the convenient way to filter down to plugins that have LOOT warnings that are useful was understood, didn't know quite how to describe it.
The choice to simply turn off the message from occurring (ignore no metadata for sorting warning) or a way to 'add all to custom group' in a one click fix would be useful.

I'm more relieved now knowing this is purely just a cosmetic thing, I was panicking thinking all those mods had somehow been corrupted.

I'm assuming these mods that have this warning are find to be left as is and require no user side fixing.

Thank you for further elaborating. I also had a panic attack because I was going to go test out a new mod and I had to uninstall and reconfigure a bunch of plugins in order for it to work.. I had to go through the process of uninstalling a ton of plugins which is the usual for me but when I was looking to see if I was missing plugins which tends to happen nearly all of the time when doing these sorts of things, I read LOOT messages often to tell me if something is wrong, or if I'm missing anything, or if I should read something. 

I'm just glad I'm not alone in this issue or else I would've actually gone mad. Now I can just wait for the potential fix later to finish the mess I almost made. I knew for a fact this wasn't something that wasn't supposed to exist. Like why it is telling me "This is usually fine" and making it a message I have to read if it's pretty much fine when it's pretty much a non-read fine issue. 

[Nagev]

2 hours ago, imprimis432 said:

Glad to hear it, good to know my explanation of the convenient way to filter down to plugins that have LOOT warnings that are useful was understood, didn't know quite how to describe it.
The choice to simply turn off the message from occurring (ignore no metadata for sorting warning) or a way to 'add all to custom group' in a one click fix would be useful.

I'm more relieved now knowing this is purely just a cosmetic thing, I was panicking thinking all those mods had somehow been corrupted.

I'm assuming these mods that have this warning are find to be left as is and require no user side fixing.

Correct, no intervention is required if your game runs smoothly.

You _can_ get rid of all those messages by applying a group to those plugins (i.e. select all of those plugins and assign them to the "default"/or any other relevant group) that will create userlist entries and Vortex will know that even though the masterlist has no metadata for them, your personal userlist definitions do; so the message will be gone.

Need to find out why @red48dude is unable to apply the grouping though - sounds like the bulk action is failing for some reason, can you try to apply a group and see if your log files mention any errors?

[Nagev]

Update - the fix has been committed a few hours ago https://github.com/Nexus-Mods/extension-plugin-management/commit/7f5e044d101083ad0183dd0552e6e23112c5a2ec

But unfortunately the hotfix release has been pushed to tomorrow morning as we had to make sure the sorting mechanism is functioning as expected (which it is, aside from some parsing issues for Starfield which are still ongoing)

Sorry to be the bearer of bad news, was really hoping to release it today.

[red48dude]

9 hours ago, Nagev said:

Correct, no intervention is required if your game runs smoothly.

You _can_ get rid of all those messages by applying a group to those plugins (i.e. select all of those plugins and assign them to the "default"/or any other relevant group) that will create userlist entries and Vortex will know that even though the masterlist has no metadata for them, your personal userlist definitions do; so the message will be gone.

Need to find out why @red48dude is unable to apply the grouping though - sounds like the bulk action is failing for some reason, can you try to apply a group and see if your log files mention any errors?

Actually, I've already tried this. Except it just takes way too long.

You can't mass select all (CTRL+A) of these mods and set them to a group (in the bottom bar which includes Ghost, Enable, Disable, and Mark as Regular) all at once so it would take me hours and hours to fix every single plugin meaning it's basically a lost cause. 

While we're talking about these groupings it got me thinking about something else unrelated. Why can't you search mods by Highlight on the Mods page and why can't you "Group the Table" by Highlights. With someone who has many many mods, I feel as if the Highlighting feature needs to be expanded upon such Highlighting the entire mod bar by the highlight color through like a setting or something. I find the Highlighting feature very useful for separating mod types and managing mods, but this feature is greatly underdeveloped and almost seems forgotten. There is also some highlight symbols I feel like should be included such as Trees (tree mods), Water  (water mods), Clouds or (for sky related mods), Storm Cloud  (Weather related mods), and maybe some type of small weapon for weapon mods . Anyways this feature just needs more improvements. 

Another thing you can't mass select and do is Uninstall mods similar to when you click on the mod status and click the green arrow next to the  Enabled . If this feature was added to the item select bar below, you could mass uninstall mods without actually removing them from your system completely. You can only Remove, Reinstall, Enable, and Disable selected mods. 

Edited August 7 by red48dude

[Nagev]

Hey @red48dude,

We welcome any enhancement suggestions on our github page https://github.com/Nexus-Mods/Vortex/issues

Creating a ticket there will ensure that your enhancement is visible and tracked; given the amount of feedback and data we're getting from our users it's easy for us to lose track of requests. Although please keep in mind that Vortex is being phased out in favour of the Nexus Mods App (NMA), and some features will not be implemented as we wind down; all feature requests on the Vortex repo will be reviewed during the development of NMA, so chances are that even if we don't implement it in Vortex, we might do in NMA.

Not sure I understand what you mean on the mass uninstall bit - the Remove button in the toolbar _is_ the mass uninstall button; I understand that the fact that it's not consistently named can cause confusion, but unlike the regular uninstall option in the mod row; remove allows you to remove both mod and its archive if wanted.

[red48dude]

45 minutes ago, Nagev said:

Hey @red48dude,

We welcome any enhancement suggestions on our github page https://github.com/Nexus-Mods/Vortex/issues

Creating a ticket there will ensure that your enhancement is visible and tracked; given the amount of feedback and data we're getting from our users it's easy for us to lose track of requests. Although please keep in mind that Vortex is being phased out in favour of the Nexus Mods App (NMA), and some features will not be implemented as we wind down; all feature requests on the Vortex repo will be reviewed during the development of NMA, so chances are that even if we don't implement it in Vortex, we might do in NMA.

Not sure I understand what you mean on the mass uninstall bit - the Remove button in the toolbar _is_ the mass uninstall button; I understand that the fact that it's not consistently named can cause confusion, but unlike the regular uninstall option in the mod row; remove allows you to remove both mod and its archive if wanted.

The thing about the remove and the uninstall option under mod status is that one of them uninstalls the mod but keeps it on your mod list listed as a status of Uninstalled. They both actually do different things because Remove on actions will actually just remove it completely from your mod list. I just don't know why there isn't an option to mass do this with multiple mods in the multiple selection tool bar. There is a mass Remove but not mass Uninstall. 
However, now that I know a new app is in development, nothing will probably get added or changed and only fixed. I didn't even know about NMA. Man, it's going to suck when I have to abandon Vortex with 1200+ mods. 

Also, I'd like to report another issue I've been having with Vortex after last update. When I install a mod, and I get a notification to install a mod and click install and go through the entire process of installment whether it's through an FOmod or not, I no longer get the prompt(notification) to Enable. I don't use any Automation settings and sometimes I do mass enables because of Vortex's speed can be slow sometimes and idk why this prompt (notification) doesn't show anymore. 

Edited August 8 by red48dude