Honestly, if you can't fix the ability, rework it.

Get Ogre Here··8 votes·4,525 views

What I'm referring to specifically is Talon's E, Assassin's Path. The ability description reads as follows: "ACTIVE: Talon dashes a maximum of 800 units over the target structure or piece of terrain, with the dash's speed based on his own movement speed." What this description fails to mention is that he will occasionally fail to jump over a wall, even if it's way lower than 800 units.

This has been a bug on Talon probably since his rework came out, and there's been no fix. Although I must give Riot some credit, they did address the problem. @RiotRepertoir stated " I'm not sure about the nature of his E issues, though I know it uses unique tech, so I'd bet it's a difficult issue. I talked to Talon's designer about some of this stuff...". Basically he's saying "We don't know what's going on but we'll try to look at it... eventually."

Somewhere else I saw (Unfortunately I can't find the source) a Riot member state that fixing Talon's E would require a rework to the fundamental coding for pathing in the game, which would be extremely time-consuming and difficult to fix for just one ability so they decided it wasn't worth it. I think it's completely understandable that Riot would make this decision. But now to my main point of this post:

If you can't fix an ability, change the ability into something that functions as intended.

Riot won't change Talon's E, despite it not working right a lot of the time and admitting that they can't fix it. I think it shows their weakness as a company when they just give up on something because they can't make it work. Talon's E is the only situation I'm aware of with this happening, but I have little doubt in my mind that this happens with multiple other abilities in the game.

I know this post was kind of all over the place, but I just needed to get this off my chest. If you want a TL;DR, look at the title/bolded text above.

EDIT: And if you want an example of this bug happening, https://youtu.be/G1WCXQU6nng?t=20

7 Comments

Hethalean6 votes

Wow, I've seen some extreme examples, but jeez that one is insane. Not only does it shoot you back into them... it shoots you so far back out into lane.

ForFoxSakes1 votes

I think it's hard to balance or fix when you cant tell how the player was controlling where his leap goes. It goes towards the mouse cursor and you dont need to click so it could also very well be user error but system wouldnt have a command to confirm

Get Ogre Here2 votes

{quoted}

I think it's hard to balance or fix when you cant tell how the player was controlling where his leap goes. It goes towards the mouse cursor and you dont need to click so it could also very well be user error but system wouldnt have a command to confirm

If you watch a lot of Talon gameplay and/or play him a lot (like me for both of those) you know a lot of the time it's not human error. Just the game fucking up.

ForFoxSakes1 votes

[{quoted}](name=Get Ogre Here,realm=NA,application-id=3ErqAdtq,discussion-id=trukrMER,comment-id=00010000,timestamp=2018-10-11T01:55:23.070+0000)

If you watch a lot of Talon gameplay and/or play him a lot (like me for both of those) you know a lot of the time it's not human error. Just the game fucking up.

I do play talon a lot. I have an acct which mostly uses the blood moon line with him and jhin as some of my most played there. Ive never had issues when my cursor is at the edge of the opposing terrain but can screw up if your cursor is elsewhere closer to the middle of the terrain

Phieldworker1 votes

I mean if you look into the time and money it takes to code you’d understand why this is not #1 top priority.

Leto GT1 votes

Happened to me today. Was so mad.

More from Gameplay

More by Get Ogre Here