How the Gank Unfolded: A Second-by-Second Timeline

At 22:41 in Game 5, with the series tied 2–2 and Baron about to spawn, the blue-side jungler on Vi began charging Q behind the red-side raptor wall. The enemy mid laner, playing Azir, stood just outside tower range because his team wanted to establish Baron vision before the objective spawned. Eight seconds earlier, the red-side support had cleared a ward in the river brush, but the blue team had already timed that sweep and knew the vision window was about to close. The jungler moved through the lane brush, avoided a control ward in the tribush by hugging the wall, and appeared from fog at 22:44. Azir still had Flash and E available. Instead of flashing immediately, he shuffled toward his tower. Vi’s Q connected, her ultimate locked him down, and the mid laner died at 22:47. Blue team rotated to Baron at 22:52 and took it at 23:10, then ended the game shortly afterward. Analysts paused the replay at frame 22:43. The critical question was whether Azir’s screen showed Vi one frame late or whether his minimap ping was simply misread. Slow-motion replay showed Vi crossing the edge of a ward’s true-sight radius for roughly 0.2 seconds. Some analysts argued that should have been enough for a professional to react; others insisted the ward was placed after the decisive step and never actually revealed the roam. The timeline became the foundation of every later argument because it separated what happened from what players could reasonably have known.

The Vision Question: Did the Ward Actually See the Roam?

The vision debate quickly became the most technical part of the controversy. Red-side support had placed a control ward in the river pixel brush at 22:36 and a yellow trinket in the lane brush at 22:39. In theory, those two wards should have covered the two most common gank paths from the blue-side jungle into mid lane. But the blue jungler did not take either common path. Instead, he used a blast cone to cross the wall behind red buff, landed in the narrow pocket between the raptor camp and the mid lane wall, and entered the lane from an angle that was not fully covered by either ward. The control ward’s true-sight radius did touch the edge of that pocket, but only for a fraction of a second. Frame-by-frame analysis showed Vi visible on the ward at 22:43.4 and disappearing again at 22:43.6. That 0.2-second window was the entire basis for the red team’s claim that the game had failed to display the jungler correctly. Analysts disagreed on what that meant. One group argued that professional reaction time can be as low as 0.15 seconds, so Azir should have reacted if he was watching the minimap. Another group pointed out that players do not stare at the minimap during a Baron setup; they process a dozen audio and visual cues at once. The most damning detail came from the spectator overlay: it rendered Vi one frame earlier than the player clients. That did not prove a bug, but it did prove that viewers and analysts were judging the play with information the players never had. The gank was controversial not because the ward was missing, but because the ward may have seen just enough to create reasonable doubt.

Referee Review: Why There Was No Pause or Rollback

When the red team requested a referee review after the death, officials had to decide whether the gank warranted a pause, a chronobreak, or a post-game ruling. The tournament rules allowed a chronobreak only for a reproducible server error that materially affected competitive integrity. The referee crew checked packet logs, server ticks, fog-of-war calculations, and both teams’ client states. They found no desync, no packet loss, and no evidence that the game had failed to render Vi on the red-side player client. The only discrepancy was in the spectator overlay, which runs on a separate broadcast build and can lag or lead the player client by a frame. Because the player client was consistent, officials ruled that the kill stood and the game would continue. No pause was granted because the game state itself was not corrupted. Analysts were split on that decision. Some argued that when a Grand Final is on the line, officials should pause first and investigate later, especially if there is any doubt about vision rendering. Others warned that pausing after every lost fight would create a strategic loophole: teams could request reviews not to correct errors but to freeze momentum and regroup. The lack of a detailed public explanation after the series made the controversy worse. Fans saw a decisive gank, a brief referee discussion, and then a champion crowned. Without a technical report, speculation filled the gap. The real officiating failure may not have been the call itself, but the refusal to show the community exactly how the call was made.

Meta Fallout: What the Controversy Changes for Future Drafts

The long-term impact of the gank will be felt in draft rooms and coaching sessions for months. First, teams will rethink mid-lane positioning during Baron setups. If an immobile mage like Azir can be killed from a wall pocket that appears warded, then mid laners must either stand closer to their tower or require a support to shadow them until the jungler is located. Second, control ward placement will become more conservative. The river pixel brush is no longer enough if a jungler can use a blast cone to bypass the deepest part of the ward radius. Coaches will demand “buddy system” vision, where a support or jungler escorts the mid laner while wards are being placed. Third, drafts may shift toward mid laners with reliable escapes or champions who can clear vision without face-checking. The controversy also strengthens the case for better broadcast tools. If the spectator client and player client disagree by even one frame, analysts cannot honestly evaluate reaction time. A standardized fog-of-war replay, or a coach challenge specifically for vision bugs, could become a real rule proposal. Finally, the gank will be studied as a case study in information asymmetry. At the highest level, a 0.2-second gap between what a ward sees and what a player processes can decide a championship. The play was not just a mechanical outplay or a vision failure; it was a reminder that modern League of Legends is a game of incomplete information, and the team that manages that information best often lifts the trophy.