You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 19, 2023. It is now read-only.
When Get5 0.9 releases, there will be an array of new units for damage, flash times, etc. This ticket is to track any new stats that we can bring across so we can be as verbose as possible and store plenty of new information based on the match.
The text was updated successfully, but these errors were encountered:
I think the best approach for this new data is to use the OnPlayerDeath event and then maybe store them in a separate table on the API side. That way it doesn't directly interfere with the current stats collection. Maybe we can extend a call from match/%s/map/%d/player/%s/update and include something like match/%s/map/%d/player/%s/update/extras which would give more information based on that round. Displaying the data may be interesting on a front-end, but it should be a way to get player stats and use the API to join on the table, or just use a different playerstats query for the info.
Reopening this as I didn't like the way I was bringing events across. Now with SteamWorks maybe we can just send the whole raw post body as JSON and then set the api key as a header option.
When Get5 0.9 releases, there will be an array of new units for damage, flash times, etc. This ticket is to track any new stats that we can bring across so we can be as verbose as possible and store plenty of new information based on the match.
The text was updated successfully, but these errors were encountered: