> For the complete documentation index, see [llms.txt](https://cryptsofhorus.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cryptsofhorus.gitbook.io/whitepaper/the-game/game-mechanics/missions.md).
# Missions
The game is divided into seven distinct city maps, each featuring seven unique regions that activate different gameplay modes. Players will embark on A to B missions to travel between cities, navigating through 54 unique game zones. Each zone offers multi-discipline missions, enhancing variety and engagement.
Furthermore, the game will expand to include additional missions in other areas of each map, such as desert regions and even interplanetary expeditions. Each city map will contain several missions, with the difficulty level varying from one map to another.
The eight basic game modes will be:
1. Getting from A to B. Linear corridor with obstructions and avoiding enemies and predators (Felucca trip down the River Hapi avoiding enemy fire, Hippos, Crocodiles etc).
2. Clear the area of enemies. Evacuate crypts already compromised.
3. Kill the specific enemy - NPC or player.
4. Defend the entrance to crypts from enemies. Horde mode. This will be the main game mode - above ground, below ground, underwater etc.
5. Defend the crypts directly from inside - confined space attacks.
6. Retrieve the gold - this is basically a ‘capture the flag’ kind of mission. This may or may not require combat to complete.
7. Interact with the environment. Light puzzles, decipher hieroglyphics to unlock hidden passages and crypts, detective mode / Witcher vision, flip the switches etc. Can also include time-based missions.
8. Domination mode when working in teams.
These missions will be completed in - PvP, Team, and NPC.
---
# 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://cryptsofhorus.gitbook.io/whitepaper/the-game/game-mechanics/missions.md?ask=&goal=
```
`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.