> For the complete documentation index, see [llms.txt](https://wp.warped.games/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.warped.games/ownership-in-warped-universe/achievements-and-earning-items.md). # Achievements and Earning Items Greatness Must be Earned No item in the in-game store provides a gameplay advantage. Weapons, skills, and ships are unlocked through play, not purchases, whether in real-time or turn-based modes. Select cosmetics follow the same principle. Certain items can only be unlocked by completing specific challenges or milestones and are never available for purchase. These achievement-driven cosmetics are badges of effort, scarce by design and meaningful to earn. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://wp.warped.games/ownership-in-warped-universe/achievements-and-earning-items.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.