Sessions and the play log
What a Session is, when it ends, and what hangs off it: notes, Recording, Transcript, recap, and advancement events.
Ultimo aggiornamento 04/06/26
Wyrdli · Aiuto e documentazioneWhat a Session is, when it ends, and what hangs off it: notes, Recording, Transcript, recap, and advancement events.
A month into the cannery investigation, a player asks: "wait, when did we actually meet the harbour master?" You scroll the Campaign's Session list, find the Thursday it was raining, open the Session, and there's the note, the Recording, the recap. The Session is the answer to "when did that happen?"
A Session is one play sitting. It has a date, the Campaign it belongs to, the people who showed up, and the notes you took while you played. Read the list of Sessions top to bottom and you get the play log: the story as it actually unfolded, not the story as you planned it.
A Session starts empty. You add notes as you play, or after, while the table is still in your head. If you also recorded the audio in Discord, the file lands on the Session's page once Discord finishes uploading it.
A Session with no notes still does its job by anchoring the play log: the date alone tells you "we played that Thursday", and the Recording (if you have one) is enough to reconstruct the rest.
A Session isn't just a date. It has a moment when it ends, and ending it does real bookkeeping.
You close a Session with /gm session end in Discord. Three things happen together:
Every Character in the Campaign is granted one advancement point.
Each grant is recorded as an event in that Character's advancement log.
The Session is marked as ended on the web. It can no longer accumulate new advancement.
The advancement payout is the in-app reward for showing up. Players spend their points later, between Sessions, to raise an attribute by one tier.
Once a Session exists, several things attach to it:
Notes you write directly in the Session page, your running record as the GM.
A Recording, optional, the audio file captured if you ran /recording start in Discord. The Session page shows the file (plus one stem per speaker) once Discord uploads it.
A Transcript, built from the Recording in the background. Each utterance becomes a timestamped segment.
A recap, generated on demand from the Transcript by clicking "Generate Recap" on the Session page. The recap arrives as a narrative summary, a list of events, and a structured debrief.
Advancement events, one per Character, recorded automatically when you ran /gm session end.
Open any Session and all of this sits in one place. The Session is the seam between what was planned in the Campaign and what actually got played.
The Session log is the Campaign's memory. Three weeks later, when a player misremembers what the harbour master said, the Recording is on the Session page; the Transcript is in the Recording; the recap noted the line; the events list says when it landed.