Yasuo and Jax Q vs E interaction is even more bugged than I imagined and makes 0 sense. Fix this
After some testing in a custom I discovered when Yasuo's Q is dodged by Jax's E and when it isn't. I also added when it SHOULD be dodged and when it should NOT be dodged; as you can see, these don't add up at all and there's bugs on the interaction
Yasuo First and Second Q: Jax will NEVER dodge this even when he's the only/first target being hit. If Jax is the first/only target being hit, the notification "Dodge" will even show up, but Jax still takes the full damage
Yasuo Third Q: Jax will take the knockup no matter what, but will dodge the damage IF he is the only/first target being hit by it, otherwise he will take the full damage.
Now, Yasuo's Q applies on hit effects to the first target only. All other abilities in this game that apply on hit effects are FULLY dodged ALWAYS. This includes Gangplank's Q, Ezreal's Q, etc. Therefore, Yasuo's first and second Q are not working properly vs Jax's counterstrike. However, the third Q is working properly because he dodges it if he is the only target hit but won't otherwise.
What I believe makes more sense:
1st/2nd Q when Jax is only target: dodges damage 3rd Q when jax is only target: dodges damage (I'd argue he should even dodge the knockup, as other on hit CCs are dodged too, like Renekton W and Ezreal Qing with Red buff)
Tl;dr Yasuo's First and Second Qs are bugged vs Jax's E, his third Q works properly
I've made threads before but nothing
, his shadow stopped working for the rest of the match, it still wouldn't be too high on the priority list, because even if it happens every time he buys it, no one is actually building the item on him nor is it even a item he should be building, and if a bug is not high on the priority list they simply wont waste time and resources on fixing them, so just because a bug has been fixed yet, it does not mean Riot is not aware its there, or that they don't care about the game, they just think there are more important things to take care at the moment. Also what is that bug you're talking about?
etc
's w as well
or
since it'd show on-hit damage as an entirely separate number.