> 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/rules/fair-play.md). # Fair play Skill is the point, so every run gets checked. ## The server scores every run The server scores every run again from your taps. Its score is the one that counts. ## No bots, no scripts Bots, autoclickers and scripts that tap for you break the rules. So do modified games, faked or replayed runs, and AI tools that do any of this for you. ## Account review If your runs look wrong to us, your account goes under review while we check it. Minting, listing items and sending items to your wallet pause, and runs drop no items or codes. Your runs still earn crowns and gems. Think it's a mistake? Email ****. ## Cheaters get removed We can remove any account we suspect of cheating, at any time. Before season rewards, we review every account and take away crowns earned by bots and farming. Play your own runs, on your phone, with your own thumbs. --- # 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/rules/fair-play.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.