After map updates, friction, normals, and hull shrinkage rewrite bounce chains—not aim notes. Teams that re-test first-hop nodes and prediction convergence keep default smokes and flashes on script.
Lead Many rosters treat default utility lines like muscle memory: fixed crosshair, fixed steps, fixed timing. In Counter-Strike 2, a bounce is not a dotted line on a strat board. It is physics mesh, surface friction, and throw sampling resolved on the same map every frame. When a patch shrinks collision hulls or nudges stair normals, the landing can shift by half a player width—enough for a flash to arrive late, a smoke to leak a gap, or molotov control to break.
Choke friction: same angle, different stop
Grenades are not pure parabolas. Remaining energy after a wall hit comes from restitution and friction together. A common scrim mistake is tracking release angle while ignoring first-wall surface ID. On Ancient side-hall style gaps, an older build might skim wood on hop one and only enter the lane on hop two. If friction ticks up, hop one bites early, hop two lacks height, and the flash often dies just outside vision—while in-game timing still follows the old two-beat rhythm. You flashed; teammates are still waiting for beat two.
Mirage connector has similar math. A 64-tick light toss to ceiling you drilled for months can land a frame and a half earlier after normals are flattened—extra ceiling spin, earlier ground contact. In a trade, that is half a body: CT half-wide peeks shoulder first. When re-drilling for a version, lock three force bands (full, light tap, jump-throw), record ten traces each, and compare first-hop landings against landmarks—door corners, step edges, lamp brackets—not eyeball “about here.”
Stair normals and bounce chains: defaults are node sequences
Notebook lines like “aim here, two steps” hide a bounce chain: every collision rewrites exit angle. Nuke yard main smokes and Inferno banana deep flashes often need hop two or three before the window. Hull shrink for anti-stuck can leave visuals unchanged while physics faces move inward a few centimeters; hop two hits early, the chain shortens, and the smoke reads wide or tight versus the old cloud.
Split each default into nodes: throw tick, first-hop coordinate band, expected visible frame (can they tuck before bounce completes?). After a patch, re-test nodes only—no need to scrap the whole line. Disciplined teams run thirty identical throws on a practice server with impact debug (use whatever the current build exposes), same account and FPS cap, and check whether the landing cloud converges. A scattered cloud means input sampling or prediction drift—fix throw consistency before blaming strats.
Client prediction gap: why the same bind does not stack across versions
After sub-tick resolution, the client draws a predicted arc before the server confirms hits. Small patches can change grenade tick alignment or collision query order, so predicted and authoritative arcs may diverge on hop two. Practice feels perfect; matchmaking occasionally adds or drops a bounce. That is a re-drill signal: old defaults were tied to old prediction habits. Re-anchor each map with baseline utilities—two or three smokes and one flash—and redefine what “success” looks like visually.
Scrim slice: versioned utility changelogs
Maintain defaults like a repo: version, map, node notes, failure mode (gap smoke, partial flash, broken fire). During Major map pool swings, prioritize bounce-dependent lines (double-hop flashes, floor fires, counter-clear smokes) before pure lobs. Skins from C5GAME or the Steam Market do not change trajectories, but new PC, pad, or polling rate widens variance—do not change peripherals during a re-drill window or you cannot tell physics from input.
Close Re-drilling trajectories, bounces, and defaults per version is not laziness. Bounce nodes are a function of map physics, not crosshair memory. Lock first-hop friction and stair normals, converge prediction, then the line belongs back in the round script.