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