Tavern Studio Feature - EN

World Books and Lorebooks in Tavern Studio

World books store reusable background information for roleplay, fiction, and long-running character chats. They help the model remember places, factions, rules, relationships, and setting details without forcing every detail into a character card.

SillyTavern users may call this workflow World Info. Other communities may call it a lorebook. Tavern Studio uses the same practical idea: structured background memory that can be attached to characters and chats.

What a world book does

A world book keeps lore outside the main prompt until it is relevant. Instead of pasting an entire setting into every message, users create smaller entries that can be activated by keywords, context, or manual selection.

This is especially useful when:

a story has recurring locations or factions;
several characters share the same setting;
the model forgets important background details;
the character card is becoming too large;
different chats need different parts of the same lore.

World book vs lorebook vs world info

World book, lorebook, and World Info are overlapping terms. The important concept is not the label; it is the workflow. The user is storing structured knowledge outside the character card and deciding when that knowledge should enter the model context.

For SillyTavern migration, the key question is whether the existing World Info entries still trigger in the right places after moving into Tavern Studio.

Creating and editing lore entries

A useful lore entry is usually short, specific, and easy to trigger. It should describe one concept clearly: a location, rule, relationship, event, item, faction, or secret.

When editing entries, check:

whether the entry is too broad;
whether trigger terms are too common;
whether the content repeats the character card;
whether the entry adds useful context at the moment it appears;
whether it increases token use without improving replies.

Using world books with characters and chats

World books work best when they support the character rather than replace the character. A character card should define personality, voice, and starting situation. A world book should hold setting memory that may or may not be needed in every exchange.

For example, one character can be linked to a personal lorebook while a campaign chat uses a shared world book for locations and factions.

Importing SillyTavern world info

If you already have SillyTavern World Info, migrate a small set first. Test entries that should trigger often, entries that should trigger rarely, and entries that depend on specific names or phrases.

After import, run a short test chat and check whether the model sees the right details. If the world book is active but the model ignores it, the issue may be triggers, depth, context size, model behavior, or competing prompt instructions.

World-book generators, editors, and recommenders

Lorebook generators and recommenders can help draft entries, but generated lore still needs review. Long generated entries often include repetition, spoilers, or broad triggers that activate too often.

Treat generated world books as drafts. Prune them, split large entries, and test trigger behavior before relying on them in a real roleplay session.

Shared world books are lore assets, not Tavern Studio installers. If you use a community lorebook, import it into the world-book manager separately from the app itself.

Before using a shared lorebook, check spoilers, tone, trigger terms, token cost, and whether it assumes a specific character card or preset.

When to use the detailed world-info guide

This page explains the feature. For depth, insertion behavior, triggers, and testing steps, use the world-info guide.