Wyrdli and Discord together
Discord covers the in-Session moments: rolls, strikes, advancement, recording. The web covers everything else. Here's where each one fits.
Ultimo aggiornamento 19/08/26
Wyrdli · Aiuto e documentazioneDiscord covers the in-Session moments: rolls, strikes, advancement, recording. The web covers everything else. Here's where each one fits.
The real work of running a Wyrdli Campaign happens on the web. Building the world, designing the arcs, auditing the Canvas, reviewing what happened last week, prepping the next Session: all of that needs space, a real keyboard, and time to think. Discord covers a small but useful slice on top of that: the moments that need to resolve in seconds while everyone is listening.
Almost every part of Wyrdli lives on the web. The Campaign sidebar, the entity lists, the Canvas, the Play view, the recaps, the Recordings, the Templates: all of it is on the web because all of it benefits from room and a pointer.
On the web you build the Campaign: Characters, Locations, Factions, Items. You design the discovery graph: Secrets, Clues, Scenes. You audit it with the Canvas. You read the Recordings and recaps after the Session. You search for something you wrote three months ago. You write Templates so the AI generates entities in the Campaign's voice.
When you sit down to prep on a Sunday afternoon, you open the web. Discord doesn't enter into it.
Discord is where the game is being played, and the actions you take there are the ones that need to happen now, mid-sentence, without breaking the rhythm of the table. The Discord side of Wyrdli is intentionally small: a handful of slash commands you can fire while the players are listening.
Rolls. /roll for a player, /gm roll for a GM check.
Strikes and heals. /gm strike to wound a Character, /gm heal to remove strikes.
Advancement. /character advancement for a player to spend a point and raise an attribute.
Recording. /recording start and /recording stop to capture the Session's audio.
Ending a Session. /gm session end to close the night and pay out advancement.
The GM has every player command plus the GM-only ones; players have only the player commands.
The two surfaces keep the same Campaign in sync. The split is functional, not architectural.
A Character's name, avatar, and attributes can be edited on either side. Use /character … in Discord, or open the Character on the web; both land in the same place. A roll resolved in Discord posts back as a Discord embed and isn't kept; rolls are stateless. The strike or heal that follows it, on the other hand, is stored against the Character. The Session that /gm session end closes is the same Session you see on the Session list on the web, and the advancement payout from that command shows up in each Character's events log. The Recording that /recording start begins lands on the matching Session's page on the web, where you generate the Transcript and the recap.
The simple rule: if it persists, both sides see it. If it's just a moment (a roll), Discord shows the moment and nothing is kept.
Both the GM and the players have a Discord surface. The split is intentional. Players run the player commands: /character … (view and edit their own Character), /roll, and the player half of advancement. The GM has all of the player commands plus the GM-only ones: /gm roll, /gm strike, /gm heal, /gm session end, and /recording start / /recording stop.
On the web, the same separation holds: a player can edit their own Character; the GM can edit the whole Campaign.
If you're a GM new to Wyrdli, treat the web as home. Build the Campaign there, prep there, review there. Discord is the thing you open when the players are about to arrive in voice, and the slash commands are the thing you reach for during play.