Grenade lineups are not fixed coordinates but solutions to the current patch's physics and collision map. Learn why memorizing old demos fails and how to recalibrate by tracking bounce count and final bounce direction.
Introduction
Many players practice grenades by opening an old match demo, copying a landing coordinate, and memorizing it. The problem is you're copying the endpoint, not the process. Every bounce a grenade takes in the air is the result of server physics and map collision volumes working together. When the patch changes, the ledger must be rewritten.
1. Bounces Are Not Reflections, They Are Attenuated Restarts
From release to landing, a smoke may undergo three to five collisions. With each collision, tangential velocity is partially retained, normal velocity is partially absorbed, and a bit of random perturbation is added. This means the landing point's sensitivity to release angle is nonlinear: in the flat-flight phase, a one-degree deviation moves the landing point half a meter; in the bounce phase, a one-degree deviation can move it two meters.
So a default lineup that looks like "stand here, aim here, jumpthrow" is essentially a set of initial conditions that converge under specific parameters. Change the parameters, and the convergence point drifts. Throw the old line, and the smoke still lands, but its edge shrinks toward the side you didn't want.
2. The Three Quantities That Actually Change
First is collision volume height. Many crates and low walls on maps have collision boxes slightly taller or shorter than their models. A grenade grazing the top surface versus hitting the side face leads to two different fates. A patch tweaking one crate's collision volume can kill a lineup you've practiced for half a year.
Second is release point coordinates. Character model, crouch height, and weapon-switch animations all affect the grenade's spawn point. A few centimeters of spawn point shift gets amplified into an entire lineup offset over long throws.
Third is air drag and gravity combination. These two parameters rarely change, but when they do, all parabolas deform globally, and the farthest lineups break first. Close-range smokes still hold, but long-range smokes already leak.
3. How to Relearn, Not Re-Memorize
My approach is not to memorize coordinates, but to record "bounce count" and "the incident direction of the final bounce".
- In an offline map with trajectory display on, run each default lineup three times and see how many bounces it actually takes.
- Remember which surface the last bounce came off and which direction it went.
- During practice, only adjust release height and fine-tune your crosshair, never move your standing position.
This way, after a patch update, you only need to recalibrate the "final bounce" instead of hunting pixel-perfect standing spots from scratch.
4. Patch Health Check List for Default Lineups
After every major update, I pick five most-used default lineups for a checkup: one close-range smoke, one long-range smoke, one jumpthrow molotov, one wall-bounce flash, and one over-the-top HE. Run them once and record the landing offset direction. If two or more of the five offset by more than half a body width, the patch's physics or collision volumes have changed, and all other lineups need rescanning.
Grenades are not knowledge points; they are solutions under the current patch. When the patch changes, the solution must be recalculated. Those who treat old demos as gospel will always be one patch behind.