[GAMEPLAY] Movementspeed Buffs are not accurate (Ghost & Predator)
[GAMEPLAY] Movementspeed Buffs are not accurate (Ghost & Predator)
The Movementspeedbuffs Ghost and Predator do not buff the Movementspeed by the said amount in some Key Scenarios.
#I.
Lvl 1 Annie has 335 Movement Speed without any Runes that might Buff it. Lvl 1 Ghost is said in the Tooltips to grant a maximum of 28% MS after 2 seconds of Acceleration.
28% of 335 is by my Calculator and hopefully any other 93,8 However Lvl 1 Annie gains 91 MS. This is actually a lot closer to 27% (27,164..%)
#II.
Lvl 6 Annie has 335 Movement Speed without any Runes that might Buff it. Lvl 6 Ghost is said in the Tooltips to grant a maximum of 33% MS after 2 seconds of Acceleration.
33% of 335 is 110,55 However Lvl 1 Annie gains 104 MS. This is actually a lot closer to 31% (31,044..%)
Here we can see that this is not just about rounding up or down, because then it would be 31 or 32 instead of 33.
#III.
Lvl 1 Annie with Boots of Speed and Predator Keystone has 360 (335 Base + 25 Boots) Movement Speed. Predator active is said in the Tooltips to grant 45% MS after 1.5 seconds of Channeling.
45% of 360 is 162 45% of 335 (Maybe it only Buffs Basemovementspeed? Hint no.) is 150,75 However Lvl 1 Annie gains 156 MS.
#IV.
Lvl 5 Annie with Sorcerer's Shoes and Predator Keystone has 380 (335 Base + 45 Boots) Movement Speed. Predator active is said in the Tooltips to grant 45% MS after 1.5 seconds of Channeling.
45% of 380 is 171 With these Numbers Lvl 1 Annie gains 171 MS.
The same is true for Lvl 1 Annie.
I have tried this over 4 games in practice mode many times. These 4 Examples happened every time I tried to recreate them.
Conclusion
I conclude that there is in Fact a Bug with Movement Speed Calculation, however for some Reason it exists only without Boots and with Boots of Speed. Buying Sorcerer's Shoes negates this Bug somehow.
I find it interesting as I would expect a very exact Number like 33% to hold true. It is very surprising that in this Example the actual Percentage is actually 31%. That is why I think this is a Bug not intended by developers.