> For the complete documentation index, see [llms.txt](https://dronewars.gitbook.io/litepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dronewars.gitbook.io/litepaper/core-mechanics/uap-ranks.md). # UAP Ranks Both attacking and defending UAP's earn battle experience, or a rank. Ranks are split into two different categories and have 10 levels:\ \ 1\. **Offense** * Striker * Blazer * Raider * Enforcer * Warblade * Stormbringer * Marshal * Slayer * Reaver * Conqueror \ 2\. **Defense** * Sentry * Guard * Bulwark * Warden * Shieldmaster * Protector * Commander * Sentinel * Guardian * Overlord UAP's ranked higher in Offense will perform better in attacks, giving the player an additional attack boost multiplier, while UAP's which rank high in Defense are better suited to be protect conquered territories. \ \ If a player does not want to rank up their UAP's themselves, they can simply buy already ranked up UAP's by other players in the [marketplace](/litepaper/game-economy/marketplace.md). \ \ Alternatively, for certain ranks players will be able to use $UAP to level up quicker. \ \ \ \ --- # 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://dronewars.gitbook.io/litepaper/core-mechanics/uap-ranks.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.