Skip to content

Link session logs

A session log is the transcript of what actually happened at the table. This page shows you how to point a session at its transcripts, how the tool archives them into the repository, and what it can read out of them. When you are done, the transcript is readable alongside the session forever, even if the site you copied it from goes dark.

Three different things share the word 'log'

A session log is the copy-paste or recorder export of what was said and done in-game. That is the only kind you ever deal with. The Discord messages the tool sends players are delivery, not logs. The tool's own internal operational logs are a separate mechanism you never touch.

1. Copy the transcript URL

Transcripts live outside the repository. They sit on krisaphalon.ct8.pl, Pastebin, or Google Docs. Copy the URL of each transcript that belongs to the session.

2. Add the URL under - Logi:

Write a - Logi: block in the session's metadata and put the URL on a bullet under it:

### 2026-07-01, Eraster rozmawia z Tussalem, Anward

Eraster spotkał się z Tussalem w jego willi w Thuzal. Wypili herbatę i zjedli obiad.

- Lokacje:
    - Thuzal/Rezydencja Tussal
- Logi:
    - https://nerthus.pl/logizsesjierasteraztussalem
- PU:
    - Eraster: 0.2
    - Lord Tussal: 0.2

One URL per bullet. Several logs for one session are fine and common - a recorder export alongside a chat copy-paste, or one transcript per part of a long evening. Give each its own bullet:

- Logi:
    - https://nerthus.pl/logizsesjierasteraztussalem
    - https://krisaphalon.ct8.pl/get/2026-07-01_Eraster_rozmawia_z_Tussalem_Anward

Two sessions may point at the same URL. Each transcript is fetched only once, however many sessions link it. The session header and the other metadata blocks are covered in Record a session.

3. Fetch the transcripts

Fetching writes to the repository, so it is a deliberate step. It never happens because someone opened a page. Someone runs the fetch, and the tool downloads every linked transcript it has not already archived.

Each transcript is archived under nerthus.logs/, as two files: the raw text (.log) and a parsed version (.json). Both are committed with the rest of the repository. Once that commit lands, the log is readable alongside the session without visiting the third-party site again. The repository, not the outside host, is the durable home of the transcript.

What the tool reads out of a transcript

The tool decides a transcript's format by looking for [HH:MM] timestamps.

A chat transcript is a copy-paste from the game, timestamps and all:

[20:14] [Lokalny] Eraster: Dziękuję za zaproszenie, Lordzie.
[20:15] [Lokalny] Lord Tussal: Herbata stygnie. Siadaj.

A recorder export is the JSON a narrator's log recorder produces, and it is what the krisaphalon.ct8.pl links hold. Chat and recorder transcripts both yield who spoke.

A prose transcript is a hand-written narrative summary, with no timestamps:

Eraster przybył do rezydencji o zmierzchu. Lord Tussal czekał już przy stole.

Prose parses fine and is archived like anything else. It yields no speakers at all, and it does not announce that. Paste a chat or recorder transcript when you want to know who spoke.

The tool also reads the places the party moved through and turns those movements into doors between locations, which belong to Locations.

If a fetch fails

Some transcript hosts sit behind a login wall, and many ct8.pl links now do. A URL behind a login wall cannot be fetched.

A failed log is recorded and retried later on its own. It never blocks the rest of the batch, so the other transcripts in the same run still land. You do not need to change the session when a fetch fails.

A log that fetched successfully once stays in nerthus.logs/ even if its source later disappears. That is the whole point of archiving it.

  • Record a session - the session header, the body, and the other metadata blocks.
  • Locations - the location tree, and the doors the tool derives from fetched transcripts.