(Session zero) What are your lines and veils?
- Content a player never wants in the game (lines)→ Noted privately in #player-notes
- Content that should happen off-screen (veils)→ Noted privately in #player-notes
A server for a tabletop RPG group: campaign info, session scheduling, character sheets, lore, spoiler-safe recaps, voice play and GM-only prep.
Keep a tabletop campaign organised between sessions. Players find the setting, house rules and their characters in one place; scheduling happens in polls; recaps keep absent players up to date; and the game master's secrets stay in a space players can't see.
Create each category with its permissions first, then add channels inside it and keep them synced to the category. Channel types used: Text, Voice.
Reference the GM maintains. Players read; the GM posts.
Setting summary, system and edition, house rules, session length, and the table's agreed lines and veils.
One message per topic — places, factions, gods, history — with a thread for player questions. Only include what the characters would know.
Maps, letters and images the party has found.
A short recap after each session, posted by the GM or a rotating player, so anyone who missed it can catch up.
Permissions: Allow Send Messages for the recap author that week.
Out-of-character conversation between sessions.
Out-of-character chat, memes and theories.
The GM posts a Discord poll with candidate dates; the session becomes a Scheduled Event once confirmed.
Rules lookups and clarifications, so they don't interrupt play.
Rolls from a dice bot during online sessions, kept in one place.
One place for every player character.
One message per character with a sheet link and portrait. Level-ups and backstory notes go in that message's thread.
Between-session activities, shopping and short in-character scenes, one thread per character or activity.
Where the game is played.
Session voice. The GM shares a screen for maps or a virtual tabletop.
Permissions: Allow Video so the GM can share a screen; give Game Master Priority Speaker here.
For split parties or a quick private word with the GM.
Secrets and prep. Players never see this category.
Session plans, encounters and loot.
Plot twists, NPC motives and hidden information.
Character arcs and anything a player shared privately about their goals or limits.
Create roles in this order, from the top of the role list down. A role can only manage roles below it, and bot roles must sit above any role they assign.
Different staff setup or bots? Adapt this hierarchy in the roles generator.
Runs the campaign. Usually also the server owner.
Helps run sessions or runs a second table.
Members of the party.
Spectators or players trying a one-shot.
Notified when a session is scheduled or moved.
No Community features required. The table is invite-only: the Game Master assigns Player when someone joins the campaign, and holds a session zero before the first game.
Try Discord's built-in features first. Bot names are examples to evaluate, not endorsements; CordNexa has no affiliation with any bot. Review the permissions a bot requests before adding it.
Shared, visible rolls for online sessions.
Native first: Discord has no built-in dice roller. Players can roll physically or in a virtual tabletop instead; add a dice bot only if the table wants rolls in Discord, and confine it to #dice.
Finding a date that works for everyone.
Native first: Discord polls and Scheduled Events cover most tables.
Examples: Sesh (recurring events and calendar sync are Sesh Premium)
These steps are specific to this kit. For the reasoning behind each stage — permissions, onboarding, testing and launch — see how to make a Discord server.
Create a server for the campaign (or one server with a category per campaign). Community features aren't needed.
Game Master → Co-GM → Player → Guest → Session Ping.
Make THE CAMPAIGN read-only for everyone except the Game Master, and GM ONLY hidden from everyone except Game Master and Co-GM. Keep channels synced to their categories.
Include the system, the tone, house rules, session length and how scheduling works.
Agree expectations, lines and veils, and character concepts. Record anything private in #player-notes.
Post a poll in #scheduling, then create a Scheduled Event for the chosen date.
Use View Server As Role → Player to confirm GM ONLY is hidden and THE CAMPAIGN is read-only.
Create a role per campaign (for example Table: Curse of the Moon) and a category per campaign visible only to that role. Share TABLE TALK across tables if players overlap.
Give each player a private channel visible only to them and the GM, or use private threads if your server has Boost Level 2, which Discord requires for private threads.
Add an IN CHARACTER category with a channel per scene and a rule about posting order and turn deadlines.
Keep the server for scheduling, recaps and character sheets, and drop the voice category.
Need stricter or more relaxed wording? Customise these rules in the rules generator.
Welcome to the table! Start with #campaign-info for the setting and house rules, then add your character to #character-sheets. Answer the poll in #scheduling so we can find a date, and join The Table in voice when the session starts. Questions? Ask the Game Master.
Want a shorter, professional or bot-ready version? Try the welcome message generator.
Create read-only channels for campaign info, lore and recaps, an out-of-character chat, a scheduling channel for polls, a character-sheet channel and a voice channel for play. Keep your prep in a GM-only category that players can't see.
Use a channel visible only to that player and the GM, or a private thread. Private threads are available on servers at Boost Level 2 and need the Create Private Threads permission.
Yes. Give each campaign its own role and category so players only see their table's lore, recaps and handouts.
Not necessarily. Polls and Scheduled Events handle scheduling. Dice can be rolled physically or in a virtual tabletop; add a dice bot only if your table wants rolls in Discord.
CordNexa is independent and not affiliated with or endorsed by Discord. Discord features change over time; this kit was last reviewed on 2026-09-28.