> 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/crowns.md). # Crowns Crowns are your season rank. Every play earns crowns, and they add up over the season. ## How many you earn Every song has a **perfect score**: every note Perfect, no misses, on a base device with no power-ups. Your crowns depend on how close you get to it. A perfect run on an average-length song earns the full crowns: | Difficulty | Perfect run | | ---------- | ----------- | | Easy | 80 crowns | | Medium | 100 crowns | | Hard | 120 crowns | Get 75% of the perfect score on Medium and you earn 75 crowns. The perfect score is counted at Medium points. That's why Easy lands at 80 and Hard at 120. ## Longer songs pay more A longer song takes more effort, so it earns more crowns. An average song is about 2 minutes 50 seconds. A song twice as long earns 1.5x, and a shorter one earns less. > crowns = your score ÷ perfect score × 100 × song length ÷ 2:50 A perfect Medium run on a 4-minute song earns about 140 crowns. Gems work differently: they're full on any song of 2:30 or longer. So long songs are best for crowns, and songs around 2:30 are best for gems per hour. ## Past the perfect run Gear and power-ups take you past the full amount. A perfect Medium run on a 1.5x device earns 150 crowns. Crowns have no cap. ## Extra crowns When you play someone's song, its creator gets royalties: 5 extra crowns for every 100 you earn. When a player who used your invite code plays, you get a plug bonus: 3 extra crowns for every 100 they earn. Both come on top. They never come out of anyone's crowns. ## Play at your level Hard pays the most, but only when you can hold a streak there. A clean Medium run beats a messy Hard run. Get better first, then move up. --- # 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/crowns.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.