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

# Bossing

Bossing is a core part of progression, testing both **skill** and **damage output** across various encounters. Whether you're tackling solo challenges or coordinating party clears, **understanding boss mechanics, optimizing rotations, and refining your execution** are key to success.

This section will guide you through **best practices, strategies, and specific class rotations** to maximize your efficiency in boss fights.

### **What You’ll Find Here**

✅ **Bossing Fundamentals** – Key mechanics, useful buffs, and general bossing tips.\
✅ **Class-Specific Rotations** – Optimized skill usage for different boss fights.\
✅ **Advanced Strategies** – Techniques to push for higher clears and smoother runs.

***

Explore the subpages for more in-depth information on specific bosses and strategies!


---

# 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://www.hoyoung.directory/knowledge-base/bossing.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.
