Insurgency: Sandstorm
Scenarios, map rotation, mod.io content and the tokens the server needs.
Everything in Your panel applies. These are the Sandstorm specifics.
Startup parameters
- Hostname
- Map Name and Scenario — the map and the game mode played on it
- Max Players
- Additional Switches — extra launch arguments
- GST and GSLT — Steam tokens for public listing
Scenario matters as much as map. The same map has different scenarios for push, firefight, checkpoint and so on, and picking a scenario that does not exist for your map is the usual reason a server starts on something unexpected.
Map rotation
The rotation and mutators live in the server's configuration files, edited in the file manager. Adding a map to the rotation takes a couple of minutes.
You can also tune the server-side rules the game exposes — bot counts and difficulty on co-op modes — then restart to apply.
Community maps and mods
Sandstorm has official mod support through mod.io. You enable it by adding the mod IDs and your mod.io credentials to the server config. Once set, connecting players are prompted to download what the server uses.
Both the mod list and the credentials are editable in the file manager or over SFTP.
Memory
Plans start at 8 GB. Sandstorm is demanding, and the number that pushes it up most is bot count on co-op scenarios — a full checkpoint server with heavy bot waves uses considerably more than a small versus match.
Add memory for a full player count, heavy bots, or a rotation of large community maps.
Admin
Admin lists live in the configuration files. The console is available for server-level commands.
Backups
Sandstorm servers keep less persistent state than survival games, but your configuration and mod setup are worth protecting. A manual backup before a rotation overhaul saves rebuilding it by hand.