alistar's fancy combo

ShieldmateExcel·9/1/2015, 10:38:43 AM·1 votes·405 views

Since last update on the travel speed of alistars W headbut i have notice some wierd glitchy behaivior when doing it in combination with his Q pulverise. I know this skill combo needs some mastery and can happen to fail, but after maining him the combo is pretty easy. How ever... since the update the whole combo just feels wierd and awkward. Some times the Q fails to connect and pushes the target back, even in one occasion he even knocked up the target and then kocked him back after the knock up duration.

What used to be the great opening on nice team fights is now an awkward skill and just feels pretty wierd. I just want to know if more players have noticed this and if riot might want to look into it.

Greetings ShieldmateExcel

1 Comments

Toastey9/1/2015, 10:56:18 AM1 votes

riot generally has super spaghetti code when it comes to multiple layers of CC + movement. knockups are coded in two parts: a movement block (which prevents right-click movement and dashes/displacements) and a stun (which prevents casting spells or any other player control). in the case of alistar's q, the stun portion slightly outlasts the movement block.

however, when multiple move blocks and stuns are chained, there are gaps in the information sent to the game. sometimes the game chokes and sputters and spits up weird results when trying to add up staggered move blocks, stuns, and displacements. what ends up happening is that people get displaced before the move block is activated but while they're stunned because for some reason the displacement's information was processed first, but the game didn't register that the ability should (or should not) have gone off anyway.

this is where you get weird interactions like tristana getting stunned or knocked up as she's starting rocket jump, then finishing the jump animation anyway. it's also where the famous Unflashable Cho Silence comes from. and unflashable annie stuns, unflashable morg bindings, unflashable ashe arrows--you get the idea. they actually had a big chunk of a patch not too long ago trying to fix this whole "CC crossup" problem, but it obviously hasn't done anything at all.

for now, we're just stuck with buggy interactions between CC and displacements.