ggtracker / ggtracker/sc2reader
Question about parsing replay files
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 169
- Forks
- 152
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I'm a computer science student at the University of Adelaide and I am working on a project which focuses on combining the game commentary transcript and replay statistics using GPT to improve the professional player’s efficiency.
I downloaded some replays and parsed them using S2Protocol(https://github.com/Blizzard/s2protocol) and found a lot of information but don't know what to use. I parsed game events but couldn't understand the meaning.
I would really appreciate it if you could let us know how to parse a replay file. For example, where could we find the data for units or buildings, like location, action, clusters, birthtime, dead time, attack/track, abilities, building type, building orders, etc.. Besides, there is still some raw data we can’t figure out the exact meaning of some attributes. We are very interested in knowing where we can find the complete documentation.
Thank you and this repo is so helpful to us who would like to try to analyze data from the SC2 game.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is named. Start with the linked Blizzard S2Protocol repository and the parsed-event example in the issue, then determine whether sc2reader exposes the requested unit and building data. Done would require a concrete documentation path for those fields and clarification of the unexplained raw attributes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100