Describe the bug
When loading a new world, an OSC client receives the /avatar/change event after already receiving (resent) avatar parameters. The order of events is not clear. This makes it hard to distinguish between resent parameters and user-interaction driven parameters. There is also no "world changed" event to help with that.
To Reproduce
Steps to reproduce the behavior:
Make sure you have a lot of custom avatar parameters defined
Load a new world
Look at all received events and their order
Expected behavior
When loading a new world, an OSC client should receive the /avatar/change event prior to receiving any other (resent) avatar parameters.
Describe the bug When loading a new world, an OSC client receives the
/avatar/change
event after already receiving (resent) avatar parameters. The order of events is not clear. This makes it hard to distinguish between resent parameters and user-interaction driven parameters. There is also no "world changed" event to help with that.To Reproduce Steps to reproduce the behavior:
Expected behavior When loading a new world, an OSC client should receive the
/avatar/change
event prior to receiving any other (resent) avatar parameters.Info (please complete the following information):