> For the complete documentation index, see [llms.txt](https://tera-arise.gitbook.io/tera-arise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tera-arise.gitbook.io/tera-arise/game-systems/combat-mechanics.md).

# Combat Mechanics

Some core combat mechanics have been altered in TERA Arise.

Determination of whether a player is attacking from the front, side, or back has been made slightly more lenient. In particular, the front and back of an entity are now 120° arcs, while sides are 60°. Additionally, only a player's position is considered for these calculations, where previously direction was factored in.

Another change is the introduction of the break mechanic. Bosses have a break gauge which is filled by using CC (knockdown, stun, and stagger) skills, and which decays over time. When full, the boss is stunned for 5 seconds and takes increased damage, during which the gauge empties back to zero. Ordinary CC skills only deal small amounts of break damage, but break-oriented [class aspects](/tera-arise/game-systems/classes-and-roles.md) have ways to deal massive break damage.


---

# 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://tera-arise.gitbook.io/tera-arise/game-systems/combat-mechanics.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.