Default Utility Lines Aren't Painted on Walls: Recalculating the Three Costs of Retraining After a Patch from Grenade Bounce Decay

November 17, 2026 at 16:00:09

Every patch, pros retrain default utility. The reason isn't feel—it's the physics of bounce decay. We break down how collision coefficients, air drag, and friction shift your smoke landings, and why retraining is a cost-accounting exercise in time, information, and economy.

Introduction

Every patch, someone asks: why are the pros retraining default utility again? The answer isn't in the training menu—it's in the bounce decay curve of grenades. Trajectories aren't painted on walls; they're calculated.

Section 1: A Bounce Isn't a Tap—It's Three Energy Taxes

A smoke grenade from release to rest undergoes at least two bounces and one roll. On each collision, normal velocity decays by the restitution coefficient, and tangential velocity loses energy to friction. These coefficients aren't constants in the engine—they vary with surface material and impact angle. If a patch touches the collision volume or material parameters of any map, your default smoke landing point drifts.

Concrete example: Mirage CT smoke thrown from CT spawn. First impact on a box, second roll down the CT ramp. If the box's collision height is nudged by 2 units, the incidence angle of the first bounce changes, tangential loss changes, and the final roll distance can differ by half a body width. Half a body width in a default line is the difference between "blocks the angle" and "doesn't."

This isn't mysticism—it's geometry. A default utility line is a set of parabolas with fixed parameters. Change the parameters, and the line breaks.

Section 2: Default Lines Are a Version Contract, Not Personal Feel

Pro teams practice default utility not to "hit the spot" but to "hit the same spot with five players." That demands absolute reproducibility within a patch. But the engine's physics stepping isn't perfect—more bounces mean more accumulated error. So default lines are usually designed with "few bounces, more direct drop"—first impact is the target, or only one bounce.

If a patch alters air drag or gravity by even 0.5%, long throws drift. What you're retraining isn't "feel"—it's recalibrating that contract line.

Take Inferno banana default molotov: thrown from T entrance, target is to burn the CT entrance. The line relies on one bounce then roll to spread. If rolling friction is increased, the fire won't cover fully, and CTs can walk the edge. You think "the fire is smaller," but actually the friction account changed.

Section 3: Retraining Priority—Count Bounces First, Then Distance

Not all lines deserve immediate retraining. Priority depends on two variables: bounce count and flight distance. More bounces = higher patch sensitivity; longer flight = greater air parameter influence.

A practical check order:

  1. Test all default smokes with "two or more bounces" first—these drift most easily.
  2. Then test long-range molotovs—air drag changes hit them hardest.
  3. Finally test direct-drop utility—usually most stable, but collision volume changes directly alter landing.

Example: Ancient mid default smoke from T entrance to mid entrance requires one bounce then roll to the wall base. If the wall base collision volume is thickened, the roll is stopped early, and the smoke fails to block CT entrance. Such changes won't be in patch notes—only retraining reveals them.

Section 4: Three Costs—Time, Information, Economy

Retraining default lines isn't "practice an extra half hour." It has three costs:

  • Time cost: A default line retrained to reproducibility takes at least 50 throws. Across five maps' main defaults, that's a dozen-plus hours.
  • Information cost: During the window when old lines fail, opponents may have adapted to the new patch while you're still using old landings—the information structure of default rounds collapses.
  • Economy cost: Missed utility loses rounds; the chain reaction on half-buys and force-buys costs far more than practice time.

So a pro team's utility coach, after a patch, doesn't read the changelog first—they go into the map and test bounces. They're not calculating "feel"; they're calculating these three costs.

Conclusion

Default utility lines are version contracts, and bounce decay is the fine print. Every patch can rewrite the terms. Retraining isn't diligence—it's stopping the bleed. Next time you see a pro repeatedly throwing the same smoke on an empty server, don't think it's boring—they're re-signing the contract.