Skip to content
This repository has been archived by the owner on Jun 19, 2023. It is now read-only.

[Enhancement] Bring More Player Info Across #34

Open
PhlexPlexico opened this issue Apr 4, 2022 · 2 comments · Fixed by #33
Open

[Enhancement] Bring More Player Info Across #34

PhlexPlexico opened this issue Apr 4, 2022 · 2 comments · Fixed by #33
Assignees
Labels
enhancement New feature or request

Comments

@PhlexPlexico
Copy link
Owner

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.

@PhlexPlexico PhlexPlexico added the enhancement New feature or request label Apr 4, 2022
@PhlexPlexico
Copy link
Owner Author

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.

@PhlexPlexico PhlexPlexico linked a pull request Apr 19, 2022 that will close this issue
@PhlexPlexico PhlexPlexico self-assigned this Apr 19, 2022
@PhlexPlexico
Copy link
Owner Author

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.

@PhlexPlexico PhlexPlexico reopened this Sep 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant