[BUG] attackSpeed value in championStats (MatchV5 Timeline) is faulty/misleading

[citrito]

Bug Description
attackSpeed value in championStats (included in MatchV5 timeline endpoint) is unclear

Problem Description

• Querying the MatchV5 timeline endpoint includes the championStats of each participant for the individual frames
• In the initial frame the attackSpeed value seems to be always 100 across all participants
• It seems like the initial attack speed is taken as reference base value since the attack speed rune shard does not modify this value
• If the point above is wrong, then it is unclear what the value represents as the value is different to the shown game value (attacks per second) and the base attack speed/attack speed ratio values

Expected Result

• assuming that this is not intended: a value closer to the actual representation in-game
• assuming this is intended: help regarding interpretation of this value
• another assumption would be that the value represents the multiplier of following multiplication: base x (1+bonus AS%) in order to determine the game stat value

[DoctressWasTaken]

Attackspeed is always calculated against the base attackspeed of the champion.

Its not like other stats that get added to the baseline when leveling up.

e.g. Cait will have 0.7 base attackspeed at lvl 1 and 0.7 base attackspeed at lvl 18. But she will have +120% attackspeed from levels.

Thats why everything you buy or have in runes is bonus attackspeed.

[citrito]

@LightshieldDotDev Thanks for the insight. Then I am still left wondering why the attack speed rune shard does not have any effect on the shown value. Does the first frame represent the champions in their "raw" state?

[DoctressWasTaken]

Good point, can you give me the matchId for one of the games you looked at?

[citrito]

@LightshieldDotDev Sure! Hope this helps

• KR_5416343612 (region Asia)
• https://www.op.gg/summoner/userName=Cuzzzzzzz (it's the Lee Sin 6/3/10 game, Lee also goes AS Rune Shard, Rakan for example doesn't)

[DoctressWasTaken]

Ye, seems to not include runes in the first frame. He has 113 in the second frame which would account for lvl 2 + the rune

[RiotTuxedo]

The first frame is the starting state for the players. The frame after is the best frame to determine the starting state after modifiers are applied.

[citrito]

@LightshieldDotDev Could eventually determine the starting AS value from the lvl 2 value if the second frame jumps straight to it. Thanks for looking into this

@RiotTuxedo Thanks for the hint and clarifying this