Managing the Perfect CS:GO Server

Everything learnt from managing the Counter-Strike server at work.


I currently work at Autopilot, and at 12:30 PM each day, we play Counter-Strike: Global Offensive (CS:GO). Players include the CEO, CTO, designers, software engineers and support team members. We run our own public server so anyone working remotely, overseas or from home can always join.

I have tried a lot of different settings to increase participation and engagement. This post is to share everything I've learnt about running a game server at work.



LinuxGSM (Linux Game Server managers) is the software powering the server. Valve provides other alternatives on their Developer Wiki. Previously, we used csgosl which provides a GUI but I found it limited for advanced customisation.

Ansible deploys the server, configuration and plugins. The repository can be found on GitHub:


Classic Casual has been the best mode for us. It allows more than 5 players per team, kill-cams and automatic Kevlar + Helmet and Defuse Kits per round. I tried tweaking Competitive mode to more like Casual but it didn't provide any benefits.

30 min games have been preferred over a first to 15. Depending on the map and amount of players, a first to 15 could take almost all of lunchtime. The moment the first player joins the server, the 30 min timer starts counting down.

Team collision has been enabled to make things a bit more realistic. Friendly-fire has been left disabled, to prevent rage quit moments.

64 ticks as 128 ticks was causing a lot of our Mac players to lag. We found some players did slightly better at 128 ticks...

Depending on the number of players, a small or larger map is generally chosen. Older nostalgic maps that Valve has removed such as de_dust and de_aztec are available using the Steam Workshop.


We ran a competitive ranking ladder using the RankMe plugin. The front-end is still accessible at which uses niekcandaele/CSGO-RankMe-stats


It was all fun and games until it wasn't. What I found was:

  • Players were focused on individual performances as there weren't set teams
  • Players felt the need to use the best guns rather than experimenting
  • CT Players would play too safe and let the bomb explode or round timer end
  • We began to lose players as a clear gap begin appearing good and bad performers
  • The lunchtime casual nature of Counter-Strike became too competitive

With blessing from the CEO, the ranking system was removed and games became fun again.


These are the current mods I've set up (also available in the Ansible repo linked before):

When Operation Shattered Web release in November, it broke a few of the plugins above so if something's wrong, disable plugins and wait for an update.


Slack Bot

I wrote a Slack Application to run commands on the server. It connects to the CS:GO server using the Source RCON Protocol to allow console (~) commands to be issued to the server.


This helped players that didn't know the commands off by heart to easily change the current map, restart the game, end warmup times, etc.

I'll be looking to add more functionality to the application such as a daily map voting system and sharing the results of a match after a game.

The code is available on my GitHub: