In 4.4 you made it so that Recalls would still be interrupted even if the target was shielded. At some point this change was unmade, but I cannot find it documented, so I assume it was accidentally reverted.
Tested for Karma's active shield and Galio's passive shield.
Classic WoW soon1 votesits weird because some shield will do this, and others wont.
Thresh shield does this frequently.
UnboundHades1 votesu need to take above 1 damage(so basically 2+ damage) for the back to be stopped you can test this with deaths dance or just full armor in practice tool against minions.i personally like this because i do ap rakan and get a 900 health sheild and its funny when people try to stop my back with pure damage
Eeyore1 votesI'm fully aware of the logic behind the former feature and the cause of the current bug, but this isn't a debate for whether or not the mechanic is good for the game - only that the mechanic isn't working as (was stated to be) intended.
I personally think shields should not make it so a champion isn't classified as taking damage - especially since I'd wager that isn't applied consistently. Does Mundo still heal when he "hits" a shielded target? Does Leona still gap-close when she "hits" a shielded target? Does Janna lose Boots of Mobility if she's damaged while shielded? Does Garen lose his health regeneration? Recall should be interrupted by taking actions - whether or not the ability deals damage shouldn't even be relevant. If Zilean's Time Bomb or Fizz's Fishbait hit you (two abilities that deal no damage and apply no interrupting crowd control effects at least initially) - you should still have Recall cancelled (and, I believe, both do).
UnboundHades1 votesfizz ulti does do damage with the bleed and zil q does stop backs even if sheilded and think of it this way u are trying to do something then someone tries jumping on you but he hits a wall instead should the thing you where working on be destroyed even if the person didnt touch you(i know its random af but its 2 am and im not creative)