-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Admin messages sometimes don't come through. #2890
Comments
Definitely happens, and I've seen similar things happen when you talk (you will say something, it won't show in chat, but others will see it). I suspect it is a BYOND issue, but I'm going to leave this labelled as a bug until we know for certain. |
This occurs with ALL chat messages, not just bwoinks. It tends to happen around the lag spikes. |
Sometimes your messages don't send too. I've had a few times where I say something and it doesn't show up but it was apparently said. Not sure if it happens around lag spikes or not |
This still happens |
Still happens to this day. Not sure if it's fixable. |
It's likely a problem with byond. Baystation has the issue too. |
Do we know if Baystation is tackling this problem, too? Might want to exchange notes with them if they are. |
It's unknown what the cause is. Again, I suspect it's actually a byond issue. |
This can probably be closed, seeing as it's not something that can be fixed. |
Yeah it happens on other servers too. I THINK it might be goonchat related. |
@Henri215 should probably close this, as it's marked as "Cannot/Will not fix" |
Will this lone issue remain open for ten whole years? Find out next time on Paraball Z |
516 might solve it with webview. It is probably an issue with trident. Afaik all servers experience it and lost messages show in logs, it just doesn't get through on the users end. |
What it says on the tin. Sometimes you'll get a message, but you'll just hear the BWOINK noise and not see it. It seems completely random. Other admins/ mentors will still see the message.
The text was updated successfully, but these errors were encountered: