[Gameplay] Recall last tick not reacting to damage

PaperMache7·9/24/2014, 2:47:33 PM·2 votes·2,888 views

When damaging a champion while his recall is almost done (during the last 0.25s) the damage won't stop the recall.

I'm aware that this likely due to the way ticks work in this game is silly.

5 Comments

RiotRiot Afic9/24/2014, 3:35:44 PM4 votes

yep, just like your other post (flashing as last tick of morg ult etc.) this will be related to how often the game ticks. Unfortunate side effect of having an online game where the server needs to communicate to the client!

Lumus Avatar9/24/2014, 2:53:20 PM1 votes

As far as I'm aware that has been been part of the game. I have seen Rioters reference it in their explanation of gameplay and they don't seem to intend to change it.

I think your assessment is right. I remember reading that damage is applied at the end of a tick. So if damage and return occur on the same tick, then they will return and then take damage. Something like that - point being that they cannot be interrupted during the last .25 second of the return channel.

ValyrianBlade9/24/2014, 2:59:27 PM1 votes

One could argue the big is that the damage hit the player when they should have based without taking damage :p. In some cases I'm sure people have died immediately upon recall.