This guide takes you from a Discord server to your first adventure on WestMarches.games. Do the steps in order. The first four connect the site to Discord. The rest set up your house rules, and you can come back to them whenever you like. Until the essential steps are done, admins also see a checklist of them on the community's home page.
You need a Discord server where you have the Manage Server permission, because Discord asks for it before it lets you add a bot.
The site reads each person's Discord roles to decide what they can do there, so the roles come first. In Discord, open Server Settings → Roles and create these:
| Role | What it unlocks on the site |
|---|---|
| GM | Posting adventures and handing out rewards after a session. |
| Player | Creating characters and signing up for adventures. |
| Admin (optional) | Changing community settings. You can always change the settings of a community you create, so you only need this role if someone helps you run it. To post adventures or make characters yourself, give yourself the GM and Player roles too. |
Everyone who plays needs the Player role. The site can't use @everyone for it, so a member without the role can read the community but can't make a character or join an adventure. Decide now how people get it: by hand once they have introduced themselves, or automatically through a question in Discord's onboarding (Server Settings → Onboarding, on Community servers).
If players should be pinged about new adventures, make roles for that too, such as "Adventure pings" or one role per level tier. Turn on "Allow anyone to @mention this role" for each one, because GMs can only ping roles that have it.
The site posts to Discord through its bot, and you choose which channel each kind of post goes to. Start with three channels:
| Channel | Type | What the site posts there |
|---|---|---|
| #adventures | Forum | A post for every new adventure, kept up to date when the GM edits it. Signup openings, reminders and recaps go into the adventure's own post, so each adventure gets its own discussion. |
| #characters | Forum | A post for every new character. GMs and the player can talk about approval underneath it. |
| #rewards | Text | Rewards handed out after a session, marketplace purchases, and currency transfers, so there is one place to check where a character's gold came from. |
If you would rather read every recap in one feed than in each adventure's post, add a #recaps text channel as well.
The three channels stay readable when the bot is the only one starting posts. In each channel's permissions, deny @everyone "Send Messages" (a forum calls it "Create Posts") and allow "Send Messages in Threads" ("Send Messages in Posts" in a forum). Members can still reply under every post.
A deny on @everyone applies to the bot as well. Add the bot's role to each of the three channels and allow it to send messages, and do the same for any private channel you want it to post in. Step 4 warns you if you missed one.
The rest of the server is up to you. A welcome channel with your rules and a voice channel to play in are a good start. For a fuller layout, Stephen Collins describes every channel on his group's server in part 2 of his toolkit series.
Sign in with Discord and open Create Community. The form has five steps:
A new community posts nothing to Discord until you choose the channels. Open Settings → Discord Notifications and set:
| Setting | Channel |
|---|---|
| Adventures | #adventures |
| Characters | #characters |
| Rewards Distribution, Marketplace Purchases, Currency Transfers | #rewards |
| Adventure Reminders, Adventure Recaps | Leave empty to post in each adventure's own thread |
When you pick a channel, the site checks that the bot can post there and shows a warning if it can't. Reminders and recaps stay greyed out until you switch them on in the next step.
These settings shape every character and adventure, so settle them before players arrive. All of them can change later.
Start the World Wiki with the pages players look for first: your house rules, and the home base where adventures begin and end. Other GMs can't open the Wiki Editor until the first page exists, so create one before you invite them.
Then write down how rewards work: how much XP and gold a session is worth, and what earns a bonus. Put it on a page only GMs can see. When several GMs hand out rewards, a shared rate keeps every table's characters levelling at the same pace.
Before anyone else joins, check that posts reach Discord. Create an adventure, publish it, and look for it in #adventures. Drafts are never posted, so make sure it is published.
If nothing shows up, open Discord Posts in the settings menu. It shows the error when a post failed, and you can create a fresh post from there once the cause is fixed. Delete the test adventure when you are done. Its Discord post stays behind marked as deleted, so remove that by hand.
Post your community's link in your Discord welcome channel, together with the player guide, which explains signing in, making a character and signing up for adventures. Give new players the Player role as they arrive. If someone can't find the Create Character button, check their roles first, because it only shows for people with the Player role.
When the session ends, the GM opens the adventure and uses Distribute Rewards to give XP and currency to everyone who played. Levels update from the experience ladder, and the rewards are posted in #rewards.
Everyone who played can then add notes on the adventure page. Public notes are the recap: they are posted in the adventure's thread and appear on the wiki's recaps page. Private notes are visible only to the person who wrote them.
Each adventure on the site is one session. When a story runs over several sessions, post each session as its own adventure. Copying the first one saves typing it out again. More on this in Adventures.
The channel layout and the advice on multi-session stories draw on Stephen Collins' Building an Online TTRPG Toolkit series, which follows a new group through setting up Discord and WestMarches.games. Part 4 is his review of the site.