Insurgency Server Admin Commands and How to Use Them

Insurgency (2014) and Insurgency: Sandstorm use different administration systems. The 2014 Source game reads server.cfg, authenticates RCON with rcon_password, and expects the rcon prefix in the in-game console. Sandstorm uses SteamID64 entries in Admins.txt, RCON launch arguments or Game.ini, and a different command set. Confirm the game and server build before copying any command. Then identify players with the version’s own tools, use the correct moderation or map command, and verify names with help, maps, or scenarios when the server rejects an instruction.

Which Insurgency game and server version are you administering?

The first step is deciding whether the server runs Insurgency (2014, Source) or Insurgency: Sandstorm. Their configuration files, authentication, identifiers, map controls, and command syntax are not interchangeable.

Area	Insurgency (2014, Source)	Insurgency: Sandstorm
Admin identity	Console output from users or status; target a user ID or Steam ID	SteamID64 lines in Insurgency/Config/Server/Admins.txt; RCON can also target a name, ID, or net ID
Main configuration	insurgency/cfg/server.cfg	Game.ini, launch arguments, and Admins.txt
Remote access	Set rcon_password, then issue rcon commands in the game console	Enable RCON with launch arguments or Game.ini; connect through an RCON client or host panel
Map control	changelevel plus mapcycle.txt and mode-specific mapcycle files	travel, travelscenario, and MapCycle.txt
Availability	Source commands documented for the installed server build	Build-sensitive; confirm with live-server help

Keep separate notes for each game. A valid Source command can be rejected by Sandstorm even when the spelling looks familiar, and a Sandstorm travel command is not a substitute for Source’s changelevel.

How do I enable RCON on an Insurgency (2014) server?

For the 2014 Source game, put the password in insurgency/cfg/server.cfg, load the server, and authenticate from the in-game developer console. Every server action that follows needs the rcon prefix.

1. Stop the dedicated server before editing its files.
2. Open insurgency/cfg/server.cfg. Add a private password line such as rcon_password your-long-random-password, then save the file.
3. Start or restart the server so the configuration is loaded.
4. Join the server and open the game console. Enter rcon_password your-long-random-password. The password is not displayed back to you.
5. Test access with rcon status. If it returns server and player information, authentication worked.

Do not publish the password in screenshots, chat, startup scripts shared with other administrators, or public configuration repositories. Anyone who obtains it can execute server commands.

Insurgency (2014, Source) authentication and test commands

rcon_password <password>
rcon status

When a hosting control panel provides a server console, its console generally runs the command directly and does not need the in-game rcon prefix. In the game client, use the authentication command first and prefix subsequent server commands with rcon.

What are the essential Insurgency (2014) admin commands?

Use users or status before moderating anyone. Source assigns a user ID and reports Steam IDs; using the wrong name or ID can affect nobody or the wrong player.

Command	Purpose and syntax	Important qualification
users	Lists connected players and their server IDs and Steam IDs	Run it before a kick or ban when you need an exact identifier.
status	Shows server, map, and player status	Use the returned user ID or Steam ID for later commands.
kick <name-or-userid>	Removes a player	Names containing spaces can be ambiguous; a user ID is safer.
dropclient <userid>	Drops a client by Source user ID	It does not use a SteamID64.
banid <minutes> <SteamID>	Bans a Steam ID; 0 means permanent	The Steam ID must come from users or status.
banid <minutes> <SteamID> kick	Bans and immediately removes the player	Use the same verified Steam ID as the preceding form.
addip <minutes> <IP>	Bans an IP address; 0 means permanent	IP bans can affect shared networks and are less stable than Steam-ID bans.
listid / listip	Lists Steam-ID or IP ban entries	Check these before adding a duplicate entry.
removeid <SteamID> / removeip <IP>	Removes a matching ban entry	Use the exact value stored by the server.
changelevel <map>	Changes the active map	The map name must exist on that installation.
maps [partial-name]	Lists maps, optionally filtered by a partial name	Use it to discover the exact spelling accepted by changelevel.

Insurgency (2014, Source) moderation example

rcon users
rcon kick <userid-or-exact-name>
rcon banid 0 <SteamID> kick
rcon listid

The example first obtains the identifier, removes the player, applies a permanent Steam-ID ban, and verifies the stored ban. Replace every placeholder with the value shown by your own server; do not literally type the angle brackets.

How do I change maps and rotations in Insurgency (2014)?

Use changelevel for an immediate switch. Edit the map-cycle files when you want future rounds or restarts to follow a planned rotation.

Change the current map

1. Run rcon maps or rcon maps <partial-name> to find a valid map name.
2. Issue rcon changelevel <map>.
3. Watch the server console for the level-load result. A misspelled or unavailable map will fail rather than create a new map.

Edit the rotation

The base mapcycle.txt and mode-specific mapcycle files control which maps are selected in rotation. Back up the existing file, preserve its format, and restart or reload the server according to the host’s procedure after editing. A manual changelevel changes the active level but does not by itself rewrite the rotation file.

How do I add myself as an admin in Insurgency: Sandstorm?

Sandstorm’s built-in administrator list uses SteamID64 values, one per line. The server guide places the file at Insurgency/Config/Server/Admins.txt. Windows server configuration commonly uses InsurgencySavedConfigWindowsServer; Linux uses Insurgency/Saved/Config/LinuxServer.

1. Install or update the dedicated server with SteamCMD. Sandstorm’s Steam application ID is 581330.
2. Stop the server before changing administrator files.
3. Create or open Insurgency/Config/Server/Admins.txt.
4. Enter your complete SteamID64 on its own line. Add each additional administrator on a separate line; do not use a display name.
5. Save the file, start the server, and join with the account whose SteamID64 is listed.
6. Use the default admin-menu binding, Keypad Subtract, unless you have changed the key binding.

A missing file, a truncated ID, extra characters, or editing the wrong server instance prevents recognition. Confirm that the server process is reading the same installation directory you edited.

How do I enable Sandstorm RCON?

Sandstorm accepts RCON settings in startup arguments or in Game.ini. The launch form is explicit and easy to test on a new installation.

Sandstorm launch-argument form

-Rcon -RconPassword=<password> -RconListenPort=<port>

Use a long, unique password and a port that is reachable from your administration network but not unnecessarily exposed to the public internet. If your provider has a separate RCON toggle, make sure it does not overwrite these arguments.

Sandstorm configuration form

The same RCON settings can be placed in Game.ini using the server’s documented configuration format. Restart after changing the file; a running process will not reliably apply new listener settings. Connect with your RCON client or hosting panel, then run help immediately to see the commands exposed by that build.

What are the essential Sandstorm admin commands?

Sandstorm’s command names and accepted arguments can change with updates, so treat the live server’s help output as authoritative. The following core commands are documented for current dedicated-server workflows.

Command	Purpose and syntax	Usage notes
help	Displays available commands and help text	Run it after every update or when a command is rejected.
listplayers	Lists connected players and identifiers	Use the returned ID or net ID rather than guessing from a name.
kick <id/netid/name> [reason]	Removes a player	The optional reason can explain the action to the player.
ban <id/netid/name> [duration] [reason]	Temporarily bans a player	Check the build’s duration format with help ban.
banid <netid> [duration] [reason]	Bans by network identifier	Use the exact net ID from listplayers.
permban <id/netid/name> [reason]	Applies a permanent ban	Verify the target before using an irreversible action.
unban <netid>	Removes a ban by network identifier	Keep a record of the identifier and reason for the original action.
say <message>	Sends a server message	Use concise notices for restarts, rule reminders, or scheduled changes.
restartround [0/1]	Restarts the current round	Confirm the meaning of the optional flag with help restartround.
travel <travel-url>	Travels to a level using a travel URL	Use a valid URL format from the installed server’s documentation.
travelscenario <scenario>	Loads a named scenario	Discover exact names with scenarios.
maps [filter]	Lists maps, optionally filtered	Useful for checking whether a map is installed and spelled correctly.
scenarios [filter]	Lists available scenarios	Use the returned spelling with travelscenario.
gamemodeproperty <property> [value]	Reads or sets a game-mode property	Only change properties you understand; values vary by mode.
listgamemodeproperties [filter]	Lists game-mode properties	Filter the output when the full list is long.

Sandstorm (current dedicated-server build) discovery and moderation

help
listplayers
kick <id-or-netid> <reason>
ban <id-or-netid> <duration> <reason>
permban <id-or-netid> <reason>
unban <netid>

Unlike an in-game Source console command, these lines are entered in the Sandstorm RCON or server console context. A provider panel may expose the same server console directly, so do not add a literal rcon prefix unless that panel specifically requires one.

How do I identify the correct Sandstorm player before kicking or banning?

Run listplayers and match the displayed name with the player’s ID or net ID. Names can be duplicated, changed during a session, or contain characters that make a text match unreliable.

1. Enter listplayers and copy the target’s exact ID or net ID.
2. Use a reversible action such as kick when the situation is uncertain; include a clear reason.
3. For a ban, verify the identifier a second time and select the duration deliberately.
4. For a permanent ban, use permban only after confirming the evidence and the server’s moderation policy.
5. Record the identifier, time, action, and reason in your administrator log so another admin can audit or reverse it.

banid is useful when the net ID is the reliable value but the player’s display name is not. Use unban with that same net ID when an appeal is accepted.

How do I change Sandstorm maps and scenarios?

Sandstorm separates map and scenario control. Use maps and scenarios to discover valid names, then use travel or travelscenario for the live change.

Immediate map or scenario change

maps [filter]
scenarios [filter]
travel <travel-url>
travelscenario <scenario>

1. Run maps or maps <filter> to confirm the map is installed.
2. Run scenarios or scenarios <filter> to confirm the scenario spelling and availability.
3. Use travelscenario <scenario> when you want to load a named scenario directly.
4. Use travel <travel-url> when the server’s documented travel URL is required.
5. Watch the console for a successful level load and warn players first with say <message> if the switch will interrupt a round.

Set the normal rotation

Insurgency/Config/Server/MapCycle.txt controls Sandstorm’s scenario rotation. Edit it with the server stopped, preserve the expected scenario-entry format, and restart the process. A one-time travelscenario command changes the current level but does not rewrite MapCycle.txt.

Where are Sandstorm gameplay settings stored?

General gameplay settings are placed in Game.ini, while the Windows and Linux server configuration directories differ. The cited server guidance lists IdleLimit as 150 seconds by default, but defaults are build-sensitive; check the generated configuration and your installed version before relying on that value.

• Windows configuration directory: InsurgencySavedConfigWindowsServer
• Linux configuration directory: Insurgency/Saved/Config/LinuxServer
• Administrator list: Insurgency/Config/Server/Admins.txt
• Scenario rotation: Insurgency/Config/Server/MapCycle.txt

Keep a backup before changing Game.ini. A malformed setting can prevent startup, while a setting copied from another game or an older build may simply be ignored.

Why is an Insurgency admin command failing?

Most failures come from using the other game’s syntax, an incorrect identifier, an unavailable map, or a command removed or renamed by an update. Diagnose in this order.

1. Confirm the game. Source requires rcon_password and the rcon prefix; Sandstorm requires its RCON connection and normally accepts commands without that prefix.
2. Confirm the console. A host-panel console and an in-game console can apply different prefixes and authentication steps.
3. Check authentication. For Source, retry rcon_password and test rcon status. For Sandstorm, verify the password, listener port, and launch or Game.ini settings, then reconnect.
4. Check the identifier. Run Source users/status or Sandstorm listplayers; do not infer an ID from a scoreboard position.
5. Check spelling and availability. Run Sandstorm help, maps, or scenarios; run Source maps before changelevel.
6. Restart after file changes. Administrator lists, RCON listeners, map cycles, and many Game.ini settings are read at startup.
7. Read the server log. It can distinguish a parse error, permission failure, unknown command, and missing asset.

What security practices should Insurgency server admins follow?

• Use a unique RCON password that is not reused for your hosting account, Steam account, or panel login.
• Restrict the RCON listener port to trusted administration addresses where your host supports firewall rules.
• Give the SteamID64 admin list only to people who need administrator access, and remove former staff promptly.
• Prefer Steam IDs or net IDs over display names for moderation, then log every kick, ban, unban, and map change.
• Use temporary bans when facts are incomplete and reserve permanent bans for confirmed violations under a published policy.
• Back up server.cfg, Game.ini, Admins.txt, and rotation files before editing.

What is different about administering the two Insurgency games?

The practical difference is not just command spelling: each game has a separate identity source, configuration workflow, and map model.

Task	Insurgency (2014)	Sandstorm
Grant admin access	Configure Source server access and authenticate with rcon_password	Put SteamID64 values in Admins.txt; enable RCON separately if needed
Find a player	users or status	listplayers
Remove a player	rcon kick <name-or-userid> or rcon dropclient <userid>	kick <id/netid/name> [reason]
Ban	banid for Steam ID or addip for IP	ban, banid, or permban
Change active level	changelevel <map>	travel or travelscenario
Set rotation	mapcycle.txt and mode-specific mapcycle files	MapCycle.txt
Verify commands	Use Source command reference and server output	Run live-server help, because updates can alter availability

Keep the two workflows isolated in your documentation and scripts. A version label beside every command block prevents the most expensive mistake: executing a valid command against the wrong game.

Frequently Asked Questions

Can I use a player’s Steam display name for every Insurgency command?

No. Display names can be duplicated or changed. Source administrators should use the user ID or Steam ID returned by users or status, while Sandstorm administrators should prefer the ID or net ID from listplayers.

Do Sandstorm server commands work from the in-game chat box?

RCON and the dedicated-server console are separate from ordinary player chat. Send commands through the configured RCON connection, the server process console, or a provider panel that exposes that console.

What should I do if my Sandstorm admin menu key does nothing?

Verify that your complete SteamID64 is on its own line in the server’s Admins.txt, that you edited the active installation, and that the server was restarted after saving. The default binding is Keypad Subtract and may have been changed locally.

Why did changing the map once not change the next rotation?

A live travel command affects the current level only. The next selection still comes from the relevant map-cycle file, so edit and reload the rotation when you want a persistent change.