A Comprehensive List of Talon Bugs - By Yamikaze, a Challenger Talon One Trick

Yamikaze··45 votes·16,154 views

Hi guys, I'm a challenger talon otp. I have ~2k games on new talon and ~2k games on old talon. Here's a comprehensive? list of bugs for Talon.

  1. The infamous backflip bug. I believe this is a pathing bug but the most common case of this is when you jump from the edge of a turret to the other edge (hard to explain but think from the bottom right of a square to the top right), you will backflip ~60% of the time.

  2. If you jump the bottom right nexus turret on red side, the jump won't go on cooldown and you can jump again.

  3. If you ult too fast after you auto, sometimes you don't get the invisibility from ult.

  4. Sometimes if you die just after you auto, you will still do damage with the auto and proc passive (if you have 3 stacks), but your ult fizzles away instead of closing on the target. Not sure if this is intentional.

  5. Probably not a bug but melee q is 50 range longer than your autos. This feels awful for Talon because if a target is past melee range, you will want ranged q to keep up with them. At that range, melee q is just a self-stun that prevents you from chasing enemies and securing the kill. This also means you can flash into what you think is out of melee range, but still cast melee q and not be in range for the next auto. Happens way too often to every Talon I've watched. Could also just make the auto after melee q faster or extend the range of your next aa if melee q is going to stay longer than your aa range.

  6. ~~ Ranged q is 50 range shorter than it should be.~~ FIXED

  7. Talon R hitbox is inconsistent. In this clip: https://clips.twitch.tv/BoxyInspiringTriangleSeemsGood , yasuo doesn't take damage from the first half of my ult (and the passive stack stays at 1), despite obviously being in the ult range. The passive didn't just reset because I autoed him before I ulted, which refreshed the stack duration. nvm im blind lol

  8. If you ult too close to a yasuo wall, all of your blades disappear, not just the ones in that direction. On the other hand, for rake, each of the 3 blades are coded separately, meaning if yasuo blocks 2 of the 3 blades, the 3rd one still comes back.

  9. Sometimes Talon walks away from a wall if you try to e over it. Probably the same pathing bug as backflip.

  10. Autos after melee q are inconsistent. Sometimes your auto doesn't go off at all, and it's sometimes slower than usual. Makes it hard to time your combos. Shown here (credit to Blood Moon Talon): https://imgur.com/a/uXSzUpR

  11. Visual bug when you e right after you q. The flip animation doesn't play. You can also moonwalk if you combo a certain way but I'm not certain how to reproduce it (e.g. here, after the passive proc on tali: https://clips.twitch.tv/AwkwardFuriousDelicataPJSugar ).

27 Comments

Mordepool5 votes

Love seeing. Bug threads. It gives me hope Riot might act on it some day

AnataBakka1 votes

they did it with quinn, don't know why. It was good for them, but i really hope they will do it for other champs too

they also did it with rengar after they changed his q. They fixed numerous bugs, but not only with his q

Mordepool1 votes

Still waiting on Morde

forist2 votes

I've been having a bug with the aa q aa cancel every once in awhile ever since the rework. If I post a video of this in practice tool, after work tonight, will you take a look at it?

Yamikaze1 votes

[{quoted}](name=Blood Moon Talon,realm=NA,application-id=LqLKtMpN,discussion-id=mV6wFAdY,comment-id=0001,timestamp=2018-05-09T00:09:16.786+0000)

I've been having a bug with the aa q aa cancel every once in awhile ever since the rework. If I post a video of this in practice tool, after work tonight, will you take a look at it?

Yeah sure. I know what you're talking about if it's the second auto not going off. Happens once in a while to me

forist4 votes

Sorry, for the cell phone quality, but here's a quick example of the bug i mean:

https://imgur.com/a/uXSzUpR

You can see in the first rotation that the auto attack counter properly resets after the melee q. However, in the second rotation not only does the auto attack not reset after the q, but talon literally just freezes and stands there for a full 2 seconds before being able to auto attack again.

This bug is super annoying for me when I'm trying to maximize dps with my melee q during an all in. Any thoughts on this or similar experiences?

Yamikaze1 votes

[{quoted}](name=Blood Moon Talon,realm=NA,application-id=LqLKtMpN,discussion-id=mV6wFAdY,comment-id=000100000000,timestamp=2018-05-09T03:11:53.471+0000)

Sorry, for the cell phone quality, but here's a quick example of the bug i mean:

https://imgur.com/a/uXSzUpR

You can see in the first rotation that the auto attack counter properly resets after the melee q. However, in the second rotation not only does the auto attack not reset after the q, but talon literally just freezes and stands there for a full 2 seconds before being able to auto attack again.

This bug is super annoying for me when I'm trying to maximize dps with my melee q during an all in. Any thoughts on this or similar experiences?

Oh, yeah. I've definitely experienced this. It's #10 but I'll include your link for reference. Thanks :)

Demonblade Talon2 votes

There's a few things I think they should change with him. I'll list them

  1. revert his rake and ult
  2. for his Q to turn into a blink when he's in ult
  3. for his passive to change from 'hit 3 abilities then aa to proc' to execution style like old duskblade.(still a bleed, just procs by chunking them to 30% hp)
Yamikaze8 votes

[{quoted}](name=Demonblade Talon,realm=NA,application-id=LqLKtMpN,discussion-id=mV6wFAdY,comment-id=0004,timestamp=2018-05-09T00:54:46.062+0000)

There's a few things I think they should change with him. I'll list them

  1. revert his rake and ult
  2. for his Q to turn into a blink when he's in ult
  3. for his passive to change from 'hit 3 abilities then aa to proc' to execution style like old duskblade.(still a bleed, just procs by chunking them to 30% hp)

Just because you don't like new Talon doesn't mean he needs a revert :)

DuskDaUmbreon1 votes

5 is not a bug. Also probably isn't terribly bad, since 9/10 times you'd want the dash, it's for an additional auto for a kill. Since your Q does more than your autos, doubling the damage on it really shouldn't have any serious impact on you.

8 is probably because they end up spawning inside the wall's hitbox. So that's not a bug, but just a normal interaction (Projectile is destroyed on hitting Yasuo's wall) that seems odd.

And, for 7, that's probably some weird interaction where Yasuo isn't inside Talon's blades from his ult during any tick for it. If he passes through it just at the right time, it's entirely possible that Yasuo might not actually be within any of his blade's hitboxes when it checks for collision. Which is probably less a bug and more just a weird, once in a lifetime interaction.

Yamikaze2 votes

{quoted}

5 is not a bug. Also probably isn't terribly bad, since 9/10 times you'd want the dash, it's for an additional auto for a kill. Since your Q does more than your autos, doubling the damage on it really shouldn't have any serious impact on you.

8 is probably because they end up spawning inside the wall's hitbox. So that's not a bug, but just a normal interaction (Projectile is destroyed on hitting Yasuo's wall) that seems odd.

And, for 7, that's probably some weird interaction where Yasuo isn't inside Talon's blades from his ult during any tick for it. If he passes through it just at the right time, it's entirely possible that Yasuo might not actually be within any of his blade's hitboxes when it checks for collision. Which is probably less a bug and more just a weird, once in a lifetime interaction.

5 is really bad but I agree it's not a bug. Melee q is a self-stun past melee range because you can't follow up with an auto afterwards, meaning you also don't get the passive proc (the standard talon combo ends with q-aa). Talon's auto range after melee q should either be increased or melee q should be decreased.

8 is a bug because each of Talon's blades in ult should be coded individually (like the 3 blades for w, but they're all coded as the same, meaning they all disappear if one hits the wall.

7 i just didn't notice the ult did damage lol. my b

Ðiamant1 votes

Another huge problem with Talon's E that doesn't happen as often but is just as frustrating is with player made terrain. trying to use E when next to player made terrain sometimes results in him standing still, backflipping, or just walking back and forth, can happen with anything from Azir wall to Jarvan ult or Trundle pillar. More of an extension of Bug 9.

Yamikaze1 votes

{quoted}

Another huge problem with Talon's E that doesn't happen as often but is just as frustrating is with player made terrain. trying to use U when next to player made terrain sometimes results in him standing still, backflipping, or just walking back and forth, can happen with anything from Azir wall to Jarvan ult or Trundle pillar. More of an extension of Bug 9.

Hm.. yea probably a bug but I find it's pretty easy to play around it by spamming e while moving your mouse around in the general direction.

Ðiamant1 votes

It's the delay that gets me, that time spent button mashing and moving your mouse could be time spent running away and not getting cc'd

1RiceBowl1x1 votes

For number 2 did you mean the bottom right nexus turret?

also theres a visual bug for when you E (usually during combat/right after combat) you dont go over the terrain but "through" it.

Yamikaze3 votes

{quoted}

For number 2 did you mean the bottom right nexus turret?

also theres a visual bug for when you E (usually during combat/right after combat) you dont go over the terrain but "through" it.

Yeah that bug happens when you e right after you q. Also, yes. Forgot to mention nexus turret lol

Andevar1 votes

Ah the infamous E bug...the amount of times I've lost a kill or died because of it...

And for the melee-Q, I've always thought of it as Talon thrusting the blade, thus having a longer range compared to him just slashing with it.

Ðiamant1 votes

For 11, the moonwalk is caused by tiamat active from my experience

Suffer1 votes

I was able to trigger the moonwalk before I started buying tiamat on Talon though, so it is probably not because of it.

Yamikaze1 votes

{quoted}

For 11, the moonwalk is caused by tiamat active from my experience

Yeah that could be it. I don't think I've seen it until I started buying tiamat a few months ago.

AidanWR1 votes

I believe number 4 is intentional due to the fact that the blades don't converge on him if he dies while in ult, but I could be reading the situation that you laid out wrong

Yamikaze1 votes

{quoted}

I believe number 4 is intentional due to the fact that the blades don't converge on him if he dies while in ult, but I could be reading the situation that you laid out wrong

The thing is, when this happens, your auto and passive will proc, but your ult won't. Since your auto went off, this means the blades should converge because you died after you autoed. But they don't.

AidanWR1 votes

Yeah, I did read the situation wrong. It should converge

Andevar1 votes

The moonwalk has something to do with rake I'm pretty sure. It usually happens when you take right after an auto or a melee Q (I think? Probably should check).

AnataBakka1 votes

it would be nice if you had videos for more of those bugs 3. But do the blades converge? 8. How close? 9. I didn't understand this one 11. Video? 11.2. Every champion moonwalks after patch 7.22

anyway, feels nice seeing another list of bugs. Let's summarize, we have morde, illaoi, heimerdinger, sion and now talon. Won't take long till the entire game becomes a bug. What if we made a team comp of these champs?

Daddy FeedLord1 votes

wow challenger say hi to qt for me will ya lol

More from Report a Bug

More by Yamikaze