> For the complete documentation index, see [llms.txt](https://docs.hoodloot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hoodloot.com/game-mechanics/legend-ranks.md). # Legend Ranks {% hint style="info" %} **Legend Ranks are coming soon.** The full system — the ranks, their costs, and their multipliers — is revealed at launch. Here's the idea. {% endhint %} Legend Ranks are HOODLOOT's endgame — a **prestige** system for players who've climbed as far as a single run allows. The premise: **ascend** a Legend rank to give up your current progression in exchange for a **permanent Loot Rate multiplier** that applies to everything you loot from then on — this run and every run after it. It's the deepest strategic lever in the game. Ascend too early and you throw away a strong position; ascend too late and you sat on a smaller multiplier for too long. Timing it will be the real endgame. Full ranks, costs, and multipliers drop when Legend Ranks go live. *** ## See Also * [Gameplay Loop](/getting-started/gameplay-loop.md) — where ascension will sit in the overall loop * [Virtual Mining](/game-mechanics/virtual-mining.md) — the reward formula the multiplier scales * [$SHARE Token](/game-assets-and-token/share-token.md) — where the burn goes --- # 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.hoodloot.com/game-mechanics/legend-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.