Boards›Report a Bug

Can't Flash Garen's Damage

Keensense·2/14/2018, 9:30:45 PM·1 votes·573 views

What happened: The last few days I've played a bunch of games vs Garen and every other game I'd have a moment where I flashed and Garen did damage after the flash. I know that a lot of the time melee auto attacks still go through after a flash, but I think that Garen's Q and R have much more leniency towards getting the damage than other abilities.

How to recreate: Flashing over terrain before the Q or R animation from Garen even starts and still getting hit with the damage.

Why this is a problem: I could have saved flash in each of these cases had I seen that I would have been hit with damage anyway.

Possible solutions: Make the animation start earlier, when the damage can't be negated. As it is I can flash before I see any indication that he is about to hit me with Q or R and still get hit with the damage after flashing over terrain. OR Make Garens abilities unable to target champions from over terrain immediately after flashing.

4 Comments

Colgate Gator2/14/2018, 9:34:20 PM2 votes

{quoted}

Possible solutions:

Flash earlier.

Critmaster Garen2/14/2018, 11:05:48 PM2 votes

its a general game mechanic that all ability casts follow through once the animation already started, unless its a channeled ability (like karthus ult).

since garens q and ult animations are rather slow, it can easily happen that the enemy flashes during the animation and the abilities still connect at their new position.

the only way to "fix" that would be to speed up garens q and ult animations and make them almost instantaneous, which id be fine with.

redniwediS2/14/2018, 9:40:08 PM1 votes

Garen's Q is an auto attack modifier, so it follows all the rules of a regular auto attack. Not a lot that can be changed with this one.

There have been times in the past where either Riot tried making the R flashable, or a bug rendered it flashable and breakable by a line of sight change, and the decision was made to return it to it's current state. It's not a bug, it's an intended feature.