--- title: "The First 30 Regulars: A Growth Playbook" excerpt: "A concrete playbook for taking a CS 1.6 server from empty to a self-sustaining core of thirty regulars, covering the seeding problem, fixed peak hours, retention hooks, and turning players into a community." category: "hosting" tags: "growth, community" image: "" read_time: "9 min read" ---
A CS 1.6 server becomes self-sustaining at roughly thirty regulars — enough that at any popular hour a few are online, which pulls in browsers, which keeps it populated without you babysitting it. Getting to that number is a chicken-and-egg problem: players join servers with players. This playbook is the sequence that actually works, in order, from a stone-cold empty server to a living community.
An empty server stays empty because nobody joins first. You break the loop by being the first player every day at the same time. Pick one hour that suits your timezone's evening, be on the server yourself, and invite anyone you can — friends, a few AI bots for warmth (see real bots vs fake padding). Browsers who see 2–3 real players at 8pm every night will try it; an empty server at random hours they will not. Consistency of time matters more than raw hours online.
You are competing for a finite, mod-specific population. A vanilla public in an ocean of vanilla publics is invisible; a well-run mod server with a smaller audience can own its niche. Choose deliberately — zombie, gungame, CSDM, classic pubs — using picking a mod with players, and commit to it. Do not change mod every week; regulars form around a stable identity, and each switch resets your progress.
A first-time joiner decides in minutes. Remove friction: no forced download of 80MB before they can play (keep custom content lean, use FastDL so it is fast), spawn protection so they are not instantly farmed (CSB Spawn Protection), and a clear MOTD that says what the server is and how to reach the Discord. A new player who spawns, gets a fair fight, and sees where the community lives is a candidate regular.
Give players reasons to return that compound over time:
The server is where they play; the community is where they commit. Stand up a Discord and funnel every joiner into it — put it in the MOTD, announce it in-game with an adverts plugin, and wire live status into it (Discord integration). Once thirty players are in a Discord that pings when the server fills, they seed each other. That ping — "6 online, come play" — is what replaces you as the daily seeder.
You cannot be online every hour, and a server that is only well-behaved when you are watching will not grow. Promote trusted regulars to admins with limited flags so the seeding hour and moderation continue without you — but guard against abuse (preventing admin abuse). A core of a few reliable admins across timezones is what finally makes the server run itself.
Track two numbers weekly: unique players who returned on a different day (that is a forming regular) and the size of your Discord. When your fixed peak hour reliably has real players before you personally log on — when the server seeds itself — you have crossed the threshold. At that point browsers do the recruiting for you, and your job shifts from filling the server to keeping the community you built healthy. For the tactics that feed this loop, keep getting players onto a new server to hand.