Talk:Movement speed/@comment-28582998-20160529020138/@comment-26110806-20160607161300

@92garfield

You're right about the 7.7 limit, but the timeline...

" t = 3, B uses Q => A = 0, B = 0"

I don't think this happens. I remember at the time I didn't fully test how Malphite's Q worked, just enough to know the feat would work, but in theory, the movement speed B steals from A should outweigh the one A steal from B, meaning B's movement speed should be higher than 0. Not nearly as high as after the slow from A wears off, though.

Notice that even though the steal "should" lower the movement speed below 0 and doesn't, that "negative" movement speed is still probably stored there in the event that you try to give it flat movement speed.

However, I can't be sure without testing it in a custom, as in that game, we had a lot of tenacity (couldn't hurt), so the slow on B would have already worn off.

As for the order of casting, I think you nailed it, though  the general formula you presented is a lot slower than reality, especially at the start:

At the time, I made a program in python, just to have an idea of how long it would take to get to a certain movement speed value. I just tested with the actual formula vs ignoring the addition of the base movement speed at every step, and the difference is considerable: To reach 10k, 21 steps vs 149 steps. To reach 1 million, 1155 steps vs 2870 steps. Each step being a Malphite Q. (assuming base movement speed=400, no idea why I didn't just use the actual number)

If you have any more questions, I'll try to check this page from time to time, or you can just pm my youtube acc.