CS2 reads tangential speed and wall thickness on bounce two—not your crosshair screenshot. Patch week shop guide: inspect the sequence, write off worn timelines, and only then decide if an old lineup is worth keeping.
Shop framing
If you treat default smokes and flashes like a skin listing, the first throw is the thumbnail and the second touch is wear pattern. Same pixel lineup, different patch: the arc still looks right while the grenade checks into another room. Muscle memory bought on an old map build rarely transfers; you are not bad at nades—the SKU changed.
Inspect: first touch sells the normal, second touch sells thickness
Force-buy smokes and anti-clear flashes fail more from one extra wall tick or one missed crate lip than from a “wrong” crosshair.
- Touch one sets the reflection angle (the normal).
- Touch two decides window entry, door jam, or whiff.
Map groups fix clipping, step height, and rail colliders between versions. You can stand the same spot, throw the same line, and still lose the execute because the bounce chain rerouted. On C5GAME or Steam you can swap knives and finishes without touching this physics chain—client and map version do.
Inspect checklist (two ledger entries):
- Release height and walk speed (muzzle velocity and hang time).
- Only the corner after touch two—smoke hugging the beam, flash clearing the sill.
Cross-version: if touch-two drift exceeds half a body width, tag the whole line delisted, not “nudge one tile.”
Wear: fuse frames and hang time (explosion drifts worse than landing)
HEs, molotovs, and some tac flashes share a nasty rule: fuse and impact can align on the same tick. Thicker collision pushes first contact farther out while fuse frames stay put—the blast center slides. Audio still says “old timing”; the damage bubble or fire front eats your anchor first.
Pro VODs on patch day: same exec rhythm, flash pops on the outside of the frame, clear step gets a half-second hole. That is not vibes—it is longer or shorter air time with “walk two steps, throw” never updated.
Re-record against blast center vs anchor (window corner, crate edge, pit lip), not minimap arc screenshots.
Worth buying back into the line?
Build a line lifecycle sheet for your server build: map, spot name, role, last verified date, touch-two note (e.g. “one crate pop, then in”). After any client or map hotfix, retest double-bounce / ceiling kiss lines first; pure lobs can wait.
Community “hidden arc nerf” is sloppy talk. Safer shop copy: visible aim point and invisible brush thickness fell out of sync. Default lines are map-bound config files, not personal flex—especially during league week.
Shop verdict
Do not inherit muscle memory across builds. First aim is the door; second landing and fuse frame are what make the exec cash out. Patch drops → void the sequence → re-verify → then decide if the line is worth your ranked hours.
Expert mutterings
I still see teams screenshotting touch one like it is float value. Float does not open B window—touch two does. And no, listing a new knife on C5GAME will not fix a hotfix’d func_brush. Sorry.