Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Garbage data for sourcename? #46

Open
Turmfalke2 opened this issue Jan 4, 2021 · 5 comments
Open

Garbage data for sourcename? #46

Turmfalke2 opened this issue Jan 4, 2021 · 5 comments

Comments

@Turmfalke2
Copy link

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.

@howardchung
Copy link
Member

What match ID was this?

@Turmfalke2
Copy link
Author

5770770321

@howardchung
Copy link
Member

Looking at the match data I don't see anything obvious. If you have the replay try watching it in client and seeing what's going on?

@Turmfalke2
Copy link
Author

I have played that game and I was the bounty hunter.

This is also not a one of issue, every instance of me (bounty hunter) tracking someone has sourcename set to lycan. I would like to understand why this is the case, or what the sourcename is supposed to containe.


$ jq 'select(.type == "DOTA_COMBATLOG_MODIFIER_ADD" and .inflictor == "modifier_bounty_hunter_track") | .sourcename' /tmp/b  | sort | uniq -c
     42 "npc_dota_hero_lycan"

@howardchung
Copy link
Member

It's possible that it's just incorrect data written to the replay and not used by anything. not all fields are used by all combat log events

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants