> 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/introduction/faq.md).
# FAQ
Is HY Storyline Mandatory? 
## Yes.
#### 💡 Lv. 10 - **The Missing Trainee 3**
* Nimbus Cloud (Flying)
**Note:** Lock Nimbus Cloud to continue using up jump!
#### 💡 Lv. 200 - **Sealing the Fiends: The Final Act 2**
* Exclusive Spell (Echo)
* Fiend Seal (ATT +10%, Final Damage +10%)
Is HY a Combo Class? 
### No. We don't Combo.
Different skills have different uses so play around with them to adapt to the situation
Does HY need Cooldown Reduction/Reset?
### We don't need CDR Hat or CD reset IA
We cut off 1-2sec of our AoE skills with CD hat but it wont change anything, cooldown skipping IA is unreliable and we have natural resets from our V skill.
*However* CDR Hat can be used for training if Consuming Flames is required in every rotation.
The loss of main stat to all our burst skills to increase the damage to Cudgel  is not worth it.
Attack Speed Modifiers?
In addition to our  Booster, Hoyoung only requires both
**1.**  **Decent Speed Infusion** AND
**2.**  **Green Pot** to hit AS0
### We do not need AS+1 IA
### KMS vs GMS
GMS gains 6-7% FD from AS0 on a dummy compared to KMS\
Will be less in practice due to movement in boss fights
---
# 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/introduction/faq.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.