Docs/Overview

Overview

World Knowledge is a project-wide library of shared lore, facts and rules. Upload a document once, choose which NPCs can read it, and those NPCs use it in conversation.

World Knowledge is your project's shared library of lore, facts, history and rules. Upload a document once and decide which NPCs have access to it. When a player asks something the document answers, every NPC that can read it answers from it.

How it differs from per-NPC knowledge

Mistscale has two knowledge layers. They look similar but solve different problems:

Per-NPC knowledge

Files attached to one specific NPC, inside the NPC editor. This is that character's personal knowledge.

World Knowledge

Project-level documents you can share with many NPCs at once, managed from the World Knowledge page in the dashboard.

Audiences

Named groups of NPCs (e.g. guards, tavern_folk) so you assign a document to a group instead of one NPC at a time.

Tip
Use World Knowledge for anything more than one character should know, such as kingdom history, faction politics, and shared rules. Keep truly personal details (a character's own backstory) in the per-NPC Knowledge layer.

Core concepts

Document
A piece of world knowledge (a .txt, .md or .pdf file). It is split into sections and indexed when you upload it.
Audience
A reusable group of NPCs. Assign a document to an audience and every member can read it.
Visibility
Either Everyone (all NPCs) or Restricted (only the audiences/NPCs you choose).
Published
The one switch. A published document is readable by the NPCs it is shared with; an unpublished document is a draft no NPC can read.

Who can read it: Everyone vs Restricted

  • Everyone — every NPC in the project can read the document. Best for shared, public world facts.
  • Restricted — only the audiences and individual NPCs you assign can read it. Best for secrets, faction-only lore and hidden quest clues.
Heads up
A Restricted document with no audiences or NPCs assigned is readable by no one. After uploading a restricted document, open it and assign at least one audience or NPC.

Drafts: prepare now, go live later

Publishing is the one switch. Upload documents as drafts (Make it readable now off, the default) and set up who can read them; nothing reaches an NPC until the document is published. Sharing changes on a published document take effect on the NPC's next reply.

When a batch is ready, the Deploy button publishes every draft in the project in a single action.

Where to next