Set up your Discord server
Add the Wyrdli bot to a Discord server, pick the channels you'll use for play and voice, give the bot the permissions it needs, and confirm you're the GM.
Add the Wyrdli bot to a Discord server, pick the channels you'll use for play and voice, give the bot the permissions it needs, and confirm you're the GM.
Wyrdli lives in the web app, but the table sits in Discord: rolls, character commands, session start and end, voice recording, all of it runs through the bot. This article walks through the Discord side from scratch, so a fresh server is ready to host a Campaign by the time you're done. Keep it open in one tab and the Wyrdli web app in another; you'll bounce between them.
A Discord server you administer (or admin permission on someone else's). One server hosts one campaign at a time; if you're running two campaigns, use two servers.
A Wyrdli web account, signed in.
Five minutes, plus a moment to decide which channels the campaign will use.
In the Wyrdli web app, open the bot invite link from the Discord-integration panel. The link opens Discord's authorisation flow in a new tab.
Pick the server you want from the dropdown and review the permissions Discord lists. The bot needs to read messages, send messages, embed links, use slash commands, and connect to voice channels. Approve all of them; the bot won't work right with anything trimmed.
Confirm the install. Discord drops you back on the server with the bot added to the member list.
If the invite link doesn't open, you're probably not signed in to Discord in the browser you clicked from. Sign in there first, then try the link again.
The bot can post in any text channel, but the table feels less chaotic if there's one channel for play and the players know which one it is.
Choose (or create) a text channel for play: #table, #cannery-1986, whatever fits. This is where slash commands go.
Pin a short message in that channel so anyone joining knows where to type. "This is the play channel for The Cannery. Slash commands here." Two lines is plenty.
Choose the voice channel the table will sit in during sessions. The bot joins this channel when you start a Recording; make sure everyone playing has permission to be there.
The Campaign on Discord is what ties the bot to the right Wyrdli record. You only do this once per server.
In your play text channel, run /campaign create followed by the campaign's name (/campaign create The Cannery, for instance). The bot creates the Campaign in Wyrdli and registers this server as its home.
The user who runs the command becomes the GM automatically. The bot confirms in the channel; the same Campaign now appears in your campaigns list on the web app.
By default, every bot reply lands in the channel the command came from. If you want roll results, strike notices, and session-end summaries to sit somewhere else (a dedicated #play-log, say), run /gm session set-channel in the channel you want to use. The play channel stays for slash commands; the log channel collects the receipts.
One Discord server hosts one Campaign at a time. To run a second Campaign, add the bot to a second server and run /campaign create there. Don't try to share one server between two Campaigns; the bot will route everything to whichever Campaign was created last.
Set up your first campaign walks you through laying the first arc into Wyrdli once the server is ready.
Add players to your campaign covers invites and Character creation from the player side.
Discord commands is the full reference for every slash command the bot answers to.