> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/plugins-and-integrations/convai-unity-sdk/features/narrative-design.md). # Narrative design Find guides for setting up, configuring, scripting, and troubleshooting the Narrative Design system in the Convai Unity SDK. Narrative Design gives Convai characters a structured story graph of sections and triggers. This section covers everything from understanding the runtime model to the complete scripting API.


How narrative design works Understand the runtime pipeline, sections, triggers, template keys, and component placement.	How narrative design works
Narrative design quick start Add a Manager and a collision trigger to a character and confirm a section change in Play Mode.	Narrative design quick start
Configure the narrative design manager Add, sync, and configure the Manager component — the listening post for section transitions.	Configure the narrative design manager
Configure narrative design triggers Place world triggers with collision, proximity, timer, or manual activation.	Configure narrative design triggers
Configure narrative template keys Inject runtime values into the character's narrative objectives from the Inspector or code.	Configure narrative template keys
Narrative design scripting reference Full C# API reference for IConvaiNarrativeDesign, NarrativeDesignFetcher, and programmatic control.	Narrative design scripting reference
Narrative design usage examples Four worked examples from a simple welcome kiosk to a fully adaptive multi-section scenario.	Narrative design usage examples
Troubleshoot narrative design Diagnose every TriggerStatus state, common misconfigurations, and fetch failures.	Troubleshoot narrative design

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.convai.com/api-docs/plugins-and-integrations/convai-unity-sdk/features/narrative-design.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.