Kalstia ult bug -possibly major

JAGMAG·Oct 29, 2015·2 votes·392 views

So i was playing a game were i was Kogmaw bot (monarch kogmaw) with a kalstia and she bound me

I only ulted a enemy once all game usually using it for escape buttttt when i did ult an enemy i went in and even got the knock up before i was sorta knock backed/teleported to were the ult started before i launched and there was no knock backs on their team

i dont have a kalstia player to try and replicate it with sorry :c but it did happen and if it can be replicated its sorta a huge major bug

4 Comments

ZombiemasterOct 29, 20152 votes

This is an intended mechanic of Kalista's ultimate. Whoever she binds with, when they go in with her ult, after the knock up they will be placed away from the target location at a distance equal to their maximum attack range.

So with melee champions, since they don't have a lot of attack range, they essentially stay where they ulted to, but ranged champions will get pushed back a little after the knock up.

JAGMAGOct 29, 20152 votes

ok thanks i guess ive just never seen it with a long ranged champ before

also thou it was a huge displacement so are you sure? like it was closer to kogs w range then his normal auto range and even then i still think it was outside of his w range i had to walk back about 3 steps to get in auto range

ZombiemasterOct 29, 20151 votes

I am sure that is how it works. When using Kalista's ultimate, the launched champion will be put back to their attack range from the target location.

Now, I don't know for sure if it takes into account attack range modifiers like Kog's W or Twitch's ultimate, it's possible that it does. Maybe you had Kog's W active when you ulted and then the duration ran out shortly after you were pushed back, I don't know. Or maybe there is a bug that pushes ranged champions further than it should.

lofi n chillhopOct 29, 20151 votes

it's possible that it used the w range to calculate where he should go, maybe it was active when she ulted you? and either way I kinda think that it should use the base range. so maybe it is a bug after all xD