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

# Troops

Shard Wardens, Harpooners, Spark Archers, gatherers — and the Infirmary.

Your army is hired in three barracks. Each kind of troop beats one kind and loses to another — a circle with no single best choice.

| Troop             | Barracks              | Fights as                                          | Strong against | Weak against  |
| ----------------- | --------------------- | -------------------------------------------------- | -------------- | ------------- |
| **Shard Wardens** | Shard Warden Barracks | Infantry, a wall of shields — the base of any army | Spark Archers  | Harpooners    |
| **Harpooners**    | Harpooner Barracks    | Long harpoons that keep the enemy at a distance    | Shard Wardens  | Spark Archers |
| **Spark Archers** | Spark Archer Barracks | Arrows with an amber spark that strike from afar   | Harpooners     | Shard Wardens |

**Gatherers** are not fighters. They mine resources on asteroids and work all the time while they stay there. They are hired one by one in any barracks.

{% hint style="success" %}
The first squad from each barracks is a gift — a castle quest pays it when the barracks is built.
{% endhint %}

## Hiring

* Choose the troop and the amount in the barracks. The troops come out in turn; the whole order has one price and one time.
* While the hire queue is busy, a new order waits — or use a speed-up.
* **Tiers.** Every troop has **tiers I to V**. Tier I is open from the start; the **University** opens tiers II–V at its levels 5, 10, 15 and 20.

## Troop tiers

| Tier    | Opens at       | What changes                                         |
| ------- | -------------- | ---------------------------------------------------- |
| **I**   | from the start | Cheap and fast to hire — the mass of your first army |
| **II**  | University 5   | Much stronger than tier I, still quick to hire       |
| **III** | University 10  | A real step up; starts to need crystal               |
| **IV**  | University 15  | Strong and dear                                      |
| **V**   | University 20  | The strongest — and the most expensive goal          |

Higher tiers hit harder, take more damage and **carry more loot**, but cost more, take longer to hire and **march slower** — tier V is the slowest. Research the military sciences of the same tier to make them stronger still.

## The Dock

All your troops and gatherers stand at the **Dock**. Click it to see the whole army: how many fighters and gatherers you have and where they are now. Armies leave from the Dock on marches.

## The wounded and the Infirmary

After a battle your fallen soldiers go to the **Infirmary** — as long as it has free beds.

* **Beyond the beds, the fallen die.** Without an Infirmary, every soldier who falls dies.
* Healing costs a part of the hire price and time — much less than hiring new troops.
* Every level of the Infirmary adds beds and speeds up healing.
* Heal quickly to keep the beds free for the next battle.

{% hint style="warning" %}
When you attack a castle, most of your fallen go to the Infirmary and the rest die. Defenders' fallen go to their own Infirmary.
{% 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://electrum-decisions.gitbook.io/electrum-decisions-docs/army-and-map/troops.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.
