Skip to content

The Metronome Method

Written by Bassel Bakr

Written from my own training and experience, not assembled from published sources. Treat it as one informed opinion rather than settled fact.

A metronome takes the decision of when to shoot away from you. Everything below is how to use that without wasting a week.

  • Measure your own pace. Targets divided by seconds, times 60. Start there, not at a guess.
  • Let accuracy pick the tempo. Over 90% raise the beat, over 80% stay and work, under 80% lower it.
  • The beat is a reference, not necessarily a trigger. Sometimes one target per beat, sometimes three.
  • It teaches you to budget tension. The tick gives you no time to fix an overshoot.
  • Check it unpaced. The run without a beat is the one that counts.

What the beat is cutting

Take one shot apart. A flick, a moment confirming the crosshair is on the target, a trigger pull.

When the shot is bad, micro-corrections wedge themselves in. Micro, confirm, micro again.

None of it feels like time passing. All of it is.

One shot drawn as a bar of time. On the first bar the beat arrives partway through the first micro-correction and the trigger goes at 310 milliseconds. The second bar keeps correcting instead, taking 510 milliseconds for the same shot. A dashed line marks where the beat falls across both.Bassel Bakrhttps://github.com/Bassel-Bakr/aimCommitthe beat arrives, the shot goesFlickConfirm½310 msFine-tunemicro, confirm, micro againFlickConfirmMicroConfirmMicro540 msthe beatone shot, start to trigger
The same shot, committed and fine-tuned. A beat set near the first bar arrives partway through the second one's micro-corrections.

Set the beat near the first bar and the second has nowhere to go. You land the flick or you miss.

Find your own pace

Play the scenario you actually train, once, at normal effort. Note the run length and the targets you shot.

shots per second  =  targets / seconds
starting BPM      =  shots per second x 60

Sixty seconds and 92 targets is 1.53 shots per second. About 92 BPM.

Run it twice more if those disagree by more than a few percent. A pace you cannot reproduce is not a pace.

Set the beat by accuracy

Start at the number you measured. Accuracy tells you where to go next.

Read the paced run and do what its accuracy says.

Over 90%: the beat is still inside what you can do. Push it up, 5 or 10 BPM, and go again.

Over 80%: this is the tempo worth working on. Stay there until 90 comes back, then climb again.

Under 80%: the beat is ahead of your aim. Lower it until you are back in the band above.

Accuracy plotted against tempo. The line is flat while the beat asks for no more than you already do, and falls away above your own pace, slowly at first and then steeply. Three bands across the chart say what to do with a paced run: above 90 percent raise the beat, between 80 and 90 stay where you are and work, under 80 lower it. Two dashed lines across the chart wall off the tempos that land in the middle band.Bassel Bakrhttps://github.com/Bassel-Bakr/aim90%+ raise the beat80%+ stay hereunder 80% lower it50%80%90%100%Accuracyyour own pacework here60100140180220Beats per minute (BPM)
Accuracy against tempo, with what to do at each level. The tempos that land you between 80 and 90 percent are the ones worth working on.

There is a difference between a tempo you nearly hold and one far above it. The first teaches. The second only trains missing on time, and your accuracy says so inside one run.

Run it in blocks

Here is a shape to start from, not a rule. A block is a handful of runs with the metronome on, then one with it off.

Train a whole session to a beat if you want to. The part worth keeping either way is the unpaced run, because that is the one that tells you whether any of it reached your aim.

  1. 3 runs with the beat.
  2. A run without it.
  3. Read the paced accuracy: over 90% raise the beat, over 80% stay, under 80% lower it.
  4. Read the unpaced run, held to your normal standards.
  5. If the unpaced run got worse, measure your pace again and reset the beat from it.

A worse unpaced run usually means the tempo drifted away from what you can hold. Re-measure and set the beat from the new number, the same way you found the first one.

The beat is a reference, not necessarily a trigger

The tick is not an order to click. It measures how fast you are going, and what you do with any one beat depends on what is in front of you.

On spread targets, one shot per beat is an honest rate.

In a cluster, one beat is enough for two or three targets. Take them.

On a flick across the screen, one target can cost two beats. That is not a failure either.

Learning which of those you are in is the skill. The metronome only makes your pace audible while you learn it.

Do not chase the tick itself. Landing slightly before or after a beat changes nothing; drifting further behind every beat is what matters.

Clusters and long flicks

Static scenarios do not space targets evenly. That is where one-shot-per-beat falls apart.

Give a cluster the same beat you give the far target and you spend the cluster waiting. Give the far target one beat and the tick arrives before your crosshair.

Four targets, three of them clustered and one far away, shot twice against a steady beat. On the beat: the crosshair reaches each clustered target early and waits for the tick, then the far target is fired at before the flick arrives, and missed. Beat as a reference: each shot goes when the crosshair lands, running ahead of the beat inside the cluster and behind it on the long flick, and all four hit.Bassel Bakrhttps://github.com/Bassel-Bakr/aimBeat1234On the beatwaits in the cluster, then runs out of timeBeat as a referenceahead in the cluster, behind on the long flick
Four targets, three of them clustered. One shot per beat wastes the cluster and fires at the far target early. Used as a reference, the cluster runs ahead of the beat and the long flick runs behind it, and every shot lands.

Budgeting tension

This is what I think the tool actually trains.

A fixed beat leaves no time to repair an overshoot. Grip too hard, the flick overshoots, and the micros needed to fix it do not fit before the tick.

Grip too loose and the flick arrives late, which the beat punishes just as fast.

One flick to one target, made five ways, against a fixed beat. A fast flick with a fast correction lands early and waits. A fast flick with a slow correction overshoots and spends the rest of the time crawling back. A balanced hand takes one motion and a short correction. A slow flick falls short and snaps on at the end. A slow flick with a slow correction is still correcting when the beat arrives. The clock under each lane shows where that hand spent its time.Bassel Bakrhttps://github.com/Bassel-Bakr/aimFast, fastno time to fix the overshootFlickMicro150 msFast, slowovershoots, then pays it backFlickMicro300 msBalancedone motion, short correctionFlickMicro300 msSlow, fastarrives short, snaps onFlickMicro300 msSlow, slowcut off short by the tickFlickMicro420 msthe beatone shot, start to trigger
One shot, five ways to spend it. Three of them land. Rush the correction and the crosshair stops long; drag both halves out and the beat fires the shot while you are still short.

The tempo quietly teaches you how much force a shot needs, and no more. See Tension Management for what those two failures feel like away from a beat.

Fade it out

The metronome is scaffolding. Leave it up permanently and you find out, in a game, that your timing was borrowed.

One block, one scenario, a few sessions a week.

Take a week off it every month. If your unpaced pace moved, the tool did its job.

What to run it with

Any metronome. A phone app, a browser tab, a click track.

Loud enough to hear over the game, no louder. Listening for the beat instead of the targets means the volume is doing your aiming.

Further resources