> For the complete documentation index, see [llms.txt](https://loot-heroes.gitbook.io/loot-heroes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://loot-heroes.gitbook.io/loot-heroes/looterra/dungeons.md).

# Dungeons

Players will venture into the daily dungeons of Looterra facing off against computer AI opponents in Quadra. You will select your hand of 7 Hero Cards. If you do not own any Hero NFTs you will be able to select from the default cards provided, which will be limited strength and have no Gear NFTs equipped.\
\
In order to clear a dungeon you will have defeat multiple opponents. The elemental alignment of the dungeons rotates daily providing opportunities for players to tune their lineups for specific challenges. 

![Dungeons of Looterra](/files/705H1JiIy9M2SV5OwqYU)

### Dungeon Schedule

Monday -> Wind \
Tuesday -> Fire\
Wednesday -> Ice\
Thursday -> Water\
Friday -> Earth\
Saturday -> Lightning\
Sunday -> Light & Dark

{% hint style="warning" %}
Ability to earn LOOT coming soon: <https://lootheroes.io/dungeons>
{% endhint %}


---

# 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://loot-heroes.gitbook.io/loot-heroes/looterra/dungeons.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.