Guides

Seed the names the table is about to hear

1. Run /prep in the campaign's voice channel for your private Session Prep link.
2. Type the name, how the table says it, its folder and tags, an optional picture and a DM note.
3. It stays hidden from players; the transcriber and the checker learn the spelling straight away.
4. After the game, press Reveal on the names the table said: everything, the name only, or the parts you choose.

Record and finish a session

Make sure everyone knows the session will be recorded. Where possible, have each player use their own Discord account and headphones; separate Discord tracks help keep speakers straight. One shared account or microphone does not give the bot a separate Discord track per person.

An assigned Campaign Manager, Bot Admin, Discord administrator or server owner can start and stop recording. The person starting it must join the campaign voice channel. The campaign folder and session-files destination must be ready: check the replies to /set_game and /set_transcripts.

A website account is not required to record. Use your Discord account for the recording commands; link a website account when you are ready to use the checker or open your private campaign website.

1. Run /start_recording and wait for confirmation.
2. Play normally.
3. Run /stop_recording and wait for the review card.

Review names, then facts

1. Press Open Fact Checker Website on the review card.
2. Names first: approve the known ones in one go, then decide each spelling, alias or new record.
3. Facts next: confirm, correct or drop each one. The batch row drops all the table talk at once, and the last batch can be undone.
4. Finish the review: the files, records, purses and website update on their own. /review_session reopens it; /record_event files a change the transcript never said; /discard_review and /restore_review keep a session out of the vault, or bring it back.

Get onto the campaign website

Website access is for mapped campaign members, assigned Campaign Managers and administrators. If you are a player who skipped the roster step, use /set_character to map yourself to that campaign first, or ask its manager to do it. A website account alone does not grant access to a private campaign.

Run /wiki in your campaign's voice channel, or select that channel in the command. Its reply is private to you.

If your Discord is already linked, use the same website account: the reply grants access to this campaign automatically. Sign in and open its campaign link; no new account or linking code is needed.

1. If this is your first visit, open the sign-up link in the private reply. Enter your Discord display name and a separate website password of at least ten characters, confirm it, and press Create account. If you already have an unlinked website account, sign in instead.
2. Open Account. Under Discord link, enter the newest code from the private reply and press Link Discord.
3. After linking is confirmed, open the campaign link from that same reply. No second command is needed after a successful link.

The code works once and expires after ten minutes. A new code replaces the old one; if it expires or linking fails, run /wiki again. Keep the code and your website password private. There is no separate campaign password and no second account for each campaign.

Find things in the records

1. Campaign home for the front page; Browse files for the published folders; the notes tree for single pages.
2. Full search, filtered to people, places, things, quests, sessions, lore or creatures.
3. Request a change when something is wrong: edit, change spelling, or remove. It starts a discussion; the reader itself is read-only.
4. In Discord, /add_note adds your own notes (private to you and the DM by default), and /campaign fetches any session's transcript, summary or status.

Ask him in Discord

1. Mention him in a server text channel: @Summurizer How does /set_game work?
2. For your game, name it: @Summurizer In campaign: The Lost Mine, what was the blacksmith's name?
3. Campaign questions need your own /set_character mapping, and he uses only the latest approved release you are allowed to see.
4. He reads no channel history, keeps no memory of earlier questions, and his reply is public in that channel.

What a notice means and what to do

1. A release fails quietly first: he tries again after ten minutes, three times, and only then posts "release failed" in the transcripts channel with the reason.
2. "Human review is not complete for N facts": open the checker and decide the rest, then press Finish again.
3. "The reviewed Mapped transcript changed after review": the transcript was edited after the review closed; tell the bot owner, who can re-pin it.
4. Nothing published for an hour: /bot_info shows this server's sessions (waiting, releasing, failed) and each website's state; "stuck" names the cause, and re-approving the website from /campaign clears the common one.
5. The bot owner is told automatically about error spikes, stuck publishing and failed releases; you do not need to chase him.

When he gets it wrong

1. Run /bug_report and say what you were doing and what happened.
2. A button that did nothing, a name he keeps mangling, an answer that makes no sense: all of it is useful.
3. You do not need to understand the code.