> 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/play.md).

# How to play

Open [play.deadtiles.com](https://play.deadtiles.com) and sign in with Phantom or Solflare. The Android app can also sign in with Seed Vault. The game is free.

You wake in Birchport Hospital, short on food and water. Doctor Clark patched you up. The first session walks you through the rest.

## First hour

1. Walk. On a computer, click the ground or use WASD. On a phone, drag the stick or tap the ground.
2. Talk to Doctor Clark and ask what happened. Accept the work he offers.
3. Eat the tuna and drink the water in your pack. If hunger or thirst hits zero, you start losing health.
4. Open the map. Birchport's hospital, barracks, and market are marked.
5. Leave the ward and report to Captain Davis in the barracks mess hall.
6. Read the next job before you take it. That is how Davis says you earn the National Guard's trust.

When the tutorial ends, you are on your own. Scavenge, stay fed and warm, follow the story Davis offers, and build somewhere safe. Davis and Clark post more work on their boards. The Field Guide in your Journal covers the same ground as this book.

## What carries over

Skills, faction standing, and the work you have already finished stay with you. Gear does not, if you die before you stash it. See [Death](/deadtiles-docs/stay-alive/death.md).


---

# 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/play.md?ask=<question>&goal=<user_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.