Blizzard / Blizzard/s2client-proto
Anonymized replays - add back tracker events
- Dominant language
- Python
- Stars
- 4k
- Forks
- 440
- PR merge metrics
- No merged PRs in 30d
Description
From a processing standpoint the tracker events allow the user to make heads or tails actions that happened inside the replay without building the game engine.
The events I would like to see added back in are NNet.Replay.Tracker.*
As far as I know there is no personal information or information that would allow something to back fill an account in the tracker events.
Stripping the init data for player information, portrait , and randomizing hotkey usage would be enough to make it very difficult to figure out the actual account.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the protocol definitions for NNet.Replay.Tracker.* and tracing how anonymized replay data is processed. Review the existing handling of player information, portraits, and hotkey usage, then determine how tracker events can be restored without exposing account-identifying data. Done means the requested tracker events are available while the stated anonymization constraints remain intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100