The duel starts before you see anyone
Watch two players of roughly equal mechanical skill and the difference in their duel results is rarely the flick. It's where the crosshair was resting when the enemy appeared. One player's crosshair travels the corners of the map glued at head height, sliding along the edge where an enemy is most likely to emerge; the fight, when it comes, is a tiny correction and a click. The other player also has fast hands and uses them, every single fight, to solve a problem that good placement had already half-solved. Over a match, the second player is doing three times the aiming for the same kills. The scoreboard says "aim diff"; the demo says placement diff.
That is why placement pays better than any other skill in CS2 and feels like the least fun to work on: none of it makes a highlight, and all of it produces wins.
A flick is a repair job. Placement is the job you were supposed to do first, and repairing is always slower than never breaking.
Head level is a habit, not a setting
The core instruction, "keep your crosshair at head level", is easy to say and hard to do, because head level is not a constant. It changes with every ramp, stairs, catwalk and drop on the map. Strong players re-derive it continuously as they move: leaving a bombsite through the ramp, the crosshair lifts before the enemy would be visible; crossing to a lower connector, it drops. The aim never leaves the character-height band where heads live. This running background calculation is what "good crosshair placement" describes, and it is why the skill feels invisible: nothing to see, just fights that keep going right.
The practical way to audit it: in your next match or demo, pause at the exact moment of first visibility for every duel you take. Note where the crosshair sits relative to the enemy's head: on the head, above it, at chest, at knees, pointed at the wall two meters short. Most players who complain about consistency find the same two answers, chest or short, plus the occasional floor. The gaps are measurable, which means they are fixable.
The pre-aim line
Height is half of placement; the other half is the horizontal line, which pixel of the corner you are looking at. The rule of thumb that self-corrects for most angles: hold the edge where the enemy's head will first slide into view, offset from the wall by about a head's width of empty space. That way the swing brings the head to your crosshair instead of one body-width past it. When an enemy emerges right at your crosshair, that is not luck; the offset was right. When they appear past it and you chase, the offset was too tight toward the wall.
A few context notes that turn the rule of thumb into judgment:
- Off-angles punish pre-aim less than you think. Holding the primary angle still wins most fights; the fix for a player who pre-aims off-angles is review, not abandoning pre-aim.
- Wide swings and close swings need different lines. Against a wide-swinger, the enemy slides a long way into the open, so hold a bit off the wall. Against a tight player, hold the edge itself.
- Gaps between cover are the real duels. Most first contacts happen crossing open space, not at the corner itself. That line, where you would be if you were the enemy playing YOUR position, is the one to hold while crossing.
None of this is a mouse skill. It is map knowledge worn as muscle memory, built in-game by walking maps, watching demos and playing deathmatch with self-rules, not in a range.
What the range can do for it
Two things, both real but both partial:
- Train the stop that placement depends on. Placement gives the enemy to you at head level; the Peek drill supplies the other half, strafe out, counter-strafe to a genuine stop, fire the moment the shot is accurate. Moving inaccuracy doesn't care how good your placement was, and a perfect pre-aim shot fired mid-strafe is still a miss. Peek is where counter-strafe timing gets honest, because the trainer refuses to award the shot until the movement has fully bled off.
- Train the vertical recovery. Real placement isn't static: it starts two head-heights below where it should, because you were looking at a lower angle or checking a radar pixel, and it has to arrive at head level fast. That "lift from ground to head" is a wide, upward flick with a direction constraint, and Flick and Spidershot build exactly that class of correction: arrive at the target from wherever you started, don't overshoot the new line, reset.
What no browser range can give you is which pixel to hold on Inferno ramp or how head level shifts through Nuke's ramps. That knowledge has to be bought in-game. But if placement gives you 70% of a duel, the range can own the conversion step, firing accurately the instant the enemy arrives in your line. That is the end of the fight, where everything you banked either pays out or does not.
A 20-minute placement session
- 5 min: walk one map position. Pick one spot you play often. Walk it slowly, crosshair never leaving the character-height band, stopping at each angle to ask where the head appears. Boring and effective.
- 10 min: deathmatch with one rule. Every death, review where your crosshair was at the moment you died. Keep a count: "short, low, fine, low, short". Watching the count move over sessions is the practice.
- 5 min: two range drills. One round of Peek for stop timing, one of Flick for the rise-to-head correction. These are the mechanics placement hands off to.
Do that weekly and your aim ranking will improve without your benchmark moving a point, because half of aim was never on the benchmark. The other half, the honest score and the weakest-ratio analysis, is what the range is for. Know which half you are feeding.