When CyberScribe generates a Session Summary or Plot Hooks, it builds a single combined prompt from up to five levels of instructions. These levels are stacked with a clear priority order — higher levels always take precedence over lower ones.

Priority Ladder

Instructions flow from highest priority (top) to lowest (bottom):

Admin-level Instructions Highest priority
Site-wide defaults set by the administrator. Applies to every game, every GM.
"No sexually explicit or racist content allowed in summaries."
GM-level Instructions Overrides system, campaign, session
Your personal default instructions. Applies to every campaign and session you run.
"Make summaries 1 page with a prose TL;DR at the top, then point-form highlights below."
Game System-level Instructions Overrides campaign and session
Instructions for a specific rule system. Applies to all campaigns within this system.
"Always include XP gained, items gained or lost, and NPCs killed in the summaries."
Campaign-level Instructions Overrides session only
Instructions for a specific ongoing story. Applies to all sessions in this campaign.
"The party is in Vallaki. Emphasise the oppressive burgomaster and the looming festival."
Session-level Instructions Lowest priority
Instructions for a single session. Added to the prompt but can be overridden by any higher level.
"One player was absent — exclude their character from the summary."

How the Combined Prompt is Built

When you click "Generate Summary" or "Generate Hooks", CyberScribe assembles the following sections in this order:

  1. Session Transcript — the full text of your uploaded audio (if transcribed).
  2. Session Notes — any notes you've written for this session.
  3. Session Info — session number, date, game system, campaign name, GM name, and list of player characters.
  4. Session-level Instructions — lowest priority.
  5. Campaign-level Instructions — overrides session.
  6. Game System-level Instructions — overrides campaign.
  7. GM-level Instructions — overrides system.
  8. Admin-level Instructions — highest priority, overrides everything.

The final line tells the AI: "Priority: Admin > GM > Game System > Campaign > Session".

Setting Your Prompts

Each level has its own settings page:

  • Session prompts — on the Session Settings page.
  • Campaign prompts — on Campaign Settings.
  • Game System prompts — on Edit Game System.
  • GM prompts — on Game Master Settings.
  • Admin prompts — on the Admin AI Config page.

Viewing the Combined Prompt

On any session, click "View Summary Prompts" or "View Plot Hook Prompts" to see the exact combined prompt that will be sent to the AI — including each level's contribution and the total estimated token count.

Practical Example

The Admin sets: "No sexually explicit content."
The GM sets: "1-page summary with TL;DR then bullet points."
The System sets: "Include XP and NPC kills."
The Campaign sets: "Party is in Vallaki — emphasise the festival."
The Session sets: "One player was absent — exclude their character."

The AI receives all five. The Admin's content restriction is absolute — no lower level can override it. The GM's format preference is applied, the System's mechanical detail is added, the Campaign's story context is included, and the Session's specific note about the absent player is respected — as long as it doesn't conflict with anything above it.

Generation Settings

Your administrator controls the AI model and parameters (temperature, top P, etc.) on the Admin AI Config page. These settings apply to all summaries and hooks across the site.