Installation Prerequisites [Windows Only]
Before proceeding with your server installation, make sure you have installed the following prerequisites.
Like other games published on Steam, Insurgency: Sandstorm's server files are published through a command-line tool known as
SteamCMD. This GUI-less Steam client allows you to install and update the server files easily.
You can download SteamCMD from the following links:
If you’re using Windows, unzip SteamCMD to a known folder location or create a new one to use for the installation. You will frequently be navigating back to this location during the installation process.
Most commands through SteamCMD require knowledge of the app ID. For Insurgency: Sandstorm, the app ID is
For a basic server setup, please follow the instructions below:
SteamCMD and wait for it to update. This can take a few minutes.
login anonymous and hit Enter. This will log you in anonymously, allowing you to download most game servers.
app_update 581330 validate and hit Enter. This will install and validate the Insurgency: Sandstorm dedicated server.
quit and hit Enter once you have received a message stating that the app was fully installed.
You will now be able to find your dedicated server in the common subfolder located within the Steamapps folder. The full path should look like this: SteamCMD\steamapps\common. You can create a shortcut to this folder for ease of access in the future.
Please note that the root directory for SteamCMD will vary based on what you have named it.
You can find more information about SteamCMD and how to use it here.
Once SteamCMD is installed, you will need to create a script to launch the server with your desired options and settings. On Windows, this is a batch file; on Linux, this is a shell script.
1) Create a new text document in the
2) Open it and press
CTRL + Shift + S. A window should appear and ask you to save the file.
3) Name the file
start.bat and hit Enter.
cd .steam/steamapps/common/sandstorm_server to navigate to the newly created Server directory.
touch start.sh and hit Enter.
A new file with the specified name will be created in the specified location. You will need to edit this file with the specific command line for your operating system to launch the server.
The command line should include the starting map, the scenario, and any other launch parameters. For example:
InsurgencyServer.exe Oilfield?Scenario=Scenario_Refinery_Push_Security?MaxPlayers=28 -Port=27102 -QueryPort=27131 -log -hostname="My Server”
Insurgency/Binaries/Linux/InsurgencyServer-Linux-Shipping Oilfield?Scenario=Scenario_Refinery_Push_Security?MaxPlayers=28 -Port=27102 -QueryPort=27131 -log -hostname="My Server"
In this example, the server will be started on Refinery (Oilfield) Push Security, hosted on port 27102 with a maximum of 28 players.
For your server to show up on the server browser, you will have to forward both
UDP. You can find tutorials on port forwarding on a lot of websites. We suggest portforward.com, which offers tutorials for most router manufacturers.
You will need to put the ports that you have forwarded in the script that you created earlier.
Now that you have forwarded your ports, you will need to make sure that your Firewall allows the connection to be made for your server to show up in the server browser.
Windows + R. This will open the Run window.
2) Paste the following string:
wf.msc and hit Enter.
Inbound Rules on the left panel, then click
New Rule on the right panel.
Port and hit Next.
TCP and make sure you have
Specific local ports selected, then put the ports you have forwarded into the box separated by a comma (for us, this is
27102 for our game port and
27131 for our query port).
Allow the connection and hit Next.
7) Make sure that all of the boxes are checked and hit Next.
8) Name the rule:
Insurgency Server and hit Finish.
Repeat steps 3 to 8, but instead of allowing TCP at rule 5, you will need to allow UDP. In total, you should have two new rules in the Inbound Rules section.
You can edit your rules by going back to the Inbound Rules tab, right-clicking the rules you created, and then clicking Properties.
It's a good idea to reference your distribution's documentation to facilitate the configuration of the Firewall.
Once you’ve added your Inbound Rules to the Firewall, you can now launch your server with the batch/shell script file we created earlier in the Launching section. Please note that the server will be running a default configuration. The default configuration cycles through all Versus PVP scenarios available and follows the Official game rules.
If you wish to modify the server’s configuration, you can find the information you need within the following sections of this guide.
Command Line Arguments
Most server configuration is performed through .INI files and launch parameters. These files can be edited with any text editor such as Notepad, Notepad++, Sublime Text, and VSCode.
The configuration files can be found in the following directories (relative to the server's installation directory):
If the directory does not already exist, you will need to create one manually. You will also need to create new .INI files:
1) Create a new folder named
WindowsServer inside of the Config directory found here:
2) Create a new text document in the
3) Open it and press
CTRL + Shift + S. A window should appear and ask you to save the file.
4) Name the file
Engine.ini and hit Enter.
5) Open the new text document again and press
CTRL + Shift + S.
6) Name the file
Game.ini and hit Enter.
mkdir -p Insurgency/Saved/Config/LinuxServer. This will create a new LinuxServer directory if it is missing.
cd Insurgency/Saved/Config/LinuxServer to navigate to the newly created LinuxServer directory.
touch Engine.ini and hit Enter.
touch Game.ini and hit Enter.
Two new INI files with the specified names will be created in the same location.
|-log||Enables log window.|
|-hostname=”My Server”||Set the name of the server as it appears on the server browser (replacing My Server with the name of your choice).|
|-EnableCheats||Enable cheats for testing.|
The UDP port that game connections are made to (replace xxxx with port number).
|-QueryPort=xxxx||The port that Steam runs server queries on (replace xxxx with port number).|
Travel parameters are placed at the end of the map name in the command line, following it with a question mark (?) and then the setting variable and its value. In the example below “MaxPlayers” is the travel parameters.
|password||Sets a password for the server.|
|MaxPlayers||Maximum number of players that can join the server. On coop servers, this is only the number of human players.|
The game has a built-in admin menu that provides basic functionality such as kicking, banning, and changing the level. To add admins, you will need to know their 64-bit Steam ID (aka steamID64). You can find this by using an online converter such as STEAMID I/O.
You will then need to create a file named
Admins.txt inside the following directory: Insurgency/Config/Server.
1) Create a new folder named
Config inside the Insurgency folder found in the root directory.
2) Create a new folder named
server inside the newly created
Config folder. Your path should now look like this: Insurgency/Config/Server.
3) Create a new text document in the
Server folder named
mkdir -p Insurgency/Config/Server. This will create the new Server directory.
cd Insurgency/Config/Server to navigate to the newly created Server directory.
You can also override the file by specifying a command-line switch. For example, -AdminList=OtherAdminList would make the server read from OtherAdminList.txt instead.
For each admin you want to add, you will need to put their steamID64 on a new line inside the Admins.txt file. You can do this for as many admins as you would like to add. Adding new admins will require a server restart or level change for any changes to be reflected in-game. When a player with admin privileges connects to the server, they will be able to open the admin menu bound to the Keypad Subtract button by default and can be re-bound in the key bindings menu.
Remote Access (RCON)
Rcon can be enabled to provide remote access to the server for administrative tasks that don’t require you to join the server. This is implemented using the Source Engine Rcon Protocol which has clients available for it such as mcrcon and Simple SourceDS RCON.
Rcon can be enabled either through modifying Game.ini or through the server’s command line. To enable it via the command line you can provide the arguments -Rcon -RconPassword=password -RconListenPort=27015 replacing the password and port with your preference.
Through Game.ini you can add the following options:
The following additional config variables are also available:
|bAllowConsoleCommands||True||When enabled, any unknown rcon commands will be interpreted as console commands.|
|bUseBroadcastAddress||True||If enabled, then the rcon socket will listen on all available network devices.|
|IncorrectPasswordBanTime||30||The amount of time (in minutes) a client is banned from attempting to connect to rcon if they’ve reached their maximum number of attempts.|
|ListenAddressOverride||0.0.0.0||If bUseBroadcastAddress is False, this is the network IP the rcon socket is bound to.|
The maximum number of failed authentication attempts before the IP address is temporarily banned.
You can get a list of commands at any time by typing
help into the console. This will show a summary of all available commands, their usage, and a description of the command's function.
The table below shows the available commands. Mandatory parameters are shown surrounded by "<" and ">", while optional parameters are surrounded with "[" and "]". A "net ID" typically refers to a user's Steam ID.
|ban||<id/netid/name> [duration in minutes] [reason]||Bans a player from the server.|
|banid||<netid> [duration in minutes] [reason]||Bans a player (by net ID) from the server. Does not require the player to be on the server.|
|gamemodeproperty||<property> [new value]||Gets or sets a gamemode property for the length of the scenario.|
|help||Displays a list of commands.|
|kick||<id/netid/name> [reason]||Kicks a player from the server.|
|listban||Shows the ban list for the server.|
|listgamemodeproperties||[property filter]||List all properties available for the currently loaded gamemode.|
|listplayers||List players currently connected to the server.|
|maps||[level filter]||Lists available maps.|
|permaban||<id/netid/name> [reason]||Permanently bans a player from the server.|
|restartround||[0 = no team switch, 1 = swap teams]||Restarts the current round.|
|say||<message>||Shows a message to all players in the chat box.|
|scenarios||[level filter]||Lists available scenarios.|
|travel||<travel url>||Transitions the server to a different level.|
|travelscenario||<scenario>||Change level to given scenario.|
|unban||<netid>||Lifts a ban for a user.|
By default, any unknown commands will be executed as console commands.
Any Insurgency: Sandstorm community server is capable of hosting a stats-enabled game. In order to accomplish this, you must first generate a GameStats Token. This can be accomplished by doing the following:
1. Visit the GameStats Token Generator and authenticate through your Stream profile.
2. Click on "Generate Token" which will create you a GameStats token.
Your token will look something like this:
Simply add the generated token to your launch parameters, and stats will be enabled! Make sure to not share your GameStats token with a third-party. Server admins found to be abusing the system will have their tokens revoked and your account will be investigated. If you suspect your GameStats token has been shared, please generate a new token.
In order for your server to be able to authenticate with the stats server, you must authenticate your server through using a Steam GSLT (Game Server Login Token). GSLTs can be obtained from Steam's Game Server Account Management page. As this page states, there are various criteria your Steam account needs to meet in order to generate a token, this includes ownership of the game, linking your Steam account with a phone number and having your account in good standing.
In order to generate a token for Insurgency: Sandstorm, enter the App ID as 581320. The memo field can be set to anything so use it to help you remember which token you are assigning to each of your servers. You must use a unique token for each individual server you are hosting.
To start your server with GSLT authentication add -GSLTToken=xxxxxxxxxxxxxxx to the server's command line where "xxxxxxxxxxxxxxx" is the token displayed on the Steam Game Server Account page.
By default, the game servers will not attempt to report to the stats system. Following the GSLT login steps above, adding
-GameStats to your server's command line will enable the opt-in to the system.
Optional: Official Rules
The game ships with a ruleset which are considered official rules; this locks down the options you can change on your dedicated server. If you are running a mostly vanilla server, you may consider opting into this ruleset for your server to appear under the "official rules" filter. To opt-in, add
-ruleset=OfficialRules to your server's command line.
By default, a server will cycle through all Versus PVP scenarios available.
The server can be configured with a map cycle file that contains a list of scenarios separated by newlines. By default, this file must be placed in Insurgency/Config/Server/MapCycle.txt. This can be defined on the command line using the
-MapCycle parameter. So if you wanted it to read MyOtherMapCycle.txt, you would specify
If this file does not exist, you will need to create it.
1) Create a new text document in the Server folder named
cd Insurgency/Config/Server to navigate to the Server directory.
touch MapCycle.txt to create the text file.
For example, a Skirmish only server's MapCycle.txt should look like the following:
Additionally, you may define an entry with an override game mode as some game modes can share scenarios. For example, to have Hardcore Checkpoint Security on Hideout, you would enter the following:
|Scenario_Hideout_Push_Security||Push Security (INS2014 layout)|
Power Plant (PowerPlant)
For Checkpoint scenarios “Insurgents” and “Security” refer to the faction you play as. For Push, the faction names represent the team you attack as. Firefight for most maps will contain a West and an East layout.
In addition to day scenarios, night scenarios are also available. This is controlled through the travel parameter
?Lighting=, valid values are Night or Day.
For the map cycle, you control this through a Lighting parameter, similar to the Mode parameter. You should make sure that this parameter is specified for the correct voting image to show. For example:
This will set the map cycle entry to use Hideout (Town) at Night on the Checkpoint Security scenario. You can mix Day and Night scenarios in the same map cycle by explicitly defining the Lighting parameter for both Day and Night, for example:
This will allow you to play Hideout Checkpoint Security on both Day and Night which will show the appropriate images on the voting screen.s
Mods are delivered using Mod.io. To get started, you will need a Mod.io account. Once you have signed in, click your username at the top right, and click API Access from the left navigation.
Under OAuth 2 Management, under Generate Access Token, enter a name to give your token and give it read access (write access is not needed) and click Create Token.
You will be presented with your auth token, you may copy this to your clipboard. In your server's Engine.ini, you will enter the following to authenticate your server with the token (replace "TOKEN HERE" with what you just copied):
Now you have entered your authentication token and your server is ready to start accepting mods. Your server must include
-Mods on the command line for this to function.
To specify a list of mods your server is running, you can add a text file in the following directory
Insurgency/Config/Server/ specifying each mod ID line by line. If this file does not exist, you will need to create it.
1) Create a new text document in the Server folder named
cd Insurgency/Config/Server to navigate to the Server directory.
touch Mods.txt to create the text file.
You can also override the text file read by specifying
-ModList=MyCustomModList.txt on the command line.
If you wish to specify a list of mods on the command line, you may do this through specifying
-CmdModList="mod1,mod2,mod3" where mod1,mod2,mod3 is a comma-separated list of mod IDs.
You may specify a map to travel to after mods are downloaded by specifying the
ModDownloadTravelTo= command-line argument, followed by the travel URL argument to change to.
An excellent resource for newcomers is the community guides available on Mod.io.
Mutators (formerly rulesets) are packaged gameplay configuration assets which the game ships with. You may use these on your own servers by specifying
-mutators=MutatorName on the server command line where "MutatorName" is from the following options:
|File Name||Mutator Name||Description|
|AllYouCanEat||All You Can Eat||Start with 100 supply points.|
|AntiMaterielRiflesOnly||Anti-Materiel Only||Only anti-materiel rifles are available along with normal equipment and explosives.|
|BoltActionsOnly||Bolt-Actions Only||Only bolt-action rifles are available along with normal equipment and explosives.|
|Broke||Broke||Start with 0 supply points.|
|BulletSponge||Bullet Sponge||Health is increased.|
|Competitive||Competitive||Equipment is more expensive, rounds are shorter, and capturing objectives is faster.|
|CompetitiveLoadouts||Competitive Loadouts||Player classes are replaced with those from Competitive.|
|FastMovement||Fast Movement||Move Faster.|
|Frenzy||Frenzy||Fight against AI enemies who only use melee attacks. Watch out for special enemies.|
|Guerrillas||Guerrillas||Start with 5 supply points.|
|Hardcore||Hardcore||Mutator featuring slower movement speeds and longer capture times.|
|HeadshotOnly||Headshots Only||Players only take damage when shot in the head.|
A live fragmentation grenade is dropped on death.
|LockedAim||Locked Aim||Weapons always point to the center of the screen.|
|NoAim||No Aim Down Sights||Aiming down sights is disabled.|
|PistolsOnly||Pistols Only||Only pistols are available along with normal equipment and explosives.|
|ShotgunsOnly||Shotguns Only||Only Shotguns are available along with normal equipment and explosives.|
|SlowCaptureTimes||Slow Capture Times||Objectives will take longer to capture.|
|SlowMovement||Slow Movement||Move slower.|
|SoldierOfFortune||Soldier of Fortune||Gain supply points as your score increases.|
|SpecialOperations||Special Operations||Start with 30 supply points.|
|Strapped||Strapped||Start with 1 supply point.|
|Ultralethal||Ultralethal||Everyone dies with one shot.|
|Vampirism||Vampirism||Receive health when dealing damage to enemies equal to the amount of damage dealt.|
|Warlords||Warlords||Start with 10 supply points.|
You may specify multiple mutators by using a comma-separated list. For example, to enable Hot Potato and Vampirism, specify
-mutators=HotPotato,Vampirism on the server command line.
Some mutators can be configured beyond what is provided by the defaults. These mutators are listed below. All Mutator settings go in Game.ini.
Headshots Only settings can be configured under
|INI Entry||Default||Travel URL Parameter||Description|
|bCheckMeleeDamage||false||N/A||Should melee be checked for headshots|
Hot Potato settings can be configured under
Travel URL Parameter
|GrenadeClass||/Game/Game/Actors/Projectiles/BP_Projectile_M67.BP_Projectile_M67_C||N/A||The grenade type to be dropped on death.|
|ThrowbackWeaponClass||/Game/Game/Actors/Weapons/Grenade/BP_Grenade_M67.BP_Grenade_M67_C||N/A||Weapon used for throwing back the dropped grenade.|
|false||HotPotato_bIgnoreHeadshots||Don't drop a grenade if it was a headshot?|
|bBotsOnly||false||HotPotato_bBotsOnly||Only drop grenades for bots?|
Vampirism settings can be configured under
|INI Entry||Default||Travel URL Parameter||Description|
|bCountFriendlyFire||false||Vampirism_bCountFriendlyFire||Count friendly fire towards health gain?|
|MaxHealth||1000||Vampirism_MaxHealth||The maximum amount of health that you can gain from damaging other players.|
A bunch of general gameplay options can be added to Game.ini. Below is a table that lists the section they need to be under (find or add them to the file) as well as the options available under that section.
|bKillFeed||False||Is the kill feed enabled?|
Is the kill feed enabled for dedicated spectators and replays?
Show information about a death (killer, weapon) to the victim?
|bKillerInfoRevealDistance||False||Reveal distance of kills?|
|TeamKillLimit||3||Limit for the number of team kills one player can perform before being kicked.|
Grace timer between team killing incidents.
How long until a player’s TK count reduces by 1.
|bDeadSay||False||Can alive players see messages from the dead?|
|bDeadSayTeam||True||Can alive players see messages from dead teammates using team-only chat?|
|bVoiceAllowDeadChat||False||Can alive players hear voice chat from dead players?|
|bVoiceEnemyHearsLocal||True||Can proximity voice chat be heard by enemies?|
|bKillFeedGameStartingIntermissionTime||5||The additional time to wait for additional players during the starting intermission.|
How long players are frozen before transitioning to the round intermission screen.
How long is spent on the intermission screen.
|PostGameTime||15||How much time is spent between last post round and game over.|
|bAutoAssignTeams||True||Should teams be assigned on connect?|
Enables friendly fire.
Damage modifier for friendly fire.
|FriendlyFireReflect||0||Damage modifier for friendly fire that is mirrored back at the attacker.|
|bAutoBalanceTeams||True||Enables auto team balancing.|
|AutoBalanceDelay||10||How long to wait after detecting unbalanced teams.|
|bMapVoting||True||Enabled map voting at the end of each game.|
|bUseMapCycle||True||Enables the use of the map cycle. If disabled, the current map loops indefinitely.|
Allow both teams to talk to each other between rounds.
|IdleLimit||150||How long a player can be idle for before being kicked.|
|IdleLimitLowReinforcements||90||How long a player can idle for when there are low reinforcements.|
|IdleCheckFrequency||30||How frequently to check for idle players.|
For example, enable the kill feed, show kill distance and disable friendly fire you would enter the following in your Game.ini:
Gamemode options can be defined through Game.ini, with each section corresponding to a given gamemode. The INI sections are as follows:
Any of the below settings under the general sections can be applied globally by putting them in the appropriate INI section.
|ObjectiveCaptureTime||Varies||How long it takes to capture territorial objectives.|
|ObjectiveResetTime||-1||How long objective progress decays with no one on the point. Negative value disables.|
|ObjectiveSpeedup||0.25||Additional capture speed-up for each player on the point.|
|ObjectiveMaxSpeedupPlayers||4||Maximum players taken into account for capture speed-up.|
|MinimumPlayers||1||Minimum players required on each team to start the game.|
Maximum number of rounds to play.
|WinLimit||Varies||Number of rounds required for game victory.|
|GameTimeLimit||-1||Maximum duration a game can last. Negative value disables.|
|PreRoundLimit||10||Amount of “freeze time” at the start of a round.|
|RoundTime||Varies||Duration of the round.|
Amount of overtime given when there’s an objective being contested after the round timer expires.
|TeamSwitchTime||10||Minimum additional time spent between team switches.|
|SwitchTeamsEveryRound||Varies||How often to switch teams. 0 = never, 1 = every round, 2 = every other round, etc.|
|bAllowPlayerTeamSelect||True||Allow players to switch to the other team?|
|BotQuots||Varies||Bot quota to fill.|
|InitialSupply||15||Amount of starting supply points.|
|MaximumSupply||15||Maximum supply that can be earned.|
Enable supply gain throughout the round.
|bAwardSupplyInstantly||False||Should supply gain be awarded instantly?|
|SupplyGainFrequency||150||Score threshold for earning supply.|
|RoundTimeExtension||300||How long a round is extended for each successful capture.|
|AttackerWavesPerObjective||5||Number of waves attackers get per-objective.|
|AttackerWaveDPR||0.25||Percentage of attacker team that has to be dead to trigger a reinforcement wave.|
|AttackerWaveTimer||20||Duration of attacker reinforcement wave timer.|
Number of waves attackers get per-objective.
Percentage of defending team that has to be dead to trigger a reinforcement wave.
|DefenderWaveTimer||35||Duration of defender reinforcement wave timer.|
|LastStandSetupDelay||10||Delay for the last defender spawn zone to be disabled.|
|AdvanceAttackerSpawnsDelay||30||Delay in advancing the attacker spawns.|
|StartingWaves||15||Number of waves each team starts with.|
|CapturingBonusWave||2||Number of waves a team gains for capturing an objective.|
|RegressSpawnsTimer||10||Timer used for giving players a chance to fallback after losing an objective.|
Starting reinforcement waves for each team.
Number of bonus waves to get when an objective is taken while the team cache is still intact.
General Coop [/Script/Insurgency.INSCoopMode]
AI difficulty factor (0-1 range).
|bUseVehicleInsertion||True||Use vehicle insertion sequences where possible.|
|FriendlyBotQuota||4||Friendly bots for coop.|
|MinimumEnemies||6||Minimum number of enemy bots.|
Maximum number of enemy bots.
|DefendTimer||90||Time to defend against counter attack with small player team.|
|DefendTimerFinal||180||Extend duration of counter-attack by this on the final point.|
|RetreatTimer||10||Time to force bots to retreat after a counter-attack.|
“Dead player ratio” that must be reached before respawning the bot team.
Bot respawn delay.
Time bots will rush the cache after destruction.
|CounterAttackRespawnDPR||0.2||“Dead player ratio” that must be reached before respawning the bot team during a counter-attack.|
|CounterAttackRespawnDelay||20||Bot respawn delay during counter-attack.|
|ObjectiveTotalEnemyRespawnMultiplierMin||1||Multiplier of bots to respawn with minimum player count.|
|ObjectiveTotalEnemyRespawnMultiplierMax||1||Multiplier of bots to respawn with maximum player count.|
|FinalCacheBotQuotaMultiplier||1.5||Increase in bot quota for final objective if it’s a cache.|
Community servers can opt into enabling player voting on their servers. This can be enabled by entering the following into Game.ini:
This will enable voting and include the vote kick issue, which as of now is the only supported voting issue. When additional vote issues are available, you would add a new line below for each issue you want to enable.
When voting is enabled, players can press Esc and click “Call Vote” to vote for a vote issue. Pressing F1 will vote yes and pressing F2 will vote no.
Vote Kick Options
INI Section: [/Script/Insurgency.VoteIssueKick]
|bCanTargetEnemies||false||Can the vote target an enemy player?|
|bRequiresMinimumToStart||true||Does this issue require a minimum number of players to show their voting intentions before commencing the vote?|
|DefaultVoteBanDuration||120||How long a ban for any other reason will last in seconds.|
|IdleVoteBanDuration||-1||How long voting an idle player will ban them for in seconds, -1 represents a kick only.|
Minimum ratio of team required to start a vote.
|MinimumPlayersRequired||3||The number of players required to start a vote.|
|MinimumYesNoDifference||2||For the vote to succeed, yes must have this number of votes over no.|
|VotePassRatio||0.75||Ratio of team required to vote yes for vote to pass.|
How long until this vote can be called again.
If something is unclear, or you require additional information, please create a support ticket. We're always here and happy to help.