> For the complete documentation index, see [llms.txt](https://docs.hzz.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hzz.im/g/dayz/ring-1.md).

# Ring-1 教程

- [Ring-1 使用教程](https://docs.hzz.im/g/dayz/ring-1/use.md)
- [Ring-1设置透视物品为中文](https://docs.hzz.im/g/dayz/ring-1/esp.md)
- [Ring-1更新公告](https://docs.hzz.im/g/dayz/ring-1/update.md): 其他更新公告请移步售后群内公告查看，这里只是发送部分更新日志公告
- [Ring-1功能展示与中文注解](https://docs.hzz.im/g/dayz/ring-1/show.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.hzz.im/g/dayz/ring-1.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.