Description

When a player with a specific role joins the server, he often gets added to the default group without any call. I use the LuckPerms API in some of my plugins to receive Cached data, but never add a player to the default group. The issue happens without any error in console or other information, so I don't know what I did wrong.

Reproduction Steps

Join the server in a Velocity network and you may have been added to the default group.

Expected Behaviour

Sometimes you get added to the default group without any context or call.

Server Details

git-Purpur-1632 (1.18.2) - Velocity 3.1.2-SNAPSHOT (git-7d77bfb5-b184)

LuckPerms Version

v5.4.50 both Velocity and Purpur

Logs and Configs

https://gist.github.com/VerklicktTV/c870f5d5917a67645077609049d2bbde

Extra Details

In some plugins I add/clear MetaNodes of an user

Okay, it also happens on server without any plugins exempt LuckPerms in the velocity network

what does /lp user <name> info show for someone who is supposedly put back in the default group?

what does /lp user <name> info show for someone who is supposedly put back in the default group?

Both in Velocity + Purpur that the player has the default group after rejoining

is that what that command is telling you?

is that what that command is telling you?

Yes, it does

Also happens when you switch servers in velocity network

well luckperms doesnt just change player data for "no reason". one of your plugins must be causing it to do that.

well luckperms doesnt just change player data for "no reason". one of your plugins must be causing it to do that.

I never call a method in my plugins which changes the players group

And as I said it doesn't happen everytime so I think the problem is caused by an error

The weirdest thing is that the default gets added as primary group to the user even if the group the player already has, has a higher weight

I think it still is a bug of LuckPerms but I kinda "fixed" it with a proper group weight configuration