Chapters
Chapters let you break a long roleplay into clean segments inside the same Chat / World. Treat them like checkpoints or scenes. Each chapter holds its own message history, so swapping chapters changes what the model sees and keeps context focused.
Click a chapter in the list to switch. Messages do not carry over across chapters unless you explicitly include them via Lorebooks or custom prompt design.
Ways to use it
- Duplicate a chapter to try alternate branches without losing history.
- Start each chapter with a clear player goal in Scenario to guide the model.
- If the tone drifts, tighten the Scenario and lower Max Depth in the active Chat Template.
Note
Chapters are in active development. More cross‑chapter features are planned.
- Keep context small and relevant for the current scene.
- Swap tone or goals without rebuilding your Chat Template.
- Prepare branching paths by duplicating a chapter and editing its scenario.
Use the editor to define the fields below. These values are available to Prompt Format Template sections, Custom Prompts, and Quick Buttons via placeholders like {{chapter.title}} and {{chapter.scenario}}.
| Field | Purpose |
|---|---|
| Title | Display name of the chapter. |
| Scenario | Scene summary, goals, constraints, or setup text. Inject into System Prompt sections; e.g., “Chapter Context” with {{chapter.scenario}}. |
| Chat Start Message | The user’s first message for this chapter. Seeds the opening turn when the chapter begins. |
| Use AI... | If enabled, Chat Start message will be used to give AI Instructions to write the Start Message, using current Chat Template. |
Behavior:
- When “Use AI to generate…” is on, starting the chapter shows a button that triggers the LLM to create the first user message; otherwise the field’s text is inserted directly as the first user turn.
- Token counters near fields help you plan within your model’s Context Size.
Common placeholders you’ll use in templates and prompts:
{{chapter.title}}{{chapter.scenario}}
These integrate with your Prompt Format Template sections (e.g., “Chapter Context” only renders when a scenario exists).
Upcoming features aim to:
- Feed chapter‑scoped memory into Lorebooks or persistent World Memory.
- Attach Agents to detect chapter completion and route to the next chapter automatically.
- Chapters currently do not affect each other automatically. There’s no built‑in state transfer between chapters yet.
- Cross‑chapter summaries must be done manually (e.g., add a recap to the next chapter’s Scenario or a Lorebooks entry).