> For the complete documentation index, see [llms.txt](https://whitepaper.dragonary.com/dragonary-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.dragonary.com/dragonary-whitepaper/english-whitepaper/gameplay/pve-battle/daily-missions.md).

# Ember Missions

The daily missions consist of 3 or more battles that seek to grant unique rewards per day so that the player can create more dragons or improve in-game items.

**Do you want to breed dragons?** These missions are for you! You will get the needed items for breeding your dragons or fusing them to obtain a dragon of higher rarity.

There are 7 types of Ember Missions, one for each element, at the same time, each element will have different difficulties, increasing the reward amount as they get harder and harder.

Ember missions consume 10 energy points for each attempt. If you lose, win, or manually exit the mission, energy will be consumed.

### DAILY MISSIONS REWARDS

* Obsidian (Object used by goblins for mining CYT)
* Sparks (Used to craft ember)


---

# 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://whitepaper.dragonary.com/dragonary-whitepaper/english-whitepaper/gameplay/pve-battle/daily-missions.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.