Key takeaways
- A whitelist is the single most effective moderation tool, and it costs one command per player.
- Write the rules before the first player joins. Rules invented after an incident always look personal.
- Decide the claim question – protected land or trust-based – on day one, because changing it later breaks builds.
Technical setup takes an afternoon. The part that decides whether a server lasts six months is what happens in the first week, and almost none of it is technical.
Whitelist first
An open server on a public list will be found by automated scanners within hours. A whitelist removes that entire category of problem, and for a friends server it costs nothing – you add ten names once.
If you want to grow past that, an application step is the cheap version of moderation. Anyone willing to write three sentences about why they want to join is already a better bet than anyone who found your IP on a list.
Three rules, written down
Long rule lists do not get read. Three do. The ones that matter in practice: do not take what you did not build, do not build within a set distance of someone else without asking, and do not use anything that automates play.
Write them before opening. Rules that appear the day after an incident always read as a judgement on one person, and that is how communities split.
The claim decision
Two models. Protected claims, where a plugin enforces boundaries and griefing is impossible. Trust-based, where nothing is protected and the rule is social. Both work. Mixing them later does not, because a plugin added after six months will not know who built what.
Small friend servers usually do better on trust: the plugin adds friction to every shared build, and the people involved are not the threat. Public servers need claims, because the threat is exactly the people you have not met.
Logging is not moderation, but you need it
A block logger will not stop anything. It answers the question that always comes up – who broke this, and when – and turns an argument into a lookup. On a trust-based server it is the one plugin worth installing, precisely because it replaces suspicion with a fact.
Our view is that the most damaging thing on a small server is not griefing. It is an unresolved incident that everyone has a different account of, and the quiet loss of trust that follows. A log is cheaper than that conversation.
What to do on day one
Whitelist on, three rules posted where people will see them, a block logger installed, a claim model chosen, and one person other than you who can kick someone at 2am. That is a functioning server. Everything after it is decoration.
The performance side of the same setup is covered in the tuning guide, and the mod list question in the small SMP piece.
The permissions question
Give one other person the ability to act while you are asleep. A server where only the owner can kick is a server where an incident runs for eight hours because it started at 2am in your timezone.
Keep the list short. Two people with real authority works. Six people with partial permissions produces inconsistent decisions and an argument about who was allowed to do what.
Spawn is a statement
Whatever sits at spawn tells every new player what the server is. A bare platform says nothing and gets built over. A small hub with signs explaining the rules, a map of claimed areas and a path out to unclaimed land does more moderation work than any plugin, because it sets expectations before anyone picks up a pickaxe.
Protect it. Spawn is the one area worth locking down even on a trust-based server, because it is the first thing anyone sees and the only thing everyone shares.
Handling the first real incident
There will be one. Someone takes something, someone builds too close, someone leaves a lava trail across a shared path. The response that keeps a server alive is boring: check the logs, establish what happened, apply the written rule, say what you did in public, and move on.
What kills servers is a decision made in private that other players hear about second-hand. Even a decision people disagree with survives if the reasoning is visible.
When to grow
Not until the small version works. A ten-player server with active building and a settled culture can absorb newcomers. A quiet server with three regulars cannot – adding twenty strangers to it does not create activity, it creates a stranger server. The mod list and hardware side of growing is covered in the server specs piece.
Chat and voice
Most servers end up running a chat platform alongside the game, and that is where the community actually lives. It is also where moderation problems appear first – a dispute in chat precedes a dispute in the world by a day or two.
Keep the same three rules applying in both places, and keep announcements in one channel rather than scattered. A server where the rules differ depending on which window you are in is a server with no rules.
Images: Valhelsia Structures project gallery on Modrinth.