Skip to content
GrindhouseDocs

Prefire editor

Build your own prefire route in game. Set the start, walk the path, mark the end and stand where each bot should hold. Save it and it's in your Library, ready to play.

Open.dev then .new [name], or New route
A route needsA start and at least one bot
BotsUp to 25 per route
SavedPer map, in your Library

What you're building

A route has four parts: a start (where you stand and which way you look when a run begins), the path you walk, an end marker, and the bots that hold angles along the way. You record all of it by walking the map yourself. In game, chat calls a route a scenario.

.start (H) your spot and view direction path: a point every 48 units as you walk .end (J) .bot (F) turns to face the route .botcrouch a crouching bot holds the site .bringaim: keeps your angle
A route seen from above. In game the start and end are tall green and red beams and the path is an orange line on the floor.

Build a route

  1. Open the editor

    Press New route in Library → Prefire routes (or on Play → Prefire), or in game type .dev (developer mode; .dev prefire on a map with no routes yet), then .new. .new A site from palace names it straight away. The map opens in editor mode and chat shows the five steps. The center line keeps score: EDITOR · start ✘ · route 0 · end ✘ · bots 0 · unsaved.

  2. Set the start

    Stand where the run should begin, look the way you'll go, and type .start (H). Every run starts here, facing this way. The center line shows ● REC: your path is being recorded. .start again starts the path over and clears the end.

  3. Walk the route

    Walk it the way you'd play it. A point is added every 48 units (about 1.2 m) while you're on the ground, and the orange line grows behind you.

  4. Mark the end

    Where the route ends, type .end (J). Recording stops and chat shows the route's length in meters. The end marker shows where the route goes; a run still ends when every bot is dead.

  5. Place the bots

    Stand exactly where a bot should hold and type .bot (F), then step away. Crouch first, or use .botcrouch, for a crouching bot. You must be on the ground, about a meter from any other bot. Bots join the other team.

  6. Fix mistakes

    .undo (G) removes the last bot, .del (U) the one you aim at, .crouch (N) toggles crouch on the one you aim at. Aim at a bot or give its number for .bring, .bringaim, .botgun ak 2 and the rest of the manual bot commands.

  7. Save it

    Type .save A site from palace. A route needs a start and at least one bot. Without a name it's called Scenario 1, Scenario 2 and so on; names can be up to 48 characters. Chat confirms Saved "A site from palace" · 6 bots and it appears in your Library.

  8. Try it

    .test plays it right away. .edit brings you back to the editor.

Tip:

Walk the path the way you'd really take it. The goal time for a rated run is based on the distance along your path to the last bot.

Which way bots look

  • When you .save, every bot turns to face the nearest point of your path.
  • During a run those bots turn to watch you. With bots shooting back, they aim and fire once they see you.
  • .bringaim (aim at a bot, or .bringaim 3) moves the bot to where you stand and gives it your facing. That bot keeps the angle in every run, which suits a bot holding a tight off-angle.

Test and edit

  • .test plays the route as it is in the editor, saved or not. With unsaved changes chat says Testing your unsaved version, and the run isn't rated.
  • .edit (or .pf_edit) takes the route you're playing back into the editor, from a test or a normal run.
  • Edit in game in a route's menu in Library → Prefire routes opens a saved route in the editor.
  • The center line shows unsaved until you .save again. .new with unsaved changes drops them and says so.
  • In the editor, bots never shoot, a bot you kill comes back (unless .respawnbots off), and when you die you respawn on the start once you've set one.

Let the game make routes

Instead of placing every bot yourself, the game can find the walk and the angles. Each of these runs on your cloud server, so join it while it works; it takes a moment per route.

Generate

With a start and an end set, .gen walks the map from the start to the end (or to where you stand) and puts a bot on each hidden angle along the way: 8 by default, up to 20 (.gen 16). A walk with fewer hidden angles gets fewer bots. On the 2D map editor (a route's Edit on the map), Generate in game does the same; the route and bots come back into the editor, and Save keeps them.

Route pack

Library → Prefire routes → Make route pack (or .genpack in the editor) makes routes for the map's common paths: T spawn to each site and to mid, CT spawn to mid, and mid to each site, with a bot on every hidden angle (4 to 10 a route). Each is saved to your routes as it's found ("T spawn to A site" and so on); making the pack again replaces those routes. A path that would be the same as one already made is left out.

Variations

Open a saved route with Edit on the map and pick one under Variations, or type .genvar in the editor. The game saves the new route next to the old one ("A long (shuffled)").

VariationIn gameWhat changes
Shuffle bots.genvar shuffleEach bot moves to another hidden angle near its own, gun and armor kept.
Walk it back.genvar reverseThe same walk the other way round, with the angles hidden from that way.
2 more bots.genvar more [n]Bots on the angles furthest from the ones already held (2, or 1 to 4 in game).
2 fewer bots.genvar fewer [n]The most crowded bots go; at least one stays.

In game, .genvar puts the variation in the editor: .save keeps it as a new route. .gen again, a map change or leaving the editor stops a pack or a variation under way.

A route from a round

In a match's 2D replay, follow a player and press Prefire route: their walk that round, from 8 seconds before the first enemy they met until the last (or their death), with a bot where each enemy stood when they met, facing them, crouching if they were. Save route keeps it in your Library. On Scouting → Rounds, the route button beside Watch does the same for the player you scout.

One-time binds

Paste this once into the CS2 console (~). CS2 keeps binds, so the keys work every time after.

bind "h" "css_start"; bind "j" "css_end"; bind "f" "css_bot"; bind "g" "css_undo"; bind "u" "css_del"; bind "n" "css_crouch"; bind "l" "css_restart"

L restarts a prefire run. These keys replace their normal CS2 action (F inspect, G drop), so change them to any keys you like. The same line is under How to build a route in the Library, with a Copy button.

Note:

The utility binds use H, J, N and L too. CS2 keeps one bind per key, so whichever line you paste last wins. More on Binds.

Rename and delete

Open Library → Prefire routes and pick the map. Each row shows the route's bots, the share of your runs you cleared and your personal best, with Play and a ⋯ menu. The menu lists the rest (crouching bots, length in meters, runs, when it was edited) and has Edit in game, Rename, Publish to the Community hub… (your own routes) and Delete.

  • Rename: the row turns into a text box. Type the new name and press Enter or Save.
  • Delete: pick Delete, then Delete again at Delete forever?. On a copy from the Community hub the menu says Remove from library and asks Remove from your library?.
  • Share: Publish to the Community hub… puts it on the hub. Once it's published, the row shows how many players added it and the menu has Open on the Community hub. See Publish your own.
Library, Prefire routes tab: the map chips, New route, the How to build a route fold, and route rows with their personal bests, Play and a ⋯ menu, one of them a copy by another player
Library → Prefire routes. Each row has Play; edit, rename, publish and delete are in its ⋯ menu.

Where routes are saved

Your routes are kept with your Grindhouse account. Every cloud server you start gets them, and a route you save or change in game is sent back to your account while you play.

Commands

CommandWhat it does
.dev [off|prefire|anchor|util]
.developer
Developer mode: stops what the mode is playing at once (the round or run ends, the bots go) and turns on the editing commands of the mode you are in (.new, .edit, .bot, .save, .test …), which do what that mode edits: an Anchor spot, a prefire route, a utility lineup. .dev again turns it off and plays on; changing mode turns it off too. On a map with no prefire routes yet: .dev prefire, then .new.
Example: .dev
.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
.edit
.pf_edit
Opens the route you're playing in the editor.
.pf_helpShows the prefire commands in chat (the editor's while you edit) and the full list in the console.
.start
.pf_start
Sets the start where you stand, facing where you look, and records the route as you walk. Typing it again starts the path over and clears the end.
.end
.pf_end
Sets the end of the route where you stand and stops recording.
.gen [bots]Generates the route: the walk from the start to the end (or where you stand) along the map, with a bot on each hidden angle along it. 8 bots by default, up to 20. Typed while a pack or a variation is being made, it stops that.
Example: .gen 16
.genvar [shuffle|reverse|more|fewer] [n]A variation of the route in the editor: shuffle moves each bot to another hidden angle near its own, reverse walks it the other way round, more / fewer adds or takes away n bots (2 by default). It goes in the editor; .save keeps it as a new route.
Example: .genvar reverse
.genpackMakes the map's route pack: T spawn to each site and to mid, CT spawn to mid, mid to each site, each walk with a bot on its hidden angles, saved to your routes one by one. Made again, it replaces those routes.
.bot
.pf_bot
Prefire editor: places a route bot where you stand, crouching if you are. Stand on the ground, away from the other bots. Route bots always join the other team, so a team name is refused here. Up to 25 bots per route.
.botcrouch
.botduck
Prefire editor: places a crouching route bot where you stand, on the other team.
.undo
.pf_undo
Removes the last bot you placed (in utility mode, the last dummy).
.del [id]
.delete .pf_del
Removes the bot you aim at, or bot number id. The other bots are renumbered.
.crouch [id]
.pf_crouch
Toggles crouch on the bot you aim at, or bot number id.
.save [name]
.pf_save
Saves the route; it shows up in the Library. Needs a start and at least one bot. Without a name it's called Scenario and a number.
Example: .save A site from palace
.test
.pf_test
Plays the route you're editing, saved or not; with unsaved changes the run isn't rated. .edit goes back to editing.

Every bot you can place, move, equip, crouch, arm or respawn: Bots & difficulty. Playing routes: Prefire.

Questions

.save says "Set a start position first".

Every route needs a start. Stand where it begins and type .start, then walk it and save again.

.bot says "There's already a bot here".

Bots need a little room: step about a meter away from the nearest one. To move a bot instead, aim at it and use .bring.

.bot says "Stand on the ground".

You were in the air or in noclip. Land first; bots are placed exactly where you stand.

Can a route have more than 25 bots?

No. 25 is the limit per route. In the editor you see all of them; a run plays 10 of them, picked at random, with five up at a time (see Which bots you get).