Default smokes and flashes are muscle memory tied to first landing, second-bounce normal, and hang height—not pixel-perfect coordinates. When patches shift collision, friction, or grenade gravity, your crosshair reference stays while the smoke lands short. Re-drilling by version means rebuilding an error budget, not replaying a clip.
Lead
Competitive defaults are anchored to three linked cues: where the grenade first touches geometry, the surface normal that sets the second hop, and how high the cloud sits when it blooms. Client-side props look unchanged after a minor build, yet a one-tick change in hull thickness or throw physics can park the same lineup on the wrong side of a ledge. Version-aware practice is about how much landing ellipse you can spend before the round’s utility fails its job—not about memorizing someone else’s POV.
Trajectory segments: don’t merge pre-screen angle with the gravity leg
Most stable pro lines split into two phases. Before the grenade leaves frame, you align off crosshair ticks or screen edges; after release, you trust the parabolic segment to a predicted zone. Preview arcs and server resolution match at short range, but wall bounces inherit material tags—Concrete, Metal, and Wood apply different restitution, so one aim point becomes two landing bands.
When you re-calibrate, widen the target instead of chasing a new wallpaper reference:
- Pre first touch: Note whether standing and crouch-walk share the same release angle; gait shifts muzzle height.
- Post first touch: Slow-mo the first ground contact—glancing side hit versus a square lip strike (steeper normal usually kills second-hop height).
- Terminal: Check if the smoke heart hugs the floor or floats; post-patch lip colliders often thicken by half a unit, so old lines still “look” aligned but bloom low.
Three lines in your notebook beat ten bookmarked duplicates.
Bounce chains: why the same crosshair flips on small patches
Bounces are discrete collision responses, not smooth curves. Incident angle, friction, and velocity caps all clamp. Silent map hotfixes often decouple decorative meshes from the playable hull, or swap prop models under legacy names. You still pre-aim the old crate corner; the first hop lands on a new invisible lip and the second hop jumps quadrants.
Fix acceptance criteria, not a single pixel:
- Functional: One-way still holds, fire seals the choke, flash pops past first cover.
- Geometric: Landing relative to site anchors (default box, light truss, step edge)—roughly a step left or right is enough in-server.
- Timing: Can they still see shoulder line in the 0.2s before bloom? That fails before “full screen smoke” does.
If any axis drifts, tag the line pending re-cal—teammate “still works” is not a test harness.
Version windows: weekly training tables
During Major cycles or map pool swaps, archive lines as map × side × version anchor. Anchors should be lived references—“A-door lintel third course + two crouch steps + jump throw”—with a note on current practice-server feel (does the heart sit on the frame top). When patch notes mention collision, nav, or grenade wording, schedule 30 minutes of bounce-chain spot checks even if your home map isn’t named: three default attacks and two retake smokes per main map, measuring first-hop drift direction only.
In team blocks, treat default line failure as tactical risk in round scripts: if the second contact lacks smoke, default to slow default or exec rather than mid-round aim search. Solo grind prioritizes site seal and mid info lines; fancy routes can wait—they bleed most on material sensitivity.
Close
Throw physics and bounce rules live on the server; sight pictures are client cosmetics. Keeping pre-patch muscle memory is a bet that hulls never moved. Rebuilding defaults per version maps landing ellipses back to functional checks—the clip still plays, but your drift budget was rewritten quietly.