Aim Trainer Open the trainer

Flicks, Tracking, Switching: Which Aim Skill Are You Actually Bad At?

Three different skills share one crosshair, and they fail in different ways. Test them separately before you grind the wrong one for another season.

Aim Trainer · · 6 min read

One crosshair, three abilities

"Bad aim" is a diagnosis with no information in it. What you have is three trainable abilities that happen to share an input device, and a match that can't tell you which one lost the duel:

There's a fourth in this family, worth naming because it masquerades as the other three: micro-precision, small corrections on targets that barely move. Players with strong flicks and bad micro call it "inconsistency". It isn't; it's a different muscle of the same hand.

Test them in four minutes

The cleanest self-test doesn't need a battery of isolated modes. Run the Benchmark (Gridshot, Precision, Tracking and Flick, 60 seconds each) and look at how each score compares to its own fixed reference, not to the other drills' raw numbers.

That last part matters, because the score scales are different (a good Gridshot score dwarfs a good Precision score; the drills count different things). The benchmark handles it by dividing each score by a fixed par (Gridshot 7000, Precision 4200, Tracking 4500, Flick 8000), capping the ratio at 1 and comparing the four ratios. Your weakest skill is the drill with the lowest ratio, full stop.

If your lowest ratio is…In a round, that looks like…Train with
Flicklate on wide swings, whiffing the follow-up snapFLICK + SPIDERSHOT
Trackingsprays that tag, losing long-range duels to strafing enemiesTRACKING + REACTIVE TRACK
Gridshotfewer kills per spray window, a raw speed deficit with no single whiff to blameGRIDSHOT + TARGET SWITCH
Precision"how did that not hit?", Deagle feels cursed, one-taps won't stickPRECISION

One caveat: a single benchmark is a snapshot, and snapshots lie a little. Your weakest ratio should repeat twice in a row, a week apart, before you declare it a weakness and restructure your training around it. What you do not want is to spend a month training a skill that was only tired on a Thursday.

A scoreboard can't tell you why you lost the duel. The four ratios in a benchmark can at least narrow it down.

Train the weakness, about 60/40

Once you've found the weak skill, the temptation is an all-in month: nothing but tracking, every day, until it stops being embarrassing. Two problems with that. Weak skills are weak partly because they're unpleasant, so an all-weak-skill diet dies by day four and leaves you with nothing. And strong skills rust slowly but definitely, so they need maintenance, not a monastery.

A split that survives contact with real life: sixty percent of your reps on the weak skill, forty on everything else. That weak-skill block still follows the rule from the improvement plan: three focused sets on one drill, notes between sets, stop when the score sags. The maintenance block is the Warmup routine or a couple of Gridshot minutes, not a second full session.

Re-run the Benchmark after three or four weeks of that, and expect the ratio ordering itself to shift, usually the weak skill climbs and mid-pack skills start flipping places. When the order stops changing no matter which drill you emphasize, you've stopped finding big mechanical deficits. That's the point to spend the attention elsewhere: on the placement half of aim, or on just playing more matches.

The skill that isn't on the list

Notice what isn't in the table: deciding when to flick, which angle to hold, how to swing a corner so the fight starts with your crosshair already near the enemy. None of that lives in a drill, and all of it changes your duel win rate more than a 5% Gridshot improvement will. The range can tell you your hand is 12% slow on tracking. It cannot tell you that you're taking every fight at a range your weapon loses. Train the hand, spend the hand wisely.

Find your weakest ratioFour minutes: Gridshot, Precision, Tracking, Flick. Each score against its par, then one rank for the whole run.
Start the Benchmark