Shaco · Matchup · Tale 017
Turning Pyke's All-In
Jul 14, 2026
In this loop
Pyke's hook lands out of the fog and drags Mason's Lux in — the read every lane fears
Ignite comes right back, not to punish the hook, to punish the all-in Pyke has to commit to next
He commits anyway — the backstab auto and Q crit land but don't quite finish him
One more auto closes it out before Pyke can reset
Flash over the wall to get clear, kill banked, Mason still standing in lane
- 0:01Pyke's hook lands out of the fog and drags Mason's Lux in — the read every lane fears
- 0:02Ignite comes right back, not to punish the hook, to punish the all-in Pyke has to commit to next
- 0:03He commits anyway — the backstab auto and Q crit land but don't quite finish him
- 0:05One more auto closes it out before Pyke can reset
- 0:06Flash over the wall to get clear, kill banked, Mason still standing in lane
Pyke fished for a support kill and mailed himself first blood instead.
Level 1, and Pyke gets the read first: hook out of the fog, Mason’s Lux dragged in before either of us can react. The only answer in the moment is Ignite, thrown back not at Pyke’s health bar but at the all-in he now has to commit to, since a hooked Lux at level 1 is dead if nobody shows up. He commits anyway. That’s the mistake I need, because it means I get to commit too: backstab auto into a Q crit, and it’s close but not close enough to finish him solo. One more auto does it, right as Ignite ticks the last of his health away, and I flash over the wall to get clear before his own teammates can answer. Mason lives. Pyke doesn’t. A hook that should have opened bot lane up for Pyke instead hands me first blood off his own all-in, and the disaster read turns into the exact kind of turn a box never even had to be part of. The game still slipped away from us later, but this fight didn’t.