01
Step one: define the realm and its scope
Begin by stating what the server is and who it is for, in two or three sentences. Name the game or mode, the tone, such as relaxed roleplay or competitive survival, and the age or experience expectations. Then list where the rules apply: in-game chat, voice channels, forums and linked social spaces. Worked example: a roleplay server might open with 'This realm is a story-first world for adult players; these rules cover the game, voice and forum.' Scope first prevents later arguments about whether a behavior counted as inside or outside the community.
02
Step two: group rules by behavior, not by number
Cluster the rules under a few headings such as respect for people, fair play, roleplay standards and shared resources. Under each, write short, positive-first lines and attach one concrete example. For the same server, fair play might say 'No exploiting glitches; report them to staff instead,' followed by a sample of what counts as an exploit. Grouped rules are easier to scan on a phone and easier to update. Avoid long legal phrasing, since members will skim, and unclear wording is the main reason moderators end up making judgment calls under pressure.
03
Step three: add consequences, appeals and review
Finish with a plain ladder of responses: reminder, temporary mute, temporary removal, then permanent removal for serious cases, noting which actions skip steps. Explain how a member can appeal, who reads the appeal and how long it takes. In the example, appeals might go to a staff form with a response window the team can realistically meet. Add a review note stating when the rules are revisited with member feedback. A visible process makes enforcement feel fair, and a dated page tells players the community pays attention to how the world is run.
