vortex destroys groups after update

[calscks]

after updating to the latest version, vortex complains about invalid group rules, and claims that some vanilla groups don't exist for whatever reason.

 

 

after "fixing" it, I tried to re-set some of my plugins to the vanilla groups mentioned, because they won't be deleted nevertheless since they're "vanilla".

and then vortex complains about duplicated entries, and errors on loading the userlist.yaml.

 

it seems like vortex completely messes up the userlist.yaml. it claims it couldn't find some vanilla groups yet the groups can be observed in the node tree.

[IKobi]

Just had this happen to me as well, I'll just ignore the error since it makes no sense.

 

The groups it claims don't exist are perfectly fine and listed in the groups, the load order is as I set it too.

[AugustaCalidia]

What happens if you exit Vortex, rename masterlist.yaml and userlist.yaml, and then restart Vortex?

 

What is the version number for your Vortex update?

Edited May 14, 2019 by Augusta Calidia

[IKobi]

What happens if you exit Vortex, rename masterlist.yaml and userlist.yaml, and then restart Vortex?

 

What is the version number for your Vortex update?

 

Honestly when I started Vortex today the warning was gone, I didn't change anything.

[HadToRegister]

I've gotten that Group warning before.

I close it and my groups are still there after I close Vortex and reopen it.

I think it's a quirk, or the yaml file doesn't get read correctly after an update and Vortex freaks out