nebulous235 Posted August 6 Share Posted August 6 Vortex says LOOT can't find any metadata for ALL my plugins! Help? 1 Link to comment Share on other sites More sharing options...
Swordofthedragon Posted August 7 Share Posted August 7 same 1 Link to comment Share on other sites More sharing options...
Codykeyman Posted August 7 Share Posted August 7 Yeeep I have the same issue too. very frustrating Link to comment Share on other sites More sharing options...
vortexposer Posted August 7 Share Posted August 7 (edited) Do you meme this https://github.com/Nexus-Mods/Vortex/issues/15929 Changelog: Vortex/CHANGELOG.md at v1.12 · Nexus-Mods/Vortex · GitHub Edited August 7 by vortexposer Link to comment Share on other sites More sharing options...
Nagev Posted August 7 Share Posted August 7 Hi there - first of all, that enhancement is cosmetic, LOOT will still sort your plugins according to the masterlist they provide and your personally defined userlist as it always has. Can you give me an example of a plugin that exists in the LOOT masterlist and Vortex is complaining about it not having metadata? Link to comment Share on other sites More sharing options...
imprimis432 Posted August 7 Share Posted August 7 Still looking for solutions This is not a cosmetic issue, it was working fine, Vortex updated, now LOOT integration is broken and wont autosort and wont get rid of the ongoing issue. I also seem to notice installing mods that would normally prompt a LOOT message that a compatibility patch is needed with the info on where to get the patch is also not occurring. < this seems to be temperamental and ongoing testing is being done. As for an example, imagine this under practically every plugin, I got off lightly compared to the OP in the linked post above who has this issue for 900+ mods. 1 Link to comment Share on other sites More sharing options...
Nagev Posted August 7 Share Posted August 7 Hi there - I guarantee that all of the patches you just posted in your snippet DO NOT have masterlist metadata. To be clear - we are still investigating any potential issues with sorting as part of the 1.12.0 release, but you're latching onto a 100% cosmetic enhancement which has nothing to do with any sorting failures. 1 Link to comment Share on other sites More sharing options...
LeapinL Posted August 7 Share Posted August 7 (edited) I have the same issue. Today when I updated Vortex, I suddenly had all these notes saying That No Metadata could be found for this plugin. It seems to be affecting all types of plugins. I don't know much about loot as I have only used it through Vortex. Almost all "groups" changed to default. I haven't noticed any issues with the load order, but I haven't tried to sort anything today. Edited August 7 by LeapinL 2 Link to comment Share on other sites More sharing options...
Pickysaurus Posted August 7 Share Posted August 7 If you want to check if a plugin exists in LOOT, you can enter it's name and select the game you're playing here: https://loot.github.io/search/ I think the confusion might be that none of these plugins had LOOT info, but Vortex was not showing this message in the last version. This was an enhancement to better inform users that LOOT is not doing anything specific when sorting these (it just uses the master data). 2 Link to comment Share on other sites More sharing options...
Nagev Posted August 7 Share Posted August 7 1 hour ago, LeapinL said: I have the same issue. Today when I updated Vortex, I suddenly had all these notes saying That No Metadata could be found for this plugin. It seems to be affecting all types of plugins. I don't know much about loot as I have only used it through Vortex. Almost all "groups" changed to default. I haven't noticed any issues with the load order, but I haven't tried to sort anything today. @LeapinL - as I mentioned, that message is purely cosmetic and will not affect your LO in any way - what concerns me in your reply however is your statement that almost all groups changed to default, 1.12.0 has no userlist (grouping information) enhancements in place and should have never caused any of the groups to change to default; are you certain that change occurred as part of the update? Can you please send me your userlist.yaml file which can be found inside your staging folder. If privacy is a concern, just send it to me through a forum message. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now