
Write for a subject that can be recognized in chat
An entry should answer the useful questions about one subject. For a railway depot, that might mean its opening hours, the person in charge and where unclaimed freight is stored. Leave out the full history of every delivery unless that history matters to the story.
Pick keywords that identify that subject in ordinary dialogue. A precise place name is less likely to activate irrelevant material than a broad word such as 'station' or 'room.' The wording of the trigger matters as much as how clearly you write the entry.
Distinguish stored lore from the entries being used
Only relevant entries brought in by keyword matching use the conversation's context. A Lorebook holds up to 5,000 entries, each no longer than 2,000 characters, but that capacity does not make the whole book active. Loaded material shares limited space with instructions and other conversation information.
Keywords are checked against the latest four messages, not against the contents of other Lorebook entries. If an entry is overlooked, mention its subject explicitly and check the keyword spelling. If too much unrelated lore appears, make the triggers more selective or separate an entry that covers several subjects.
Choose what to publish and what to track elsewhere
Keep a book Private for personal use. Public discovery and reuse follow the review process described in our Lorebook guide. Treat those entries as published text and remove private information before sharing. Sharing the book does not share your chat history.
Use a Lorebook for a depot's location or its regular staff. A changing quantity, such as supplies remaining during a journey, is a job for a Rulebook. Separating setting facts from changing state makes it easier to decide where an update belongs.
Questions
When does information from a Lorebook enter the conversation?
Entries can supply world knowledge when their keywords match the chat. They add relevant background alongside the character definition rather than replacing that definition.
Does storing thousands of entries give a character constant access to them all?
No. The context has limits, and relevant lore occupies part of that space. Focused entries and selective keywords are more useful than expecting every stored detail to remain active.