-
Notifications
You must be signed in to change notification settings - Fork 16
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
"bound must be positive" when calling getRandomPlayer #49
Comments
From what I can tell on that line, this should only happen if Not too sure, I would have to do some more research myself as well. |
This is all I've got in the logs:
I am running waterfall (fork of bungee). But yea, doesn't make much sense to me either. |
That explains some more, specifically these lines:
I'm pretty sure that should not have happened. The same user somehow disconnected from the server twice despite only being connected once. I could be wrong but I think only one of those messages should have appeared. FirstJoinPlus would have worked properly on the first disconnect it saw (when they timed out), but when it saw the second it resulted in an error since they were already removed from the player list on the first disconnect. Possibly a bug in the server code? I'm assuming this was only a one time occurrence. Again, just not really sure how |
I'll double check, but if I recall it always prints their reason for losing connection (disconnected being the normal way), and then prints whatever is in event#getQuitMessage (which is interesting, because I silence quit messages, so normally for me this would not print). So probably is a server bug(?) since it seems quitevent was called too late? |
I'll investigate more if need be, but I have things to do and may PR a fix later if someone else doesn't find it before me.
The text was updated successfully, but these errors were encountered: