> 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-unity-sdk/embodiment/emotion.md).

# 情绪

查找 Convai 角色面部表情与心情的指南，从初始设置到脚本 API 和故障排查。

情绪驱动 Convai 角色的面部表情以及其持续时间更长的静息心情。它的部分输入随 Convai 的回复一起到来；其余部分则由你来配置和编写脚本。本节涵盖从首次可用的基础设置，到心情控制、分类体系编写，以及完整脚本 API 的所有内容。

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>情绪系统如何工作</strong><br>了解数据管线、其输入来源，以及表情如何传达到脸部。</td><td><a href="/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/emotion/how-the-emotion-system-works.md">情绪系统的工作原理</a></td></tr><tr><td><strong>情绪快速入门</strong><br>添加 Emotion Controller，运行设置，并查看你的角色如何对对话产生情绪反应。</td><td><a href="/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/emotion/quick-start.md">情绪快速入门</a></td></tr><tr><td><strong>心情</strong><br>通过代码设置和清除角色的静息心情，并了解心情与瞬时情绪有何不同。</td><td><a href="/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/emotion/moods.md">心情</a></td></tr><tr><td><strong>情绪配置文件</strong><br>在一个可移植资源中配置平滑、混合、微表情持续时间和心情。</td><td><a href="/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/emotion/emotion-profile.md">Emotion 配置文件</a></td></tr><tr><td><strong>情绪输出绑定</strong><br>了解组合后的情绪分数如何传递到角色的脸部和着色器属性。</td><td><a href="/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/emotion/output-bindings.md">Emotion 输出绑定</a></td></tr><tr><td><strong>情绪分类</strong><br>了解内置的 Plutchik 词汇表，以及如何编写自定义词汇表。</td><td><a href="/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/emotion/emotion-taxonomy.md">Emotion 分类体系</a></td></tr><tr><td><strong>情绪脚本 API</strong><br>通过代码读取实时情绪状态、控制心情，并响应情绪事件。</td><td><a href="/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/emotion/scripting-api.md">Emotion 脚本 API</a></td></tr><tr><td><strong>情绪编辑器窗口</strong><br>使用 Emotion 编辑器窗口的四个选项卡和 Emotion Timeline 录制器。</td><td><a href="/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/emotion/emotion-editor.md">情绪编辑器窗口</a></td></tr><tr><td><strong>情绪示例</strong><br>涵盖触发器、锁定表情以及由心情驱动的行为的完整场景。</td><td><a href="/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/emotion/usage-examples.md">情绪示例</a></td></tr><tr><td><strong>情绪故障排查</strong><br>针对表情无法移动以及其他常见问题的逐步修复方法。</td><td><a href="/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/emotion/troubleshooting-and-diagnostics.md">排查情绪问题</a></td></tr></tbody></table>

### 下一步

从 [情绪快速入门](/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/emotion/quick-start.md) 以便让表情在你的第一个角色上运行。然后阅读 [情绪系统如何工作](/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/emotion/how-the-emotion-system-works.md) 以了解数据管线及其输入来源，然后再进入心情控制和参考页面。


---

# 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-unity-sdk/embodiment/emotion.md?ask=<question>&goal=<user_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.