-
Notifications
You must be signed in to change notification settings - Fork 117
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
RUI element gets assinged the wrong text #524
Comments
Should this be closed now? |
Still happens, so no. Gave a quick look and it might be due to successive RUI calls overriding the parameters through server to client string commands? Overall, I'd suggest completely getting rid of threading, doesn't seem to be required. Processing a queue of pending RUIs and an array of ongoing RUIs every frame should work fine and keep the code a lot more maintainable in the long run. For sending data, I would suggest packing everything in a single server to client command instead of multiple for each data type. You could probably encode data based on RUI type and read it back (with some sanity checks) on the client. And then directly queue it instead of waiting for the final |
Still happens, has been plaguing me for a while. |
Also would like to say this is not exclusive to |
When I try to execute an announcement with
NSSendAnnouncementMessageToPlayer
at the same time as I executeNSEditStatusMessageOnPlayer
on the same player (same function or function called at the same time) the text from the status message appears in the announcement.This is what the person who killed the player sees (with the wrong text):
and this is what the killed person sees (the right text):
The text was updated successfully, but these errors were encountered: