How to Write Discord Server Rules That People Actually Read

Open almost any Discord server's #rules channel and you'll find the same thing: a 2,000-word essay nobody has read since 2021. Twelve paragraphs of legalese, three different fonts, a half-broken table of contents, and somewhere around rule 14(c)(ii) a line about "respecting the community." Then the same server logs a raid the next weekend and the mods wonder why the trolls didn't comply.

Rules don't fail because people are bad. They fail because they're written for lawyers, not humans. If your goal is a server where members actually know what's allowed — and where your mod team can enforce consistently without a 40-minute Slack debate — you need rules that are short, specific, and visible. This guide shows you how to write them, with before/after examples for the rules every server gets wrong, and a full template you can copy at the end.

Why most Discord rules fail

There are four common failure modes, and most rules channels have all of them at once.

They're too long. A 3,000-word rules document is not a rules document, it's a Terms of Service. Nobody reads ToS. Your members are here to chat, play games, or watch a stream — they'll skim for 20 seconds at most.

They're too vague. "Be respectful" sounds reasonable until you try to enforce it at 2am on a Saturday. Respectful by whose standard? Yours? The member's? The mod who just woke up? Vague rules are unenforceable rules, which means they're not really rules — they're vibes.

They're too legalistic. "The administration reserves the right, at its sole discretion, to revoke membership privileges..." Stop. You run a Discord server, not a Fortune 500 HR department. Legalese signals that you don't actually know what you want to enforce, so you're hedging.

They're buried. Even good rules fail when they live in a #rules channel three categories down that members visit once on join and never again. If your rules aren't surfaced at the moment of joining — and reinforced when broken — they might as well not exist.

A good Discord rule passes three tests: a new member can understand it in five seconds, a moderator can enforce it without asking a teammate, and a troll can't argue around it.

The ideal format: 8 to 12 rules, max

If you have more than 12 rules, you have too many rules. Past that count, members stop reading and mods stop remembering. Aim for 8 to 12 short, specific lines, each one numbered and ideally fitting on a single line on desktop.

The structure that works:

1. A one-line opener that sets the vibe of the server ("This is a friendly community for indie game devs. Be cool to each other.")
2. Eight to twelve numbered rules.
3. A short "what happens if you break a rule" section.
4. A line telling people how to report problems and how to appeal.

That's it. No table of contents. No appendix. No "by remaining in this server you agree..." — they already agreed by joining.

Writing each rule: before and after

Here's where most servers go wrong. Let's fix the five rules every server has.

Rule: "Be respectful"

Bad: "Be respectful to all members. Treat others how you wish to be treated. Disrespect of any kind will not be tolerated."

Good: "No personal attacks, slurs, or harassment. Disagree with ideas, not people."

The good version names the behaviours you'll actually act on. "Disrespect" is a feeling; "slurs" and "personal attacks" are observable.

Rule: "No spam"

Bad: "Do not spam the chat. Spamming will result in punishment."

Good: "No repeat messages, no walls of emoji, no mass-pinging. Keep links to one per message unless asked."

Spam is four different behaviours. Name them. This also makes AutoMod configuration trivial — you can match the rule to the trigger.

Rule: "No NSFW"

Bad: "This is a SFW server. Inappropriate content is prohibited."

Good: "No nudity, gore, or sexual content anywhere in the server, including pfps and usernames."

"Inappropriate" is undefined. "Nudity, gore, sexual content" is enforceable. Including pfps and usernames closes a loophole every server gets caught on.

Rule: "No self-promo"

Bad: "Self-promotion is not allowed without permission."

Good: "Self-promo (your stream, YouTube, server, project) only in #self-promo. One post per week per person."

Gives a where, a what, and a how-often. Mods don't have to interpret intent.

Rule: "Follow Discord ToS"

Bad: "All members must abide by the Discord Terms of Service and Community Guidelines at all times."

Good: "Follow Discord's ToS. You must be 13+ to be here."

One line. The age requirement is the only ToS detail worth surfacing, because it's the one mods enforce.

Rules every server needs vs. rules specific to yours

There's a baseline every server should have, and then there's the layer that makes your server your server.

Universal (every server needs these):

• No harassment, slurs, or personal attacks
• No NSFW content
• No spam or mass-pinging
• No advertising or DM solicitation
• Follow Discord ToS / 13+
• Listen to moderators

Community-specific (depends on what you do):

• A gaming server might add: "No cheating talk or sharing of exploits."
• A creator server might add: "No leaks of unreleased content."
• A study server might add: "No answer-sharing for graded work."
• A trading or crypto server needs: "No financial advice presented as fact. No shilling."
• An art server: "Credit original artists. No AI-generated work in #gallery."

The community-specific rules are the ones that actually shape culture. The universal rules just keep the lights on.

Where to put the rules so people actually see them

A rules channel alone is not enough. Layer the rules across the join experience:

1. Membership screening / Discord's built-in rules gate. Discord lets you require new members to agree to rules before they can chat. Use it. This is the single highest-leverage placement — it's the only moment when a member is paying full attention.
2. A clean #rules channel with the full list, locked so only mods can post.
3. Phantom's welcome message that links directly to #rules and highlights the top three rules new members break.
4. Pinned reminders in high-traffic channels for context-specific rules (e.g. pin the self-promo rule in #self-promo).
5. An onboarding flow using Discord's Onboarding feature plus Phantom's welcome system to walk members through the server.

If a member breaks a rule and says "I didn't know" — they're often telling the truth. The fix isn't a harsher punishment, it's better surfacing.

Make consequences visible

The single biggest credibility upgrade you can give your rules is telling people what happens when they're broken. Most servers hide this because they want flexibility. The trade-off isn't worth it — vague consequences feel arbitrary, and arbitrary moderation breeds drama.

A simple, public escalation ladder:

• First offence: warning
• Second offence: timeout (1 hour to 1 day depending on severity)
• Third offence: longer timeout or kick
• Repeat / severe: ban

Serious things — slurs, NSFW, raiding, doxxing — skip the ladder and go straight to ban. Say that out loud in the rules.

This is where Phantom's moderation tooling earns its keep. Every /pmod warn, /pmod timeout, and /pmod ban is logged with reason, moderator, and timestamp, so your team has a consistent record and members can see (via the mod-log channel or their own infractions) that consequences are being applied evenly. Phantom's AutoMod handles the obvious stuff — repeat messages, mass-mentions, banned words, invite links — automatically, so your humans only see the cases that need judgement.

/pmod warn user:@member reason:Rule 3 — repeat messages in #general
/pmod timeout user:@member duration:1h reason:Rule 1 — personal attack

When a member gets warned, they should see which rule they broke. "Rule 3" is enforceable. "Being annoying" is not.

Updating rules without starting drama

Rules aren't static. As your server grows, new edge cases appear and old rules need sharpening. The trick is changing them without making it feel like a coup.

Do:

• Announce changes in an announcements channel before they take effect, with a one-line explanation of why.
• Give a grace period (24-72 hours) before enforcement starts.
• Keep a short changelog at the bottom of the rules channel: "Updated Oct 2024: added rule about AI-generated art."
• For big changes, run a quick poll. Phantom's polls make this trivial and members feel heard even when the outcome doesn't change.

Don't:

• Silently edit rules and then enforce them retroactively. This is the fastest way to lose trust.
• Add a new rule every time one person annoys you. If a behaviour has happened once, talk to the person. If it's happened five times, write a rule.
• Write rules in response to a single dramatic incident. You'll over-correct.

A copy-paste rules template

Here's a full template you can drop into a #rules channel and customise. It hits everything above in under 200 words.

# Server Rules
Welcome! This is a community for [what your server is about].
Keep it friendly and read the rules below before chatting.

1. No personal attacks, slurs, or harassment. Disagree with ideas, not people.
2. No NSFW content anywhere — including pfps, usernames, and DMs to members from this server.
3. No spam: no repeat messages, walls of emoji, or mass-pings.
4. No advertising or DM solicitation. Self-promo goes in #self-promo, one post per week.
5. English only in public channels so mods can moderate.
6. Use channels for their purpose. Check the channel topic if unsure.
7. No doxxing, leaking private messages, or sharing others' personal info.
8. No cheating, exploit-sharing, or piracy talk.
9. Listen to moderators. If you disagree with a mod action, DM a mod — don't argue in public.
10. Follow Discord's Terms of Service. You must be 13+ to be here.

## What happens if you break a rule
- 1st time: warning
- 2nd time: timeout
- 3rd time: longer timeout or kick
- Repeat or severe (slurs, NSFW, raiding, doxxing): immediate ban

Report problems with /report or DM a @Moderator.
Appeal a ban here: [link]

Last updated: [date]

Swap rules 6-8 for the ones that fit your community. Cut any rule you can't remember enforcing in the last three months — it's dead weight.

The takeaway

Good rules aren't about covering every possible scenario. They're about giving your members a clear signal of what this place is, and giving your mods a tool they can actually use. Short, specific, visible, with consequences that escalate predictably and a way to appeal.

Rewrite your rules this week. Cut them in half. Then cut them in half again. Wire the obvious enforcement to Phantom's AutoMod so your team only handles the judgement calls. You'll have fewer arguments, better consistency, and — for the first time — a #rules channel people actually read.