> 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/getting-started/your-first-hour.md).

# Your First Hour

The first steps Vedar shows you, and the Keeper's Path that leads on.

*"I am Vedar Highnoon, mentor of the Circle of War. This castle is yours now, and the hero is your hand in battle. Let me show you where to start: it takes a couple of minutes."*

## Vedar's three first steps

{% stepper %}
{% step %}

### Raise the castle to level 3

The first builds are fast — under a minute each. Open the castle (key **H**), choose the Castle and press **Upgrade**.
{% endstep %}

{% step %}

### Open the hero and spend the free points

There is no battle without it. Press **C**, put your free points into characteristics, see what changes and press **Save**. Then spend your combat skill points the same way.
{% endstep %}

{% step %}

### Press "To battle" and defeat the Dummy

On the map, press **To battle**, then **Train with the Dummy**. The Dummy is a fighter of your level that strikes fair and takes no offence. Beating it is how a young hero gains levels.
{% endstep %}
{% endstepper %}

## The Keeper's Path

After Vedar's steps the **Keeper's Path** takes over. Its current goal is always at the top of the screen. **Click it** — the game takes you exactly where the goal is done. Every step pays **Seals** and **speed-ups**.

The Path walks you through everything the game has:

* raising the Castle and building the first barracks — the first squad is a gift;
* choosing your subclass at level 5;
* clearing the **Amber Grotto**, your first dungeon;
* fighting a 5 on 5 battle in the Circle of War;
* sending gatherers to an asteroid and defeating a monster on the map;
* buying an item in Tala's shop;
* joining a legion or founding your own.

When the Path is done, **daily tasks** and **achievements** lead on. See [Goals and Rewards](https://electrum-decisions.gitbook.io/electrum-decisions-docs/reference/goals-and-rewards.md).

## Useful keys

| Key             | What it does                              |
| --------------- | ----------------------------------------- |
| **H**           | Into your castle and back to the map      |
| **C**           | Hero page: characteristics, gear, skills  |
| **I**           | Shared inventory: Seals, speed-ups, items |
| **R**           | Fly the camera to your castle             |
| **M**           | The big map                               |
| **F3** or **/** | Search for players and places             |
| **Space**       | Confirm the main action in many windows   |

{% hint style="success" %}
**You are protected while you grow.** A new Keeper's castle has a newbie shield. See [Newbie Shield and War Frenzy](https://electrum-decisions.gitbook.io/electrum-decisions-docs/getting-started/newbie-shield-and-war-frenzy.md).
{% 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/getting-started/your-first-hour.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.
