Waterdog
Waterdog copied to clipboard
I don't get a kick message on PreLoginEvent
Version of Waterdog version git:Waterdog-Bootstrap:1.14-SNAPSHOT:23f03cd:275
Expected Behavior When using setCancelReason you should always see a Kick Message
Actual Behavior You don't always see the kick message
Crashdump, Backtrace or Other Files No
Describe the bug If you cancelt the PreLoginEvent and set a cancelreason and then want to join, you don't always see the reason immediately.
To Reproduce Cancel the PreLoginEvent and put a Cancel Reason join on the server and you will see that you don't always see the message. (Only sometimes)
Screenshots
Server software used: Nukkit
Additional context
Can Confirm that
MCPE issue I believe. I think mojang busted the disconnect screens.
Well but when using f.e. Nukkit, deconnect message shows up just fine
Because pocketmine is very broken right now.... Also if you use $player->close() instead of the kick function it usually shows a mesaage!!
On Fri, Sep 20, 2019, 12:28 AM Tobias G [email protected] wrote:
Well but when using f.e. Nukkit, deconnect message shows up just fine
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/yesdog/Waterdog/issues/57?email_source=notifications&email_token=AI5WPOHECESVADKBWVSHVJDQKRGONA5CNFSM4IPNPIZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7FQU5Y#issuecomment-533400183, or mute the thread https://github.com/notifications/unsubscribe-auth/AI5WPOESIZ2BDE4DLBSVDRTQKRGONANCNFSM4IPNPIZA .
Actually this occurs mostly if you kick the user through a bungeecord plugin itself