> 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/scouting.md).

# Scouting

Look before you strike — the Scout Tower and scout reports.

A **scout** flies to a castle or an asteroid held by an army and reports what it saw. Scouting is the way to know what you are going to fight.

## The Scout Tower

The **Scout Tower** opens at Castle level 5. With it:

* you can **look into another castle**;
* you **learn of a raid in advance** — an alarm shows the size of the army coming at you. Without the tower you know that an army is coming, but not how big it is.

## The scout report

The report comes in mail and shows the **defenders**, the **coordinates** and what can be taken.

* Without a scout report, the defenders of a castle stay **hidden** and there is **no battle forecast** — a blind siege is allowed, but you go in without knowing.
* With a report, the siege window **forecasts the battle** against the defenders the scout saw.

## Rules

* You cannot scout a castle under the **newbie shield**.
* Scouting another player is an act of aggression: it ends **your own** newbie shield and starts **War Frenzy**. See [Newbie Shield and War Frenzy](https://electrum-decisions.gitbook.io/electrum-decisions-docs/getting-started/newbie-shield-and-war-frenzy.md).
* Nothing beyond the Veil can be scouted.
* The target gets an **alarm** that a scout is on its way.


---

# 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/scouting.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.
