You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if you impersonate into someone with a luckperms prefix/suffix that in combination with their username is longer than 16 characters (for example if my prefix is 10 characters and my username is 10 characters), it would be longer than 16 characters when you try to impersonate them, causing you to essentially be softbanned until the impersonation is cleared in some way because the game wont let you join with a username longer than 16 characters
this also seems to cause everyone else on the server to disconnect? i wasnt disconnected for some reason (i suspect its because i have /op)
the person with the blue colored prefix is the real person, the one that has the yellow tag is the one impersonating him.
The text was updated successfully, but these errors were encountered:
if you're not planning on fixing this or if it's going to take a long time, can you add a server config or gamerule where we can disable impersonations? I understand that luckperms compatibility isn't a top priority for most devs but being able to disable this would be useful for a lot of people
if you impersonate into someone with a luckperms prefix/suffix that in combination with their username is longer than 16 characters (for example if my prefix is 10 characters and my username is 10 characters), it would be longer than 16 characters when you try to impersonate them, causing you to essentially be softbanned until the impersonation is cleared in some way because the game wont let you join with a username longer than 16 characters
this also seems to cause everyone else on the server to disconnect? i wasnt disconnected for some reason (i suspect its because i have
/op
)the person with the blue colored prefix is the real person, the one that has the yellow tag is the one impersonating him.
The text was updated successfully, but these errors were encountered: