> 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/dragon-cannon.md). # Dragon Cannon ![](/files/mgIsSJCua1q7uYfOcQpn) {% embed url="" %} **Dragon Cannon** is a tank that uses Cooling Shell and Dragon Ball Shell as weapons that freeze enemies and impede movement.It has the characteristic of increasing attack power when an ally tank is destroyed through the passive Dragon's Wrath.\ \ **Basic weapon -Cooling Shell(skill 1)** \ Fires a Cooling Shell that freezes enemies hit.\ \ **Special weapon - Dragon Ball Shell(Skill 2)** \ Fires Dragon Ball Shell containing fire energy that deals fire and fuel damage to enemies hit.\ \ **Passive - Dragon Wrath** \ Dragon Cannon's attack power increases for a certain period of time when an ally dies. --- # 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/dragon-cannon.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.