> For the complete documentation index, see [llms.txt](https://book.rochat.ai/rochat_book_zh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.rochat.ai/rochat_book_zh/ru-he-zai-rochat-shang-chuang-jian-jue-se/jue-se-she-ji-fang-fa-yi-shou-dong-jian-li/jue-se-ti-shi/ru-he-dui-jue-se-de-hui-fu-jin-xing-yin-cang.md).

# 如何對角色的回復進行隱藏？

在 Rochat 平台中，狀態欄是一個重要的功能，用於顯示角色的當前狀態、情緒、位置等關鍵信息。為了優化對話體驗和提升沈浸感，我們對角色回覆的消息增加了文字隱藏的功能，**允許作者控制何時顯示或隱藏這些信息。而通過使用 <> 標簽**，用戶可以靈活地管理角色的狀態欄，達到更加個性化和動態的效果。

* 针对角色的作者，可以通过长按消息框，**查看原始消息**，查看完整的角色输出文字。这个可以帮助作者进行作品的调试。
* 你可以结合**角色提示**功能，让角色更稳定的输出带有 <> 标签和 \`\`\` \`\`\` 标签的内容，从而带来更有趣的互动。
* <> 标签中的文字对于模型本身仍然可见，这意味着它仍然会影响整个对话。

## **如何讓角色的回覆隐藏部分內容？**

舉一個簡單的例子，我們想讓角色在每一次回覆的開頭，都對之前的對話進行一次簡短的總結。這樣能夠幫助我們提升對話的記憶能力。但是我們又不想每次看到這樣的總結，影響互動體驗。

我們可以在**角色提示**中這麼設計我們的 Prompt:

```
[在每一輪的回覆開頭使用下面的模板]

<這是歷史對話的總結/>

- 以 < 開頭，/> 結尾
- 始終在標籤中對歷史對話進行簡短的總結，不超過 50 個字。
```

使用上述的設定，角色將會在每一輪回覆的開頭先輸出對話的總結 (對於玩家不可見)，接下來才會繼續角色扮演。


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://book.rochat.ai/rochat_book_zh/ru-he-zai-rochat-shang-chuang-jian-jue-se/jue-se-she-ji-fang-fa-yi-shou-dong-jian-li/jue-se-ti-shi/ru-he-dui-jue-se-de-hui-fu-jin-xing-yin-cang.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.