Growth
Methods
A searchable set of ways to get players. Each one carries a cost, a difficulty, a time estimate, and an honest note on what it returned.
The part nobody writes down
Not because the build was bad. Because nobody tells you what to do on day 3, day 30, or the morning the player count stops going up. ServerPlaybook is the operational side of running a server, written by people who have actually done it and are willing to show the numbers.
Get the first release
One email when it opens. Nothing else, ever.
What is inside
No motivational filler. Every page tells you what to do, what it costs you, and what to expect back.
Growth
A searchable set of ways to get players. Each one carries a cost, a difficulty, a time estimate, and an honest note on what it returned.
Sequence
What to be doing at 0 players, at 50, at 250, at 1000. The order matters more than the tactics.
Pre-launch
Finding testers, running feedback rounds, bug templates, and knowing when you are actually ready to open the gates.
Reach
Server lists, forums, promo slot auctions, Discord, short form video. Which ones convert and which ones waste your money.
People
Hiring helpers who last, writing partnership outreach that gets a reply, and structuring deals with creators.
Revenue
Rank design, pricing, founder packs, and staying on the right side of the EULA without gutting your income.
Sample entry
Every entry is the same shape, so you can compare two options in ten seconds instead of reading two blog posts.
Paying for a pinned or banner placement on an established community forum. Slower than a server list, but the traffic knows what a server is and sticks around longer.
Common mistake Judging the slot on the join spike. A forum slot that sends 40 players who mostly stay beats a list spike of 400 who are gone by Tuesday, and only one of those is worth renewing.
The ladder
The advice that works at 30 players actively hurts you at 500. Each stage gets its own checklist.
Who is writing this
This is being written by people who have launched networks, watched most of them fail, and paid for the mistakes in server bills and burnt weekends.
Everything here has been run at least once. Where a method did not work, that gets written down too, because the failed attempts are the half nobody publishes.