> 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/mission-rewards-and-player-progression/summary.md). # Summary Designed for Balanced, Meaningful Progression The mission rewards system in Warped Universe has been designed to provide a sustainable, fair, and rewarding progression experience. By carefully balancing item rarity, resource usage, and upgrade opportunities, we ensure that every reward feels meaningful and progression remains driven by player effort and strategic decision-making. As development progresses, these mechanics will be continuously monitored, refined, and adjusted to ensure a balanced and enjoyable experience for all players. Our goal is to build a progression system that evolves with player feedback and stands the test of time. --- # 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/mission-rewards-and-player-progression/summary.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.