Swarm Hosts / Guides

Counter-Strike: Source

Counter-Strike: Source uses a shared TCP/UDP game port and stores persistent server files under /home/steam/css. Swarm Hosts waits for a Source-query response before marking the Swarm Server ready.

Quick facts

  • Persistent data: /home/steam/css
  • Network: one published port number on both TCP and UDP
  • First start: installs the dedicated server before the readiness check can pass
  • Public access: use the assigned host or relay address and published port

Launch and settings

  1. Choose Counter-Strike: Source.
  2. Set the server name, starting map, player limit, and a unique join password, or clear the join password if the server should be open to everyone.
  3. Set a private RCON password if you want to use Server Actions.
  4. Review bot quota, bot difficulty, team-play, starting-money, LAN, and tickrate settings.
  5. Launch and allow up to 15 minutes for a first-time install on a slower host.

After launch, open Settings → Counter-Strike: Source Settings to change the managed values. Saving settings recreates or restarts the server, so connected players will be disconnected.

Server Actions

Open Server Tools → Actions after the server is running and a non-empty RCON password has been saved. Swarm Hosts offers:

  • Server status
  • List players
  • List installed maps
  • Broadcast message
  • Set bot quota
  • Set bot difficulty
  • Restart round
  • Change map
  • Kick player

Map changes and player kicks require Swarm Server admin access. Disruptive actions require confirmation. The page accepts typed fields only; it does not accept arbitrary RCON, console-variable changes, plugin commands, shutdown, or shell input.

See Server Actions for the shared safety model.

Connect

Players can join through the in-game server browser or client console:

connect <host>:<published-port>

The TCP and UDP mappings must use the same published port number. Share the endpoint shown by Swarm Hosts, not the container's default port.

Mods and plugins

MetaMod:Source and SourceMod are manually managed under the persistent cstrike/addons tree. Create a backup, stop the Swarm Server, upload a compatible plugin set through Files & Backups, then start and validate the server. Automatic plugin discovery and dependency resolution are not currently available.