Its 2017 and hooks still do this thing...

YoungFarmer·Feb 27, 2017·34 votes·4,020 views

[zombie-brand-mindblown]

39 Comments

Shuyin178Feb 27, 201716 votes

The hitbox for hooks really needs fixed, I swear it's gotten worse over time. I think part of the issue now a days stems back to when the camera view got changed from that fish-eye effect to what it is now back when SR got updated. Naut, Blitz, and Thresh all have super messed up hit-boxes on their hooks that sometimes feels random.

YoungFarmerFeb 27, 20175 votes

{quoted}

The hitbox for hooks really needs fixed, I swear it's gotten worse over time. I think part of the issue now a days stems back to when the camera view got changed from that fish-eye effect to what it is now back when SR got updated. Naut, Blitz, and Thresh all have super messed up hit-boxes on their hooks that sometimes feels random.

Its like sometimes the hook goes right through you and you're like, "wait that didn't hit me" and the other times it misses by a mile and still hits you.

doiminat0r3600Feb 28, 20171 votes

Even in this clip, the hook went through a minon.

I've seen times where hooks go through our tanks and hit the backline. Like WTF Riot.

SkorchFeb 28, 20171 votes

I mean i dont know if that counted as going "through a minion" as champion hit boxes are much larger the hook hitbox barely clipped the leftmost edge of the champions hitbox but surpassing the blue minion in front of MF, then the hook updates to look attached to MF. Thus technically not going through the minion, but looking like it did.

Unless you are talking about blitzcranks minions in which case id just be sad.

NewGuy101Feb 28, 20171 votes

the hook hit because it (somehow) clips her model. The hook then centers itself into the middle of the model and pulls back. They do this last part for visual clarity because otherwise it would have the model being grabbed by an actual invisible hook (imagine how much angrier it would be if you got hooked and the hook pulling you back wasn't even touching you).

JJI744Feb 28, 20171 votes

For reasons unknown, the hitbox on hooks (possibly other skillshots as well) becomes larger when they reach max range. Making stuff like this possible .Think a red confirmed this a long time ago.

YalathanilFeb 28, 20172 votes

Ikr, as someone who plays blitz support when autofilled, the hitbox on his hooks are really wierd. You can visually clip someone with the hook at max range, but never get the actuall hit.

BjornackFeb 27, 20176 votes

what worse is slow down the video to .25 of the normal speed and watch the hook, there is a second one created to curve off the path to get the target not in range

RavenMagusFeb 27, 20171 votes

It's a clean hit. That's how every hook ability in the game looks like if they hit the very edge of the champion's hitbox, because the animation afterwards has the hook attached to the center of the champion's model as opposed to wherever it landed. Amumu's bandage toss and Thresh hooks both have weird looking issues like that sometimes, but a hit is still a hit.

I honestly don't think this is a bug or anything. It's just a case of the edge of the hook barely clipping the edge of the champion hitbox.

BjornackFeb 28, 20172 votes

{quoted}

It's a clean hit. That's how every hook ability in the game looks like if they hit the very edge of the champion's hitbox, because the animation afterwards has the hook attached to the center of the champion's model as opposed to wherever it landed. Amumu's bandage toss and Thresh hooks both have weird looking issues like that sometimes, but a hit is still a hit.

I honestly don't think this is a bug or anything. It's just a case of the edge of the hook barely clipping the edge of the champion hitbox.

you would actually be called wrong calling this a clean hit. There is no way that rocket grab was even close to the champions hitbox for it to grab as well as minion coverage.

now i could understand what you are saying about hitboxes if the grab connected with the support nami. however this issue with blitzcrank,thresh and even amumu was supposed to have been fixed2 season ago if i remember correctly when riot decided to teak mana barrier on blitzcrank.

if you clearly watched the video at the suggested speed i mentioned then you would clearly see that the rocket grab hitbox clears both nami and miss fortune, but right at the moment of connection you see a bug where the skill shot splits into two rocket grabs where the one that misses nami disappears as miss fortune is grabbed.

the point is not about the champion hit box as it is about the skill shot hit boxes of the hooks, which again like i mentioned before, was suppose to be fixed 2 seasons ago so that the hooks were more acurate with out jump an entire width of the skillshot away.

RavenMagusFeb 28, 20171 votes

{quoted}

however this issue with blitzcrank,thresh and even amumu was supposed to have been fixed2 season ago if i remember correctly when riot decided to teak mana barrier on blitzcrank.

It's been around forever. It's just a graphical inconsistency caused by how the animation is. It's not even a bug at all.

if you clearly watched the video at the suggested speed i mentioned then you would clearly see that the rocket grab hitbox clears both nami and miss fortune, but right at the moment of connection you see a bug where the skill shot splits into two rocket grabs where the one that misses nami disappears as miss fortune is grabbed.

It's not splitting into two. it hits, and then the skillshot hook is replaced by the animation hook, which is automatically attached to the center of the champion's hitbox. It looks strange on an edge case like this, but it's not bugged, and there's no second skillshot or anything.

If you think about it in terms of a Morgana Q, even if the Q hits the edge of your champion's hitbox, the immobilizing circle appears around your champion's center, not the edge where it hits. This is the same, it just looks like it "splits in two" because it's still connected on a string to Blitzcrank.

BjornackMar 1, 20171 votes

{quoted}

It's been around forever. It's just a graphical inconsistency caused by how the animation is. It's not even a bug at all.

It's not splitting into two. it hits, and then the skillshot hook is replaced by the animation hook, which is automatically attached to the center of the champion's hitbox. It looks strange on an edge case like this, but it's not bugged, and there's no second skillshot or anything.

If you think about it in terms of a Morgana Q, even if the Q hits the edge of your champion's hitbox, the immobilizing circle appears around your champion's center, not the edge where it hits. This is the same, it just looks like it "splits in two" because it's still connected on a string to Blitzcrank.

so you clearly do not know that a skillshot that is a straight shot does not curve at the target it is fired at when the target is clearly out of the space the skill shot is occupying at the same time.

the fact that a skillshot jumped off the activated path it was aimed at by the player utilizing it at a target clearly out of the space it was occupying when activated means that in order for the skillshot to make contact with a hitbox that was out of ranged it had to be either a bug,glitch or some sort of hack/script making it hit a mark that wasnt near it. the fact that when slowed down you can see how the skillshot dupicates itself to correct itself and then diabling the original is not natural

RavenMagusMar 1, 20171 votes

Yeah, that's the thing. It didn't jump off the path. There is no jumping. What you're talking about is just a graphical inconsistency (note: inconsistency, not a bug). That "second hook" isn't the hook magically duplicating itself, or magically curving off course. That "second hook" isn't a skill shot at all. It's the graphical equivalent of the Morgana binding circle around your character: it's what you get when the actual skillshot has already hit.

BjornackMar 2, 20171 votes

{quoted}

Yeah, that's the thing. It didn't jump off the path. There is no jumping. What you're talking about is just a graphical inconsistency (note: inconsistency, not a bug). That "second hook" isn't the hook magically duplicating itself, or magically curving off course. That "second hook" isn't a skill shot at all. It's the graphical equivalent of the Morgana binding circle around your character: it's what you get when the actual skillshot has already hit.

no, i would happen to know i am right since they only conceivable way that an issue such as that would not be considered a bug or what not would be if the blitzcrank was lagging and the server was compensating for that issue by making blitzcrank land a hook.

a graphical inconsistency would not be making new assests of itself to jump off a path and you cannot make the comparison to a morgana snare since her snare was created as an oval like projectile that runs on a straight path that was given 2 hitboxes due to the odd nature of an oval that over lapped the with of path it traveled on.

a blitzcrank hook is a square that fits inside the hitbox of the path it travels on making it unable to connect with something outside of its path unless that target is with the hitbox of the path.

i can tell you blitzcranks hooks are a little more on the buggy side then they were last patch since i just played a game as him a day ago with three hooks back to back all on target and they passed through every target, but when i cleanly missed it still jumped off track to hit a target more then 1/4 of the lane away from where i aimed and you call that a graphical inconsistency, more like a bug, since graphical inconsistencies are bugs caused by a misaligned coding problem that will later be hot fixed with a patch that will fix the mistake in the coding of the inconsistency.

RavenMagusMar 2, 20171 votes

By "graphical inconsistency" I mean it looks weird, but within game coding parameters it's actually perfectly normal.

I'm not sure how to explain it any more. If you don't understand what I'm saying, then I'm sorry.

BjornackMar 3, 20171 votes

{quoted}

By "graphical inconsistency" I mean it looks weird, but within game coding parameters it's actually perfectly normal.

I'm not sure how to explain it any more. If you don't understand what I'm saying, then I'm sorry.

im not sure how you dont think that a skillshot fired in one direction but ends up on a seperate path isnt normal for the skill shot.

when you throw a lasso straight it doesnt magically apear to the right of where you were aiming does it.

because nothing about what happened with that hook was normal by any parameters because if it was fired at Qt it would of hit a minion, yet when you look at the champion placements to the skillshot, by all right if it was going to hit either miss fortune or nami, it would of hit nami since she was closest to the hit box yet it connects with the further of the two.

i would of said lucky hook if nami was grab but miss fortune being grab was not possible at all.

and as far as graphical inconsistency goes, if there any inconsistency then it has to do with graphical coding that is making it look wierd so to speak

RavenMagusMar 3, 20171 votes

{quoted}

im not sure how you dont think that a skillshot fired in one direction but ends up on a seperate path isnt normal for the skill shot.

Because that "separate path" is not even part of the skillshot at all. That's my entire point, and what I've been trying to say all along. The skillshot doesn't curve, it doesn't end up on a separate path, there is no second skillshot or second grab.

It looks weird due to how it's coded, but it's not a bug. As weird as it looks, that's just how it is when a hook hits the very edge of a hitbox.

Try it on Cho'gath sometime, as that's the most obvious example. Hit a Cho'gath at the very edge of his hitbox and you will see the graphic snap to the center of his hitbox after landing. AFTER landing.

BjornackMar 4, 20171 votes

{quoted}

Because that "separate path" is not even part of the skillshot at all. That's my entire point, and what I've been trying to say all along. The skillshot doesn't curve, it doesn't end up on a separate path, there is no second skillshot or second grab.

It looks weird due to how it's coded, but it's not a bug. As weird as it looks, that's just how it is when a hook hits the very edge of a hitbox.

Try it on Cho'gath sometime, as that's the most obvious example. Hit a Cho'gath at the very edge of his hitbox and you will see the graphic snap to the center of his hitbox after landing. AFTER landing.

you do realize your point is invalid since again i will point out to how oblivious you are to how the skill shot is reacting to the hitbox, yes i know it snaps to the center of the champion when hitting at the of hot box, that was not the problem.

the problem is how the skill shot reacts to one hit box versus another hit box, as you can clearly see, its not that it creates a second skill shot, its that it forcefully moves it to make it look like it has created a second skill shot when in reality to how the coding is suppose to work with the skill shot is like if you were trying to throw an object on a rope at a target but you aim 5 feet to the right or left of it, then whipping your arm to hit your target at its maximum range.

but then again we are talking about hit boxes. so go back and closely look at where the nearest hit box is at the maximum range for the skill shot at the moment of connection to miss fortune, you can clearly see that if either of the two were to be grab that it would of been nami not miss fortune. that being said look at how Qtie positioned himself to have to only minion block the hook for him, which makes blitzcrank have to aim at nami to make it worth anything.

and again you can clearly see that where the hit boxes were from miss fortune and nami that nami would of been and should of been the one hooked not miss fortune.

i made it a point to mention to slow down the moment of connection to one quarter of normal speed so you can see how fare the skill shot readjusted itself just to him a player that was actually protected by an obsticle as opposed to the other player that was wide open.

this is not the normal behavior of a rocket grab skill shot, there is no reason to try the skill shot on a cho'gath to test hit box activation of the skill shot when we are talk about the correct path the skill shot was suppose to take relative to a hit box that was closer to it the a different one that had variables preventing the connection with a hit box further away.

if you are going to make a point on where the hit boxes for these types of skill shots hit, then explain a clean hook that straight up passes threw a target instead of gabbing them. the answer to that is that their is a bug in the coding that is preventing the correct intended actions of those types of skill shots to act correctly with champion hit boxes.

My point through all this was that there is a coding problem with Rocket grab, death sentence and bandage toss that is causing the skills to act in a manner that was not programmed for them in a first place and it is causing a bug for them to act in these types of manners making the impossible possible for the intended actions of the skills themselves.

RavenMagusMar 4, 20171 votes

It misses the minion and hits Miss Fortune.

It actually looks like it's in line to hit both of them, but Miss Fortune is very slightly more forward than Nami.

The skill shot didn't magically "readjust itself", that's just ridiculous.

That's all there is to it.

BjornackMar 4, 20171 votes

{quoted}

It misses the minion and hits Miss Fortune.

It actually looks like it's in line to hit both of them, but Miss Fortune is very slightly more forward than Nami.

The skill shot didn't magically "readjust itself", that's just ridiculous.

That's all there is to it.

ok so you are saying that you missed the fact that bliztcrank twisted as the skillshot hit miss fortune.

you have got to be pretty blind to not see that the skill shot readjusted itself, and yes it did, and as far as who is further forward is irrelevant, since and i will say it again the only reason miss fortune gets hooks is because of the readjust ment.

i have had this conversation with those that actually know what coding and big issues are and they all agree that this was not how that skill shot should have worked since if you were to of set up the same situation but this time aimed for the miss fortune,the skill shot would of traveled the max distance on its path towards a minion, (which is the first enemy the skill shot needs pull said enemy back to him), and in fact would of been a failed pulled.

but like i said before you refuse to look at how the skill shot actually moves towards the miss fortune who is actually not in hit box range to be grab like nami. its not a problem of who is further up, it is who is closer to the hit bx of the skill shot, which in this case the nami was by all accounts.

and i will make another not to the fixing of this problem that was suppose to be done back in season 5. Riot had also changed the way the hit box for blitzcranks hand was during rocket grab and made it smaller rather then larger to prevent smaller hit boxes such as the ones that belong to minions from being grab when it would of been clear to pass by them.

all i see in your so called points are that you are trying to say there is nothing wrong with any hook similar to rocket grab connecting with an enemy hit box that the hook is not even closer enough for it's own hit box to activate on.

RavenMagusMar 4, 20171 votes

{quoted} ok so you are saying that you missed the fact that bliztcrank twisted as the skillshot hit miss fortune. you have got to be pretty blind to not see that the skill shot readjusted itself

Okay now I think you're just making things up. Now Blitzcrank twitsted himself too?

Yeah, okay. Sure. Why not.

Look, if you just want to say that the hitbox itself is just bullshit/too large and shouldn't have hit, then sure, I'll buy that. That's an acceptable argument. But there was no twisting or turning or double skillshot or magical redirection, that's just silly.

foinhasFeb 27, 20172 votes

blitz hook is a very strange ability to use. You point in one direction, the hook fires in a different direction, only to catch an enemy in a THIRD direction.

9kPluzZFeb 27, 20172 votes

Jesus christ, this guy's voice make want to kill myself

JoseraphFeb 28, 20172 votes

Hit boxes are around the feet, not the actual model.

DarkRitualFeb 28, 20171 votes

Also worth noting, the skilkshot flies through the air, but the hitbox extends to the ground. While not as important in this case, it has been in others.

warpenguin555Feb 27, 20171 votes

Rito please

SkZ DoPeFeb 27, 20171 votes

i was like "ye, but he wins his games anyway instead of me", then i saw the end [zombie-brand-clap]

SkiasFeb 28, 20171 votes

{quoted}

i was like "ye, but he wins his games anyway instead of me", then i saw the end [zombie-brand-clap]

No stopping those EoN assassins in the end

JohnnyNeverSinsFeb 27, 20171 votes

wait for rito to fix it haha

MokkunFeb 28, 20171 votes

Where the server thinks things are, and where your computer thinks things are, are not the same. This causes weird issues with skill shots of all forms, and will as long as we have any average noticeable latency. Add that to the fact that hit boxes in this game have never been 1:1 with ability, or especially champion, size, and the hook re-attach to center point, and you get some really odd visual distortions.

BoilTheOilFeb 28, 20171 votes

this is why i dont play league anymore lazy company

idontgiveabotherFeb 28, 20171 votes

I watched a video on how hitboxes work and that was most likely from the edges of this hitbox. If the ability goes along the edge of the characters hitbox, it's still gonna hit. It is pretty bullshit though, no percentage/specific area the hitbox circle has to be covered for said ability to register. Character models aren't the exact hitbox, although many problems would probably arise from that ahem big boy chogath. Either way thats probably what happened despite it being stupid as fuck.

BlueBilberryFeb 28, 20171 votes

As a support, I have no problem with a hook like that. Perhaps if I had a QTPie to English translation it might help me understand the other side of the equation. :)

DepressedAhriFeb 28, 20171 votes

Animation =/= hitbox.

I have both level 7 Ahri and level 7 Blitzcrank. Certain parts of Ahri's tails are not part of her hitbox, and it's extremely abusable once you learn which parts, because you can dodge skillshots, and it tilts enemies because it "should have hit you."

Blitzcranks hook has a slightly wider hitbox than the animation, with reason. Go into the practice mode as Blitzcrank, with the original skin, and shoot a hook. Notice how small his arm actually is. A good representation of Blitzcrank's actual hitbox would be his hook using Battle Boss Blitzcrank, because it has a wider arm. Wider than the fist, actually.

As for comments about Thresh, I have not played him as much, so I cannot say much for him, but using Dark Star Thresh, there is currently a bug I've noticed from playing against it, where if the hook is to the bottom right of a target, it will search for a target to hit, despite hitboxes. I've only noticed it on this skin.

As for comments about Nautilus, his hook GOES THROUGH targets and IS an AoE hook. Not everyone seems to know this, apparently. My current ADC duo did not, after almost reporting this as a bug. Darius' hook is also AoE and goes through targets.

As for comments about Amumu, I'm unsure if this is an overlooked bug, or if it is a hitbox issue.

MagikarpIsBossFeb 28, 20171 votes

Hitboxes should be matching the animation.

Also, naut hook is not like Darius. It is not aoe and it hits one person. I have never in my life seen it hit more than one person. It also doesnt go through targets. It hits one thing, and then its done.

RacoonHunterFeb 28, 20171 votes

I once had an amumu pull himself to an ally next to me, after throwing his q no where near the champion or myself.. crudly drawn here where X is the two champion and A being amumu with the arrow pointing the direction of the q.. yet it hits one of the two X's.... X X

A ------>

Mighty MorteinFeb 28, 20171 votes

He's right about Naut's hook though. It feels like there's a bit of heatseeking on it sometimes. But to be fair, the hitbox is like.. half a lane wide. It's pretty silly.

HigeMar 4, 20171 votes

actually, it did hit, the minion hitbox is smaller than a champion's

What happened is that Blitz barely aimed a little off from the minion's hitbox and hit what was behind which was MF's hitbox, although it was closer to Nami but she was faster and a bit further away. Of course this is but an edge case that was mere luck, there's no way to actually calculate a minion's hitbox like that and hit something behind it successfully all the time