> 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/the-county/building.md). # Building Press B, or the build button, with a hammer to place walls, doors, storage, and the rest. Each piece needs its materials deposited before it goes up. Most structures cannot be built inside Birchport. A fireplace is the exception. It is also how you get health back in town: stand beside it once it is lit. See [Survival](/deadtiles-docs/stay-alive/survival.md). Build everything else out in the county. A small storage box holds 8 slots. A large one holds 24. Gear in a box is not on your body when you die. The market also rents a safe deposit box. See [Trade](/deadtiles-docs/money/trade.md). Cloth, wood, and guns are made at a workbench you find. Metal needs a lit furnace. The recipes are in [Crafting](/deadtiles-docs/the-county/crafting.md). Other survivors lock their buildings with a code. When you build your own, you can set a code too. A locked door stays locked until someone has the code or picks it. See [Combat](/deadtiles-docs/stay-alive/combat.md) for what a lockpick costs you in time and noise. A base is where loot stays when you die. Anything still on you drops with the body. --- # 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/the-county/building.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.