AIME / FIELD NOTES
What Is a Lorebook in AI Roleplay? (World Info Explained)
Long roleplay breaks in a predictable way: the city rules vanish, a rival’s name drifts, magic systems rewrite themselves mid-scene. People reach for a fix called a lorebook — also world info, or in Chinese communities 世界书.
This page explains what that mechanism is, how it differs from long-term chat memory, how it shows up inside character cards, and what that means if you use AIME. It is an explainer, not a ranked app list.
We build AIME and the AIME Character Atlas. Important honesty up front: as of 2026-10-26 (Asia/Shanghai), AIME’s public homepage emphasizes long-term memory, voice, group chats, and Tavern card import — it does not advertise a dedicated lorebook / world-info editor UI. Do not read this article as “AIME has lorebooks.” Where cards already embed lorebook-like data inside a PNG, our import path talks about preserving embedded fields — that is not the same as a separate lorebook uploader. Details: import guide and Atlas explainer.
Public mechanism wording below aligns with community and third-party documentation summaries (including BestCompanionsAI’s roleplay explainer, checked by that site on October 20, 2026). Implementations differ by app; trust each product’s own docs.
Lorebook in one minute
A lorebook (world info) is a set of entries. Each entry usually has:
- Trigger keywords (or keyphrases), and
- Content — the fact or paragraph to insert.
When a keyword appears in recent chat (within whatever scan depth the front-end uses), the system adds that content to the prompt for that turn. When the keyword is absent, the entry stays out, saving context for the live scene.
That is why people call it “facts that appear on demand,” not “paste the whole encyclopedia into every message.”
Community character-card specs may also define budgets (how many tokens lorebook text may consume) and how far back the scanner looks. Exact numbers are product-specific — we are not inventing industry standards here.
Lorebook vs long-term memory
These words get mixed in marketing. They solve different jobs.
| Dimension | Lorebook / world info | Long-term chat memory |
|---|---|---|
| Typical content | Places, factions, magic rules, NPC bios | What you two already talked about; preferences; plot progress |
| Typical trigger | Keywords / scan of recent text | The product’s memory system (summaries, stored facts, etc.) |
| One-line feel | “The world remembers its own rules when relevant” | “The character remembers us” |
AIME’s public product language is about long-term memory for ongoing conversations. For a plain-language breakdown of memory layers and a low-sensitivity test you can reuse on any app, read AI chat long-term memory.
You can want both. A lorebook will not automatically replace chat memory, and chat memory will not automatically keep a 40-page setting bible tidy.
How it shows up in character cards
A Tavern character card already carries core fields: name, description, personality, scenario, first message, and more. Those fields are “always available” material for the front-end.
Separately, the community V2 outline allows an optional nested character_book (lorebook-like data inside the card file). Public field explainers mention it as optional — see, for example, Sillycard’s V2 outline notes. That means:
- A PNG can carry world-info entries embedded in the card.
- Whether an app exposes an editor for those entries, or injects them at chat time, depends on that app.
AIME Card studio’s documented honesty (import / Atlas articles): empty-state copy about not discarding extensions or lorebook data already inside the card refers to preserving what the PNG carries. It is not a claim of a standalone lorebook file upload or a full SillyTavern world migration.
Building cards from scratch? Start with core fields in How to Make a Tavern Character Card. Finding examples: where to find cards.
Where people use lorebooks today
High level only — re-check each product:
- SillyTavern and similar local front-ends are built around character cards, group chats, and world info controls. You connect your own model backend.
- Some hosted roleplay sites publicly document lorebook features (third-party explainers commonly name SpicyChat and Janitor among others; Character.AI has discussed a Lorebook in beta / paid-first contexts in external summaries). Treat those as “check the live help center,” not as our test results.
- Companion apps sometimes use related ideas under other names (journals with keyphrases, pinned notes, shared roleplay notes). Naming differs.
This page will not rank “best lorebook app.”
What this means if you use AIME
What AIME publicly offers (homepage / FAQ, 2026-10-26): long-term memory for ongoing chats; natural voice; multi-character group chats; Character Atlas for Tavern V2/V3 discover / import / publish.
What we are not claiming today: a dedicated lorebook manager UI, keyword entry editor, or one-click import of standalone lorebook files / full desktop SillyTavern worlds beyond what Card studio and the import guide actually support.
Practical tips:
- Put must-not-forget world facts into the card’s description and scenario when you author a card.
- If you maintain a complex lorebook in SillyTavern, keep using ST for that authoring workflow; export a compatible PNG when you want the character on your phone via Atlas.
- Use AIME’s memory for relationship and plot continuity — that is the product promise we actually print.
- Re-check 365aime.com and Atlas if engineering ships new world-info tooling later; do not assume it from this article.
FAQ
What is a lorebook?
A set of keyword-triggered world facts inserted into the model prompt only when those keywords appear in recent context. Also called world info or 世界书.
Is a lorebook the same as memory?
No. Lorebooks are usually triggered world knowledge. Long-term memory is usually what the chat relationship should retain. See the comparison table and our memory guide.
Do I need a lorebook for good roleplay?
Not always. Many strong scenes run on a solid character definition + scenario + first message. Lorebooks help when the setting is large and you do not want to paste it every turn.
Are lorebooks inside character cards?
They can be. Community V2 cards may nest a character book inside the file. Core fields (description, scenario) are the simpler place to start.
Does AIME have a lorebook feature?
Not as a documented standalone UI on public product pages as of 2026-10-26. AIME documents long-term memory and Tavern card import. Embedded lorebook data inside a PNG may be preserved on import per the import guide — that is not the same as “AIME has lorebooks.” If that changes, trust the live site.
Why does my AI still forget plot points?
Context windows drop old turns; summaries lose detail; lorebook entries never fire if keywords never appear. Pins, summaries, card fields, lorebooks, and product memory each cover different failure modes.
Next step
- Clarify whether your pain is world rules (lorebook-shaped) or relationship continuity (memory guide).
- Strengthen card fields — make a card or import one.
- Try AIME for remembered conversations: download / browse Character Atlas.