> For the complete documentation index, see [llms.txt](https://www.hoyoung.directory/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.hoyoung.directory/knowledge-base/training.md).
# Training
### Join Our Community for Expert Guidance
For an extensive collection of training guides, map recommendations, and community discussions, we encourage you to join our Discord server.
{% hint style="info" %}
Our Discord features a comprehensive list of training maps, efficiency breakdowns, and real-time advice from experienced players.
{% endhint %}
#### **Join Our Discord!**
Inside the server, you’ll find:
* **Training map recommendations** for all levels.
* **Optimal mobbing rotations** based on efficiency.
* **Community discussions and tips** for maximizing experience gain.
Join today and take your training to the next level!
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://www.hoyoung.directory/knowledge-base/training.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 `build a script that syncs our docs to a CMS` 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.