Skip to content
KallamoDocsBack to the site

A world for your table

This guide is for a game master running a campaign at a real table. Kallamo does not play the game for you. It keeps the setting in one place, answers your questions about it in the chat, and helps you keep the records straight between sessions.

The setup has three parts:

  • Worldbuild holds the setting: people, places, factions, items, events, the calendar and the rules.
  • A Game Master Helper profile answers your questions about that setting in the chat, prepares sessions with you, and turns your session notes into updates.
  • Memory holds what is not an entity: the campaign outline, your session notes, the rulebook.
  1. Create a workspace for the campaign on the launch screen.

  2. Build the setting in Worldbuild. Start with what the first sessions need, not the whole world.

    • Locations by size: Region, Area, Place, Spot, each inside the next.
    • Factions with territory, roster, stance, and former members.
    • Characters for the NPCs, with relationships seen from each side and Local to where they come from.
    • Items for the things that matter to the plot.
    • Events for what already happened, with who was there and what it changed.
    • Facts for what is true, whatever anyone believes.

    See Entities and templates.

  3. Add your own fields if your game needs them. In Entity types, add fields to a template, like a challenge rating for creatures or a price for items. Every sheet of that kind gets them.

  4. Cover the secrets with spoilers. Wrap a secret in ||double bars||, or use the eye beside a field. You can show a sheet on screen without revealing them, and the AI still reads them.

  5. Write what each faction and region knows in their Knowledge, and what key NPCs know, believe and remember in theirs. The helper then answers from the right perspective when you ask what someone would know. See Perspective and Knowledge.

  6. Put the rest in Memory.

    • The campaign outline and the next arc: searchable.
    • Your table rules, in a few lines: always on.
    • Session notes as they pile up: searchable.

In the Library, choose New profile and fill it in:

Field Value
Name Game Master Helper
Description Answers questions about the campaign’s world and keeps the records straight.
Connection and model A strong model with a long context window. It reads a lot of canon per answer.
Temperature 0.3. It should report the canon, not invent it.
Max reply tokens 2048 is enough for answers; raise it for session prep.
Search before replying On.
Search rounds 3. Raise it to 4 or 5 for questions that cross many sheets.

Behavior and rules:

You assist the game master of a tabletop campaign. You are not the narrator and you never speak to the players.
When asked about the world, answer only from Worldbuild, Memory and the session notes. Name the sheet or note each fact comes from. If the canon does not say, answer "Not in the canon yet" and suggest what could fit, clearly marked as a suggestion.
Secrets are for the game master: state them plainly when asked.
When given session notes, list what changed: who met whom, who learned what, what moved where, which relationships shifted, what new names appeared. Keep it as a short list the game master can check.
Keep answers short. Use tables for stats and lists.

Search instructions:

Look up every character, place, faction and item named in the question, and follow their relationships one step. Search the session notes for the last time each of them appeared.

Knowledge base. Add the game system’s rulebook or SRD as a searchable file, and a one-page cheat sheet of the rules you use most as an always-on file. These go with the profile, so the same helper works in your next campaign too. See Profile knowledge base.

Then allow it in the workspace: Configuration › Profiles & Workflows.

Pick the Game Master Helper in the message box and ask, as you would ask a co-GM:

  • “The party reaches the harbour district next session. Who is there, what do they want, and what do they know about the stolen ledger?”
  • “List every open thread involving the river guild, with the session it came from.”
  • “Which NPCs have met the party, and what does each one think of them?”
  • “What does the town believe happened at the mill, and what actually happened?”

Because smart search is on, the helper looks up each name, follows relationships and reads your notes before it answers. Turn on Retrieval and context in Settings › Diagnostics to see exactly which sheets and notes it used.

  1. Paste your session notes in the chat and ask the helper what changed. It answers with a short list.

  2. Turn the list into updates. In Worldbuild, press Update entities. It reads the latest messages and suggests what changed: new sheets, changed fields, new relationships. Locked sheets are skipped.

  3. Review. Suggestions land in Waiting for review. Accept what is right, edit what is close, reject the rest. Nothing changes your canon without you.

  4. Record what happened as an event occurrence when it matters later: who was there, what it changed.

  5. Save the notes in Memory as a searchable note, so next session’s questions can find them.

5. Keep secrets away from the wrong profile

Section titled “5. Keep secrets away from the wrong profile”

If you also use a player-facing profile in the same workspace, such as a narrator for solo practice, limit secret material to the helper: in Memory, set the item’s Profiles to the Game Master Helper only. On Worldbuild sheets, the narrator only learns what a character in the scene could know.

Export the world as a .klwb to hand it to a co-GM, or to move it to another computer. Turn on Include each character’s current values to hand over a campaign in progress.

  • Run it as roleplay. Turn on Roleplay and let a Narrator profile run scenes for one player. The Narrative State then records the session for you. See A long roleplay campaign.
  • A rules lawyer. A second profile with only the rulebook in its knowledge base, smart search on, and rules that say to quote the page. See the recipes.