-
-
Notifications
You must be signed in to change notification settings - Fork 303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ServerKickEvent isn't being fired. #758
Comments
Bump, someone? |
boh, write on paper discord for support |
They did a total mess with this crap 1.19 update, hate it. |
Can you reproduce this issue on Bungeecord itself? |
BungeeCord's situation is even worse, the kick isn't working anymore. |
I was messing around for testing the new version (1.19) and after some accurate test(s) I'm here to report that ServerKickEvent isn't started if a connected sub_server crashes (or just runs /stop).
Apparently, the issue is gone if /kick (or /ban) and /restart are being executed.
Another thing I saw after some debugging is that the proxy is using PlayerDisconnectEvent if a sub_server goes down (even in /stop) instead of kicking the player.
The issue is here after 1.19 BungeeCord's update.
Waterfall version: 1.19-496
Spigot instances: Paper 1.19-13
The text was updated successfully, but these errors were encountered: