Upload the recording, or skip straight to text.

Start a session in your campaign and give Everlore whatever you already have. Most tables upload the recording from game night. Tables that already keep transcripts can skip transcription entirely.

• One mixed recording of the whole table.
• Separate tracks, one per player, from a voice-chat recorder.
• An existing transcript or written notes, pasted or uploaded as text.
• Common audio formats including MP3, WAV, M4A, FLAC, OGG, Opus, and WebM.

Separate tracks give the best result, because each player is already isolated and speakers are identified by track instead of guessed from a shared microphone. They also cost more managed transcription time, since every track is metered separately. Companion transcribes multitrack locally without touching your allowance.

Two routes to a transcript. One destination.

Everlore needs speaker-labeled text before it can read a session. You decide where that text gets made. The cloud route asks nothing of you. The local route asks for an install and gives you a recording that never leaves your desk.

Both produce the same transcript source inside your campaign. Nothing downstream behaves differently.

The night becomes a chronicle and a pile of proposals.

With a transcript in hand, Everlore reads the full session for what happened, who was involved, and what changed. It produces two things: something to read, and something to decide on.

• A session chronicle. A readable account of events, decisions, discoveries, loot, and the thread left hanging for next time.
• Proposed campaign records. Characters, places, items, factions, lore, quests, events, and mysteries, each tied to the moment in the session that supports it.
• Proposed connections. Relationships between those records, with the evidence that suggested them.

Your wiki has not moved yet. Everything at this stage is a proposal waiting on you.

One change set. Your decisions. Then Apply.

This is the step that makes the rest trustworthy. Everlore shows you what it found, which page each change would touch, and why it thinks so. You go through it and decide.

• Approve a change, reject it, or edit the wording first.
• Merge a likely duplicate, or keep two similar names apart.
• Create a new page, or fold a discovery into an existing one.
• Ask Ember to improve a summary or recover a missing detail, then check the exact before and after.

Table speech is messy. Names get slurred, spellings drift, and players speculate with total confidence. Review is where that gets sorted out, once, instead of leaking into your wiki forever.

Approved changes land as linked, readable pages.

Apply is the only moment your campaign changes. Everlore writes what you approved, repairs the links around it, and leaves the rest alone.

• New pages get created and cross-linked to the canon they touch.
• Existing biographies and histories gain a new chapter instead of being overwritten.
• Anything you wrote by hand stays protected.
• Page history keeps earlier revisions so you can roll back a bad call.
• The Campaign Chronicle extends and the Living Web grows new connections.

Your campaign should outlive any subscription.

Everlore exports an Obsidian-ready Markdown vault of the approved campaign. Plain files, real links, and folder structure you can open with or without us.

• Approved pages, indexes, links, timeline, and campaign structure.
• Source references so you can trace a fact back to its session.
• Campaigns stay private by default. Nothing is public unless you share it.