> For the complete documentation index, see [llms.txt](https://blade-re-action.gitbook.io/blade-re-action/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blade-re-action.gitbook.io/blade-re-action/about-the-game/content-guide/battle-effect.md).

# Battle effect

The battles in Blade: Re.Action require 2 to 4 heroes.

Each hero is one of balance / speed / power / technique type as well as the enemies.

The four types can have an advantage or a disadvantage against each other, so having diverse heroes to fight with is key to success.

| Type                | Type Effect                                                   |
| ------------------- | ------------------------------------------------------------- |
| Balance (Gladiator) | Increase damage against and reduce damage from speed type     |
| Speed (Assassin)    | Increase damage against and reduce damage from technique type |
| Power (Fighter)     | Increase damage against and reduce damage from balance type   |
| Technique (Wizard)  | Increase damage against and reduce damage from power type     |
| No type             | No additional effect to or from any type                      |


---

# 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://blade-re-action.gitbook.io/blade-re-action/about-the-game/content-guide/battle-effect.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.