`/v2/wvw/matches/stats`: Wrong kills and deaths

[Taschenbuch]

Current Behavior

wvw/matches/stats returns wrong kills and deaths. example match (millersund world, EU): https://api.guildwars2.com/v2/wvw/matches/stats?world=2206

• kills: the api total KILLS per world are 10-50% lower than they are ingame in the wvw window. This way the total api kills seem to be 1-7 skirmishes too old (2-14 hours too old).
• deaths: the api total DEATHS per world are close to the wvw window values. During the first skirmish right after the match reset they can be a bit lower. Later the api deaths will be HIGHER than the wvw window deaths. (strange)
• when: It is not something that suddenly happens at a certain point during the match up. The kills and deaths are wrong right from the start of the first skirmish of a new match after the reset.
• k/d: because the api kills are much lower and the api deaths are higher than the ingame values, the k/d ratio calculated from api kills/deaths is typcially too low by about 0.1-0.3 for every world (e.g. ingame red 1.0 is api red 0.8)
• delay: sometimes there is no update of the api kills and death for up to 1 hour (i saw that) or up to 4 hours (forum guy reported that). Forum guy thread: https://en-forum.guildwars2.com/topic/86364-wvw-api-real-time-data/?tab=comments#comment-1388883

has been tested for 2 wvw match ups on dates between 15.08.21-21.08.21 at different times. screenshots: left ingame wvw window. right tool that polls the api (kills, deaths, k/d)

at reset 20.08.21:

previous match 15.08.21

Expected Behavior

kills and deaths total and per map should be close to the ingame wvw window values. A delay of 5-15 minutes is okay. But not several hours and the k/d should not be distorted that much

Steps To Reproduce

1. open wvw window ingame.
2. Select 2nd tab "Match Overview".
3. select the "Match History" tab 4 select "Kill/Death (Total)" tab
4. compare it to the result of the api response (replace world "2206" (millersund) with your world or an enemy world) https://api.guildwars2.com/v2/wvw/matches/stats?world=2206

Happening since

not sure. at least some months (forum thread if from november 2020), probably much longer

Anything else?

impact: this affects a lot of wvw websites and tools. examples:

websites

• https://kills.werdes.net/
• https://gw2mists.com/matches/eu
• https://wvwstats.com/match/2-4
• https://wvwintel.com/#2206

tools

• https://github.com/Taschenbuch/Gw2TinyWvwKillCounter
• discord chat bots
• Teamspeak worlds use chat bots/displays to show k/d etc.

script used by twitch streamers

• https://bitbucket.org/GreenyNeko/obsgw2filesystem/src/master/

---

Maybe related, but probably not really: https://github.com/arenanet/api-cdi/issues/417#issuecomment-268643700 Just an interesting note about how lye implemented the tracking bit. Given that he mentioned that it was kind of a legacy diagnostic already back in 2016, might mean that the value is no longer properly tracked almost 5 years later.

[Archomeda]

Just a guess and for @dsnider-anet to check, but maybe it's the outnumbered buff preventing counting the kills/deaths correctly because that buff prevents war score from being granted to the killing color?