In short: split the rules into sections — general, chat, cheats and mods, bugs and dupes, gameplay, accounts, trading, staff. One rule per violation, with the punishment and its length next to it. Say which mods are allowed and where to appeal. Post them where a player sees them before playing: on Discord, with a /rules command and as a link in the pause menu. You can build a base for your game mode for free in the rules generator.
The sections of a rule set
| Section | What it covers | Example rule |
|---|---|---|
| General | Agreeing to the rules, what punishments are based on, where to appeal | "Punishments are based on evidence: the anticheat log, server logs, recordings" |
| Chat | Insults, spam, advertising, personal information | "No advertising other servers — in chat, on signs, in books or in usernames" |
| Cheats and mods | What's banned, which mods are allowed, macros | "Mods without an advantage are allowed: performance, shaders, UI" |
| Bugs and dupes | Don't use them, report them | "Found a bug? Report it to staff instead of using it" |
| Gameplay | Griefing, spawn-killing, lag machines, teaming — depending on the mode | "No breaking or burning other players' builds" |
| Accounts | Alts, ban evasion, responsibility for your account | "No evading a ban on another account" |
| Trading and store | Real-money trading, scams, what store perks give | "Store ranks aren't refunded on a ban" |
| Staff | Moderators' decisions, impersonating staff, false reports | "Staff never ask for your account password" |
Wording that leaves nothing to argue about
- One rule per violation. "No insults or advertising" is two rules with different punishments. Merge them and moderators will punish differently.
- Specifics, not generalities. Not "no unfair modifications" but "KillAura, Reach, AutoClicker, Fly, Speed, Scaffold, X-Ray or anything else that gives an advantage".
- What's allowed is a rule too. A list of allowed mods (performance, shaders, a minimap that doesn't show players or caves) heads off half the questions and appeals.
- The punishment next to the rule. A player should know the price before breaking it.
- Only what you enforce. A rule nobody checks undermines the rest. If you don't run screenshare checks, don't write about them.
- A last-updated date. Change the rules — change the date and tell the players. Punishing yesterday's act under a rule added yesterday isn't fair.
The punishment scale
A punishment fits the offence and grows on repeat: a warning, a mute, a temporary ban, a permanent ban. Decide in advance where your server sits on that scale and keep it the same for everyone — newcomers and paying players alike.
| Offence | Soft | Standard | Strict |
|---|---|---|---|
| Insults | 30-minute mute | 2-hour mute | 1-day mute |
| Advertising | 1-day mute | 3-day ban | Permanent ban |
| Cheats | 14-day ban | 30-day ban | Permanent ban |
| Bugs and dupes | 7-day ban and items removed | 30-day ban and items removed | Permanent ban |
| Griefing | 3-day ban and rollback | 14-day ban and rollback | 30-day ban and rollback |
Durations and repeat ladders are easiest to run in a punishment plugin: LiteBans and LibertyBans have templates that work out the next step themselves — see ban plugins. A staff table with what to attach to each punishment is in the moderation team.
Appeals
The rules should say where to appeal a punishment, what to include (name, date, reason) and how soon to expect an answer. Repeat the same link in the ban message. An appeal is reviewed by someone other than the person who punished. How to avoid punishing honest players and how to run reviews is in false bans.
Where to post the rules
- Discord. A dedicated rules channel where only staff can post. The generator gives you the text as Markdown for Discord straight away.
- A `/rules` command in game. EssentialsX has it out of the box and shows the text from
plugins/Essentials/rules.txt— see EssentialsX. - The pause menu. Since 1.21 a server can show links in the pause menu; one of the built-in ones is "Community Guidelines". Plugins set them: in Paper's API it's
ServerLinkswith theCOMMUNITY_GUIDELINEStype. - Your website and server lists. A link to the rules in the server description — see MOTD and icon and promoting your server.
- Spawn. Signs or holograms with the key points and a link to the full text.
The rules and the anticheat must agree
The most frustrating appeals come when the rules and the anticheat say different things: the rules allow a mod and the anticheat bans for it, or the rules forbid macros and nothing catches them. Check three things. The allowed-mods list against what the anticheat allows. The ban on macros and automation against what the anticheat can actually check. The punishment strictness in the rules against the strictness in the anticheat's config.
DGuard — the best anticheat for a modern Minecraft server — is on the rules' side here: allowed mods and binds are written into its code and produce no evidence, ban or kick is set per cheat feature, and you choose the strictness. It also checks the automation that rules usually ban in a line of their own: auto-clicking, auto-fishing, auto-eating and anti-AFK. In our comparison none of the five popular anticheats other than DGuard has a full check for AutoFish, AutoEat or AntiAFK.
| Cheat | DGuard | GrimAC | Vulcan | Polar | Intave | Matrix |
|---|---|---|---|---|---|---|
| AutoClickerclicks for the player | ||||||
| AutoFishfishes by itself | ||||||
| AutoEateats by itself | ||||||
| AntiAFKfakes a player at the keyboard |
The rules generator has a "We run DGuard" line: bans follow evidence from several episodes, each comes with a report, and that report is reviewed on appeal. It's off by default — turn it on if you run DGuard. The generator runs in your browser and is free: game mode, strictness, sections — and ready text or Markdown.
FAQ
What rules should a Minecraft server have?
General terms with an appeal process, chat, cheats and allowed mods, bugs and dupes, gameplay for your mode, accounts, trading and the store, and conduct towards staff. Every point carries a punishment.
Where should I post my server rules?
Where players see them before playing: a Discord channel, a /rules command (built into EssentialsX), the "Community Guidelines" link in the pause menu, your website and server-list descriptions.
Should the rules list punishments?
Yes. Players should know the price of an offence in advance, and moderators should punish the same way. Keep the scale proportionate and stricter on repeat.
Can I sell store perks that give an advantage?
Minecraft's usage guidelines for servers allow selling gameplay perks only if they don't ruin other players' experience or give a competitive advantage.
How do I write server rules quickly?
With DGuard's free rules generator: pick the game mode, strictness and sections, and it builds the text with punishments for your website or as Markdown for Discord.
Sources
- Minecraft: usage guidelines (servers and monetization)
- Minecraft Wiki: game menu, server links
- Paper API: ServerLinks.Type
- EssentialsX: the /rules command (plugin.yml)
- EssentialsX: default rules.txt
- LiteBans: templates and ladders
- LibertyBans on Modrinth (punishment templates)
- DGuard, the best anticheat for a modern Minecraft server: checks compared with GrimAC, Vulcan, Polar, Intave and Matrix
- DGuard: installation, requirements and troubleshooting
- DGuard: supported Paper and Leaf versions