> For the complete documentation index, see [llms.txt](https://efas.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://efas.gitbook.io/whitepaper/the-journey/conquering.md).

# Conquest Battles

![](/files/-MkZGpUQNNwHpydvnbI3)

Do you see that beautiful planet with its rich mineral deposits and prosperous cities? Do you see that space station with its amazing construction and plentiful habitation modules? Do you want them?

Conquer them, and they will belong to you. The largest sci-fi planetary surface battles ever created, with a thousand combat units participating simultaneously are awaiting you.

Unlike fleet encounter battles, the surface conquest battles are asymmetrical. You will face powerful fortifications, a steady stream of enemy reinforcements, and extremely potent enemy commanders.

The more developed a city is, the more challenging it is to conquer. Check a city's military and economic development levels before declaring war. Don't engage unless you have an equally powerful armada.

The rewards of victory are bountiful. When you see your faction emblem flying above the conquered city, and the taxes rolling in, you will feel that it was well worth the effort.


---

# 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://efas.gitbook.io/whitepaper/the-journey/conquering.md?ask=<question>&goal=<endgoal>
```

`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.