-
Notifications
You must be signed in to change notification settings - Fork 79
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 stuck, creating errors #1507
Comments
could it be that it only happens if a player was killed by an ArcCW weapon and then searched by a detective? |
I can look into it whether ArcCW is the cause. But the above examples come from rounds I played as Traitor against Bots that involved no searching of bodies, certainly not through an Detective. |
ok, but in that case it only happens for the player that searched the body I think |
I tested
I might do some more testing in a few days. |
Okay, thank you. Seems like it isn't what I suspected then. I can check this in two weeks or so when I'm back home |
Removing ArcCW did resolve the issue, though this does not seem to be a common issue with the addon, so I expect some combination of my addons to be the cause. |
If we can fix this and make TTT2 more resilient, we aim to do this |
Your version of TTT2
Workshop version v0.13.2b
Describe the bug
Similar to #1292
After the round ended, multiple clients experienced a scoreboard that does not close. It does not always appear and thus is hard to state the specific circumstances. Only a re-connect or map change resolves the issue. Until a new round starts, names are empty and too few players are listed on the scoreboard.
Context
Server Errors
During startup
During game round
Client errors
The three from TTT2 above, the ArcCW error above with varying call-stacks, the following
Screenshots
In the following, the scoreboard is expected to not be shown.
In the following, only one scoreboard is expected to be shown. Behind "Bot03", one can read "Missing In Action" from the second scoreboard and next to "Bot02", an admin icon from the second scoreboard shines through.
Server console.log
Here is the section of one game round from the
console.log
. Maybe the order or errors and the weapons that were used are of interest.console.log
The text was updated successfully, but these errors were encountered: