> 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/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/narrative-design.md). # 叙事设计通过调用叙事触发器、注入模板键以及处理区段变化事件，从 Unreal Engine 驱动角色故事图。叙事设计为 Convai 角色提供一个结构化的故事图谱——命名的章节、命名的触发器，以及会根据实时游戏数据调整目标的模板键。你在 Convai 仪表板中编写该图谱；在运行时， `UConvaiChatbotComponent` (`Convai 聊天机器人`) 调用触发器并接收来自 Convai 的章节变更。 **第一次接触叙事设计？** 先从 [叙事设计如何工作](/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/narrative-design/how-narrative-design-works.md) 以了解章节、触发器和模板键。然后按照 [叙事设计快速入门](/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/narrative-design/narrative-design-quick-start.md) 在你拥有一个已在仪表板中配置好图谱的角色之后。使用 [叙事设计 | Playground](/api-docs/zh/convai-playground/character-customization/narrative-design.md) 在打开 Unreal Engine 之前创建章节和触发器。 ### 开始使用


叙事设计如何工作了解章节、触发器、模板键，以及从触发器调用到章节事件的运行时流程。	叙事设计的工作原理
叙事设计快速入门在 Blueprint 中调用一个命名触发器，并通过打印新的章节 ID 来确认章节变更。	叙事设计快速开始

### 构建并配置


叙事触发器使用 `调用叙事设计触发器` 用于命名的图谱转换，以及 `调用语音` 用于动态上下文事件。	叙事触发器
模板键填充 `叙事模板键` 映射，以便章节目标引用实时游戏数值。	模板键
获取叙事数据在运行时使用 `Convai 获取叙事章节` 和 `Convai 获取叙事触发器`.	获取叙事数据

### 参考资料与支持


叙事设计 Blueprint 参考 Blueprint 函数、事件、属性、异步获取节点以及叙事结构体的参考文档。	叙事设计 Blueprint 参考
叙事设计使用示例用于线性推进、动态上下文事件、模板键和触发器验证的 Blueprint 实例教程。	叙事设计使用示例
排查叙事设计问题修复未触发的章节事件、错误的转换、被忽略的模板键、获取失败以及会话就绪问题。	排查叙事设计问题

### 下一步 {% content-ref url="/pages/fc5915683cbb3a9ae3782e4de53c3288e9e3b7cc" %} [叙事设计快速开始](/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/narrative-design/narrative-design-quick-start.md) {% endcontent-ref %} {% content-ref url="/pages/55f4d0a125ab988f4603436fa20ceb69b527078d" %} [叙事设计](/api-docs/zh/convai-playground/character-customization/narrative-design.md) {% endcontent-ref %} --- # 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/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/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.