u/THE_CLAWWWWWWWWW

TLDR: ability buffering outcomes change depending on whether you had a champ targeted for autoing when using a dashing ability. There are many ways stuff like this can be impactful, but for the sake of brevity please just consider the following. I promise if you go test things related to this you will notice it in many cases.

---

---

In both cases below I will attempt to input E-W-Q.

In the first case I will do it while I am NOT autoing an enemy champion. In the second case I will start the E while autoing an enemy champion.

In case 1, my W and Q both go off.

In case 2, W goes off, Q DOES NOT, and I path back to the original target.

---

Case 1: https://imgur.com/a/TTuI0yj

Case 2: https://imgur.com/a/WyIAAQ2

---

EDIT: W DOES go off in case 2 IF your E remains within riven's attack range.

• https://imgur.com/a/NmMYMR1

TLDR: ability buffering outcomes change depending on whether you had a champ targeted when you cast a dashing ability. There are many ways in which this will show impacts, but for the sake of brevity please simply consider the following.

This is 100% reproducible

Q/E will work in case 1. Q/E will NOT work in case 2.

---

Case 1: The two clips are me pressing R-Q and R-E while not autoing a target.

• R-Q: https://imgur.com/a/35TJmze

• R-E: https://imgur.com/a/fPLFmNI

---

Case 2: The two clips are me pressing R-Q and R-E while autoing a target.

• R-Q: https://imgur.com/a/zZhbv5r

• R-E: https://imgur.com/a/uXdG4Dg

---

The impact and interactions that result from this are varied and quite severe. I just don't have time to go through an exhaustive list of interactions for every champ I have been investigating.

TLDR: ability buffering outcomes change depending on whether you had a champ targeted when you pressed E.

Case 1: https://imgur.com/a/ZrLfeOx I used E->W->Q while not autoing anything. All 3 go off.

Case 2: https://imgur.com/a/8HcVpwp I used E->W->Q while autoing a different dummy. Q does not go off.

I understand that this exact situation isn't the most practical example - but there are other ways this is impactful. Also just a question to see if people here are aware of how this works.

TLDR: ability buffering outcomes change depending on whether you had a champ selected when you pressed Q. This is 100% reproducible.

Case 1: https://imgur.com/a/VGdf7P1 I used W->E->Q while not autoing anything. All 3 go off.

Case 2: https://imgur.com/a/NeSvqlr I used W->E->Q while autoing a dummy. E does not go off.

---

To be clear, this actually impacts many more combos and situations but I am trying to keep it succinct for time purposes.

Consider the following 3 clips:

In the first clip there is no attack target before casting E-Q. ABILITIES WORK

In the second clip there is an attack target and I keep the E blink within attack range of that target: E-Q works.

In the third clip there is an attack target and I E out of auto range of that target: Q does not work. I am still in Q range which should show why that's actually pretty important

1. https://imgur.com/a/R0xoVQy
2. https://imgur.com/a/7SD2R2i
3. https://imgur.com/a/I7CAQ0f

Ahri seemed to be a very interesting case to me when testing how/when you can buffer E and/or q during your ult dash.

Consider the following 3 clips:

• In the first clip there is no attack target. ABILITIES WORK

• In the second clip there is an attack target and I keep the ult dashes in (auto range??): ABILITIES WORK

• In the third clip there is an attack target and I ult out of range of that target: ABILITIES DO NOT WORK.

EDIT: one note I should mention. I am fairly sure autoing minions will not cause this. You just need to have an enemy champion targeted (not actually in auto range of it)

---

In practice what this means is that if you are autoing one target, and then dash away while trying to hit e or q on a different target - you are incredibly likely to find that e and q do not go off. This is 100% reproducible.

Clips below

https://imgur.com/a/LHCZ095

https://imgur.com/a/mluIPGQ

https://imgur.com/a/pgPU1B6

I'll keep this short although I will say that these inconsistencies seem to run much deeper for gragas than my simple example here.

But I have many champions and many interactions to get through.

So I press E->Q->R.

.1. I do this from a position where I do not already have an enemy champion selected. Q and R go off at the end of E.

https://imgur.com/a/p8832qh

.2. I do this from a position where I am autoing an enemy champion. Only one goes off.

https://imgur.com/a/KkPmpvg

---

If you are curious I would appreciate if you tested out more interactions. Gragas felt weird, and it felt that just e-ing in the general direction of an enemy champion would cause q not to go off in the same combo.

For those who have seen my previous posts you're going to love this.

If you want to push back on anything I say I ask that you please watch the two minute video first that shows all of irelias abilities (and items and summoners) interacting.

---

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

TLDW (get off tiktok):

• If you are NOT autoing something before pressing Q on a target 0 then you can smoothly buffer ALL Irelia inputs during the dash.

• If you ARE autoing something before pressing Irelia Q on a target, then ANY input during that dash will NOT go off, and it WILL path you back to the target you were previously autoing.

• There is ONE and ONLY one exception. E1. Let me make this explicitly clear. E2 IS NOT AN EXCEPTION

Q -> E1 -> Q lands -> E2: WORKS AS EXPECTED

Q -> E1 -> E2 -> Q lands: E1 IS SENT OUT, E2 DOES NOT GO OFF. YOU PATH BACK TO INITIAL TARGET.

• edit: summoner spells aren't actually wrong, they're working as they should be. They just have different interactions in general.

---

Link to the previous post for more context:

https://www.reddit.com/r/IreliaMains/comments/1uz1b33/bug_irelia_q_buffering_is_significantly_more/

---

EDIT:

• One thing I realized I didn't think to say in the moment of that video was that unlike the abilities and the item active, the summoner spells do go off. My instinct that it was my expected behavior was actually right because using summoners mid dash will result in whatever your original state was. If you were autoing something you will move to it. If you weren't you just stand still.

• Buffered inputs during a dash that resets upon killing a minion will NOT buffer irelia abilities correctly with the EXCEPTION of Q

EDIT: Updated Findings: https://www.reddit.com/r/IreliaMains/comments/1v09orr/bug_serious_why_double_tapping_e_is_inconsistent/?

---

TLDR: Video here. This is not similar to previous posts I've made regarding Irelia q. https://www.youtube.com/watch?v=u9lYpe4kn54&t=2s

EDIT: I don't think I did a great enough job visualizing the true implications of this. Consider the following 3 target gif if you watched the video: https://imgur.com/a/ToXhGUz.

• Three targets: 1,2, and 3.
• I auto attack 1.
• I press q on 2.
• During that dash I press Q on 3.
• The resulting out come is my champion move commands back to target 1. It doesn't dash or walk to 3 or even stay at 2. my champion walks back to a target that I right clicked multiple inputs ago.

EDIT EXAMPLE 2: I want to further visualize the impact that can occur EVEN KNOWING about this. To preface, regardless of the auto attack setting in options, irelia will always start autoing after the end of a q. Consider the following case, it's a little tougher to follow so if it's unclear just let me know.

I do the following inputs:

• I press q on the first. NO auto.
• During that dash, I press Q on 2.
• During that dash I start to move my cursor to 3.
• My champion lands on 2, and due to the way it works.... my champion AUTOMATICALLY starts autoing it. (this isn't even mentioning that getting an auto in before q animation cancel is almost always the intended play)
• I then Q to 3
• During that dash I buffer Q back to dummy 1.

The current result of this is that:

• Irelia PROPERLY buffers the q from 1 to 2.
• Irelia PROPERLY autos 2 and Qs to 3.
• Irelia PROBLEMATICALLY walks back to 2 instead of dashing (or even moving) to 1.

CLIP: https://imgur.com/a/9DLSsmd

• And before anyone says I missed the last q on target 1 because of how the clip might look, I want to remind you of case 2 in the original video. IF I missed the q, I just would have been stationary autoing target 3. That is NOT what happens.

---

Essentially, if you are trying to buffer q dashes between targets quickly after irelia inputs an auto attack - the buffered second q results in a right click command back to the original target, NOT an actual dash. So instead of the expected behavior: Dashing to the secondary q target, Irelia ends up just walking back to the first entity she was autoing before the initial Q.

The video breaks it down clearly with a keylogger so please watch if you want to say I'm clearly wrong. I can reproduce every case.

---

You might have seen some posts I've made over time where I discuss trying to investigate why - as a very long time high elo irelia main, her q feels fundamentally wrong to me in modern league. While I stand by previous claims, I think this is a fundamental root issue with the champ's fluidity. Pinning it down over time has been a nightmare and so even if you think I am wrong, I just ask that you consider it first - and ask questions if you want to challenge anything I've said.

I am more than willing to put together a better video as well.

---

---

EDITING LIST OF TESTING NOTES:

• It's not specifically related to marks or champions it seems. Autoing a champion, dashing to a minion (within execute range), and then buffering back to the target will also NOT work properly.

• Mana is not consumed on the buffered q that gets overidden - pathing you back to the original right click target.