Yasuo Ultimate Mechanical Inconsistency [RIOT CONFIRMED]

ToxZik·8/22/2018, 2:17:00 AM·2 votes·1,288 views

Yasuo's ultimate has five conditions. The first, his ultimate must be in range (obviously), its not global. Second, the target must be "airborne". This means any displacement in the game from Vayne's condemn to Draven's stand aside is fair game to ult off of. Thirdly, Yasuo must have vision on the target, invisible targets, even if airborne, cannot be hit. Fourthly, (when ulting multiple people) champions must be within a certain range of each other. The fifth and final condition is a much lesser known mechanic. Yasuo must be facing the target he is attempting to ult. If Yasuo is running away from the target, the ultimate will not go off. It has come to my attention that not a lot of people are aware of this mechanic. Some are even going as far as to claim that this is a bug.

Yasuo ultimate "bug" (but it's not actually a bug): https://youtu.be/bASBJIL6LVQ?t=1m32s

I spent over an hour live chatting with Riot and 6 Yasuo main's amongst them concluded that this IS in fact how Yasuo's ultimate is supposed to work. However, they also said it was inconsistent. Some people could replicate it easily, some had more trouble. I was personally asked to make this post so that Riot would be aware of this and "Keep an eye on it".

2 Comments

NBOcelot8/22/2018, 7:39:04 PM2 votes

From testing this out for a bit, this seems to be purely a matter of range and not facing at all; when you press R, it's not coded to target the closest valid airborne target, but rather it's looking for valid targets in a large range around your cursor. (Likely so that lower mechanic players can fudge the cast and still get away with it because cast windows can be so small)

If you reproduce your testing but don't go to max range, your clicks near the target (the 'fudge' range ) that check for targets will always find the dummy no matter what your facing is.

The target distance from cursor is the variable you're likely seeing from the Yasuo mains you polled that 'can't reproduce' the issue. If the player has the habit of mouse-hovering the target (or target area) they want, they would never run into this.

For proof, set up a dummy right next to you and hit the tornado. Put the cursor almost a screen away as if you were over there and running away, and press R - you'll see the same results where nothing happens.