Recaps

The recap writes itself while you play.

Run /stop and the evening starts turning into something readable. The recap lands in Discord within minutes; everything else files itself in the dashboard.

Session 27 — The Eye of Zihuatl
2h 38m · 6 speakers · 7 scenes · recap ready 9 min after /stop

TL;DRZihuatl offered the party a valley, and demanded they call him sovereign for it.


At dawn after the battle in Tlalocayocan, the party approached Zihuatl. He offered them stewardship of a river valley — good stone, two thousand subjects, a modest tribute — and pressed them to acknowledge his sovereignty. They hesitated, being adventurers rather than governors, but did not refuse outright. Elandar was the one who saw he was frightening them on purpose.

1
Audience with Zihuatl0:00 – 39:47

The party presents itself to the enormous dragon ruler, who demands their fealty and offers them a valley.

+6 more scenes
0:04:23

Fenwick Do you know if there’s any other invasions anywhere else?

0:04:36

GM You are interrupted as the gigantic eye of the dragon — the reptilian iris is basically your size, Fenwick.

0:04:48

GM Arcanist, you brought your court with you. This pleases me.

Session 27 — The Eye of Zihuatl
SpeakingFenwickMarximLegoless
1:12:403:48:15
What lands in Discord a few minutes after you stop recording.

The recap is written from the transcript, not from notes — and that distinction is the whole feature. Notes record what somebody had the attention to spare to write down, which at a good table is nothing at all, because the person who would have been writing was busy playing. A transcript has everything, including the throwaway line in the second hour that turned out to matter in session forty.

The evening is also cut into scenes. A session is not one continuous thing: it is an ambush, then a long argument in a tavern, then the walk to the temple. Each gets its own summary and its own place in the index, so finding the bit you half-remember means scanning a dozen headings rather than scrubbing through three hours of audio.

None of it is a wall of text you have to read. The recap is short enough to post in a channel and be read by someone catching up on their phone. The scene breakdown is there when you want more, the transcript when you want the exact words, and every scene links to the moment it came from.

Nobody has to remember to do any of this. It happens because the session ended.

What arrives, and when

  1. The recap, in minutesPosted to your Discord channel while people are still saying goodnight. Short enough to read on a phone.
  2. The scene indexThe evening split into its actual scenes, each with its own summary, so a half-remembered moment is a heading away.
  3. The full transcriptEvery line, attributed to the character who said it, timestamped against the recording.
  4. The campaign synopsisDaria keeps a running account of the campaign as a whole, updated after each session, for the player who missed three in a row.

Questions about recaps

How long does the recap take to arrive?

Usually a few minutes after /stop, depending on how long the session ran. The recap comes first; the transcript, scene index and podcast follow behind it.

Can we change a recap that gets something wrong?

Yes. /correct tells Daria what actually happened, and the correction carries forward — later recaps and answers are written knowing it, rather than repeating the mistake.

Does the recap spoil anything the players should not know?

It is written from what was said aloud at the table, so it contains what your players already heard. Anything the GM kept to themselves was never in the recording in the first place.

Read the full FAQ →

Stop taking notes.

Daria is not open to the public yet. Join the community server and we will ping you the moment she can record your table.

Get Pinged at Launch

See also

← All featuresSee it all on the homepage →