-
Notifications
You must be signed in to change notification settings - Fork 57
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
Servers are unaware of the pos dropdown until next sent message #889
Comments
Dropdown does not send the position until you send a message. Who thought this is desirable default behaviour? |
This change was deliberate. In the past, scrolling through the pos dropdown would spam the server with position change messages (which at this time were still OOC messages hardcoded to say "/pos") and this would flood the chat very quickly. This change was made by @Crystalwarrior in 2.8. See #112 (comment) |
Well, we have a packet to set your position, so we are good to go now! |
Plottwist : That packet is server only. Fuck this application. Hard. Who thought this was a sane decision. |
complains about a change he made himself........... |
In hindsight, maybe a dropdown list was not the best option for this kind of behavior. |
Describe the bug
The position dropdown only sets position locally for the next spoken message. The server is unaware of the client pos until that point, which is really annoying when it comes to checking someone's position in /getarea or when trying to view positional evidence (such as defense/prosecution evidence, or room escape positional evidence for servers like KFO)
To reproduce
Steps to reproduce the behavior:
Expected behavior
Position is set as soon as the dropdown is changed
The text was updated successfully, but these errors were encountered: