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
{{ message }}
This repository was archived by the owner on Aug 1, 2022. It is now read-only.
git:Waterdog-Bootstrap:1.15-SNAPSHOT:fd407a5:301 by md_5
Expected Behavior
To show the disconnect message (such as "Internal Server Error" or "You've been banned").
Actual Behavior
Sometimes did not show the disconnect message. Sometimes it would show, sometimes it wouldn't. Would only show "Disconnected from the server."
Crashdump, Backtrace or Other Files
Describe the bug
Pretty straight forward. The disconnect message is not always shown, and is sometimes replaced with "Disconnected from the server." giving the player no context in which why he or she was disconnected.
To Reproduce
Get 2 accounts and kick someone from the server with a reason.
If kick message shows, attempt again.
Attempt until shown "Disconnected from the server" without a reason.
Screenshots
Server software used:
Pocketmine
Additional context
Pretty small visual problem, that is all. Without proxy shows fine. This is kind of random and you might have to try multiple times to reproduce this bug.
Version of Waterdog
git:Waterdog-Bootstrap:1.15-SNAPSHOT:fd407a5:301 by md_5
Expected Behavior
To show the disconnect message (such as "Internal Server Error" or "You've been banned").
Actual Behavior
Sometimes did not show the disconnect message. Sometimes it would show, sometimes it wouldn't. Would only show "Disconnected from the server."
Crashdump, Backtrace or Other Files
Describe the bug
Pretty straight forward. The disconnect message is not always shown, and is sometimes replaced with "Disconnected from the server." giving the player no context in which why he or she was disconnected.
To Reproduce
Screenshots
Server software used:
Pocketmine
Additional context
Pretty small visual problem, that is all. Without proxy shows fine. This is kind of random and you might have to try multiple times to reproduce this bug.