> For the complete documentation index, see [llms.txt](https://electrum-decisions.gitbook.io/electrum-decisions-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://electrum-decisions.gitbook.io/electrum-decisions-docs/army-and-map/the-map.md).

# The Map

The sphere, the Veil, coordinates, marches and the castle teleport.

The world map shows the whole **sphere of shards**: your castle and the castles of others, asteroids, monsters and the houses of the Keepers over the Core.

## Up and down the sphere

The minimap shows the sphere from the side: **the Core at the bottom, the pole at the top**. The deeper you go towards the Core, **the richer the asteroids and the more dangerous the monsters**.

## The Veil

The **Veil** splits the sphere into the northern half (Aurelion) and the southern half (Umbrael).

* **No army marches through the Veil.**
* What is behind the Veil cannot be reached, attacked or scouted from your side.
* An army coming from beyond the Veil is not shown on your map until it is through.

## Coordinates and search

* Every place has **coordinates**. Reports of scouting and sieges show them, so you can find the place again.
* **Search** (**F3** or **/**): find a player and their castle, an asteroid or a monster. **Show** flies the camera there and opens the card.
* **Bookmarks** (**B**) keep places you want to return to.

## What you see on the map

| Mark                         | Meaning                                                  |
| ---------------------------- | -------------------------------------------------------- |
| Asteroid with a number       | An asteroid; the number is its level                     |
| Monster with a number        | A monster; the number is its level                       |
| Blue / red castles           | Aurelion / Umbrael castles                               |
| A castle with a shield       | A newbie-shielded castle — cannot be attacked or scouted |
| A line                       | A march: for resources, or an attack                     |
| Green / yellow / red monster | Within reach / risky / too strong for your army          |

## Marches

A **march** is a squad on its way: gatherers going to an asteroid, an army going to a monster, an asteroid or a castle, or a scout. Marches are drawn as lines on the map and listed on the left under the hero panel. You can **recall** a march home.

## The castle teleport

A **teleport** moves your castle to an asteroid: open the asteroid's window and press **Teleport**.

* You get a teleport, for example, from the **Castle level 10** milestone.
* You **cannot teleport during War Frenzy** — see [Newbie Shield and War Frenzy](https://electrum-decisions.gitbook.io/electrum-decisions-docs/getting-started/newbie-shield-and-war-frenzy.md).


---

# 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://electrum-decisions.gitbook.io/electrum-decisions-docs/army-and-map/the-map.md?ask=<question>&goal=<user_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.
