CS2 RCON commands: the essential referenceControl the server via RCON - admin, maps, modes

Published on August 3, 2026 · last updated on November 4, 2026

Activate RCON and connect

RCON is protected by a password. Set this in your server config or the startup parameters:

rcon_password YOUR_PASSWORD

In the game console, connect to your server and authenticate:

connect IP:port
rcon_password YOUR_PASSWORD
rcon status

Afterwards, you run every command with rcon in front (e.g. rcon changelevel de_dust2). On a server at MainHoster.de, you can also enter the same commands directly via the server console in the web interface.

Important commands at a glance

Set modes via configs

You control game modes most cleanly via the supplied config files instead of individual cvars. Typical combinations of game_type and game_mode:

• Competitive: game_type 0, game_mode 1
• Wingman: game_type 0, game_mode 2
• Rush: game_type 0, game_mode 6, map rush_001
• Casual: game_type 0, game_mode 0
• Deathmatch: game_type 1, game_mode 2

After setting game_type/game_mode, reload the map so that the settings take effect.

What is permanent via RCON - and what is not

This is where most hours are lost: almost everything you set via RCON does not survive the next map change. At map start, CS2 loads the related config files and overwrites most cvars with them. The server then suddenly behaves as before again, without anyone having changed anything.

The consequence for practice:

• RCON is for testing and immediate measures - kicking a player, changing the map, trying out a value.
• Permanent settings belong in the server.cfg or in a config that is loaded at every map start.

A proven process: try out values via RCON until the behavior is right, and then transfer them to the config. That way, you test quickly and still end up with a server that runs the way you set it up after a restart.

Security: the RCON password

Anyone who knows your RCON password has full control over the server - they can ban players, change the configuration and take the server out of play. Treat it accordingly:

• A long password of its own that you do not use anywhere else. In particular, not the same as the server password for joining.
• Not in screenshots, streams or shared configs. A quick glance at the console during a stream is enough.
• Change it after every change in the admin team - just as you would with a door key.

If you want to give moderators rights without handing out the RCON password, an admin plugin via CounterStrikeSharp is the right way. With it, you grant graded rights per SteamID - kicking and banning yes, server configuration no.

RCON does not connect

Three causes cover practically all cases:

1. Wrong port. RCON runs via the same port as the game. Use the port from the web interface, not one from someone else's guide.
2. No password set. Without rcon_password in the server configuration, the interface is simply deactivated - the connection attempt then goes nowhere instead of producing an error message.
3. Too many failed attempts. CS2 temporarily blocks an address after several wrong passwords. Wait a few minutes, then it works again.

status is suitable as a first test: if the server overview comes back, the connection is established, and you can turn to the actual commands.

Frequently asked questions