> For the complete documentation index, see [llms.txt](https://deadtiles.gitbook.io/deadtiles-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://deadtiles.gitbook.io/deadtiles-docs/start/readme.md). # Welcome Deadtiles is a free multiplayer zombie survival game you play in the browser. The world fell to the dead. A few places still hold out, and everyone else scavenges what is left. You share Ashen County with other players. Stay fed, watered, and warm. The factions you meet remember how you treat them. When you die, everything you carried stays on your body. [Enter Ashen County](https://play.deadtiles.com). The same rules live in your Journal as the Field Guide. This book is the longer version, for when you are not in the county. ## What you do here * Scavenge houses, shops, and roads for food, ammo, medicine, and gear. * Take work from the National Guard, the Ashen Traders, and the Red Order. * Trade with Kevin and with other survivors. * Build somewhere safe to keep your loot. * Ship banknotes east as Deadmarks (DMRK). Settlements are generated. Learn a block, then walk until the streets stop matching. Cities carry far more of the dead than a rural road. --- # 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://deadtiles.gitbook.io/deadtiles-docs/start/readme.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.