Unintended Glitch or Masterclass Tech? the Truth Behind Camille's Flash Move
Camille’s E ability functions in two distinct phases: Hookshot (E1) attaches her to physical terrain, while Wall Dive (E2) propels her toward a designated location, doubling its dash range if steered toward an enemy champion. The controversy centers entirely on the flight path of E2.
Unlike dashes that lock summoner spells until the movement finishes, Camille's Wall Dive permits animation canceling and instant spell queuing. By pressing Flash while airborne, the player creates an instantaneous hitbox displacement. The server evaluates Camille’s stun radius not along the linear path between the wall and her original target destination, but around her coordinates immediately following the Flash teleportation.
[Wall Launch: E2] ══════════════> [Mid-Air Flash] ───> [Displaced Hitbox Stun]
│
└──> Redirects Vector & Eliminates React Window
The underlying code relies on ability buffering. The engine buffers the stun check to execute continuously throughout the dash duration. When Flash occurs, the dash state remains active for the remaining milliseconds of the flight, instantly relocating the active collision circle. If an enemy champion exists within that relocated perimeter upon arrival, the stun registers. It is mechanically identical to Shen’s Shadow Dash Flash or Gragas’s Body Slam Flash, two interactions Riot Games explicitly preserved across successive balance passes.
