> For the complete documentation index, see [llms.txt](https://rules.gatcg.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rules.gatcg.com/game-mechanics/game-mechanics-turn-order/turn-order-combat-phase/combat-phase-retaliation-step.md).

# Combat Phase - Retaliation Step

#### General Rules:

1. First, if any abilities or effects were placed onto the Effects Stack during or after attack declarations, players will receive Opportunity in turn order to respond to these effects. After the Effects Stack is empty, the game will proceed to step 2. 
2. Second, turn player receives opportunity. This point at which players are granted Opportunity during this phase is considered “before retaliation” and is the only time players may act before the game progresses until the damage step is entered.
3. Third, if there are any awake defending units, for each of those units, its controlling player may choose to rest that unit to retaliate against the attacking unit.
   1. If they do so, the unit being retaliated becomes the target of retaliation of the retaliating unit and the retaliating unit will deal damage according to its power stat to its retaliation target during the Damage Step.
   2. Units without a power stat or that have a power stat of 0 or less cannot retaliate. Weapons can’t be used to retaliate or during retaliation.
4. Then, after the Effects Stack is empty, and each player has passed on Opportunity in succession, the game immediately proceeds to the Damage Step of combat.


---

# 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://rules.gatcg.com/game-mechanics/game-mechanics-turn-order/turn-order-combat-phase/combat-phase-retaliation-step.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.