6 game breaking Yasuo bugs, some 1 year old.

N00B PWN3R··69 votes·18,566 views

Hi,

I would like to report the following six bugs and would appreciate it if a riot employee replied and shed some light on if and when these bugs will be fixed.


**Yasuo Auto Attack bug after Last Breath: **

After using Last Breath, Yasuo stops auto attacking the target and even if you command him to attack by right clicking on the target, he just stands there for a short period of 1 sec without auto attacking.

https://www.youtube.com/watch?v=c6hipRWEBgQ https://www.youtube.com/watch?v=ov5vMPEriVA

NOTE: This auto attack bug also seems to randomly happen when you E-Q, but it doesn’t happen as often and regularly as with Last Breath.


Yasuo Steel Tempest bug after Last Breath:

After using Last Breath, similar to how it blocks you out from Auto Attacking, it also blocks out the damage from Steel Tempest, you can use Steel Tempest, it goes on cooldown, but it doesn’t register any damage or a stack from gathering storm.

https://www.youtube.com/watch?v=9NkUE9dob7o


Yasuo Tornado Q increased cooldown bug:

After hitting your second Q, which grants you enough stacks of gathering storm and turns your Q in to a Tornado Q, the cooldown is slightly increased before you can use that tornado Q.

https://www.youtube.com/watch?v=uyufBHys5js


Yasuo edge of E-Q combo bug:

When you use E-Q combo and hit enemy units, at the outer part of the ability they will still be knocked up, but take no damage.

https://www.youtube.com/watch?v=9DsODnzKzRs https://www.youtube.com/watch?v=FKWCu9FKCLE https://www.youtube.com/watch?v=rLkMr7bJ9JY


Steel Tempest blind bug:

~~When you are blinded, Steel Tempest misses, while it is not an auto attack or an “empowered auto attack”. The changes to blind in pre-season patch 5.22 didn’t include Steel Tempest in the “these will now be affected by blind” list, take a look at it for yourself: http://na.leagueoflegends.com/en/news/game-updates/patch/patch-522-notes#patch-systems ~~

Also, Steel Tempest used to go through blind, read the ability detail section: http://leagueoflegends.wikia.com/wiki/Yasuo

Steel Tempest is a skill shot ability; this is not working as intended.

EDIT: NVM, working as intended.

Steel Tempest dodge bug:

When Jax uses Counter Strike, your Steel Tempest will be dodged, while it is not an auto attack or an “empowered auto attack”. The changes to dodge in pre-season patch 5.22 didn’t include Steel Tempest in the “these will now be affected by dodge” list, take a look at it for yourself: http://na.leagueoflegends.com/en/news/game-updates/patch/patch-522-notes#patch-systems

Also, Steel Tempest used to go through dodge, read the ability detail section: http://leagueoflegends.wikia.com/wiki/Yasuo

Steel Tempest is a skill shot ability; this is not working as intended.

EDIT: NVM, working as intended.


I hope a riot employee responds, I understand that not replying doesn’t mean a bug report is ignored, but I would like to get some information, because some of these Yasuo bugs are 1 year old!

Thanks in advance.

70 Comments

RiotRiot Exgeniar71 votes

Yo,

  1. Q being dodgeable and missable while blind is intended.
  2. Q3 Cooldown bug, I think I have a fix.
  3. Aa / Q after Last Breath: need to look into it.

~Exgeniar.

N00B PWN3R14 votes

Hello Riot Exgeniar, thank you for your reply.

I will suggest you try to reproduce the following bugs with Berserker Greaves + Shiv so your Steel Tempest has a 1.33 sec cooldown.

Q bug after Last Breath:

  1. Get tornado Q.
  2. Stand pretty far away from your target, so when you use Q, it travels and your Q cooldown starts dropping.
  3. Then use your ultimate when target is knocked up.
  4. Now mid ultimate animation, your Q should be ready for use again, when you slam the target down with your ult, simultanously use Q.
  5. If done fast enough, Q animation wil go off, but it won't do damage nor grant a stack of gathering storm, but it will go on cooldown.

AA bug after Last Breath:

  1. Get tornado Q (have auto attack on and right click on target, before or after using Q)
  2. Use it on target to knock them up (try both methods, standard Q from distance and E-Q combo)
  3. Use ultimate, do not move after ult, tell your target to not move either.
  4. After Yasuo does his ultimate animation and arrives at the ground, he stands there for 1 sec, not auto attacking.
  5. When you are in the air and slam the target down or even after it, you can try to right click on target again, he still won't auto attack for 0.5-1 sec.

I will make videos about these bugs if needed, but not now, later today.

Also, you didn't comment on the E-Q bug when you have a tornado Q ready. The outer part of the circle knocks targets up, but doesn't deal damage. Take a look at the caster minion in this video, gets knocked up, doesn't take damage:

https://www.youtube.com/watch?v=9DsODnzKzRs

Now, which part of this is a bug, I am not sure, it is for you guys to decide based on the range of that ability combo. Either the minion shouldn't be knocked up, or if it is knocked up, it should take damage.

420 Stylish3 votes

[{quoted}](name=Riot Exgeniar,realm=NA,application-id=LqLKtMpN,discussion-id=GuGhiGoh,comment-id=0000,timestamp=2016-02-28T13:01:59.439+0000)

Yo,

  1. Q being dodgeable and missable while blind is intended.
  2. Q3 Cooldown bug, I think I have a fix.
  3. Aa / Q after Last Breath: need to look into it.

~Exgeniar.

Thanks for looking into this. With Yasuo being my go to champion beyond Zed I find it frustrating I can't have a fluent gameplay experience with him, namely the can't AA after last breath or E/Q. With that being said, has anyone used the PROJECT: Yasuo skin and feel that it isn't as smooth going as his classic/High Noon Skin? It feels slower and clunky when compared to his classic(for me at least) and I feel myself choosing classic over PROJECT solely for this reason. Anyone else feel this?

TacoTheKitten2 votes

[deleted]

RiotRiot Exgeniar3 votes

Probably. Sounds unfair.

N00B PWN3R3 votes

When was this change made? I didn't see any notes of it in the patch notes and I recall Steel Tempest being allowed to be used during Last Breath for at least 1-1.5 years after Yasuo's release.

Poske5 votes

[{quoted}](name=Riot Exgeniar,realm=NA,application-id=LqLKtMpN,discussion-id=GuGhiGoh,comment-id=0000,timestamp=2016-02-28T13:01:59.439+0000)

Yo,

  1. Q being dodgeable and missable while blind is intended.
  2. Q3 Cooldown bug, I think I have a fix.
  3. Aa / Q after Last Breath: need to look into it.

~Exgeniar.

Can Confirm The AA/Q after last Breath

In the meantime if you move a little right after you ulti everything is fine. Just make a move command before auto/q

RiotRiot Exgeniar4 votes

Noted. That's important to know. Thanks

AMYS GRAVE3 votes

http://boards.na.leagueoflegends.com/en/c/bug-report/iAHQz0GW-gameplay-so-its-been-over-a-year-and-tfs-w-can-still-pass-through-yasuos-windwall?comment=000000010001

Can you please look into some of the other inconsistencies with yasuo windwall.

Would be nice to know what it works on and what it doesn't.

Copy Pasted from my old post on the subject :

  1. Non-creature objects with travel speeds are stopped by windwall

  2. if it goes off screen it gets a pass...

  3. Naut ult is an exception.

So creature objects should get through? ones like... maokai sapling fizz chum the waters azir soldiers zed living shadow hecarim ult ghosts ...because they don't.

Non creature objects that have travel speeds (and don't go off screen) that should be stopped like ... syndra toss ekko parallel convergence ... but they don't.

Or that ground based projectiles get stopped like ... Aatrox's blades of torment braum's glacial fissure Naut rip tide Zyra grasping roots Poppies new ult Naut Depth charge * (the listed exception) VelKoz Tectonic disruption * (also an exception, the visuals are destroyed but the ability goes through) ... as long as you remember the exceptions.

It's ok, item projectiles are all blocked like ... mikails crucible talisman fotm passive botrk active * ... one of these things is not like the other.

At least ranged auto attacks are consistent being blocked ... Azir soldiers Kayle after using Righteous fury Thresh Vel'Koz Viktor after firing Siphon Power TF pick a card empowered attacks (only some of them i think) ... but they don't. I can almost understand Thresh and Vel because their attacks are part of them, but then Zyra would need an exception too because her AA are her whipping her vines on her hands and drawing them back just like them.

But effects with no travel time get through consistently ... Lee Sin cripple (Cripple is a point blank autotargeted debuff) lulu whimsy (a zero travel time targeted ability) ...with a few exceptions.

Champions are allowed through... blitz grab tahm tongue ...but i guess not all parts of all champions are created equally.

At least when orianna ball interacts with windwall it always does the same thing. it stops there. except if you try to move it through windwall it stops and drops, but if you try to shield an ally and the ball hits the windwall the ball immediately returns to ori because of course it does.

Speaking of player summoned units like ori ball, olaf axe is stopped in place, while thresh lantern is destroyed. Why the difference here?

The exceptions to this ability know no bounds.

Meanwhile braum shield works by its own set of rules entirely where AOE effects still hit braum and his nearby allies, projectiles are no longer projectiles for his shield... Lux shield Draven axes Leona zenith blade Jinx rockets (first one damage mitigation but gets full AOE anyway) Nami bubble Cass miasma Mundo cleavers ... why are these no longer projectiles?

But Braum shield does block non projectiles like... VelKoz Ult Lux Ult Cho Rupture (blocked from center of ability not from cho) ... why? Who knows?

With your three simple rules and all these exceptions memorized you too can understand what "projectiles" are, but remember, they are different for different walls.

EDIT: formatting + links for reference - http://leagueoflegends.wikia.com/wiki/Yasuo/Projectiles http://leagueoflegends.wikia.com/wiki/Braum

UrPalAl1 votes

Is there a chance you can look into Jayce as well? There are so many bugs that I have seen on him now. Sometimes his jump won't allow him to jump over terrain, he just jumps, spins and place, and then falls back down. Other times, Jayce's shockblast fails to explode and grant vision. In addition, sometimes if you fire at a monster, vision isn't granted at all, and you can't jump to the monster as a result (or a person on the other side of terrain).

Sniff1 votes

Ok, this is getting a little ridiculous now, I mean I have waited patiently for over a year now for someone at riot games to fix these bugs. Time and time again a Riot employee has said hey we'll look into them, I immediately think "oh yay progress!" three months after this has been posted here there have been no updates no evidence of bugs fixed in any patch and it's just like come on man. Like I understand fixing bugs in a game isn't a simple task but one full year now, for 6 simple bugs. Yes, league community I am getting salty because this is long waited too long now.Yasuo

Pledgie8 votes

Honestly this post needs more upvotes i thought i was crazy when i tried yasuo for the first time and noticed a couple of these right off the bat.

ModCaptainMårvelous7 votes

Uh ok. These are bugs but these are NOT gamebreaking bugs.

A gamebreaking bug is something like the Rengar EW interaction where Rengar could toss out bolas infinitely. That completely broke the game and made him S+++++ tier. Aatrox becoming invisible after Q is also a gamebreaker.

Yasuo having a bug where his Q might not come out isn't gamebreaking. It's unfortunate but it's certainly not so bad that he warps the entire game because of it.

Slamurai Jack4 votes

I've honestly lost out on probably 100 kills over the 1000 or so games I've played Yasuo because of these bugs. It makes a pretty significant different.

ModCaptainMårvelous6 votes

Significant =/= Gamebreaking.

Gamebreaking, again, would be "After pressing R and then doing a little dance at your keyboard, Yasuo's next Q hits everyone on the map" or "Instantly has 3 stacks". I'm not disparaging that the bug isn't a big deal (In this case yeah, it is) but it's certainly not to the point of breaking the game.

N00B PWN3R5 votes

In my opinion these bugs are gamebreaking for Yasuo, because I miss at least 1 kill every game because of one of these bugs. 1 kill means a lot, especially at higher mmr competitive games.

ModCaptainMårvelous6 votes

Again, still not gamebreaking. Sucks, it could mean a loss, but it doesn't completely break the game.

N00B PWN3R1 votes

Yes, you are right.

RiotRiot Exgeniar12 votes

We have very different definitions of 'game-breaking' . When I say something that's 'game-breaking' , it's probably something that we are going to disable a champion and start a redeploy train on. With that said, these bugs are definitely power impacting, and are considered major defects to competitive players.

N00B PWN3R2 votes

I see, thanks for clearing that up. Power impacting it is.

eve candy5 votes

I knew it that i wasn't bad , it's just Yasuo who deals no damage after ult , and i was dumb enough to not see this. [slayer-jinx-catface]

Spaceplanet4 votes

Oh My God finally someone addressed that issue for the Q tornado being delayed... its really annoying when u can't use it

Ruin Lance4 votes

thanks so much for making this post dude. Yasuo has been like this for way too long and makes him feel clunky to play a lot. Sometimes I even lose games because of these (especially the attacking after ult thing.)

Spaceman5pff3 votes

Oh good! Exactly what we need, effective Yasuo buffs https://pbs.twimg.com/media/BlmMUvoIQAAedfG.jpg

Pledgie22 votes

dude, these are bugfixes.

Spaceman5pff2 votes

Bugfixes that EFFECTIVELY BUFF HIM.

"EFFECTIVE YASUO BUFFS"

Like I know you people play Yasuo, but you must still have enough of a brain to read properly..... right?

TrickMagnet28 votes

imagine being this much of a madbad that you have to cry foul over a champion's kit actually working properly

TrickMagnet20 votes

this is your brain on bronze, kids

Remlap122320 votes

It boggles my mind how these idiots here want a champion to stay bugged because they hate them. That's completely ridiculous.

Wanting a champion to be nerfed extremely hard because their kit is toxic, I understand, but it being literally broken is not the way to do it.

Pledgie6 votes

im pretty sure any and all bugfixes to any champion will "effectively buff" them as you called it

Hyrum Graff5 votes

{quoted}

im pretty sure any and all bugfixes to any champion will "effectively buff" them as you called it

"We fixed a bug where X was doing too much damage."

Sinlaire3 votes

Garen "Fixed a minor mistake in which his damage was scaling on his own health and not his targets"

best one i remember. good times.....

ClownNAround1 votes

Its been said before but i have to comment on something as idiotic as you just said, its a bug, its not effectively buffing him its making it to where he works as intended by riot, there is nothing wrong with bug fixes on any champion, i hope you were joking because this is just another level that i wasnt ready for yet on LOL. [zombie-brand-mindblown]

Xeynid1 votes

Ok, let's be fair here.

it IS an effective buff. Like when Rumble's flamespitter didn't work properly so they buffed the fuck out of its damage, then they made it work properly and Rumble was the most broken top laner in the game for a while. That bugfix was an effective buff, and, depending on the severity of the bug, it can be a huge effective buff.

HOWEVER, if a bugfix would give an effective buff to a champion, then Riot should just fix the bug and nerf the champion afterwards if a nerf is necessary. A champ shouldn't have to have bugs in their kit.

ClownNAround1 votes

But they aren't changing any numbers. Well they shouldn't. That's not required for yas's kit to work properly. Unless a nerf is deserved afterward. There should be 0 number changes. They aren't buffing damage from any single spell or aa. Just making it to where his kit goes off like it's suppose to.

Xeynid1 votes

It doesn't matter that they're not directly changing any numbers. If they fix these bugs, Yasuo will land more Q's that deal damage than he normally would. Yasuo will hit with more abilities and will deal more damage.

If a champion had a bug where every other time they used an ability it did no damage, fixing that bug would double their damage output without changing any numbers. Same principle applies here.

But, like I said, champions shouldn't have bugs in their kits. Yasuo should get these bugs fixed, but it's important to remember that fixing these bugs is a minor buff to him and may mean he needs a small nerf afterwards.

Myer2 votes

Yo my boy thank you for this post.

UltraGigaNiga1 votes

Also, when I ult, occasionally I stay on the spot of where I ulted without traveling to the enemy. This bug has allowed me to kill someone under tower without actually taking any damage from the turret and in other times it has allowed the enemy to escape.

N00B PWN3R6 votes

Last Breath positioning you out of turret range if possible is working as intended.

Stars Shaper1 votes

It doesn't work for me several times >.< I need to learn the conditions for it to happen.

yay nibbers2 votes

It will place you just outside of turret range as long as they are close enough to the edge. If they're closer to the tower rather than the edge of ita range it'll just put you right on them as usual.

Stars Shaper2 votes

Ok, thank you for the infos :)

Flemman1 votes

If bug 1 and 2 are common bug, I imagine that any fix will boost his damage output in a fight by quite a lot (aka breaking the balance) and probably will lead to future power adjustment in his kit.

As I find him pretty ok now, I would prefer that bug to become normal for him (at least for the Q)

N00B PWN3R5 votes

I've played Yasuo since his release and I'd rather have his kit and gameplay be bug free and smooth, if he needs power adjustments after these bug fixes, so be it.

Wimbledofy3 votes

that doesn't makes sense. So what you are saying is that yasuo's Q should remain as is and DO NO DAMAGE AND GO ON COOLDOWN after being used? Imagine your favorite champion, now imagine every time you use your q or ult after using you E or W (or whatever ability) that it does no damage and goes on cooldown.

Flemman1 votes

It's just some though, if no damage q is a very common thing now, maybe it's better to make him unable to use Q (removing the bug and the unfair cd) right after is R than just bugfix it and nerf him hard after just because of the amounth of damage he gain from it.

We saw some champ be nerf for less than that, as I find him balanced atm, I fear random powershift

Wimbledofy2 votes

So now you're basically suggesting yasuo silences himself after he ults. 1 extra Q that he should already have will not make him op.

Flemman1 votes

don't know exactly the damage of a late game yasuo Q but, from memory, it's a lot

I know poeple don't like to think in that way but that's only logic, if you add a good amounth of damage (and easy to land) to a champion who manage to be succesfull without it, you increase his overall damage output during a game and that will lead to futur nerf.

I don't really mind in the end as I don't play him but, if he happens to go out of the line once again despise being balance now, I will probably start to ban him once again (yasuo main already had the "always ban" era, don't think they need a second one :s)

More from Report a Bug

More by N00B PWN3R