-
Notifications
You must be signed in to change notification settings - Fork 8
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
Note GainExperience quirks in documentation #46
Comments
Hi, thank you for the report!
So the
That is a great suggestion, particularly since there are many events in the WebSocket However, this requires enumerating all experience IDs (or all active ones used in the current version of the game) and testing what their If you come across any other exceptions or experience ID reference (particularly for their |
(note: this issue is referring to the documentation at https://auraxium.readthedocs.io/en/latest/api/payloads.html#events, not the github or code documentation)
Some GainExperience events do not look quite how you might expect.
For example, grenade assist experience events (IDs 550-555) unintuitively have character_id = killing player & other_id = player killed. There can be multiple events sent for a single kill if the player killed was afflicted by multiple kinds of grenades. I don't know if there are other kinds of experience events that behave like this.
It'd be useful to have a doc page listing what character_id and other_id pertain to for each experience ID, or at least the weird or non-obvious cases. Perhaps group them by character_id-other_id combinations: killer-killed, player-assisted teammate, no other_id etc.
Could also note somewhere experience events that do not seem to actually get sent.
The text was updated successfully, but these errors were encountered: