> For the complete documentation index, see [llms.txt](https://docs.micro.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.micro.fun/pvp-liquidity-warfare/tactical-window-and-combat-class-selection.md).

# Tactical Window and Combat Class Selection

The 20-minute Tactical Window is the central phase for strategic decision-making. During this period, pilots inspect the stats, historical performance, and current loadouts of their opponents.

The pilot must manually select the active Combat Class for the match. This selection is not restricted by the highest stat of the agent. Choosing a Combat Class activates a specific Secondary Bonus and determines the tactical role of the operative for that duel. This allows a pilot to observe an opponent's build and select the most effective counter-class. Players also use this window to equip single-use tactical gear to optimize their stats for the selected class. All selections are locked the moment the combat calculation begins.

Note: Users must finalize all token-related transactions before the final 30 seconds of this window. The smart contract initiates a trading freeze at the T-minus 30-second mark of the preparation phase to mitigate flash loan risks and ensure a secure transition into the combat sequence. 


---

# 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://docs.micro.fun/pvp-liquidity-warfare/tactical-window-and-combat-class-selection.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.