Hello! I need help with this API : Halo Wars 2 - Match Events
There seems to be some sort of bug, because not every death is being recorded properly.
Take this match for example.
If I use that API to retrieve that match’s events, especifically the “Deaths” events there are many missing deaths in there. I ended that game with no units, and if you request the events using this ID fd904d6e-5c1e-472f-a95c-b9c0169cd2f6
You will find out that many of my units never registered as dead. I can pinpoint an example to make it easier: Unit with InstanceId = 77 (a jumpack brute) was killed but it never registered as dead, and the events API makes it seem as if the unit lived throughout the whole match.
Couple of things that come to my mind, maybe when an unit dies inside a garrison it doesn’t get registered, or if it dies when falling for example in SENTRY’s bridge it doesn’t get registered either.
Anyways, can somebody help me with this please? I’m trying to wrap up my application but I just found out this bug yesterday and there’s no way to go around it for the moment.
Hi ll Blaky ll!
Thanks for the precise example. We took a look at that unit and agree with your conclusion that it doesn’t seem correct. We’re tracking this internally.
I’m sorry we don’t have a concrete answer for you yet. Thanks again for bringing this to our attention.
> 2533274803816431;2:
> Hi ll Blaky ll!
>
> Thanks for the precise example. We took a look at that unit and agree with your conclusion that it doesn’t seem correct. We’re tracking this internally.
>
> I’m sorry we don’t have a concrete answer for you yet. Thanks again for bringing this to our attention.
Thank you very much for the answer!
I’ve come to track some matches and after doing calculations there are matches where I end up with up to 400 population just out of living units, which doesn’t seem right. I tried to see if maybe units killed by leader powers weren’t being registered but some units do show leader powers as cause of death.
This missmatch happens ONLY in long matches, matches that I end up in less than say 10 - 15 minutes they get recorded perfectly as far as I can tell, it seems that just as matches get longer and longer the kill registration stops working somehow.
Thanks again, please let me know if you guys find out a fix successfully 
The information about this only happening in longer matches is interesting. Thanks for the additional information!
> 2533274803816431;4:
> The information about this only happening in longer matches is interesting. Thanks for the additional information!
Also, I don’t want to make a new thread for this but the game objects metadata API is missing the media tag from a lot of the new units as well as form some units and buildings.
For example Skitterers, Goliaths and new units do not have a media tag.
Some units like neutral sentinels do not exist on the API.
Some units like Suicide Grunts are recorded with a different ObjectTypeId than the one registered on the Game Objects API.
There are some buildings that have a different id as well for example cov_bldg_heavy instead of cov_bldg_light.
Other events like bringing down a base shield (not the building, just the shield) it registers as a vfx_shield death, something like that, but there’s no game object for that.
I’m figuring this out because my app is using the pics for units and buildings and sometimes they do not match so I have to manually look them up using POSTMAN, in the case of neutral sentinels I’m hard-coding the id for ander’s sentinels in the meantime.
Regards!
> 2533274803816431;4:
> The information about this only happening in longer matches is interesting. Thanks for the additional information!
Hello! Any news about this 
Not yet, sorry. I’ll update this thread with news as it becomes available.