> For the complete documentation index, see [llms.txt](https://knight-dead.gitbook.io/dead-knight-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knight-dead.gitbook.io/dead-knight-whitepaper/overview/gaming-features/pve/explorer.md).

# Explorer

![](/files/bh7SkrSvjNDKZ3kO11RV)

Players need to have a Dead Knight to explore the world of Undead Realm, the number of exploring quests everyday will be limited; Each quest will have a random lot that players will get a small amount of DK token and experience point.

{% hint style="success" %}
**Further description:** Explorer mode is the same as auto farming idle battle mode in other idle games. The players select their NFTs, enter the map and farm the mobs at their current levels. The more powerful NFT + the higher level of character + NFT items will help players move to the higher-levelled map.
{% 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://knight-dead.gitbook.io/dead-knight-whitepaper/overview/gaming-features/pve/explorer.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.