Skip to content
GrindhouseDocs

Prefire

Run a route you built, or one another player shared, and clear its angles against the clock. Five bots hold spots at a time, each kill brings up the next, and every finished run is rated.

StartPlay → Prefire, or .prefire
RatedYes, every finished run of a saved route of 5 or more bots
Bots10 per run, 5 at a time
DefaultsBots shoot back · Hard · Auto-restart on

How it works

A route is a path through part of a map plus the bots that hold angles along it. You start where the route starts, looking where its author looked. Walk it, clear the bots, and beat your time. In game, chat calls a route a scenario; it's the same thing.

You build routes yourself in the prefire editor, or add other players' routes from the Community hub. Routes are saved per map.

Clock startsYour first move or shot
Bots per run10, five at a time
Run endsAll 10 dead, or you die
RestartL or .restart
Next / previous route.next · .prev

Start a run

  1. Pick Prefire and a map

    Open Play, choose Prefire under Movement & routes and pick a map. Routes on <map> below lists your routes there, with the map's runs and clear rate next to the heading.

  2. Read the route list

    Each row shows the route's name, its bots, the share of your runs you cleared (or Not played yet) and your personal best. Copies from the Community hub carry a by <author> chip. The rest (crouching bots, length, runs) is in the row's menu in the Library, which the link under the list opens.

  3. Play one route

    Press the play button on a row to run only that route.

  4. Or play them all

    Press Play on the mode's picture (it reads Play 5 routes), or Ctrl Enter. Every route on the map plays in a loop: see the playlist.

Play starts your cloud server (or switches the one that's running). A map with no routes yet shows Create your first route instead, which opens the editor.

The Play page with Prefire selected: the map row, the routes on Dust II with their personal bests and play buttons, New route, and the More settings and How it plays folds
Play → Prefire: the routes on the map with personal bests. More settings has the bot options.

Type .prefire to play every route on the current map, in a loop. Change map first with .map mirage if you need to. You have to be on T or CT.

A map with no routes says so; build one with .new (see the prefire editor). .aim, .util or any other mode command leaves prefire.

The run

  1. You land on the start

    You spawn on the route's start, facing where its author looked, with full health and your loadout. Five bots stand on their spots. The center of the screen says move to start.

  2. The clock starts when you do

    Your first step or your first shot starts it. A knife swing doesn't.

  3. Clear the bots

    Bots hold their spots and turn to watch you. With bots shoot back on they fire once they see you. A bot whose angle the author saved with .bringaim keeps that angle instead. Each kill brings up the next bot on its spot a moment later, so five are up until the run's last ones.

  4. The run ends

    When the run's 10 bots are dead the run is CLEARED. If you die first it's DIED. The end marker only shows where the route goes: reaching it doesn't end the run.

Whenever you respawn during prefire you land straight on the start, never at the team spawn.

Which bots you get

A run uses 10 of the route's bot spots, picked at random each time, so a route with more than 10 bots plays a little differently every run. A route with 10 bots or fewer plays all of them. The bots come up in the order the author placed them, which is the order along the route, so the next one is ahead of you.

3/6 bots · 5.42s / 9.8s ELO 1064/1102 · Grinder Bots killed / bots in the run Run time / goal (rated runs only) Your prefire rating / peak · rank
The center text during a run. Before your first move it says "move to start"; a run that isn't rated shows "unrated" instead of a goal.

Results

When a run ends, chat shows the route's name and your numbers, and the center of the screen flashes the result (for example CLEARED 8.42s / 9.8s ★ PB).

Time
From your first move or shot to the last kill (or your death).
Goal
The goal time for this run, shown on rated runs. See Elo rating.
Personal best
Your fastest clear of this route. A new one says ★ NEW PERSONAL BEST; otherwise chat shows your best.
HS
Share of your kills that were headshots.
Accuracy
Share of your shots that hit.
Reaction
Median time from a bot coming into view (inside 50° of your crosshair, in line of sight) to your first shot at it.
Counter-strafe
Share of your shots after moving that you fired stopped.
Elo
On a rated run, a line like GH ▸ Prefire · Grinder │ ELO: 1064 (+21).

The route list on the Play page and in the Library counts finished runs (cleared or died): each row shows the share you cleared, and the heading the runs on the map. Restarts and skips don't count. Your prefire rating is on Progress.

Your session: .stats

Type .stats any time in prefire (the editor too) for the session so far, in chat:

  • How many runs you finished, how many you cleared and how many you died in, and your best clear this session with its route.
  • Headshot %, accuracy, median reaction time and counter-strafe % over all those runs together.
  • Your last run: its route, CLEARED or DIED (with the bots you got), time, headshot %, accuracy and reaction time.

Like the route list, it counts finished runs only: restarts and skips don't count. The session starts when you enter prefire and ends when you change mode or map. Before your first finished run chat says "No finished prefire runs yet this session." Your all-time personal bests are on each route in the route list.

Restart, skip and the playlist

Restart with .restart or L (with the binds). The run starts over from the start, and the one you left isn't rated or counted.

Skip with .next, or go back with .prev. In a playlist they move to the next or the previous route, in the playlist's order; .prev on the first route goes to the last. On a single route you started from the list, they build the map's playlist and carry on with the route after it (or before it). The run you leave isn't rated or counted.

The playlist (.prefire, or Play in the bottom bar) runs every route on the map in name order, the same order as the list:

  • Chat introduces each one: ▶ Scenario 2/5: A site from palace · 6 bots.
  • Clear a route and the next one starts 1.5 s later.
  • Die and the same route starts again 1.5 s later, with you back on its start.
  • After the last route chat says All 5 scenarios done! and the first one starts again.
  • A route deleted while the playlist runs is skipped.
On the start bots in place Clock starts first move or shot CLEARED the run's bots dead DIED you were killed Next route after the last: the first Same route again back on its start 1.5 s 1.5 s
The playlist: a clear moves on, a death retries. Both wait 1.5 s.

.edit opens the route you're playing in the editor.

Options

Set these under More settings on Play → Prefire (the line next to it shows the current ones, for example bots shoot back (hard), auto-restart on), or change them in game. A change on the Play page reaches your running cloud server within a few seconds (a new bot setting starts a run in progress over).

OptionDefaultIn game
Bots shoot backOn.shoot toggles it and restarts the run.
Bot difficultyHard.difficulty expert: easy, normal, hard, expert, super hard or insane (or .diff 0 to .diff 5). Fresh bots join and the run restarts. It only matters while bots shoot back, so it's greyed out on the Play page otherwise.
Auto-restart after a runOnBack on the start 2 s after a clear, 1.5 s after a death. Off: chat says .restart to go again.

A playlist always moves on after a clear and retries after a death, whatever auto-restart says. Your weapon, ammo and armor come from Aim's settings: the Weapon on Play → Aim, and Ammo and Your armor under its More settings (see Aim settings and Weapons, maps & HUD); route bots hold an AK-47 unless the author gave them another gun. More on the levels in Bots & difficulty.

Elo rating

Elo-rated Prefire has its own rating. Every finished run of a saved route is rated, cleared or died, as long as the route is a real challenge: at least 5 bots in the run, the farthest of them at least 1000 units along the route (about four seconds of running). A shorter route plays as usual, unrated, and chat says so once. Each route sets a goal time from your rating, shown next to the clock.

  • Clear inside the goal: a win. The further under it, the more you gain.
  • Clear late: a small loss that grows until you're at 1.5 times the goal.
  • Die: a bigger loss, made smaller by every bot you killed first.
  • Not rated: .restart, .next or .prev mid-run, .test runs of a route with unsaved edits, and routes under the minimum above.
  • Left: going back to the editor (.edit) once the clock runs counts as leaving the run, like switching modes: a loss.
  • Wait for Go! A bot shot during the countdown starts the run over: it never counts toward a clear.

Win streaks don't boost Prefire: a route plays the same every run, so winning it again and again says you know it, not that your rating is behind. Your first 10 results still count 2.5 times (see Faster at first).

The goal is roughly the time to walk the route to its last bot, plus a little for each bot. Both shrink as your rating climbs. Each route also keeps a small offset of its own for you: fail it and the next clear there pays a little more, beat it and the next one pays a little less, so a route you struggle with pays more when you finally beat it. The offset only changes what a result is worth, never how the route plays (see Elo & ranks).

How exactly is the goal time worked out?

Goal = 1 s + the distance along the route to the farthest bot in the run ÷ a pace + a time per bot in the run. The pace rises from 110 to 200 units per second and the time per bot falls from 1.4 s to 0.45 s as your prefire rating goes from 600 to 2600, then on to 230 units per second and 0.30 s at 3900. A clear in 70% of the goal or less earns the full win.

.elo lists your rating in every rated mode. Ranks, peaks and how ratings move are on Elo & ranks.

Routes from the Community hub

Add a route on the Community page and a copy lands in your Library → Prefire routes with a by <author> chip. It plays, edits and rates like your own, with your own personal best.

  • Its run says whose it is: ▶ A site from palace by Garnet · 6 bots (in a playlist, ▶ Scenario 2/5: A site from palace by Garnet · 6 bots).
  • Your edits and .save keep the link to the author's route. When they publish a new version, the row in the Library says Version 2 is out and its menu has Update to version 2. It asks first, because the update replaces your copy, edits included.
  • Remove from library in a copy's menu asks Remove from your library?.

Ranked runs

Every route on the Community hub has its own global leaderboard, one per version of the route. Play ranked on the board (or on the quiet line under Prefire's header on Play, for the prefire map you picked) plays your copy with the ranked settings:

  • bots that shoot back on Hard, kevlar and helmet on both sides, and the AK-47;
  • a ranked clear is never rated, and commands that would change those settings are refused;
  • the board ranks the clear time; equal times go to the higher accuracy.

A normal clear counts too when your prefire settings are the ranked ones and the copy is unchanged (no unsaved edits). Your own published route counts with your original. When the author publishes a new version, update your copy to get on the new board: an old copy doesn't rank, and a ranked run won't start on it (Play ranked on the board updates it first). In the Library, a route you rank on shows your place as a small chip (#3).

Commands

CommandWhat it does
.prefirePlays every prefire route on this map in a loop: clear one and the next starts, die and you retry it. The map needs at least one route.
.new [name]
.pf_new
In developer mode (.dev): opens the prefire editor with a new, empty route on this map, optionally named. Unsaved changes to a route you were editing are dropped.
Example: .new A site from palace
.eloShows your rating in every rated mode (prefire, deathmatch, recoil, spray, spray transfer, the six gunfights, the peeks, Team Hold, Defusal, Pop, Movement, Showdown and Nade Drill): current, peak and attempts won.
.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
.pf_next
Skips to the next route. Playing a single route, it starts the map's playlist from the route after it. A skipped run isn't rated.
.prev
.pf_prev
Goes back to the previous route, in the playlist's order; from the first route it goes to the last. Playing a single route, it starts the map's playlist from the route before it. A skipped run isn't rated.
.restart
.pf_restart
Restarts the run from the start. A run you restart isn't rated.
.statsThis prefire session in chat: finished runs, how many you cleared and died, your best clear and its route, headshot %, accuracy, reaction time and counter-strafe % over all those runs, and your last run's result, time, headshot %, accuracy and reaction time. Restarts and skips don't count. A new session starts when you change mode or map.
.edit
.pf_edit
Opens the route you're playing in the editor.
.shootPrefire bots shoot back, on or off (on by default). They hold their spots and fire once they see you. Changing it restarts the run.
.difficulty [level]
.diff
Prefire bot difficulty: easy, normal, hard, expert, superhard or insane (0–5, default hard). Prefire keeps its own level, separate from aim training. A new level brings fresh bots and restarts the run; no value shows the current level.
Example: .difficulty insane
.pf_helpShows the prefire commands in chat (the editor's while you edit) and the full list in the console.

Building and editing routes: Prefire editor. Every command in one place: All commands.

Questions

Why does the clock say "unrated"?

You're playing a version with unsaved changes, usually through .test in the editor (type .edit, then .save, and play it again), or the route is under the rated minimum: fewer than 5 bots, or its farthest bot less than 1000 units along it. Add bots further along the route in the editor.

I reached the end of the route and nothing happened.

A run only ends when its 10 bots are dead (all of them on a shorter route) or you die. Look for a bot you missed: the center text shows how many you've killed out of the run's total.

The bots don't shoot.

Bots shoot back is off. Type .shoot or turn it on under More settings on Play → Prefire.

.prefire says there are no scenarios on this map.

You have no routes on that map yet. Build one in the prefire editor (type .new, or press New route under Play → Prefire) or add one from the Community hub.

My route has 17 bots, why do I only see 5?

Five are up at a time and each kill brings up the next. A run plays 10 of the route's spots, picked at random, so every spot comes up over a few runs.