> 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/basics/hexa-matrix/hexa-stat.md).
# HEXA Stat
##  HEXA Stat I
{% hint style="success" %}
Available starting at **Lv. 260**
{% endhint %}
**Heroic (Reboot):** Unlock **after you upgrade**  **Rampage 5** \
**Interactive (Reg):** Unlock **after you upgrade**  **Rampage 4**
### **Initially**
1. MAIN STAT to ATT
2. ADDITIONAL STATS to Crit Damage and LUK
3. Keep Enhancing until MAIN STAT gets to level 3 (cost increase from 10 to 20)
4. Decide if you want to max it out now, or come back to it after upgrading other HEXA Skills
{% hint style="info" %}
Max now: Small damage increase to all skills\
Come back: Focus on specific skills (e.g. burst for boss prog)
{% endhint %}
### Optimal (when maxed)
Prioritise highest levels/stat for ATT > LUK > Crit Damage
{% hint style="info" %}
ATT is affected by % lines, LUK is a flat bonus (final stat)
{% endhint %}
##  HEXA Stat II
{% hint style="warning" %}
Available starting at **Lv. 265**
{% endhint %}
**Heroic & Interactive:** Unlock **after**  **Universal Harmony** (Mastery I) **reaches Lv. 18**\
Use [MapleScouter](https://maplescouter.com/optimizer) to check what is best for you personally.
##  HEXA Stat III
{% hint style="warning" %}
Available starting at **Lv. 270**
{% endhint %}
**Heroic:** Unlock **after you upgrade**  **Apotheosis 5** \
**Interactive:** Unlock **after you upgrade**  **Tiger 1**\
Use [MapleScouter](https://maplescouter.com/optimizer) to check what is best for you personally.
---
# 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/basics/hexa-matrix/hexa-stat.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.