2

Roadhog's hook is wonky. It's a known thing.

But wonky to the point where he grabs me through walls ? I'm just running behind a wall and I'm getting reeled back to Roadhog.

And no, I'm not lagging when this happens.

  • Can I have an explanation on the downvotes ? – Karlyr Oct 14 '16 at 22:57
  • 2
    Short answer: no. Long answer: it's just latency. – Unionhawk Oct 14 '16 at 23:06
  • There's more to it... But I'll precise the question since it wasn't clear enough. – Karlyr Oct 15 '16 at 1:34
  • This is personal opinion having played him myself long enough, but I feel that Roadhog has a tiny bit of control after throwing the hook which allows him to correct its trajectory in any situation or curve it around walls as you unfortunately notice. It could also be latency between what the enemy sees when they throw the hook and what you see when hit by the hook. – VanBuzzKill Oct 15 '16 at 1:53
  • Curve ? never seen this happen... I've seen a delay before the hook leaves Roadhog's hand compared to when he presses the button. – Karlyr Oct 15 '16 at 2:00
8

First, let's state how Roadhog's hook actually works.

Roadhog's hook has a delay on the Shift press, meaning you can move your cursor a bit after the Shift button press and the hook will launch towards that direction instead of the position where you first pressed shift.

Roadhog's hook doesn't have a "perma hitbox" either. Meaning you can run into a hook and not get grabbed because the hitbox time has expired.

It's also not a hitscan (To debunk the mythical rumor). Hitscan would imply that the hook would instantly acquire a target (even after the Shift delay) which isn't the case since it still has travel time.

The phenomenon that you are experiencing is called "acquisition time". Roadhog's hook has landed on you but has not reeled you in yet leaving a little bit of time for you to move behind a wall. (a bit due to server lag and the prediction system that Blizzard has implemented)

Yes, it feels bad for the player getting reeled in, but it means that Roadhog had a window where he did see you, the hook had a clear path and got you. Everything past that is history.

The othere way that Roadhog could hook you through a wall is because of his hook hitbox. Roadhog's hook hit box has roughly the shape of Soldier-76 being a lot taller than wider. Though not what is described in the question, it might happen that he hooks you from over a wall that's ending just a bit over your head.

In the previous video, Roadhog never even saw the Mei. He threw his hook in the general direction of Mei. Mei then walked nearer to the edge while the hook was traveling towards her.

Clear result : Mei is getting hooked due to both the large hitbox and the fact that the hook has somewhat of a travel time.

|improve this answer|||||
4

As of the new patch (1.7.0.2) on January 24, 2017, Roadhog's hook mechanics have been changed. If you are hooked by Roadhog but somehow manage to get behind cover before he pulls you in (either because your momentum kept you moving or Roadhog was knocked behind a wall and lost line-of-sight to you), the hook will break and you will not get pulled at all. This change drastically reduces the number of "through-the-wall" pulls that happen.

|improve this answer|||||
3

I must disagree with the other answer.

The hook has a huge hitbox.

Check this video at 4:00 for more details. Basically the hook is actually twice as large as the model shows. Soldier is definitely crouching and the shooter is aiming quite high, yet he got hooked.

The hook and the animation have a weird mechanic, and that's why many people were dragged trough walls and across the map before people got teleported to the point where they got hooked. When you hit the button to hook someone, and the croshair is on the target, this doesn't mean that you'll hook them. Nor is the case when the hook starts to fly towards the target. The hit scan actually triggers about half way into the throwing animation. Roadhog kind of points to his target, while throwing, this is the exact moment when he'll hit-scan and hook you. And that's what I'm talking about. (1 minute into the video)

|improve this answer|||||
  • The hitbox is large, agreed. But the 'hitscan' that you are pointing out is just the delay on the key press. Please see : youtu.be/ZblWGZIiCMo?t=15s – Karlyr Oct 14 '16 at 22:04
  • @Karlyr Did you watch this video youtube.com/watch?v=MiC9kRcRz3k&feature=youtu.be&t=62 ? – Иво Недев Oct 14 '16 at 22:05
  • 1
    Yes. I did. To repeat myself : The button press doesn't launch the hook immediately. – Karlyr Oct 14 '16 at 22:07
  • 1
    To send you footage of the same video : youtu.be/MiC9kRcRz3k?t=1m35s . The hook would have landed there if it was a hitscan. If you pause the exact frame the hand is all extended the hitbox of the hook would have landed on the robot. – Karlyr Oct 14 '16 at 22:10
  • In your first video even, warowl says that it has a travel time and it's not an hitscan. – Karlyr Oct 14 '16 at 22:19

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.