Why most rule lists fail

The usual list is thirty lines of overlapping intentions: “be respectful”, “no drama”, “no inappropriate content”, “follow Discord ToS”. None of it tells a moderator what to do when someone posts a borderline meme at 2am.

A rule works when it names the behaviour, not the feeling. “No harassment” is a feeling until you say what harassment looks like in your server: slurs, following someone between channels, repeatedly messaging after being asked to stop.

The template

Copy this, change the examples to fit your community, and delete anything you would not enforce.

Make each rule enforceable

Compare “be nice” with “no slurs or threats, and stop when someone asks you to”. The second one gives a moderator three concrete things to check: was there a slur, was there a threat, was there a request to stop that was ignored.

If a rule cannot be checked against a message, it is not a rule — it is a hope. Move the vague parts into a short “how we treat each other” paragraph at the top and keep the numbered list for things that can be enforced.

Match consequences to rules

Write the ladder down where staff can see it, so a first-time mistake and a deliberate attack do not get the same response.

Publish them where people see them

A rules channel nobody opens is decoration. Put the short list in the channel new members land in, link it in your welcome message, and pin it in #general. If you use verification, put the list on the verify screen so agreeing to the rules is part of joining.

Lyx can post and keep that message for you: set the welcome channel with /welcome channel, and the rules stay one click away in the verify panel.

Keep them current

Rules drift because servers change: a channel is added, a meme format becomes a problem, a new game brings a new kind of spam. Review the list every few months and after every incident that made a moderator improvise.

When you change a rule, say so in your announcement channel and give people a date it starts. A rule that appears overnight and is enforced immediately feels arbitrary, even when it is sensible.

Handling edge cases

Context beats keywords. A racial slur quoted to report it is not the same as a slur aimed at a member; a joke between friends is not the same as harassment. Train moderators to read the surrounding ten messages before acting.

Give people a way to appeal. Lyx can take appeals through a form or a ticket so a disagreement does not turn into a public argument, and so the decision is written down instead of remembered.

Common questions

How many rules should a server have?

Between eight and twelve. Beyond that people stop reading, and moderators stop remembering which rule covers what.

Should rules be in a Google Doc or a Discord channel?

A Discord channel, pinned and linked from the welcome message. A document nobody opens is not a rule set. Keep a staff copy with the enforcement ladder separately.

What if a member breaks a rule that is not written down?

Act on the closest written rule, then write the missing one afterwards and tell the community. Punishing someone for an unwritten rule is how servers get a reputation.