-
-
Notifications
You must be signed in to change notification settings - Fork 294
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
Scoreboard. Error after player respawn. Sponge. #212
Comments
Did you check wether or not this happens in BungeeCord too? If so you'd report to them instead. |
I reported, but they refused to correct it. |
Bungeecord, and by extension Waterfall, requires tracking stuff like scoreboards properly, your issue here is that you're redefining an objective that already exists, although the objective doesn't exist on the new server until you're creating it, you're sending it while to the client the existing version is still defined, as bungeecord hasn't been able to clean that up yet. It's not really possible to fix this here (Bungeecord needs to be able to handle cases where they didn't connect to the new server, removing objectives too early would cause a crash should the server send data for objectives that don't exist). I would suggest adding some random text to the objective name internally so that you can ensure that they don't match up across server instances. |
I can make a random name for the scoreboard, but in this case I get a memory leak. Thanks for the info. |
I'd recommend naming scoreboards using uuids in this case. |
If I had found a way to delete the old values of the scoreboard, I would not have to write here. |
Reporting an issue does not require you to not have a work-around. ^^ |
I use a static Scoreboard with automatic update of values on the timer. I'm using a server with Sponge API.
After respawn, when the scoreboard is updated, player is thrown from the server, and the following error appears in the BungeeCord console.
https://pastebin.com/kf6UppCz
If you connect directly to the Sponge server (without using WaterFall), then the problem does not arise.
The text was updated successfully, but these errors were encountered: