> 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/unreal-engine/guides-v2-under-development/getting-started/simple-talking-cube.md).
# 简单对话立方体
一个从零开始的最小示例，帮助你熟悉插件的主要组件。
1. 创建一个新的第一人称项目。
2. 启用 Convai 插件，并将 API 密钥添加为 [此处所述](/api-docs/zh/cha-jian-yu-ji-cheng/unreal-engine/guides-v2-under-development/getting-started/download-and-setup.md#set-up-your-project).
3. 创建一个新的 Actor 蓝图，我们将其用作 AI 角色。\
\
4. 打开创建的蓝图，然后在组件列表中搜索并添加 `Convai 聊天机器人` 组件。\
\
注意：如果你没有找到该组件，请确保你已按照 [安装指南](/api-docs/zh/cha-jian-yu-ji-cheng/unreal-engine/guides-v2-under-development/getting-started/download-and-setup.md#installing-the-plugin).
5. 选择已创建的组件，在详情面板中找到 Character ID 字段，并粘贴你的角色 ID；你可以通过创建一个新角色，或在 [Convai Playground](broken://pages/35a85ab8078743525dfb21372f6c08398990e426).
11. 点击运行，靠近 AI 角色并按住 T 通过麦克风说话，然后在松开 T 键后角色应会作出回应。
{% hint style="info" %}
如果角色没有回应，请确保在操作系统设置中已将麦克风正确设置为默认麦克风。
{% endhint %}
## 发送文本而非语音
使用以下 `发送文本` 节点来代替，如果你想通过文本而不是语音与角色聊天。
注意，这里我们使用硬编码字符串作为输入传给角色，你需要创建所需的 UI，以从用户那里获取文本输入并将其发送给 AI 角色。
---
# 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/unreal-engine/guides-v2-under-development/getting-started/simple-talking-cube.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.
