> For the complete documentation index, see [llms.txt](https://whitepaper.somo.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.somo.xyz/the-game/battle-squad/squad-formation.md).

# Squad Formation

While players need to decide the roster of their SOMO squad for the battles, they can also choose different formation for the squad to achieve different tactic intentions. Different formations of the same rosters between the two opponents in a battle can lead to completely different result.

* SOMOs can be placed in different spots in multiple rows.
* The relevant distances and angles between your SOMO and opponent's SOMO affects the options as well as the efficiency of possible actions.
  * Targeting validation for attacks and abilities
  * Priorities for targets
  * Damage taking based on distances, area of effects and blocking of line-of-sight


---

# 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://whitepaper.somo.xyz/the-game/battle-squad/squad-formation.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.