Players pick a CS 1.6 server in seconds: the name, the map, the ping, how many people are on it. They stay for other reasons: no lag, fair admins, friends online. This guide covers both, with live CS 1.6 figures from GTScope.
See where CS 1.6 players are now
These are the CS 1.6 servers online on GTScope right now, and the people on them, without declared bots. Every one of those servers wants your players. A new server rarely wins them with a new idea. It wins them by doing the basics better: ping, stability, fair admins, a mode done well.
Make the server run well
Host it near your players
Ping decides first: a server at 60 ms loses to one at 15 ms with the same mode. Host it in your players' country; for Romanian players, a data centre in Romania. Pick a host with DDoS protection for game traffic. CS 1.6 servers get attacked, often by rivals, and a server that drops every evening never fills.
32 slots, stable ping, no lag
On a public server, run 32 slots: it is the most CS 1.6 allows, and what players expect.
Then check for lag yourself: join your server, open the console and type net_graph 3. With the server full, loss and choke should stay at 0 and the ping should not jump. If they climb as it fills, change the plan or the host before you advertise.
Test at the busiest hour, not at noon. A server that runs fine with 5 players can choke with 32.
Keep the engine and plugins up to date
Run an up-to-date engine: the official one, updated through SteamCMD, or a maintained build such as ReHLDS. Old builds have known bugs that crash a server. AMX Mod X is the usual plugin platform: keep it and every plugin current, and follow three rules:
- Take plugins from known sources, such as the AlliedModders forum. A free "server pack" from a random site is the classic hiding place for a backdoor that gives a stranger admin rights.
- Remove what you do not use. Every plugin costs CPU, and any of them can crash the server.
- Never use plugins that change players' settings or send them to other servers. Players find out and do not come back.
Pick a mode and the maps people know
One mode, in the name
Players come for a mode. Pick one they recognise (Classic/Public, Zombie, Deathmatch, JailBreak, Surf, Furien) and get it right before you add anything else. A Zombie server with balanced classes beats one that mixes five mods badly.
Say the mode in the server's name. Players read it in the game's server list, and so does GTScope: it takes the mode from the name first, then from the map's prefix. The form has no field for modes, and a Deathmatch or Furien server plays ordinary maps, so its name is the only place that says the mode. With the mode in its name, your server shows up in that mode's lists. Use the word players use, and set it in server.cfg so it survives a restart:
hostname "YourName | Zombie Plague"
Play the maps people play
These are the CS 1.6 maps played the most on GTScope these days. For a Classic/Public server, build a short rotation from them, not forty maps nobody has: every unknown map is a download, and many players leave rather than wait. For custom maps, set up fast downloads with sv_downloadurl.
Other modes have their own maps (zm_, jail_, surf_). On the CS 1.6 maps page, each map has a page with the servers that play it. Once the server is yours, its Statistics show which maps bring players and which lose them. Drop the ones that empty it.
Fair admins, clear rules, an honest VIP
Admins and rules
Players leave a server where an admin kicks them for winning. Pick a few admins you trust over many you do not know, spread over the hours people play. Write short, clear rules, show them in the MOTD and on your forum, and apply them to everyone, admins and VIPs included. Give players a place to contest a ban, and answer every appeal.
A VIP that is not pay-to-win
VIP money keeps many servers running, but the wrong VIP empties them. Sell comfort and looks: a reserved slot, a chat tag, a player model. Never sell an advantage: extra HP, extra damage, free AWPs. When people win because they paid, the others leave, and the VIPs follow.
Anti-cheat
Cheaters empty a server faster than lag. Run a server-side anti-cheat and keep it updated. Have an admin spectate a suspect before any ban, record a demo as proof, and keep a public ban list with the reasons. A wrong ban costs you a player and their friends; a cheater left alone costs you the server.
Build a community and time your events
Busiest at 21:00, quietest at 08:00 — the average of the last 15 days, by the clock of Bucharest.
| Hour | Players |
|---|---|
| 00:00 | 6,632 |
| 01:00 | 6,343 |
| 02:00 | 5,996 |
| 03:00 | 6,123 |
| 04:00 | 5,324 |
| 05:00 | 5,187 |
| 06:00 | 5,048 |
| 07:00 | 4,949 |
| 08:00 | 4,900 |
| 09:00 | 5,048 |
| 10:00 | 5,316 |
| 11:00 | 5,498 |
| 12:00 | 5,633 |
| 13:00 | 5,795 |
| 14:00 | 6,180 |
| 15:00 | 6,375 |
| 16:00 | 6,544 |
| 17:00 | 6,761 |
| 18:00 | 7,034 |
| 19:00 | 7,288 |
| 20:00 | 7,518 |
| 21:00 | 7,655 |
| 22:00 | 7,549 |
| 23:00 | 7,154 |
The chart shows the average number of CS 1.6 players on GTScope at each hour of the day, by the clock of Bucharest. The highlighted bars are the busy hours; the line under the chart names the busiest hour and the quietest. Use it three ways:
- Hold events in the busy hours: a 5v5 mix, a clan war, an AWP or knife night. Announce them days before.
- Have admins online in the busy hours, when most cheaters show up.
- Restart the server once a day at the quiet hour. A restart clears what long-running plugins pile up in memory, and few players are on to notice.
Once the server is yours, Peak hours in its Statistics shows the same for your own players, over the last 14 days.
People come back for people. Give them a Discord for daily talk and event news, and a forum for the rules, admin applications and ban appeals. Put both links in the MOTD and on your server's page. Once the server is yours, paste your Discord channel's webhook under Alerts and tick A live status message in the channel: GTScope keeps one message up to date with who is playing, the map and a link to vote.
Why fake players do not work on GTScope
Some owners fill the server with bots or fake players to look full. On GTScope that buys little:
| What you do | What GTScope counts |
|---|---|
| Bots the server declares | Never counted as players |
| A CS 1.6 server reporting over 32 players | Its players are not counted |
| "Full" at night as much as at peak | Looks fake, counts less |
| More players than slots | Those hours do not count |
The activity part of the ranking prefers real players over 7 days, compared with the other CS 1.6 servers, and it is small. What weighs most is the number of distinct people who voted this month; repeat votes count much less. Activity, uptime, favourites and reviews come after, and together they are worth at most one person's first vote of the month. The rules are on the ranking page.
Fakes also cost you real players: someone who joins a "full" server and finds bots does not come back.
Get listed or claim your server
- On the page for owners, press Add your server free and fill in the name, the game, the country, the IP and the port. An administrator approves every new server, and you get a notification on the bell when yours is approved. A server you add yourself is yours from the start.
- Already listed? Then claim it: on its page, press Claim this server, then Get my code. Add the code to the name in the console or through RCON, with no restart:
hostname "YourName | Zombie Plague GTS-XXXXX". If the name is long, put the code at the start. Press Verify Now. - When the site says The server is yours, take the code out of the name.
Your server then appears among the CS 1.6 servers, with its place in the game and in its country. As its owner, you get the statistics above, the alerts and the list of your voters.
Next steps
- Ask your players to vote, in the game, on Discord and on the forum: read how to get more votes.
- Put your banner on CS forums. The Standard Banner (560x95) fits a forum signature and shows your players and map live: see the banner and widget guide.
- After a week, open Statistics and see what kept players and what lost them.