World Info Guide

World info, world books, and lorebooks help a model remember setting details only when they are useful. This guide covers practical setup: entries, triggers, depth, testing, and when to split or merge lore.

For the feature overview, start with World Books and Lorebooks in Tavern Studio.

World info guide: the short version

Use world info when background details are important but should not live permanently in the character card. Good entries are short, specific, and easy to trigger.

Start small:

1. Create one world book.
2. Add three to five entries.
3. Test each entry in chat.
4. Adjust triggers before adding more lore.

World book depth and insertion behavior

Depth controls where inserted lore appears relative to recent conversation context. The exact behavior can vary by app and implementation, but the practical question is simple: does the model see the lore at the moment it needs it?

If lore feels ignored, test whether the entry triggers at all before changing depth. If it triggers but the model still ignores it, the entry may be too long, too vague, or competing with stronger instructions.

How to write useful lorebook entries

A useful entry should answer one clear question. For example:

• What is this city?
• Who leads this faction?
• What rule governs magic?
• What secret should the model remember?

Avoid entries that try to describe an entire setting in one block. Split large lore into smaller pieces that can trigger independently.

Triggers, keywords, and activation

Triggers should be specific enough to avoid accidental activation. A common word like "city" may fire too often. A proper noun, faction name, location name, or unique phrase usually works better.

Test triggers with short prompts. If an entry activates too often, narrow the trigger. If it never activates, add a synonym or a more likely phrase.

Using lorebooks with character cards

Character cards and world books should work together. The card defines the character's identity and voice. The world book stores setting memory that may apply across several characters or chats.

If the same lore appears in many character cards, move it into a world book. If lore only matters to one character, linking it closely to that character may be enough.

Testing whether world info is working

Use a minimal test:

1. Start a chat with the world book enabled.
2. Mention a trigger phrase naturally.
3. Ask a question that requires the lore entry.
4. Check whether the model uses the right detail.
5. Repeat with a shorter prompt if the result is unclear.

Do not test with a huge prompt first. Long context makes it harder to see whether the world book is the problem.

Common world-info mistakes

Common issues include:

• trigger terms are too broad;
• entries are too long;
• several entries repeat the same fact;
• the world book is not attached to the chat;
• the model route has too little context;
• the character card contradicts the lore entry;
• the preset changes how context is assembled.

When to split or merge lorebooks

Split lorebooks when different stories, settings, or character groups do not share the same background. Merge entries when they always trigger together and describe the same concept.

The goal is not to create the largest possible world book. The goal is to give the model the right detail at the right time.