Utility lineups aren't fixed geometry—they're three-stage systems of release point, first impact surface, and bounce margin. When any collision surface gets reworked in a patch, the whole line needs recalibration. Here's a three-layer framework for rebuilding your defaults efficiently.
The same smoke that sealed the door frame last week now only covers seventy percent of it, and your teammate asks if your hand slipped. Most of the time it didn't—your mental default lineup is still sitting on the old version's collision surfaces. A grenade's trajectory isn't a line drawn in the air; it's assembled from three segments: release point, first impact point, and bounce margin. If any one of those judgment surfaces gets re-ground, the whole line has to be relearned.
Layer One: The First Impact Point Is a Surface, Not a Line
New players tend to think of utility as parabola targeting: stand still, aim at the dot, throw, land. In reality the first impact point is a tiny judgment surface. Wall edges, door frames, crate corners—these geometries with thickness determine which face you graze. Half a grid of height difference can turn "slides down the wall" into "clips the edge and bounces back," shifting the landing spot by two or three body widths.
So the first step in relearning isn't memorizing new dots—it's confirming which surface this utility's first impact actually feeds on. My method: in a workshop map with bots off, use the same stance and same aim point for ten consecutive throws, watching only the landing distribution of the first three bounces. If the spread is tight, it's feeding on a flat plane. If it fans out, it's feeding on an edge or corner—this utility has inherently low tolerance, and in matches you need to leave wider sealing margin.
Layer Two: Bounce Margin Decides Whether It Can Be Saved
What happens after the grenade hits the wall is the only part you can still influence. The core reason default lineups need relearning per patch is that bounce margin gets rewritten by geometric detail: slight crate height adjustments, added collision faces on eaves, ground slope friction—all can turn "one bounce lands perfectly in the spot" into "two bounces and it flies past."
I break every default smoke into three numbers: distance from release point to first impact, direction offset angle of the first bounce, and remaining travel from landing to the seal point. The first two decide whether the smoke is stable; the third decides whether it can be saved. The longer the remaining travel, the more it depends on bounces and the more likely it fails after a version change. Short remaining travel is basically "direct-delivery"—lowest relearning cost.
Layer Three: Default Lineups Are a Web—Change One, Ripple Through All
Relearning a single utility is only local. The real headache is that default lineups are connected: when the A-door smoke position shifts, your timing for rotating from A door to mid, your teammate's flash-support rhythm, and the opponent's sightline bandwidth at the anchor all move with it. So my relearning order is: first lock the new landing spot for this utility, then replay your last three demos to see whether its original "blocking task" can be covered by another utility. If it can't, you need to re-schedule it within the whole default web rather than forcing old dots onto new landing spots.
Concretely, I keep a three-column table: utility name, which surface the first impact feeds on, and remaining-travel grade (short/medium/long). Utilities graded "long" get priority relearning the moment a patch drops; "short" ones can wait until last. This way a week of practice time doesn't get spread thin and wasted—it gets pressed onto the few utilities that will actually break.
One last honest note: there is no "permanently correct" default lineup—only the one with the least friction in the current version. Treat utility as a consumable that needs periodic recalibration, not as muscle memory carved in stone, and your utility won't collectively fail on the first match day after an update.