Default utility lineups break after patches not because your memory is bad, but because a grenade's memory lives in the engine's collision hulls, not your head. Using the classic Mirage mid jump-throw flash as a case study, this breaks every lineup into three segments—release, bounce, and detonation—and explains why pro teams re-check collision surfaces before they re-test throws.
Let's start with the conclusion: default utility lineups need to be relearned every patch not because your memory is failing, but because a grenade's "memory" was never in your head to begin with—it lives in the engine's collision hulls. What you memorized is the result. What the patch changes is the process.
1. Three bounces of a jump-throw flash: the trajectory is segmented, not continuous
Take the classic jump-throw flash for Mirage mid. Most people picture a smooth parabolic arc. In reality, it goes through at least three distinct "events" in flight:
- Initial velocity and angle at release: there is an extremely narrow window between the jump frame and the release frame. Release inside that window and the grenade inherits a different vertical velocity—the landing point can shift by more than half a meter.
- First collision: after hitting a wall or crate, the bounce vector is determined by the surface normal. Change the normal on a slanted face and the entire bounce angle rotates with it.
- Landing detection box: the flash's "detonation height" before it hits the ground is a box, not a line. The thickness of that box decides whether it pops in the air or on the ground, and the white-screen timing is completely different.
If any of these three segments changes in a patch, your muscle memory goes off-target at the second or third segment. All you feel in a match is "why didn't that flash blind anyone."
2. Collision hulls are the hidden variable: why the same flash is two different utilities across two patches
Visible map geometry and collision geometry are not the same thing. The wall you see may have a collision hull a few centimeters thicker, or an invisible bevel at the corner. Default lineups are "default" precisely because the collision surfaces they depend on stayed stable across multiple patches.
Once a corner's collision hull is reworked, every utility that bounces off it fails as a group. This isn't mysticism—it's geometry. When pro teams relearn lineups, the first step usually isn't "start throwing" but confirming which collision surfaces on that map were changed—because the bounce coefficient and normal direction determine where the whole line goes, not your feel.
3. The relearning ledger: recompute the "segments" first, then the "points"
My advice is to split every default lineup into three segments and relearn them that way, rather than memorizing the whole thing again:
- Release segment: confirm the jump frame, release frame, and standing pixel. This segment is the most stable and usually needs no major changes.
- Bounce segment: confirm the collision surface. This is the disaster zone for patch changes—check it first.
- Landing segment: confirm detonation height and the detection box. This decides white-screen timing and is the most easily overlooked.
The order should be: bounce segment first, landing segment second, fine-tune the release segment last. The release segment is the only variable you can precisely control, so save it for last—otherwise you'll mistake a patch change for your own shaky hands.
4. Final word
A utility lineup is not a contract carved in stone; it's a bill renewed every patch. Every smoke and every flash you memorized has a set of collision hulls and detection boxes vouching for it. When the patch moves, the vouching party changes, and you have to re-sync your watch.
So don't ask "why doesn't this flash work anymore." Ask "which segment did it miss on this time." Get that question clear and relearning becomes something you can actually account for.