> 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/gameplay/player-vs-environment.md). # Player-vs-Environment Collaborative Gameplay In single-player or co-op, players will face the Void, a formidable force that will serve as the primary antagonist in Season Zero. These opposing forces, with traits similar to those of the players, will vary in strength, numbers, and equipment, ensuring dynamic and engaging challenges that change with each mission. To accommodate different playstyles, missions will offer varying levels of difficulty, presenting challenges for both newcomers and experienced players. With each mission uniquely shaped by the evolving state of the Warped Universe, no two experiences will feel the same, keeping gameplay fresh, rewarding, and immersive. To succeed, players will have to strategically harness the forces of light and gravity, balancing both long-term plans and immediate tactics. These choices shape the Warped Universe and form the core repeatable gameplay loop. --- # 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/gameplay/player-vs-environment.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.