> For the complete documentation index, see [llms.txt](https://golden-crypto.gitbook.io/mushro-legends/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://golden-crypto.gitbook.io/mushro-legends/chronicles/mushroes.md).
# Mushroes
Unveil a diverse ensemble of 25 Mushroes, each uniquely endowed with newfound magical prowess. Embark on a profound odyssey as these extraordinary beings take up arms to safeguard their realms and counter the relentless advance of The Rot.
In Mushro Legends, each Mushro embodies a distinctive set of skills and attributes, offering players an array of strategic possibilities. As guardians of their kingdoms, Mushroes strive to reclaim the land from The Rot's blight, employing their magical abilities to cleanse and restore Porcinia to its former splendor.
Dive into the evolving narrative of Mushro Legends, where the roster of Mushroes continues to expand, promising an ever-growing roster of captivating characters. Stay tuned as we introduce new Mushroes to enrich the gameplay experience and offer you endless avenues for exploration and adventure.
Unique Mushroes
You can check the detail of each hero one by one.
---
# 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://golden-crypto.gitbook.io/mushro-legends/chronicles/mushroes.md?ask=&goal=
```
`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.