Writing Server Rules and Regulations

Server rules are not just a list of prohibitions — they define the culture and expectations of your community. This guide covers how to write rules that are clear, enforceable, and respected.

1. Start with Principles, Not Just Prohibitions

Before listing rules, state what your server stands for. A brief values statement at the top of your rules document establishes the standard members are expected to meet:

Professionalism in all in-game and out-of-game communications.
Respect for all community members regardless of rank or role.
Commitment to realistic, structured ERLC roleplay.

Rules written without a values context are harder to enforce consistently. When a situation is ambiguous, staff should be able to apply the values, not just check a list.

2. Write Rules That Can Be Enforced

Every rule must meet two criteria: it must be specific enough to apply, and it must be observable. Avoid rules that rely on staff to read intent:

Poor: "Be respectful at all times."
Better: "Do not use offensive language, personal insults, or targeted harassment toward any member."
Poor: "Do not ruin the roleplay experience."
Better: "Do not intentionally disrupt active scenes, ignore dispatcher instructions, or engage in unprompted aggressive behavior."

3. Organize Rules by Category

Group rules into logical sections so members can find relevant rules quickly:

General conduct: Behavior standards, communication, and respect requirements.
In-game rules: Roleplay standards, vehicle use, uniform compliance, radio conduct.
Discord conduct: Channel usage, posting standards, DM behavior.
Staff and rank rules: Expectations specific to members in official positions.
Disciplinary process: How violations are handled and escalated.

4. Define Your Disciplinary Process Explicitly

Members should not discover what happens when they break a rule only after they break it:

State your warning system in the rules document — what counts as a strike and what triggers each level of action.
List what each discipline level looks like: verbal warning, formal warning, temporary ban, permanent ban.
Specify whether certain violations (e.g., exploitation, doxxing) result in immediate permanent bans without warning.
Include how members can appeal a decision and the timeline for appeals.

5. Keep Rules Current

Rules that no longer apply to current server operations create confusion and enforcement inconsistencies:

Review the full rules document every 60 to 90 days.
When a rule is changed, announce the change to the community with a reason. Do not silently edit posted rules.
Remove rules that are no longer enforceable or relevant rather than leaving them in place.

6. Post Rules Where Members Will Read Them

Placement and format affect whether members read and retain your rules:

Use a dedicated #rules channel in Discord pinned at the top of the navigation sidebar.
Break rules into numbered sections — numbered references make enforcement conversations easier ("Rule 3.2 states...").
Require new members to react or acknowledge the rules before accessing the full server.
Keep the rules document readable in under five minutes. Overly long rules are ignored.

All Guides Resource Vault