> For the complete documentation index, see [llms.txt](https://beatking.gitbook.io/beatking-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://beatking.gitbook.io/beatking-docs/play/how-to-play.md).

# How to play

Notes fall down three lanes. Tap a lane when its note hits the ring.

## Timing

The closer your tap is to the beat, the better the hit:

| Hit     | How close to the beat |
| ------- | --------------------- |
| Perfect | within 55 ms          |
| Great   | within 100 ms         |
| Good    | within 145 ms         |

A tap further off than that is a miss. A tap on an empty lane is a miss too.

## Holds

Long notes are holds. Tap the start and keep your thumb down. The hold counts once you've held it for 70% of its length.

## Streak

Hit notes in a row to build your streak. Your streak multiplies your score:

| Notes in a row | Multiplier           |
| -------------- | -------------------- |
| 8              | 2x                   |
| 16             | 4x                   |
| 24             | 6x                   |
| 32             | 8x, and you go VIRAL |

A miss sends you back to 1x. So does a tap on an empty lane, or letting go of a hold too early.

## Difficulty

Songs come in Easy, Medium, Hard and Extreme. Harder songs score more.

Easy and Medium are open from the start. Hard and Extreme open once you've earned 1,000 crowns in total. After that they stay open for good, in every season.

Extreme songs never let up: long runs of notes faster than one thumb can keep.


---

# 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://beatking.gitbook.io/beatking-docs/play/how-to-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.