Open geozukunft opened 12 months ago
Thanks for the report, we'll take a look! Will comment back here when I have more info.
Hi - I was told that basicPings
and genericPings
are not mapped to any data. commandPings
is what they referred to as the "blue generic ping", but they did not specify any details.
I apologize that this is not super helpful, but it's the most info I've been able to track down on these fields so far. If we get more information we'll let y'all know and get the docs updated.
Bug Description
The value for the basicPings field in the ParticipantsDTO of match data responses is 0
Problem Description
The value basic ping shouldn't exist anymore and rather be replaced by the generic ping that got introduced last year as a replacement for basic ping (Note: they are kinda the same they just have a different name)
Expected Result
Either have the number of generic pings used shown under the basicPings field or remove the basicPings field and add the genericPings field.
Actual Result
As said above genericPings are missing and basicPings are always 0 because they no longer exist.
Developer Impact
Player Impact
Describe how this affects League of Legends players. Please include the frequency and severity of the issue.
Preconditions
There are none the issue exists in all games.
Repro Steps
Issue Comments
This seems like an issue where the new generic ping was not properly linked up and therefore match-v5 never gets that data and still has the old field in there which expectetly is always 0.
labels: api: match-v5 scope: lol topic: underlying service type: bug report