Skip to content
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

Open
sasi2006166 opened this issue Jun 16, 2022 · 5 comments
Open

ServerKickEvent isn't being fired. #758

sasi2006166 opened this issue Jun 16, 2022 · 5 comments

Comments

@sasi2006166
Copy link

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

@sasi2006166
Copy link
Author

Bump, someone?

@FrancyPro
Copy link

boh, write on paper discord for support

@sasi2006166
Copy link
Author

They did a total mess with this crap 1.19 update, hate it.

@Xernium
Copy link
Member

Xernium commented Jun 24, 2022

Can you reproduce this issue on Bungeecord itself?
If yes please move this to upstream.
The update we did wasn’t any higher quality than the Bungeecord update, simply because Waterfall is based on Bungeecord.
I don’t really see how Waterfall could break that event though

@sasi2006166
Copy link
Author

BungeeCord's situation is even worse, the kick isn't working anymore.
On waterfall the issue is partially there, for example in some setups works and on some not, but the issue is there from 1.19 update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants