Write a focused entry with recognizable keywords
Choose one subject for each entry and include only the facts needed to use it. An observatory entry might record its opening hours, where spare lenses are kept and who maintains the telescope. It does not need a full account of every observation made there.
Match the triggers to words someone is likely to say in the chat. A specific location name is more selective than a broad term such as 'town' or 'place.' Overly general keywords can bring in background that has little to do with the current scene.
Check when an entry actually enters context
Keyword matches in recent dialogue bring relevant entries into the conversation's context. Each Lorebook can store up to 5,000 entries, and each entry has a 2,000-character limit. That storage is not a promise to load the entire book: active entries still compete with other material for limited context space.
Matching checks the four most recent messages. One entry's text does not activate another entry. If a detail is missing, use its subject in the conversation and inspect the trigger spelling. When unrelated entries activate together, narrow the keywords or divide a broad entry into more focused subjects.
Choose visibility and keep story state separate
Private Lorebooks are for personal use. Our feature guide describes public books as discoverable and reusable after the relevant review process. Treat public entries as published material and leave out personal information. Sharing a Lorebook does not itself share your conversations.
A Lorebook suits facts such as where an observatory stands or who works there. Changing quantities, such as the team's remaining equipment, belong in a Rulebook. Keeping background knowledge apart from story state makes it clearer which tool to update.
Questions
How does a Lorebook help a SpicyChat conversation?
It supplies additional world knowledge through entries whose keywords match the conversation. Those entries supplement the character definition instead of taking over its role.
Will the model always read every entry in my Lorebook?
No. Relevant entries take up part of the available context, and the amount that can be included is limited. Concise subjects and selective triggers help you use that space; the book's storage capacity does not make every detail continuously active.