After CS2 split movement updates to sub-tick, a clean stop is really overlap cancellation plus a short residual-speed window before fire goes green—not the moment you release WASD. This guide walks peek rhythm, spread permission vs. visual recenter, and map friction so you stop donating wide first shots in narrow fights.
Shop take
If your in-game feel is “I’m planted but bullet one still behaves like run-and-gun,” you’re not imagining it. Competitive defaults tie fire permission to speed on the server ledger, not to when your crosshair looks settled. Sub-tick updates mean counter-strafe is less “flip keys instantly” and more unregister overlap → bleed residual velocity → spread bucket flips to standing.
Verdict: Worth the drill. One repeatable gap between release and opposite press beats another 0.1 sens tweak. Pay the 80–120 ms retract on half-peeks; you’re buying first-shot center mass, not vanity crosshair snaps.
What you’re actually “buying” with a stop
Classic stop: drop W, tap S—or drop A, tap D. On sub-tick sampling, the server can still see a brief overlap: old direction not fully cleared from the queue while the new key is already in. Non-zero tangential speed keeps inaccuracy in move mode even when the reticle visually tightens. That half-window is where wide first shots usually invoice you.
Training target isn’t raw APM—it’s key order you can repeat. Leave a consistent beat between release and press; local demos and velocity curves beat memorizing milliseconds. Mirage T ramp to A1, Anubis mid wall-hug half-model peek: one extra frame of width is the server reading you as still moving while you thought you were static.
Two ledgers: looks aimed vs. spread allowed
Recenter splits into view stability (punch stopped dragging the angle) and spread permission (move inaccuracy still attached). Sub-tick often desyncs them: crosshair back on habit point, foot speed still above fire threshold—“crosshair calm, gun dishonest.” Not magic; two checks on different clocks.
Triple narrow peek: third click before the gate opens skews systematically. On CT retake, plant then pre-aim beats tap-while-tightening. Scoped weapons magnify it: reticle locked in glass, tail speed still there—head aim, shoulder receipt at range.
Peek as four beats (default comp rhythm)
- Accel out of angle
- Opposite overlap cancel
- Residual → zero
- First shot inside permission
Stage three stretches with friction, ramps, crouch-walk toggles. Inferno banana choke, Dust2 long doors edge—wall-hug then hard stop adds a normal correction vs. open ground; the stop window feels longer.
Squad call “see them, stop, shoot” should execute as see angle → opposite first → read green → fire. Versus gambling they’re also run-shooting, half retract moves your shot into the standing bucket—small time cost, first bullet in the center column.
Expert mutterings
Sub-tick movement is accounting: counter-strafe is the residual ledger after overlap clears, not the end of your release animation. This week, one homework line only—record local demos, tag every tight peek: did “visual recenter” and “first hit” share a frame? Miss sync → fix release-then-press order, not sensitivity. Once permission matches what you see, then default lines and nade timers start paying rent instead of that invisible frame of spread tax.
No unpublished patch tables here—just default competitive input → displacement → spread chain, same facts the live game runs on.