D&D Discord Server Setup: The Channel Template That Survives Past Session 4

Search for a D&D Discord server template and you will find the same thing over and over: a one click clone with thirty channels, forty roles, colour coded categories, a rules channel, an introductions channel, and a bot commands channel nobody touches. These are built for public communities with three hundred members.

Your campaign has five people in it.

I have set up a lot of these servers, and the pattern is always the same. Week one everyone is excited and every channel gets used. By session four, three quarters of them are dead, the recap channel has one post in it from the DM, and the party is asking "wait, who was the guy with the ledger?" in general chat because that is the only place anyone still reads.

So here is the smaller structure I keep coming back to, the channels that reliably die, and the one habit that decides whether your server ends up holding your campaign or just your scheduling arguments.

Should you use a prebuilt template at all?

Honest answer: probably not, and this is coming from someone writing a guide about templates.

Discord has a built in server template feature that lets you clone an entire server structure from a link. It works well. The problem is what you are cloning. The popular public D&D templates are designed for open drop in communities, so they come loaded with moderation channels, verification systems, and role hierarchies that make no sense for a private game with your friends.

You will spend longer deleting channels than you would have spent making seven from scratch. And every channel you leave in "just in case" is a channel that sits there empty, quietly training your players to ignore the sidebar. Even the well made community templates that DMs share on r/DnDBehindTheScreen assume a bigger group than most home games have.

Build it yourself. It takes about ten minutes.

The seven channel structure

Create your server from the plus button in the sidebar, choose "Create My Own," and then set up three categories. Under each, only these channels:

The Table

• #general for everything that does not have a home. This will be your busiest channel and that is fine.
• #scheduling for "can everyone do Thursday." Keep it separate from general or it will drown out actual conversation. If your group struggles here, our guide on what to do when a player misses a session covers the alternatives to cancelling.
• Game Night (voice) for actually playing.

The World

• #maps-and-handouts for images you drop during play. Lock write permissions to the DM so it stays a clean reference instead of a meme graveyard.
• #session-recaps for what happened last game. More on this below, because it is the channel that matters most and dies fastest.
• #campaign-reference for the NPCs, locations, factions, and open quests your players keep forgetting. Also DM write only.

Out of Character

• #dice for bot rolls, so the combat channel does not fill with command spam.

That is it. Seven channels. Notice what is missing: no rules channel, no introductions, no bot commands, no memes channel. Your friends do not need to introduce themselves to each other, and the memes will go in general no matter what you do.

If your table genuinely roleplays between sessions, add an #in-character channel. Only add it if someone asks. A channel created in hope is a channel that sits empty and makes the server feel abandoned.

Roles and permissions: two is enough

Public server guides will walk you through a role hierarchy with moderators, trusted members, and half a dozen cosmetic colour roles. Skip all of it.

You need two roles:

• Dungeon Master, with permission to manage messages, manage channels, and pin. This lets you curate the reference channels and pin the current recap.
• Player, which is really just your default role with normal read and write access.

The only permission work worth doing is locking write access on #maps-and-handouts, #session-recaps, and #campaign-reference to the DM. Those three are meant to be read, not chatted in. If players can post freely in them, a reference channel becomes a conversation, and a conversation is not something you can scan quickly before a game.

Do reaction roles, colour roles, and verification gates if you are running a public community. For a home campaign they are cosplay.

The exception is an open table. If you are running a West Marches campaign with a pool of a dozen players scheduling their own expeditions, the server stops being a convenience and becomes the scheduling system, so it earns a little more structure.

Which bots are actually worth it?

One. Start with one.

Avrae is the standard choice because it connects directly to D&D Beyond character sheets, so players roll actual attacks and spells rather than typing raw dice math. If you want something lighter, any basic d20 roller will do the job.

The temptation is to load up on music bots, initiative trackers, soundboards, and encounter generators before session one. Resist it. Every bot is a set of commands your players have to learn, and the ones nobody learns just make the server feel more complicated than it is. Mike Shea's notes on playing D&D over Discord make the same point from years of running remote games: the setup should get out of the way of the game.

Add the second bot when a player asks for it. That request is the only real evidence you will get that a bot is needed.

This walkthrough covers the mechanics of building the server out if you want to see the clicks in motion:

The channels that always die, and why

Here is the part most setup guides leave out.

Look at which channels survive past the first month. #general thrives. #scheduling thrives. #dice thrives. All three have something in common: using them costs nothing. You are already typing, so you type there.

Now look at what dies. #session-recaps and #campaign-reference are almost always the first to go quiet, and it is not because your group is lazy. It is because those two channels are the only ones that require somebody to do work after the session, once the game has ended, everyone has said goodnight, and the person who would write it is tired and wants to go to bed.

That is a structural problem, not a discipline problem. You built a channel whose upkeep depends on unpaid homework, and homework loses to sleep every time.

In practice it goes one of three ways. Sometimes a player genuinely likes writing them, in which case thank that person loudly and often, because natural scribes are rarer than a good rolled stat line. Sometimes the DM takes it on, which holds for about six weeks before it turns into the thing you quietly dread on a Sunday afternoon. And sometimes the recap just appears without anyone having volunteered, because the writing came out of the session itself rather than out of somebody's evening.

What to pin, and why it matters more than you think

Whatever else you do, pin the most recent recap to the top of #session-recaps, and pin your active quest list to #campaign-reference.

Discord pins are underrated for this. Your players will not scroll. They will genuinely not scroll. If the answer to "what were we doing?" is four hundred messages up, it does not exist. If it is one click on the pin icon, half your table will read it in the car before the game.

This is the actual job the server is doing between sessions. Everything else is convenience. The reason a campaign feels sharp in month eight is that the group shares a memory of what happened, and the reason a campaign feels foggy is that they do not. We wrote about the wider habit in our guide to keeping track of a D&D campaign, and about the structure of the thing you are building in what a campaign wiki is.

The honest limit of a Discord server

Discord is a brilliant place to play and a mediocre place to remember.

It is a chat app, so it is built around the newest message. Everything is chronological, nothing is connected, and searching for a name you half remember from four months ago gives you eleven results across five channels with no way to tell which is current. Your #campaign-reference channel is a wall of posts, not a reference. The moment an NPC changes allegiance, the old post is still sitting there being wrong.

That is fine for a short campaign. Over a long one, the gap shows.

This is the gap Saga20 fills, and it is worth being specific rather than vague about it. It records the session, writes the recap, and turns what happened into a linked campaign wiki where each NPC, location, and quest has its own page that stays current. Then it posts the recap straight into your Discord channel when the game ends, so the channel that normally dies stays alive without anyone volunteering for homework. Your players get the pinned summary they will actually read, and you get your Sunday back.

If you would rather keep doing it by hand, that is a perfectly good choice. Our comparison of D&D note taking apps covers the manual options honestly, and the session recap generator is free if you just want a shareable card to drop in the channel each week.

Your ten minute setup checklist

1. Create the server, choose "Create My Own," skip the prebuilt templates
2. Build three categories: The Table, The World, Out of Character
3. Add seven channels, no more
4. Create a Dungeon Master role and a Player role
5. Lock write access on the two reference channels and the handouts channel
6. Invite one dice bot
7. Decide out loud, before session one, who posts the recap and pin it every week

The seventh step is the one that decides whether the server is still useful in six months. Everything above it takes ten minutes. That one takes a conversation, and it is worth having before the first die hits the table.