Skip to content
GrindhouseDocs

Aim

Bots appear inside your field of view, or all around you at 360°. Flick, kill, repeat, with reaction time, accuracy and kill rate tracked on every kill.

Start.aim or Play → Aim
Defaults70° cone · 1 bot · 50 kills a spot
MapsEvery map
RatedNo: stats and trends only

How it works

Aim training is a flick loop. You stand somewhere on the map, a bot appears where you can see it, you kill it, and the next one appears somewhere else in view. After a set number of kills you move to a new spot and it starts over.

  1. You're dropped at a random spot

    Anywhere on the map with open sight lines, facing the most open direction.

  2. A bot appears in your view

    Inside the spawn cone around your crosshair, between the closest and farthest distance, and always somewhere you can actually see it.

  3. Kill it, the next one appears

    A tenth of a second after the kill the bot is back on a new spot in view. With several bots at once, each one is replaced as you kill it.

  4. New spot every 50 kills

    After the kills per location (50 by default) chat shows a summary of that spot and you're moved somewhere new.

Every kill is recorded: reaction time, time to kill, headshot, accuracy, first-shot hit, how far from your crosshair the bot appeared, and how fast you were moving when you fired. You see the numbers live under your crosshair, in chat after each spot, and over time on the Progress page.

Start training

  1. Open Play and pick Aim

    Pick a map, your Weapon, how many Bots at once and a Spawn cone. The rest is under More settings (see Settings). Every choice is saved.

  2. Press Play

    The orange Play sits on the picture of the map you picked, under Aim training. Your cloud server starts. Press Connect when it's ready to join it from CS2.

  3. Shoot

    With Start training on join on (the default) you're put on CT and training starts as you spawn. With it off, join a team and type .aim.

The Play page with Aim selected: the map row, the weapon button, bots at once, the spawn cone presets, the More settings and How it plays folds, and the Play button on the picture of the map at the top
Play → Aim. The line next to More settings sums up what's inside: distances, kills per spot, the bots and your ammo.

In game, .aim starts and stops Aim training from any mode. Stopping prints a summary of the session.

A running cloud server picks up changes you make on the Play page by itself. You don't need to restart it.

Controls while you play

.skip
Moves the bots to new spots in view. No kill is counted.
.next
Moves you to a new spot now, without finishing the kills (.fov_next also works).
.prev
Doesn't move you. Every spot is picked at random, so there's no previous one to go back to; chat says so and points you to .next.
.restart
A fresh session: new spot, counters back to zero.
.stats
Your numbers so far, in chat (what they mean).
.hud
Hides or shows the stats under your crosshair (HUD).

Settings

The Play page sets what every new server starts with. Most settings also have a command that changes them on the spot in game; those changes last until your server stops or you change an Aim or Prefire setting on the Play page.

On the panel

Under the map row, Aim shows the three settings you change most:

SettingOptionsDefaultIn game
WeaponAny rifle, sniper, SMG or pistol (all 26). The button shows your gun; press it for the list, grouped into rifles, snipers, SMGs and pistols. Also your prefire weapon.AK-47.ak, .awp, .deagle…
Bots at once1–101.bots 3
Spawn cone70° · 90° · 120° · 180° · 360°. Any other width (20–360°) is set with the slider under More settings, and then shows next to the presets.70°.cone 120, .360

More settings

Everything else is in the More settings fold, grouped as Spawning, Bots, Loadout and Session. Spawning starts with a sketch of where bots can appear with your current cone and distances, seen from above.

SettingOptionsDefaultIn game
Spawn cone20–360° in steps of 570°.cone 120, .360
Closest bot100–1500 units250 (≈ 6 m)Play page only
Farthest bot500–4000 units2200 (≈ 56 m)Play page only
Kills per location5–20050.kills 30 (any number)
Bots on radarOn · OffOnPlay page only
Bots stand stillOn · OffOn.freeze
Bots shoot backOn · OffOff.shoot
Difficulty when they shoot backEasy · Normal · Hard · Expert · Super hard · InsaneHard.difficulty hard
Bot armorKevlar + helmet · Kevlar · NoneKevlar + helmet.botarmor cycles
Ammo∞ Infinite (never reload) · Infinite reserve (you still reload) · Normal∞ Infinite.ammo cycles
Your armorKevlar + helmet · Kevlar · NoneKevlar + helmet.armor cycles
Start training on joinOn · Off. Skips team select: you join on CT and Aim training starts.OnPlay page only
Learn spots while you walkOn · Off. Adds spots you walk past to the map's spawn spots.OnPlay page only

Distances are in game units, about 2.5 cm each. The closest distance always stays at least 100 units below the farthest. Bots on radar shows every bot on your radar during Aim training, at any cone; it matters most at 360°.

  • Bots stand still: static targets that always face you. They can't walk or jump, even when they shoot back. Turn it off and bots move around with CS2's own bot AI.
  • Bots shoot back: bots fire at you, which switches their AI on. If you die you respawn on the same spot a second later and the bots are placed in view again.
  • Difficulty only matters while bots shoot back, so the selector is greyed out otherwise. What each level does: Bots & difficulty.

The How it plays fold under it sums up the mode in four lines and gives the chat command, .aim.

The spawn cone

The cone is how wide an area around your crosshair bots may appear in, in degrees. It's centered on where you aim at the moment the bot spawns, so it follows your view. At 70° a bot appears at most 35° from your crosshair in any direction: left, right, up or down.

120° cone Bots appear only in the wedge you face. Your crosshair 120° Farthest 2200 u (56 m) Closest 250 u (6 m) You 360° Anywhere around you, behind too. Each new spot starts with a 3-2-1 countdown. Your crosshair You Behind you
Seen from above. Bots spawn between the closest and farthest distance, inside the cone. Past 180° the cone reaches behind you; at 360° it's the whole ring.
  • .cone 120 sets the cone in game (20–360; values outside are clamped). .cone on its own shows the current one.
  • .360 switches to 360° and back to the cone you had before.
  • Changing the cone in game starts a new stats session (why). Crossing 180° either way also moves you to a new spot, since 360° needs spots that are open all around.
  • Bots only appear where you can see them. If nothing inside the cone is open (you're facing a wall, the floor or the sky), the bot waits and appears as soon as you look somewhere open.

360° training

Set the cone above 180° and bots can appear behind you, so you train turning and checking as well as flicking.

  • Countdown at each spot. When you arrive the HUD says Look around · bots in 3…, then 2, 1 and GO!, and the bots appear. Use it to check what's around you. Bots left over from the last spot don't count if you kill them during the countdown.
  • Open spots. Where the map allows, new spots have open ground on at least three sides, so there's something to turn to.
  • Radar. With Bots on radar on (the default) every bot shows on your radar, so you can find the ones behind you.
  • Toggle. .360 switches 360° on and back off. If you started at 360°, it goes back to 90°.
Tip:

Your best kill rate is kept per cone, so 360° sessions never compete with your 70° ones.

How spots are chosen

Where you stand

Your spot is a random point on the map's walkable ground. Bigger open areas come up more often. It's at least about 20 m (800 units) from your last spot and needs open sight lines: several walkable areas within bot range that you can see. You face the direction with the most of them inside your cone.

Where bots appear

  • On walkable ground inside the cone, between the closest and farthest distance.
  • Only where you have a clear line to the bot's head and chest, with room for it to stand.
  • Never on the same spot twice in a row, away from the last 8 spots any bot used when the cone has room, and at least 120 units (about 3 m) from other bots.

Spawn spots

Every map also has a list of spawn spots: its deathmatch, T and CT spawns, plus spots learned while you play and spots you add. They're the fallback on maps without walkable-area data (a nav mesh), and training needs at least two of them to start.

  • Learned spots. With Learn spots while you walk on, any spot you walk across that's at least 220 units (about 5.5 m) from a known spot is added, in any mode, up to 4,000 per map.
  • Your own. .addspot saves where you stand and the way you face, even right next to another spot (.fov_addspot also works).
  • Community packs. Aim spot packs you add from the Community page join the same list, even while the server runs.

Spots are saved with your account, per map, so every cloud server you start has the ones you learned, added or got from the Community. Learning only adds spots; it never changes the ones already there.

The HUD under your crosshair

Two short lines sit just below your crosshair while you train: how the session is going, then the last kill.

Kills at this spot / per location Kills per minute this session Your best kills/min at this cone Hits / shots this session Last kill: time to kill Headshot (only when it was one) Your speed at your first shot MOVING follows when it was too fast 45/50 · KPM 37 [41] · Hit 54% TTK 0.77s · HS · 12 u/s
The default text HUD. .hud big shows the same numbers larger, with hits as 27/50 (54%) and the speed in green or red.
45/50
Kills at this spot, out of the kills per location.
KPM 37
Kills per minute this session. It shows – for the first 15 seconds, so one quick kill doesn't read as 60 a minute.
[41]
Your best kill rate at this cone (to the degree) from earlier sessions that lasted at least a minute with 20 or more kills. Once this session qualifies and is ahead, the bracket shows it instead, and chat says ★ New best kill rate. It's missing until you have such a session.
Hit 54%
Hits out of every shot fired this session, misses included.
TTK 0.77s
How long the last kill took, from the bot appearing to it dying.
HS
Shown when the last kill was a headshot.
12 u/s
Your speed, in units per second, when you fired your first shot at that bot. MOVING follows it when you were too fast to be accurate: above 34% of your gun's running speed, which is about 73 u/s with the AK-47. Moving while crouched counts as accurate. A first shot fired on the move also prints a red line in chat with the speed to stay under.

What the second line says

Second lineWhen
New location!You've just been moved to a new spot.
Look around · bots in 3… then GO!The countdown at each new spot when the cone is over 180°.
TTK 0.77s · HS · 12 u/sAfter a kill.
TTK 1.02s · 142 u/s MOVINGAfter a kill where your first shot was fired too fast.

HUD styles

.hud
Hides the HUD, or brings the text HUD back. While it's hidden, the 360° countdown still shows.
.hud big
Larger text in CS2's alert box. It sits higher on the screen, and CS2 pulses that box about once a second.
.hud text
The steady default box under your crosshair.
.hud off
Hidden. .stats still shows everything in chat.

The HUD belongs to Aim training. Other modes have their own center text; see on-screen info.

After each spot

When you finish a spot, chat says 50 kills done — new location. and prints the spot's stats before you move:

LineExample
Kills and rate50 kills · 31.4/min · HS 46% · accuracy 41%
SpeedReaction 284 ms (best 191 ms) · TTK 0.92 s · first shot 58%
MovementCounter-strafe 82% (14 stopped · 3 while moving · 6 standing)

The counter-strafe number is green at 80% or more, gold from 60%, red below. Stopping with .aim prints the same block for the whole session.

Stats

Type .stats at any time for the session so far, plus the current spot when it differs. Reaction time and time to kill are medians, so one slow bot doesn't skew them.

Reaction time
From a bot appearing to your first shot at it. Slower than 3 seconds isn't counted (you weren't looking at that bot yet), and neither is faster than 100 ms (a spray carried over from the last bot). With several bots, a bot's clock starts when you were free to take it: the later of when it appeared and your previous kill.
Time to kill
From a bot appearing (or you being free, with several bots) to it dying.
Kill rate
Kills per minute.
Headshot %
The share of your kills that were headshots.
Accuracy
Hits out of every shot fired, misses included.
First-shot %
How often your first bullet at a bot hit it.
Counter-strafe %
Of the first shots of each burst you fired after moving, the share you fired after stopping. Shots fired without having moved count as standing and stay out of it.
Spawn angle
How far from your crosshair a bot appeared, up to 180° (right behind you, at 360°). The Progress page charts your reaction time by spawn angle.

Tip: Make every shot a stopped one

.strafe turns on the counter-strafe gate: a shot fired while you're still moving faster than the gun is accurate at does no damage. Tap the opposite move key, then shoot. .strafe again turns it off. It works in Pop too.

Sessions and cones

Each start of Aim training is one session, saved to your history. Changing the cone in game ends the session and starts a new one, with a summary for the old cone in chat (70° CONE STATS), because bests and the Progress page's By cone table are kept per cone. Trends, bests and per-map and per-weapon tables are on Progress, on its Aim view.

Note: Not Elo-rated

Aim training has no rating. Elo covers prefire, deathmatch, recoil, spray, spray transfer, the gunfights and most of the newer modes (Pop for targets); see Elo & ranks. Aim is measured by your stats and trends instead.

Ranked runs

Aim has three global leaderboards: Aim 90°, Aim 180° and Aim 360°. Start one with Play ranked on the board, on the quiet line under Aim's header on Play, or with .ranked aim90 (aim180, aim360) in game.

  • Always on Mirage, with the AK-47, from the same spot for everyone: one bot at a time inside the cone (all around you on 360°), standing still and not shooting, 400 to 1,800 units away.
  • The screen says RANKED · AIM 90° over Bots in 3…, then 41 kills · 12 s left: a 3-second countdown with no bots, then exactly 60 seconds. When the minute is up, chat gives your kills, accuracy and time to kill and the board's answer, and the next run starts 5 seconds later.
  • The board ranks kills; equal kills go to the higher accuracy. Your median time to kill is in the detail.
  • .restart starts the minute again. Commands that would change the board's settings (.bots, .cone, .360, .freeze, .shoot, .difficulty, .armor, .ammo, .skip, .addspot), .next and other guns are refused; .ranked off goes back to your own Aim settings.

Commands

CommandWhat it does
.strafeCounter-strafe gate on / off: in Aim training and Pop a shot only counts once you've stopped. Fired while moving faster than the gun is accurate at, it does nothing.
.aimStarts aim training on this map, or stops it when it's running. From any other mode it switches to aim training.
.ranked [board | off]Ranked runs for the leaderboards. Alone it says which ranked run you're on, or lists the boards you can play from here. A board starts its ranked run: a Pop task (grid, micro, widewall, pressure, jumbo, head), aim90, aim180 or aim360. A ranked run fixes the weapon, settings and difficulty, turns cheat commands off and doesn't change your rating. .ranked off goes back to a normal run.
Example: .ranked grid
.next
.fov_next
Moves you to a new random location now. There's no previous one to go back to: .prev only reminds you that spots are random.
.restartStarts a fresh session: new location, counters reset.
.skipMoves the bots to new spots in view. No kill is counted.
.bots <1-10>How many bots are alive at once in aim training, 1–10 (default 1). Kill one and another appears in view.
Example: .bots 3
.kills <number>
.fov_kills
Kills before you move to a new location (default 50).
Example: .kills 30
.cone [20-360]How wide around your crosshair bots can appear, in degrees: 20–360 (default 70). No value shows the current cone. Over 180° bots can appear behind you and each new location starts with a 3-second countdown. Lasts for this session; a new cone starts a new stats session.
Example: .cone 120
.360Switches to a 360° cone (bots anywhere around you), and back to your previous cone.
.hud [big|text|off]The stats line on screen: kills toward the next location, kills per minute with your best at this cone, hit %, the last kill's time to kill and your speed at the shot. On by default; no argument shows or hides it. .hud big uses CS2's larger box, which sits higher and pulses about once a second.
Example: .hud big
.freeze
.fov_freeze
Bots stand still or move. They stand still by default.
.shoot
.fov_shoot
Aim training bots shoot back, on or off (off by default). .difficulty sets how well they shoot.
.difficulty [level]
.diff
Bot difficulty in aim training: easy, normal, hard, expert, superhard or insane (0–5, default hard). It matters once bots shoot back. No value shows the current level.
Example: .difficulty expert
.addspot
.fov_addspot
Saves where you stand as an aim training spawn spot on this map.
.statsYour session in chat: kills, kills per minute, headshot %, accuracy, reaction time, time to kill, first-shot hits and counter-strafe %, plus the current location.
.ammoCycles ammo: infinite (default), infinite reserve (you still reload), normal. Not in deathmatch, the Recoil control or the spray drills.
.armorCycles your armor: kevlar + helmet (default), kevlar, none. Not in deathmatch, the Recoil control or the spray drills.
.botarmorCycles bot armor: kevlar + helmet (default), kevlar, none. Not in deathmatch, the Recoil control or the spray drills.

Common questions

Why did no bot appear?

Bots only appear inside the cone where you can see them. If you're facing a wall, the floor or the sky, especially with a narrow cone, there's nowhere valid, so the bot waits until you look somewhere open. .skip places the bots again; .next moves you.

Why does KPM show a dash?

Kills per minute stays blank for the first 15 seconds of a session.

Why is there no best in brackets?

It needs an earlier session at the same cone with at least 20 kills over at least a minute. Change the cone and the best changes with it.

Changing the difficulty does nothing.

Difficulty only changes how bots shoot. Turn on Bots shoot back or type .shoot.

My kills during the countdown didn't count.

At cones over 180°, bots still standing from the last spot don't count while the countdown runs. The new bots appear at GO!

Chat says the map has no spawn spots.

Training needs at least two spawn spots on the map. Walk around with Learn spots while you walk on, or stand somewhere and type .addspot, then .aim.