Ask any veteran admin how to fill an empty CS 1.6 server and a large share will say the same thing: run 24/7 de_dust2. It is not nostalgia — it is a discovery advantage. Players browsing the server list scan for a map they already know, and dust2 is the one map every CS player has memorised. This is an honest look at why the single-map model still works, exactly how to set it up, and the point at which it stops helping.
1. Why one map fills faster than twenty
A new server's problem is not retention, it is the first few players — nobody joins an empty server, so you need something that pulls a lone browser in. A 24/7 dust2 server wins that moment three ways. The name is a keyword players actively search the browser for. The map is instantly playable with zero learning curve, so a joiner stays instead of leaving after one confusing round on an unknown map. And a familiar map lowers the bar for the second and third player, who see one person on dust2 and think "I know that, I'll play a round." Variety is a retention feature; it does nothing for cold-start discovery. Related reading: getting players on a new server and picking a mod that already has players.
2. Lock the map with mapcycle and cvars
A true 24/7 server never rotates off the map. Put a single entry in mapcycle.txt:
de_dust2
With one line, the "next map" is always dust2, so every map change reloads it. Reinforce that in server.cfg so the current and default map are also dust2:
map de_dust2 mp_timelimit 30
Keep mp_timelimit non-zero so the map still "ends" and cleanly restarts the same map — this resets scores and keeps the round flow honest without ever leaving dust2. The mechanics of what ends a map are in mp_timelimit and map flow, and how the cycle file is read in mapcycle.txt setup.
3. Put the map name where browsers see it
The keyword only helps if it is visible. Set the hostname to advertise the map explicitly:
hostname "24/7 Dust2 | Fast DM | No Lag"
A browser filtering or eyeballing the list reads the hostname, not the current map column alone. "24/7 Dust2" in the name is doing marketing work every second the server is listed. Make sure the server is actually in the list first — sv_lan 0 and a working master registration, covered in getting into the master list.
4. Decide whether to disable RTV
A 24/7 server and a Rock The Vote plugin are in tension — the whole promise is that the map never changes. If you run RTV or a map chooser, either remove it or restrict its map list to dust2 only so a vote cannot break the promise the hostname makes. Nothing frustrates a player who joined "24/7 Dust2" more than a vote dumping them onto de_aztec. If you want variety, run it as a separate server with its own rotation rather than diluting the 24/7 one.
5. Where the model breaks down
Single-map filling is a starter strategy, not a growth ceiling. Two limits show up as you succeed. First, regulars burn out — the same map every session eventually pushes your most loyal players toward variety, so a mature community usually runs 24/7 dust2 to acquire players and a second rotation server to keep them. Second, the tactic is crowded: many admins run 24/7 dust2, so you are competing on ping, slot count, and lack of lag, not novelty. That is why the hostname promises "No Lag" — on this map, performance is your only differentiator. Get the server FPS and rates right (see ReHLDS performance cvars) because a laggy dust2 loses to the dozen other dust2 servers one line down the list.
Common errors
- Server rotates off dust2 anyway —
mapcycle.txthas more than one line, or an RTV/mapchooser plugin is changing it. Trim the cycle to one entry and restrict the vote. - Map name not visible in the browser — the hostname does not mention dust2. Put "24/7 Dust2" in
hostname. - Fills briefly then empties every night — that is the retention limit, not a bug. Add a second varied server for regulars.
- Loses to identical servers — you are competing on performance and ping now. Fix server FPS and choke, not the map.
- Map restarts but scores never reset —
mp_timelimit 0. Keep it non-zero so the map cycles cleanly.
Verification
Restart the server, let a map end, and confirm it reloads de_dust2 rather than advancing — watch the console print the same map name. Open the in-game server browser from a second machine, search for your hostname, and confirm "24/7 Dust2" appears with a healthy ping. Then leave it running through a peak evening and watch the player count: if it fills from zero to a handful within a busy window, the discovery advantage is working. If it never crosses the first two or three players, the problem is upstream — the server may not be in the master list at all.
