What a whitelist actually selects for
An application detects willingness to spend twenty minutes, not intent — a griefer will write the paragraphs and a good player browsing on a Tuesday will not. That buys commitment before arrival, shared norms and a door narrow enough that bans hold, at the cost of everybody who would have been good and did not apply. The middle option is open entry with permissions unlocked later, which keeps the intake and most of the commitment effect.
By SweetMask · · 4 min read
Whitelists are justified as a filter against bad actors. They are not very good at that, and they are extremely good at something else, which is why servers that use them feel different in ways the stated purpose does not explain.
What an application form selects for is effort. Everything else follows from that.
The filter is not about intent
An application asks somebody to write a few paragraphs, wait, and possibly be rejected. Nothing in that process detects whether a person will grief, argue with admins or leave after a week.
What it detects is whether they were willing to spend twenty minutes on the possibility of playing here. That is a real signal and it is not the advertised one — a griefer who wants in will write the paragraphs, and a perfectly good player who was browsing a list on a Tuesday evening will not.
So the population that arrives is filtered for patience and for having already decided, which produces a noticeably calmer server and an entirely different intake.
What that buys
Commitment before arrival. Somebody who applied has invested before playing a minute, and people protect investments. This is most of why whitelisted servers retain better, and it is not caused by the quality of the applicants.
A shared starting point. Everybody read the same rules and answered the same questions, so the norms are established before anyone joins rather than negotiated afterwards.
Moderation that barely runs. Not because bad actors were screened out. Because the door is narrow enough that anybody removed cannot casually return, which is the one context where a ban is genuinely a wall rather than a delay.
What it costs
The people who would have been good and did not apply, and there are far more of them than the rejections.
Applications filter out the curious, the busy, the shy, and anybody who does not yet care enough about this specific server to work for entry, which describes almost everybody at the moment they first encounter it. A whitelisted server therefore cannot grow from a listing, because the listing produces browsers and browsers do not apply.
It also cannot recover from a decline. Once the population drops below the point where the server is worth applying to, the only intake mechanism is one that requires the server to already look worth the effort, and that loop only runs downward.
The form is doing something different than it looks like
Most application forms ask about experience, playstyle, and why you want to join. The answers are near-worthless as information — everybody writes the same three paragraphs and the honest answer to the last question is always "it looked good".
The form is not collecting data. It is imposing a delay and a cost, and it would work about as well if it asked nothing, which is worth knowing before spending an evening designing better questions. A whitelist people actually complete is mostly a matter of length and response time, not of what is asked.
The exception is a form that states something the applicant must agree to. That does work, because it makes the norms explicit at the one moment somebody is paying attention.
The middle option almost nobody uses
Open entry with limited permissions, and the whitelist applied to what you can do rather than to whether you can connect.
Anybody joins and plays. Building, claiming, trading or voice unlock after a form, or after a week, or after a regular vouches. That keeps the intake of an open server and most of the commitment effect of a closed one, and it moves the decision to the point where both sides have information, which is what an onboarding path is for and what a front-door application cannot do.
When the closed door is right
When the server's product is the absence of strangers. Long-running survival worlds, roleplay with continuity, communities of people who know each other: there the friction is the feature and the cost is worth paying.
When the server needs players, it is the wrong tool, and it is most often reached for exactly then.
What rejection actually costs
The part of the process nobody designs is what happens to the people you turn down, and on a small scene it matters more than the acceptances.
A rejected applicant is not a neutral outcome. They spent twenty minutes on you, they were told no by a person, and they will tell other people about it. On a large game that disappears into the noise. In a community of a few thousand players around one niche title, half a dozen rejections are a reputation.
Which means the rejection is worth as much care as the form. A specific reason, even a brief one, reads as a decision. Silence reads as contempt, and silence is what most servers deliver, because writing the message is unpleasant and there is no deadline on it.
The cheapest available improvement to any whitelist is a two-line reply that says what would change the answer. It converts a rejection into a deferral, which is frequently what it actually was, and it is the difference between somebody who reapplies in three months and somebody who tells the scene you are difficult.
The whitelist that is really a queue
Worth separating out, because it is a different thing wearing the same interface: some servers use an application not to filter but to meter.
The server is full, or the staff can only absorb a few newcomers a week, and the form is a way of admitting people at a rate the community can actually digest. That is a legitimate and underused reason to have one, and it fails when it is not said, because an applicant who was actually in a queue and thinks they were being judged draws a conclusion about themselves that was never intended.
If the form is a queue, say it is a queue and give a rough position. Almost nobody does, and it turns the worst part of the experience — the waiting without information — into an ordinary thing people are used to.
whitelistonboardingcommunityserver administration
More
Why Minecraft 1.8 PvP never died
The 1.9 Combat Update split Minecraft PvP in 2016, and the side that stayed on 1.8 never had to move, because plugins let servers keep the old fighting for newer clients.
SweetMask · · 4 min
Automated moderation arrives, and the old problems come with it
Discord's AutoMod and machine-learning filters cover every hour of the day, but they miss context and polite harassment, and they make appeals harder to answer.
SweetMask · · 5 min
Why consoles never got community servers
Consoles only let players reach what the platform can vouch for, and nobody vouches for a community server. Crossplay has let console players in as guests, never as hosts.
SweetMask · · 4 min