A game server is a place people log into. A community is the reason they still have an account on the forum the week the server is empty. Those are different products. Most “dead RP boards” still have a Discord that pings, a whitelist that works, and a node tree that looks like a wiki. What they do not have is a culture that survives a patch, a wipe, or a Tuesday when nobody is online.
This is the culture article. It is not the XenForo RP/gaming architecture piece, not the whitelist, and not the server listing. Those own rooms, gates, and directories. This one owns the calendar around the server: what the forum is for when Discord is faster, what you do on patch week, where lore lives versus looking-for-group, and how you keep regulars when the hype screen goes dark.
The Discourse notebook we queried has no gaming case studies. It mentions RpNation as a long-running roleplay community that moved to Discourse and brought its old guidelines with it — existence proof that RP can live on that stack, not a playbook. XenForo community practice does speak to gaming hubs: they naturally want a section per world or faction, and a deep tree still ruins engagement. Broad rooms plus prefixes keep conversations in one place and avoid the groups × nodes rebuild tax. That is the only software sentence this article needs. The rest is people.
Many game boards stay on XenForo. That is honest. The add-on culture (listings, whitelists, character sheets, Discord bridges) grew up there. Discourse can host a literate RP forum; it will not give you the FiveM directory ecosystem. Pick the stack for the culture you can staff, not for the trailer.
Four jobs the server cannot do alone
A server answers “can I play right now.” It is terrible at memory, argument, and waiting. The community around it has to own those.
| Job | Happens when | Wrong home | Right home |
|---|---|---|---|
| Play | Tonight, voice, in-character, in-raid | A 40-reply lore argument | The server, plus a thin LFG surface |
| Find people | Before tonight | A Discord message that vanishes | LFG that is still readable tomorrow |
| Remember | After the session, after the wipe | A voice rant | After-action, patch notes, decided lore |
| Argue the rules | When someone is angry | In-character chat | OOC, staff-signed, one thread |
If one channel claims all four jobs, it will be unreadable. If four channels claim the same job, each will look empty — and empty rooms kill return visits. The culture work is assignment, not more containers.
Write the assignment on a single public page. “Discord is for tonight. The forum is for anything we still need on Thursday.” If you cannot say that sentence, you do not have a split. You have two stages competing for the same joke.
Discord is the night. The forum is the week.
This is not a webhook tutorial. Integration can wait. The culture decision cannot.
Discord wins at: voice, LFG in the next twenty minutes, patch-night panic, “who is on,” social presence, the joke that does not need to be indexed.
The forum wins at: the application that should still make sense in a month, the lore that is canon, the patch-note archive, the rule that staff will quote, the after-action people will link, the argument you do not want to moderate in real time, search.
A hybrid that works looks like this:
- Discord has a small number of live channels: voice, tonight-LFG, patch-panic, off-topic.
- Discord does not get a mirror of every forum thread. Mirrors split replies and make both sides look half-dead.
- The forum has a small number of live rooms: announcements / patch, play or IC, OOC, LFG-that-lasts, lore-that-is-decided.
- Staff post the decision once, on the forum, and link it from Discord. They do not “also explain it” in three Discord channels with three wordings.
A hybrid that fails:
- Every forum post pings Discord, so regulars never open the forum.
- Every Discord pin is “the real rule,” so the forum rules page is fiction.
- Lore is a 200-message Discord thread with no summary.
- Applications live in a Google form, a Discord ticket, and a whitelist node.
Pick one canonical object per job. The other medium gets a link and a one-line pointer.
If you run voice-heavy RP, admit it: most of the play will never be a post. The forum then has to be excellent at before and after, or it is a ghost town with a pretty theme. That is allowed if you said so. It is a surprise if you sold “a writing community” and delivered a TeamSpeak with a registration form.
Patch week is a calendar, not a mood
Games have seasons. RP servers have wipes, map changes, ruleset rewrites, and “we’re switching frameworks.” Culture is what you do on purpose in the seven days around that event.
T-minus 7 — name the event. One announcement. What changes, what does not, whether characters survive, whether applications freeze. If you do not know yet, say that. Silence is how rumours become canon in Discord.
T-minus 3 — freeze the wrong work. Stop accepting applications you will not honour. Stop merging lore that will be illegal on Friday. Stop letting LFG for the old ruleset pile up without a prefix or a tag that says “pre-patch.”
T-minus 1 — staff roster. Patch night is a moderation shift, not “everyone panic-moderates in Discord.” One person owns the announcement thread. One person owns in-game / in-voice heat. They are allowed to be the same person only if the community is tiny.
Day 0 — one live thread. Patch notes or “what just broke.” Staff update that thread. They do not start a second thread every hour. Discord points at it. The active-users first-screen rule applies: this is “what moved.”
Day +1 to +3 — after-action, not vibes. A thread that asks for what happened (bugs, a scene worth writing down, a rules hole) will still be useful in a month. A thread that asks “how do we feel” will be a pile-on. Use the first.
Day +7 — close the loop. What you will change. What you will not. An unanswered official patch thread trains people to ignore staff. The XenForo engagement article said that about polls and suggestions. It is louder here because the server already changed.
Between official patches, invent nothing that looks like a patch. Fake seasons to “drive engagement” teach regulars that your calendar is marketing. A monthly scene night, a recruitment week, a lore council — those are rituals. They are allowed. They should not wear a version number.
If your game’s vendor already owns the patch clock (WoW season, FiveM artifact, a Steam update), attach to it. Do not run a competing clock. Players have a finite number of “this week matters” tokens.
Lore versus LFG versus OOC
Say “RP community” and three conversations sit down in the same chair.
Lore is decided fiction. Who rules the city, what the last war did, which names are canon. It should be boring to navigate and easy to cite. A short pinned index plus a handful of locked reference posts beats a 400-page “lore forum” nobody can search. If staff own canon, lock the canon. Argument about canon happens in OOC, not by editing the reference.
LFG is logistics. When, which voice, which character, what power level, whether newcomers are welcome. It goes stale in hours. Culture rule: stale LFG is deleted or marked, not left as a graveyard that makes the room look busy. A weekly “who is playing this weekend” thread is one object. Forty abandoned “tank LF raid” threads are a museum.
OOC is humans talking as humans: rules, meta, “I will be away,” the argument about the ruleset. OOC is where toxicity actually lives. In-character cruelty can be play. Out-of-character cruelty is the ladder. Write that distinction where a new person will see it before they post their first scene.
A fourth conversation tries to sneak in: recruitment / whitelist / “why was I denied.” That is staff process. It does not belong in lore and it does not belong in LFG. One OOC place, one policy, no public trial of the applicant.
Broad-room practice (XenForo community, applicable to any stack): do not create lore-north, lore-south, lore-history, lore-religion, lore-timeline on day one because the setting has those drawers. One lore room, prefixes or tags for the drawers. Split when staff can no longer moderate one room — the same rule the architecture article used for play-eu / play-na. Here it is a culture rule: empty lore drawers teach newcomers that the world is abandoned.
IC and OOC in the same thread is how you get a scene interrupted by a rules argument. If your medium is the forum, require a cut (“//” or a spoiler or a second post) and enforce it kindly for a week, then firmly. If your medium is voice, the forum should not try to be the session. It should be the minutes.
Staff are dungeon masters or they are cops. Pick.
Game communities destroy staff who try to be both in the same sentence.
Dungeon master energy: they run scenes, they say yes to a plot, they are in-character sometimes, they have favourites because plots have protagonists.
Cop energy: they apply the same ladder to the founder’s friend, they do not win arguments with the badge, they recuse when their faction is in the ticket.
You need both functions. You do not need both functions in one exhausted person at 01:00.
Write two hats:
- Story staff may say yes to fiction. They may not close a conduct ticket about their own scene.
- Conduct staff own the playbook. They may not rewrite canon to punish a character.
If you only have three people, rotate the hat by incident, not by mood. Recusal is not optional when the report is “your RP partner was cruel OOC.” The team article already required recusal for friends and guilds. On an RP server, the guild is the friend group. Say it.
The Admin-account rule still applies and is louder here: the root Admin must not be a character in the city. Official announcements and structured warnings come from the system actor. The founder’s rogue is a personal profile. If the nuclear badge is also the crime boss, nobody will report the crime boss.
Rewards follow the same split. A character title is fiction. A user banner that says Veteran is status. Do not hang conduct on a character rank, and do not hang canon on a post-count ladder. Global “Archmage” next to a billing dispute is how staff lose arguments — the ranks article already used that sentence. It was written for this room.
The off-season is the real product
Hype is cheap. The week after a wipe, after a failed launch, after the streamer left, after exams — that week decides whether you have regulars or a mailing list.
Culture that survives the quiet:
- A smaller live surface. Archive or lock the rooms that only existed for the event. Do not add empty nodes to look ambitious. Broad rooms, still.
- A ritual that does not need a full server. Tabletop one-shot on the forum, a writing prompt, a recap night, a “what are you playing instead” thread. One object, staffed.
- A honest census. How many people actually logged into the server last week? How many opened the forum? If the server is dead and the forum is talking, you are a fandom. That can be a good product. Rename it in your own head so you stop measuring yourself as a pop count.
- No loyalty tests. “If you were a real regular you would be here on a dead Tuesday” is how you lose the people who would have come back on patch day.
- Keep the memory. After-actions and decided lore stay. Delete the LFG graveyard. A board that looks like 2019’s last argument is not nostalgia. It is a warning label.
If you plan a reboot, treat it as a patch week with a harder T-minus-7 sentence: what carries, what does not, whether old applications mean anything. Reboots that “reset drama” without resetting the staff exemptions reset nothing.
New players are a different culture problem
Game regulars talk in patch numbers and character names. New people hear a locked door.
The lurker door from the active-users article has a server-shaped version:
- They need one sentence for how to get in (apply, buy, just connect) and one place to stand while they wait.
- They need a first post that is not “read 80 pages of lore, then write a novel.” A short intro, a first scene prompt, a “what time zone are you” in LFG — pick one.
- They need a first session that is allowed to be small. A 12-person scene that assumes three years of canon is a loyalty test.
- They need OOC answers from a human, not only from a bot that says “ticket opened.”
Whitelist and character sheets are process. Culture is whether the first denial comes with a path (“rewrite these two paragraphs”) or with silence. Silence is how Discord rumours become “the staff have a clique.” Sometimes you do have a clique. Stop recruiting if you only want your friends. That is a server, not a community. It can be an honest server.
Do not make the first post a permission puzzle. If they cannot post in the obvious OOC room until they are whitelisted, you have hidden the only conversation that would have taught them how to apply. Test this with a fresh account every time you change groups.
Platform fit, said as culture
Stay on XenForo if your culture needs a directory of other servers, a whitelist people understand as a forum application, character fields, a last-post column your veterans will riot without, and the add-on gravity that already exists. The architecture article is the cupboard. This article is the calendar you hang on it.
Consider Discourse if your culture is literate RP or a game’s discussion layer: few categories, tags instead of 80 nodes, trust levels as a sandbox, a review queue, search that people will actually use. RpNation’s move is a data point that RP can live there. It is not a promise that your FiveM listing culture will. The pros and cons close still holds: veterans who think in post-count ranks and last-post columns will ask where the furniture went. If that conversation is a civil war, do not migrate for the theme.
Do not split the culture across two forums because a faction wanted their own board. Two memories is how canon dies.
Whatever you run, the first screen on a Tuesday must show movement that is not staff talking to staff. If the server is the only movement, say so on that screen: “Play is tonight in X. Here is last week’s recap. Here is the next LFG.” A directory of empty rooms is a lie.
A weekly operator loop for a live server
Every play night (10 minutes before, 10 after).
- LFG object is current. Stale entries marked.
- After the session: one recap sentence in the after-action home, even if the play was voice. Tomorrow’s lurker needs it.
Every weekday.
- First posts from unwhitelisted / TL0 / new accounts get a human sentence.
- Discord rumours that contradict the last staff post get a link, not a second speech.
Every patch week. Run the calendar above. Do not also launch a contest.
Every month.
- Count play-night attendance and forum second-sessions separately. They are allowed to diverge. They are not allowed to be confused.
- Kill one empty container. Prefixes stay. Empty rooms do not.
- Ask one regular, in private: “What is the forum for this month?” If they say “nothing, we Discord,” either accept the fandom product or change the assignment. Do not add a node.
Worked example — a wipe you do not deserve to survive
You announce a wipe in Discord voice on Sunday. Forum rules still describe the old map. Applications stay open. Lore threads stay unlocked. Tuesday, three new people post characters for a city that will not exist. Friday, you wipe. Saturday, they charge back or they rage in OOC. You ban the loudest one and call it toxicity.
What actually broke was the calendar:
- T-minus-7 was a voice rumour, not an announcement object.
- Applications were not frozen.
- Lore was not marked pre-wipe.
- After-action was a pile-on because staff never closed the loop.
The toxic-user ladder will not fix a culture that lies about the world for six days. Write the announcement. Freeze the wrong work. Recap. Then moderate the people who are still cruel.
Checklist
- One public sentence: Discord is for tonight; the forum is for Thursday
- Each job (play, find, remember, argue) has one canonical object
- No full-thread mirrors both ways
- Patch / wipe calendar exists; applications and lore freezes are on it
- Patch night is a rostered shift, not a mob
- Lore is citable; LFG goes stale on purpose; OOC holds the fights
- Broad rooms; no empty lore drawers “for later”
- Story hat and conduct hat are different in writing
- Root Admin is not a character
- Character titles ≠ conduct ranks
- Off-season plan is a smaller surface, not a loyalty test
- New-player first post is possible before the novel
- Fresh account test after every gate change
- Monthly: kill one empty container; ask what the forum is for
A server is a night. A community is the week around that night — the sentence you can still find, the LFG that did not rot into a lie, the patch you announced like an adult, and the staff hat that did not play the crime boss with the nuclear badge. Build that week. The nodes you already have are enough.