Garbage data for sourcename?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 161
- Forks
- 68
- Avg merge
- 11d 17h
- Merged PRs (30d)
- 2
Description
hi,
I am trying to understand the parser output. For example:
{
"time": 676,
"type": "DOTA_COMBATLOG_MODIFIER_ADD",
"value": 1,
"attackername": "npc_dota_hero_bounty_hunter",
"targetname": "npc_dota_hero_bristleback",
"sourcename": "npc_dota_hero_lycan",
"targetsourcename": "dota_unknown",
"attackerhero": true,
"targethero": true,
"attackerillusion": false,
"targetillusion": false,
"inflictor": "modifier_bounty_hunter_track"
}
I read this as bounty hunter tracked bristleback, but what has lycan to do with this? What is the sourcename?
Brisleback and lycan are on the same team, so no lotus orb shenanigans.
Contributor guide
No contributing guide indexed for this repository
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 tracing how the parser handles DOTA_COMBATLOG_MODIFIER_ADD events and populates the sourcename field, using the supplied JSON as the reproduction case. Compare the parsed event with the underlying Dota 2 replay semantics to determine whether lycan is expected or erroneous. Done means the field's meaning is established and, if incorrect, the parser output and a regression check are corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100