Dust 2 callouts are usually presented as one enormous image with sixty labels on it. That is a reference, not a guide. In a real match perhaps twenty of those names get said, and the difference between knowing them and knowing all sixty is nothing at all.

The twenty that carry the map

Learn that column and you can hold a conversation with any team on this map. Everything else in the sixty name image is either a subdivision of one of these or a name that fell out of use two versions ago.

A side, where most rounds start

Long is the corridor down the right hand side from the attacking spawn, and the doors at its entrance are the single most contested object on the map. Half of all rounds are decided by who takes them and when.

Pit is the sunken area on the left as you come out of Long, and the reason a player holding it can survive an entire push without being seen from the site.

Car sits at the entrance to the site itself. Ramp is the raised approach on the far side, usually held after the bomb is planted. Site covers the plant area, and nobody bothers subdividing it during a fight.

Short, and the name nobody agrees on

Short is the zigzag from the middle up to the A site, and it is the second route into the same place, which makes controlling both simultaneously the defining problem of defending A.

Xbox is the crate near the middle that you jump on to reach Short. The name is older than most players and it has never been translated, adapted or replaced.

Goose is the passage under A coming from the middle, named after a developer of the series. It is also the area three separate groups of players call three different things, so if a call confuses your team, this is probably the one.

Ninja is the alcove between Short and the site where a defender waits without making noise, and the name tells you everything about its purpose.

Middle, the part that decides rotations

Mid is the open channel between the two halves of the map, and control of it decides whether defenders can reach the far site in time.

Top mid is the upper end of it on the attacking side. Double doors is the gap through to the defending side, usually shortened to doors. Catwalk is the raised walkway leading toward Short.

Lower tunnels connects the middle to B and is the reason the middle matters to both sites at once. A call from here is normally worth more than a call from either bomb site, because it arrives before anything has been committed.

B side and the tunnels

Fewer names, more improvisation, because there are simply fewer distinct places.

The tunnels are the main route to B from the attacking side and split into upper and lower. That distinction is the whole point: it tells the defence which direction an entry is coming from and how long they have.

Back plat is the raised platform at the rear of the site. Window is the opening on the defending side. Big box and the stack of crates on the site are where the defence sits, and in most teams all of it collapses into “by the boxes” regardless of the official names.

Dust 2 callouts that include a timestamp

Here is the part missing from every guide with a map image, and it matters more than any name on this page.

A place is half the information. The other half is time: when you saw them, whether they are still there, whether they have moved. “One Long” on its own means almost nothing ten seconds later, because by then he is somewhere else entirely and your teammate is walking into a spot you described in the past tense.

The complete version is short and contains three elements: how many, where, when. “Two Long, just now.” “One under A, a while ago.”

Add one word about status: dead, or simply out of sight. That is the line between information and a guess, and a team plays the round differently depending on which one it received.

How to learn them in twenty minutes

Load the map alone and walk the attacking routes, naming each place out loud as you pass it. Saying it aloud attaches the word to the image far faster than reading a diagram, however silly it feels in an empty server.

Then the same run through the middle, and again through the tunnels to B.

Then walk both routes from the defending side. The same places viewed from the opposite direction look different and get confused differently, so one pass does not cover it.

After that, go into a normal match and talk, even hesitantly. A name someone corrects mid round sticks permanently. A name read off an image is gone by the evening.

An empty server for that takes two commands and no downloads, and the setup is in our walkthrough of the CS2 practice server config.

Common mistakes on voice

Sentences that are too long. By the time you finish, the situation has changed. Three words is the target.

Calling from spectator without saying so. You are looking through someone else’s eyes, so say “from spec”, or your team assumes it is your own current information.

Directions instead of places. “On the right” means something different to every player depending on where they stand.

Silence after a kill. Where you killed someone and what they had is as useful as any warning, and it costs one short sentence.

Calling as a defender is a different job

Attacking calls describe where you are going. Defending calls describe what is arriving, and that changes what is worth saying.

The valuable information is a count and a direction early enough for someone to rotate, which usually means calling before the fight rather than after losing it. “Three tunnels” said while they are still in the tunnels is worth a round. The same words said after you die are a status update.

The other half is what you did not see. Silence from the far side of the map means nobody has checked it, and saying so explicitly stops your team from assuming it is covered.

What this changes in ranked

You can play entire seasons without saying a word, and plenty do, so it is worth naming what that costs.

Without communication you are playing five separate matches at once. Everyone sees a fragment of the map, nobody assembles it, and the team reacts late to everything.

Callouts are the cheapest fix available, because they require vocabulary rather than aim or reflexes. That is why they sit alongside map knowledge in our breakdown of what actually moves your rating, in CS2 ranks explained.

Once this map is comfortable, the usual next one is at the other end of the pool, and we have collected those names separately in Mirage callouts.

Names that have fallen out of use

Older guides, particularly forum threads that have been online for over a decade, carry names describing objects the map no longer has.

Using them makes you sound authoritative to nobody and confuses everybody under thirty. The map has been rebuilt more than once and the vocabulary moved with it, while the threads stayed exactly where they were.

The rule of thumb: if you hear a name once in ten matches, you do not need it. Twenty names in constant use cover the entire map, and the remainder is trivia for people who enjoy trivia.

Frequently asked questions about Dust 2 callouts

How many callouts do I actually need?

About twenty. Long, doors, pit, car, Short, xbox, goose, mid, catwalk, double doors, upper and lower tunnels, window, back plat and the two sites cover nearly everything.

What is goose on Dust 2?

The passage under the A site from the middle, named after a developer of the series. It is also the name most likely to be misunderstood.

What is the difference between upper and lower tunnels?

Lower comes from the middle, upper from the attacking side. For the defence that difference tells them which entry to expect.

Why is a crate called xbox?

Because of its shape, and because the name has been in use since long before CS2. Nobody has ever renamed it.

Should I learn callouts from an image?

An image is a starting point. The names stick when you walk the map and say them out loud.

What do I say when I do not know the name?

Describe it in one phrase with a reference point, such as “by the boxes on B”. Better than silence every time.

Have the callouts changed since CS:GO?

Almost none of the current ones. The layout survived, so old names still work, though some have quietly stopped being used.

Last updated: September 2026

Names collected from English and Polish map references and from what is actually said on servers, checked in September 2026. Several places carry more than one accepted name and none of them is the single correct one.

A CS2 autoexec is a plain text file the game reads at launch. Building one takes a minute. The interesting problem is that a large share of the configs circulating online contain commands CS2 no longer has, and the game says nothing when it skips them.

Where the file goes

One path, no exceptions. Right click CS2 in your Steam library, choose Manage, then Browse local files. From the folder that opens, go into game, then csgo, then cfg. That is the destination.

Create a text file there and name it autoexec.cfg. When saving from Notepad, set the file type to All Files, because otherwise Windows appends .txt and the game will never see the file.

The fastest way to check: turn on file extensions in Explorer. If what you see is autoexec.cfg.txt, you have already found the reason nothing loads.

Making the game read it

The file alone is not enough, and this is where most people stop without realising it. The game does not scan the folder hoping to find configs, so you have to point at it directly.

Open the properties for CS2 in Steam, find the launch options, and enter +exec autoexec.cfg.

The extension matters. The version without .cfg appears in older guides and in CS2 it frequently does nothing at all.

At the end of the file itself, add host_writeconfig. That forces your current settings into the game’s own config, which keeps them from evaporating on exit.

Proving the CS2 autoexec loaded

Do not infer it from your settings. Make the game say so out loud, which takes one line and saves half an hour of guesswork.

Near the end of the file, before the write line, add something like echo AUTOEXEC LOADED.

Launch the game, open the console, and look for that text. If it is there, the file loaded and any remaining problem is in its contents rather than its location. If it is missing, go back to the filename and the launch option.

How to open the console, and what to do when the key does nothing, is covered separately in our piece on the CS2 console not opening.

One detail that saves restarts: after editing the file, type exec autoexec in the console and it reloads without leaving the game.

Dead commands still doing the rounds

We checked these against the game’s own command and variable dumps rather than against other blogs. All six appear in configs marketed as current, and all six are silently ignored.

That is the argument for writing your own file instead of pasting somebody else’s. A config you did not write is a list of lines you cannot vouch for.

What belongs in a short file

Fifteen lines that change something, rather than two hundred that mostly do not. A short file also has the practical advantage that when something misbehaves, you can read the whole thing at a glance.

Sensitivity and the scoped multiplier, so a change of mouse is one line rather than an evening.

Viewmodel. Field of view and offsets, since this is the only thing permanently covering part of your screen that you control.

Crosshair, if you prefer keeping it in the file rather than in the menu.

A frame cap, set slightly above your monitor’s refresh rate.

Binds for anything you do often that otherwise costs a menu.

Binds are the highest value lines

Display settings are set once and forgotten. Binds fire every round, which makes them the best return per line in the whole file.

The standard set: a jump bound to the scroll wheel, a viewmodel toggle, quick buys, dropping the bomb. None of it is an exploit. Each does exactly what your fingers would do, only faster and without fumbling.

The scroll wheel jump is worth its own explanation, including why it beats the spacebar, and that is in our guide to the CS2 bhop bind on scroll.

One rule when adding binds: one key, one action. Multi state toggle scripts look clever and end with you pressing something other than what you intended in the one round where it mattered.

Pro configs and why they rarely help

Every so often a file appears with a player’s name attached and gets treated as a recipe.

Half of what is inside depends on hardware and habit: a sensitivity tuned to one mouse and one mousepad, a viewmodel set for a particular screen, binds laid out for a keyboard you do not own. The other half is audio and video tuned to a machine unlike yours.

Transplanted whole, that produces an unfamiliar game rather than a better one. The sensible use is to read it and steal individual ideas, usually a bind you had not thought of.

When the file is not the problem

There is a specific case where the echo line appears, the file clearly loaded, and one setting still refuses to work.

Most often the command is restricted on the server. A chunk of the console is limited to your own server or requires server commands enabled, and an official match will refuse it regardless of where you typed it. Which commands those are is set out in our list of sv_cheats 1 commands.

The second cause is a typo. The game does not announce it on screen, it writes a quiet line into the console that scrolled past during map load.

The third, and the most irritating, is two contradictory lines in one file. The lower one wins, so a value set twice gives you the second one while you search everywhere except the obvious place.

A second file for practice commands

Splitting the settings into two files is worth the extra minute, because the things you want while playing and the things you want while practising work against each other.

The autoexec holds what should always apply: sensitivity, viewmodel, binds, frame cap. Practice commands are a different animal. Infinite ammo, grenade trajectories, instant respawn and bot control only function on your own server, and an official match refuses them anyway.

Keeping those in a separate file, called on demand, is cleaner than one long file with half its lines inert most of the time. It also means you can hand that file to a friend without exporting your personal sensitivity along with it.

The full set of commands worth putting in it is in our walkthrough of the CS2 practice server config.

Load order, or why settings revert

The game reads its own config first, then your autoexec if the launch option points at it. That is why the file overrides the menu rather than the other way round.

On exit, however, the current state is written back. Change something in the menu mid session and that value lands in the game’s config, where it will lose to your autoexec at the next launch. It looks random and it is simply ordering.

Keep each setting in one place. Either the file or the menu. Mixing both is the source of every “it changed by itself” report.

One copy, two machines

If you play on more than one computer, the file becomes worth more than the settings inside it.

Keep it in any cloud synced folder and copy it into place after installing the game. Rebuilding every bind from memory takes an evening. Copying a file takes a second.

One value does not travel: sensitivity tuned to one mouse behaves differently on another and needs recalculating rather than copying. Everything else transfers unchanged and gives you your own game on a borrowed machine in about a minute.

Frequently asked questions about the CS2 autoexec

Where do I save autoexec.cfg?

In the game folder, under game, then csgo, then cfg. Browse local files in Steam takes you there fastest.

Does it work without a launch option?

Sometimes, and it is not worth relying on. Adding +exec autoexec.cfg settles it permanently.

How do I confirm the file loaded?

Put an echo line in it and look for that text in the console after launch.

Do I need to restart after editing?

No. Type exec autoexec in the console and it reloads.

What is host_writeconfig for?

It forces current settings into the game’s own config so they persist after you close the game.

Can a custom config get me banned?

Not when it uses commands the game exposes normally. Binds and settings are a standard part of it.

Why do commands from a downloaded config do nothing?

Because some of them are leftovers from the previous game. Check in the console whether CS2 recognises a command before keeping it.

Last updated: September 2026

Paths and commands checked in September 2026 against the current build. The list of commands that no longer exist comes from comparing common configs with the game’s own command and variable dumps, and can change with a major update.

CS2 ranks confuse people because the game runs two separate ratings side by side and calls both of them a rank. One is the familiar badge, awarded per map. The other is a single number in Premier, attached to your account. They measure different things and they move for different reasons.

Two ladders, one account

The badge ladder survived from the previous game: eighteen skill groups from Silver I up to Global Elite. The part people miss is that a badge belongs to a map, not to you. Master Guardian on Mirage and Silver on Ancient is a perfectly normal profile, because those are two independent assessments that never talk to each other.

Premier works differently. You get one number, the CS Rating, running from around a thousand to past forty thousand, and it covers every map at once. The colour beside it changes every five thousand points, which is where the shorthand people use in voice chat comes from.

Premier also requires Prime, and that gate matters more than it sounds. Without it you are looking at the badge ladder only, which is playable but disconnected from the system everyone else is measured by. What the purchase actually buys is set out in our breakdown of whether CS2 Prime is worth it.

Which CS2 rank actually means something

The honest answer annoys people with a high badge on one map.

A map badge describes how you did on that map, possibly six months ago, in a sample of matches you have long forgotten. If you play Mirage almost exclusively, your Silver on Nuke is not a verdict on your aim. It is a note that you never go there.

The CS Rating is the fairer measure. One number, all maps, updated after every match, publicly ranked on leaderboards. Valve built seasons and competition around it, which makes it the currency of the game whether or not you like the format.

If you want to know where you actually stand, look at the number. Treat the badges as souvenirs from specific maps.

What the system is actually scoring

The uncomfortable conclusion sits in the first and third rows together. Personal statistics are a garnish. The core of the calculation is the match result measured against what the system expected from both teams, and that is why a player with a negative kill difference can climb past someone who tops the scoreboard in defeats.

Why you are stuck

The usual complaint is not “I play badly”, it is “I play the same amount and nothing moves”.

That is exactly what the system is designed to produce. Your rating settles at the level where you win about half your matches, and once it has found that level it will keep feeding you matches at fifty percent until something about your play changes.

Hours do not qualify as a change. The cheapest things that do are usually these: knowing one map properly, having a repeatable opening for the round, and saying anything at all to your teammates.

The first of those we have covered in full for the map most people start with, in our rundown of Mirage callouts, because naming a place is the precondition for communicating anything about it.

Rank restrictions when queueing together

The game limits who you can enter ranked matches with, and that limit is frequently the real reason a group cannot play together.

With a wide badge gap, the game refuses to put you in the same competitive match. Premier applies a comparable restriction measured in rating points instead of badges.

The workaround is not a workaround: play unranked modes, or close the gap by playing separately for a while. Borrowed and purchased accounts solve it for a week and end in lost access, since sharing an account is against Steam’s own rules.

What genuinely moves the number

1. Commit to two maps. Premier has a veto anyway, so two well known maps remove half the variance from your queue.
2. Play openings, not duels. A repeatable entry with full information wins more rounds than winning the fight in the middle.
3. Keep calls to three words. Position, how many, what they hold. Everything else is noise.
4. Play in short sets. After a third consecutive loss you are worse than you feel, and the system records it.
5. Fix the machine once. Stable frames and a settled sensitivity do more than another hour of deathmatch.

That last point sounds like an excuse and is measurable. What actually produces frames, and which commonly recommended commands do nothing at all, is in our guide to increasing FPS in CS2.

Training that shows up in the rating

Playing and practising are different activities, and mixing them is the reason people log thousands of hours without improving.

A match tests what you already know. Practice is for acquiring what you do not, and it needs repetition under controlled conditions: the same grenade, the same entry, ten times in a row, with nobody shooting back.

An empty server and a handful of commands cover it, with nothing to download. The full setup is in our walkthrough of the CS2 practice server config.

Twenty minutes of that before a session is worth more to your rating than two extra hours played tired.

Colour tiers and the plateau they create

Nobody says “I am at twenty two thousand”. They name a colour, and it helps to know why.

The scale is cut into bands of five thousand points, each with its own colour beside the number. Grey at the bottom, upward through the tiers, to the band where a fraction of the population sits.

The practical consequence: changing colour is the only moment progress is visible. Four hundred points inside a band is the same improvement and looks like nothing, which is exactly why people quit a few hundred points short of a new tier and conclude they have hit a ceiling.

What not to do

Do not check your rank on third party sites. Trust data and full rating internals are not public, so anything promising to display them is guessing.

Do not buy a boost. Beyond breaking the platform’s rules, it lands you in matches you cannot read, which produces losing streaks and returns you to where you started with less money.

Do not use ranked as a warm up. Your first matches of the day are statistically your worst, and you are paying for them in rating.

How long a genuine climb takes

A realistic scale helps, since guides promising two colour tiers in a week are selling hope rather than information.

At a steady level of play, the rating stands still. After one real improvement, a map you finally know properly, movement becomes visible across a dozen or so matches, because that is roughly what the system needs to separate a change in skill from a good week.

Large jumps mostly happen on new accounts, where the system is still searching for your level and adjusts boldly. Later corrections are small by design, and mistaking that for stagnation is the most common misreading of the whole system.

Hidden badges and fresh accounts

Two situations that look like bugs and are not.

After a long break, a badge can vanish from your profile. It returns once you play a match on that map, because the game wants a current reference point rather than a year old one.

On a new account you start with no assessment at all, the first matches swing it wildly, and then it decelerates. That early stretch feels like easy progress and sets a false expectation for everything after it.

Neither can be accelerated by anything except playing. There is no command and no setting, despite one circulating every few months.

Frequently asked questions about CS2 ranks

How many ranks are there in CS2?

Eighteen badges in Competitive, from Silver I to Global Elite. Premier has no badges, only a CS Rating with colour bands every five thousand points.

Why is my rank different on every map?

Because Competitive badges belong to maps rather than accounts. The Premier rating is shared across all of them.

Do I need Prime for ranks?

For Premier, yes. The badge ladder is more widely available, but Premier is the system the game is built around now.

Do kills raise your rank?

Marginally. The result of the match, measured against expectation, is what the calculation runs on.

How many matches until I get a rank?

A handful of wins, after which the game issues a first badge or a first number. Early adjustments are large because the system is still estimating you.

Can I see my exact Competitive points?

No. You see a badge, not the number underneath it. Only Premier shows the figure.

Does taking a break lower my rank?

Your badge may be hidden until you play again. The rating itself does not decay for inactivity.

Last updated: September 2026

System behaviour described from public documentation and data gathered by community trackers, checked in September 2026. Valve does not publish the full rating formula, so specific details may differ from what you see on your account.