Writing a Server Description That Earns the Click
Two fields, two readers, two jobs. Most owners write the same text twice and wonder why neither works. How to write a description that survives a skim.
Everything published under this tag, newest first.
Two fields, two readers, two jobs. Most owners write the same text twice and wonder why neither works. How to write a description that survives a skim.
A rules page is the most revealing document a server publishes. The four clauses that decide your experience, and how to read the tone.
You play for three weeks and hit a wall someone else bought. One question, four store categories, and a minute of checking before you have much to lose.
The player count is the least informative number on the page. Everything useful is in the shape, and it takes five minutes a week to read.
What the submission form asks and why, what happens in the seconds after you press submit, and the two cases where a listing waits for a person.
What a listing page can and cannot do for search, why a new one is invisible for weeks, and the parts an owner actually controls.
A week-by-week account of a new listing's first month: what normal looks like, which early numbers are noise, and when quiet means something is wrong.
Bots, reserved slots, idle connections and a number sampled minutes ago. What the figure is, and the three ways it gets inflated.
Every server has a shape to its day, set by the timezone of the people who built it. Reading it opens up most of the directory.
An honest accounting of every channel a server owner is sold, and why retention sets the ceiling on all of them.
A screenshot from 2024 cannot tell a visitor whether anything is happening now. A live banner can, in one line of HTML.
Voting works and nagging does not. Rewards that close the loop without corrupting the game, and why a vote share is a retention signal in disguise.