> 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/scene-metadata.md).

# 场景元数据

查找指南、参考页面和示例，了解如何让 Convai 角色感知 Unreal Engine 关卡中的对象。

场景元数据可让 Convai 角色感知关卡中的物体。为任意 `UConvaiObjectComponent` 添加到任意 `Actor` 上——例如门、箱子或终端——关卡中的每个角色都会知道该物体的存在、名称和用途。玩家询问周围环境时，角色会使用这些信息。

如需在运行时进行变更（添加物体、移除 Actor、设置对话对象以及控制注意力），请使用 `UConvaiChatbotComponent`上的环境 API。请参阅 [运行时管理环境](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/scene-metadata/managing-the-environment-at-runtime.md) 了解完整的方法参考。

当玩家看向已标记的物体时， [注视注意力](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/gaze-attention.md) 系统可自动将这些物体设为聊天机器人的当前关注对象。请先完成场景元数据设置，然后按照 [注视注意力快速入门](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/gaze-attention/gaze-attention-quick-start.md).

<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="https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/scene-metadata/how-scene-metadata-works.md">场景元数据的工作原理</a></td></tr><tr><td><strong>场景元数据快速入门</strong><br>使用 Convai Object Component 为场景中的 Actor 添加标记，并测试角色能否在对话中使用该物体的信息。</td><td><a href="https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/scene-metadata/scene-metadata-quick-start.md">场景元数据快速开始</a></td></tr><tr><td><strong>场景元数据组件参考</strong><br>Convai Object Component 的完整属性、函数和事件参考。</td><td><a href="https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/scene-metadata/scene-metadata-component-reference.md">场景元数据组件参考</a></td></tr><tr><td><strong>运行时管理环境</strong><br>在游戏过程中，在聊天机器人的环境中添加、移除和更新场景中的 Actor。</td><td><a href="https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/scene-metadata/managing-the-environment-at-runtime.md">运行时管理环境</a></td></tr><tr><td><strong>场景元数据使用示例</strong><br>医疗培训、工业安全演练、军事模拟和运行时环境更新的完整设置示例。</td><td><a href="https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/scene-metadata/scene-metadata-usage-examples.md">场景元数据使用示例</a></td></tr><tr><td><strong>排查场景元数据问题</strong><br>诊断并修复场景物体无法识别或跟踪属性无法更新等常见问题。</td><td><a href="https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/scene-metadata/troubleshoot-scene-metadata.md">排查场景元数据问题</a></td></tr></tbody></table>


---

# 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/scene-metadata.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.
