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

# Score

Every note you hit scores points. The closer you hit it, the more it's worth:

| Hit            | Points |
| -------------- | ------ |
| Perfect        | 100    |
| Great          | 60     |
| Good           | 25     |
| Hold completed | 60     |

Points are the same on every difficulty. Harder songs have more notes, so they score more.

## Your streak multiplies every hit

Your streak multiplies the points of each hit, from 1x up to 8x. See [How to play](/beatking-docs/play/how-to-play.md). A [Beat Burst](/beatking-docs/gear/power-ups.md) gives you 16x for 10 seconds.

> hit points × streak

Your score climbs live while you play.

## Your device multiplies the total

When the song ends, your device's boost multiplies your whole score. Score 200,000 on a device with 1.5x boost and your final score is 300,000.

Your final score is the one that counts on the leaderboards. A better device scores higher on the same play.

## Why the streak matters most

A whole song at 8x is worth far more than a song where you keep resetting. One miss costs you the climb back to 8x, which is about 20 notes' worth of points. Hold the streak.

## Leaderboards

Every song has a leaderboard for each difficulty. Your best final score on it sets your spot. The player at the top is the song's king.

The crowns leaderboard ranks every player by the [crowns](/beatking-docs/play/crowns.md) they've earned.


---

# 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/score.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.