> For the complete documentation index, see [llms.txt](https://planetary-defense-guide.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://planetary-defense-guide.gitbook.io/guide/web-game/missions-overview.md).
# Missions Overview
## Key details about Missions
* **Function:** Thanks to the Division, they act as your extraction source for rewards in TLM, DEF, and various NFTs.
* **Management:** Players can determine the best strategy for selecting the missions to which they deploy their Divisions. Once a mission is complete, they can either "Claim" the rewards or choose the "Claim & Redeploy" option.
The mission panel looks like this:
* At the top, we have the list of our active missions.
* At the bottom, we have the list of available missions for each selected planet.
Each mission has **entry requirements**, **base cooldown**, **entry cost**, **rewards** and the **duration of the mission** itself.
{% hint style="info" %}
As the project is linked to **Alien Worlds**—with likely NFT integrations in the near future—the missions are based on the six planets available in Alien Worlds.
{% endhint %}
Each planet hosts various missions offering rewards in DEF, TLM, or NFTs—such as Quantum Chests. All missions have an available duration; once that time expires, the **mission is no longer available**, and new ones become available.
{% hint style="info" %}
Note: The information on this page reflects the current state of Planetary Defense's development. As new features are actually released and the game evolves, some details here may change, and this page will be updated to stay accurate.
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://planetary-defense-guide.gitbook.io/guide/web-game/missions-overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
.png)
.png)