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
Describe the bug
Good afternoon! This is not the first time I have encountered this problem. Earlier my server was on version 1.21, everything was fine, but after two weeks I began to kick when moving from one world to another world. In the error was the reason for the kick, which indicated a line mentioning packetevents. We updated packetevents and this problem disappeared. With the transition to 1.21.4 in the beginning everything was fine, now, again after 2 weeks I started to kick when moving from one world to another. I will try to attach screenshots below
Software brand
Purpur Version: 1.21.4-2377 and Bungeecord (Flamecord 2.2.9)
Describe the bug
Good afternoon! This is not the first time I have encountered this problem. Earlier my server was on version 1.21, everything was fine, but after two weeks I began to kick when moving from one world to another world. In the error was the reason for the kick, which indicated a line mentioning packetevents. We updated packetevents and this problem disappeared. With the transition to 1.21.4 in the beginning everything was fine, now, again after 2 weeks I started to kick when moving from one world to another. I will try to attach screenshots below
Software brand
Purpur Version: 1.21.4-2377 and Bungeecord (Flamecord 2.2.9)
Plugins
ProtocolLib, MultiverseCore, GrimAC, packetevents, Denizen, LuckPerms, GeyserMC, Floodgate (Purpur server)
SkinsRestorer, packetevents-bungeecord, LuckPerms, PlasmoVoice, GeyserMC, Floodgate (Flamecord server)
How To Reproduce
Expected behavior
A player should not be kicked from the server with an error
Screenshots
https://prnt.sc/jHcjANAvBP_p - the first screenshot (the latest, 1.21.4)
https://prnt.sc/J0ZnOJsOtWxc - the second screenshot (1.21)
Additional context
https://pastebin.com/sYaqdE1A - logs from bungeecord console
The text was updated successfully, but these errors were encountered: