> 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/gameplay/batalla-pve/modo-historia.md).

# Modo Historia

Dragonary tiene un lore (historia alrededor del juego) que irás descubriendo a través de misiones "en Modo historia". Estas misiones son clave en el desarrollo del juego ya que te permitirán introducirte poco a poco en las mecánicas de Dragonary. 

Con el modo historia iremos recorriendo y entendiendo que sucede en Dragonary y podremos defender el mundo de los dragones del poderoso **Darkwing "el corrupto"**, que busca destruir lo poco que queda de Dragonarya. 

En este camino de aventuras nos enfrentaremos a distintos jefes, súbditos de Darkwing. Cada misión tendrá, como mínimo, 3 batallas, en las que deberás esforzarte al máximo para sobrevivir con tus dragones. 

**¡EL DESTINO DE DRAGONARYA ESTÁ EN TUS MANOS!**

### **Recompensas en Modo Historia**

* Experiencia
* Artículos de experiencia (no implementados aún)
* Boost de experiencia (no implementados aún)
* Equipamiento de dragones (solo en raras ocasiones, no implementado aún)
* Huevos de dragones comunes (sólo en raras ocasiones, no implementado aún)


---

# 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/gameplay/batalla-pve/modo-historia.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.