> For the complete documentation index, see [llms.txt](https://atomrigslab.gitbook.io/fortress-arena/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atomrigslab.gitbook.io/fortress-arena/game-play/playable-tanks/windblow.md). # Windblow ![](/files/p7p4zJC4QeLjyYuWCztL) {% embed url="" %} **Windblow** is a tank with Tornado and Wind Shuriken as weapons. Each weapon has an effect that either pulls or repels enemies.It has the characteristic of increasing the attack power according to the strength of the wind through the Passive Propeller reinforcement. \ \ **Basic weapon - Tornado (skill 1)** \ Fires a tornado that pulls enemies at the point of impact. \ \ **Special weapon - Wind Shuriken (Skill 2)** \ Fires a shuriken made of wind that knocks enemies back a certain distance. \ \ **Passive - Propeller Reinforcement** \ Wind Blow's attack power increases with the strength of the wind. --- # 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://atomrigslab.gitbook.io/fortress-arena/game-play/playable-tanks/windblow.md?ask=&goal= ``` `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.