> For the complete documentation index, see [llms.txt](https://spacey.gitbook.io/getting-started/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spacey.gitbook.io/getting-started/game-walkthrough/towers-and-stats.md).

# Towers & stats

This is the tower interface which shows all of the tower stats.&#x20;

The name, description, rarety, item id, and item status, item levels are all shown here

![](/files/C9i7eTMxj9psy65JB6oN)

the icons in the attributes box are&#x20;

&#x20;![](/files/GrJM2XzeySep4nhg6tOu)

Attack: indicates the damage the tower deals for each attack.

Fire rate: how fast the tower shoots.

Projectile speed: how fast the bullet travels.

Rotate speed: how fast the tower turns towards the enemy.

Range: the distance at which the tower can attack.

Loading cost: how many loading points it takes to load this tower on the spaceship.

Crit chance: the chance that this tower will deal critical damage.

Crit Damage: multiplier for the damage if it is a critical hit.


---

# 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://spacey.gitbook.io/getting-started/game-walkthrough/towers-and-stats.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.
