Should I put every RisuAI chat event in a lorebook?
Usually no. Lorebooks work best for durable, triggerable information. Keep the evolving chat state in a concise current summary.
RisuAI guide
RisuAI separates character data and lore from the flowing chat. That gives you useful controls, while a long roleplay still benefits from a concise record of its current state.
RisuAI's ecosystem supports character-card and lorebook formats. Lore entries can be triggered by recent-chat keys, which helps relevant background information enter context without always occupying the same space.
A conversation summary handles a different layer: it records the developments that happened in this specific chat and are not simply part of the original card or lorebook.
Keep reusable character and world information in the appropriate card or lorebook fields.
Use thredly to summarize the specific chat's events, relationships, and current scene from copied text.
Use the result as a chat-memory brief or a fresh-session introduction, then update the lorebook only for facts that are genuinely durable world information.
thredly is independent of RisuAI. It does not read RisuAI chats automatically. Copy a conversation section or use a native export when available, then paste or upload the text through thredly's supported web workflow.
Usually no. Lorebooks work best for durable, triggerable information. Keep the evolving chat state in a concise current summary.
The card defines a reusable character. The summary records what happened in one particular conversation.