You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this match, the second player (Karthus) has the number 5008 in the entry for the last selected rune, but 5008 is the code for 'Adaptive force' (see here), which is not a rune, but a rune stat modifier, which is also listed as one of the player's selected rune stat modifiers.
Developer Impact
Frequency: Once every ~200 API calls.
Severity: When it happens, I can't analyze the match, reducing match variety. It also results in many error messages due to invalid data.
Preconditions
Unknown.
The text was updated successfully, but these errors were encountered:
Bug Description
For some LoL matches, the match-v5 API returns codes for rune stat modifiers where the codes for regular runes should be.
Example match: https://americas.api.riotgames.com/lol/match/v5/matches/BR1_2939290530
In this match, the second player (Karthus) has the number 5008 in the entry for the last selected rune, but 5008 is the code for 'Adaptive force' (see here), which is not a rune, but a rune stat modifier, which is also listed as one of the player's selected rune stat modifiers.
Developer Impact
Preconditions
Unknown.
The text was updated successfully, but these errors were encountered: