A deep dive into the physics of grenade bounces in CS2: how bounce decay and friction coefficients affect landing positions, why default lineups expire each patch, and how to verify your lineups are still viable.
Introduction
The most deceptive phrase in the training room is "I can throw this lineup with my eyes closed." What you can do with your eyes closed is the motion, not the result. From release to effect, a grenade passes through four resolution stages: gravity, air resistance, collision restitution, and friction decay. If any parameter shifts between patches, your "eyes-closed" landing spot moves from the bomb site to the corner. Default lineups need re-practice every patch not because coaches are bored, but because the server's physics ledger changes its decimal points each version.
1. A Bounce Is Not a Parabola, but a Relay of Three Decays
Many think of grenades as the high school physics projectile problem, but the server calculates segmented collisions. On the first ground contact, vertical velocity is multiplied by the restitution coefficient, and horizontal velocity by the friction coefficient; on the second contact, the same coefficients apply again. Even a 0.02 difference in these coefficients can shift the landing point by half a body width after three bounces on a long throw like Mirage mid.
So to judge if a default lineup is outdated, don't just look at the final landing spot—look at the first contact point. If the first bounce is off, everything after compounds. In the training map, marking the wall base is better than marking the landing spot—the landing spot is the result, the first bounce is the cause.
An easily overlooked point: air horizontal velocity decay and ground friction are two separate parameter sets. Your long throw from A ramp to the bomb site uses air-side decay during flight and friction-side decay on landing. If the patch adjusts the latter, you can't compensate by changing your release angle—you must change position or charge rhythm.
2. When Default Lineups Expire, the Timetable Breaks Before Accuracy
Accuracy is an individual issue; the timetable is a team issue. For the Inferno pit封锁, the default lineup assumes the smoke fully blooms at a certain frame and the fire seals the corner at another. If grenade flight time increases by a fraction of a second due to parameter tweaks, it seems harmless, but the attackers' entry timing is based on the old timetable—if they arrive before the smoke is full, it's a free kill.
This is why pro teams' nade books list not just "position + angle" but "position + angle + effect frame." When the effect frame changes, the entire execution sheet shifts forward or backward—not just one grenade, but the synchronization of five players.
3. How to Verify a Lineup Is Still Alive
Don't verify in live matches; there's no control group. Open an offline map, fix your position, throw ten times, and record each first contact point frame by frame. If the variance in contact points is high, your charge rhythm is inconsistent; if all ten are consistent but the landing spot doesn't match your memory, the patch parameters have changed. These two problems have completely different solutions; mixing them in practice only makes things messier.
For regular players, the conclusion is simple: after each major patch, re-record your three to five most relied-upon default lineups. Don't rely on muscle memory to rank up. Muscle memory manages the hand, the physics engine manages the ball.
As for skins—grenade外观 finishes have a dedicated display on C5GAME, but appearance doesn't affect any physics parameters. Don't expect to throw more accurately with a different skin. Feel is psychological, landing spot is server-side; keep these two accounts separate.