ggtracker / ggtracker/sc2reader
Missing Player Actions in Event Data and Incomplete Replay Parsing.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 169
- Forks
- 152
- PR merge metrics
- No merged PRs in 30d
Description
I hope this message finds you well. I am writing to seek assistance regarding an issue I am experiencing with the event data and replay parsing in current version.
During my analysis of the event data, I have noticed that player actions seem to be missing. In particular, I am unable to locate specific player actions within the event logs. I kindly request your guidance on this matter and any potential reasons for the missing information.
For example, player Goblin was recorded to have trained three probes in 0:30 ; however, the parsed replay data only revealed one probe train command. I am concerned that I may have missed some crucial information or misinterpreted the data. Could you please help me understand if there is any missing information or if there is a specific way I should be analyzing the replay data to avoid such discrepancies?
I genuinely appreciate your time and attention to this matter. Your expertise will be instrumental in helping me accurately analyze and interpret the data. Please let me know if you require any additional information to assist you in resolving this issue.
Thank you in advance for your support.
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
Start by reproducing the discrepancy with the attached “2022-08-03 - (P)goblin VS (P)Geralt.zip” replay and tracing how its event data is parsed. Compare the recorded three probe-training actions with the single parsed command; done means identifying and correcting the cause of the missing actions, with the result verified against this replay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100