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

# Battle Rules

<figure><img src="/files/BN8QFCsZkopOxvTQ6fJn" alt=""><figcaption></figcaption></figure>

**\[Judge Ethan]** The battle rules are designed to make sure the robot with the most exciting recycling performance is the winner. 💥

### How to Win

1. Knock out the other robot, OR
2. Finish the battle with the most [recycling points](#recycling-points)

### Knockout

3. A robot is knocked out if the player has lost control over its movement.
4. If a robot looks like it is no longer under the player's control, the battle is paused and the player must show control by driving their robot to a particular area of the arena.

### Recycling Points

5. If a battle reaches the 3 minute mark, the robot with the most recycling points wins.
6. Recycling points reward a robot for having decorations that break apart in battle.
   1. If **your robot** causes the crash, you get points for all decorations that break off— **even your own**.&#x20;
   2. If **both robots** cause the crash, each player gets points for decorations that break off **their own robot**.
   3. The more awesome the crash looks, the more points it's worth.

### Unsticking

7. If both robots get stuck for 10 seconds, battle is paused and the robots may be separated.

{% hint style="warning" %}
***\*FWEEET\******&#x20;🎺** A well tuned robot can reach high speeds. Always play RoboBattles under adult supervision. Wear safety glasses. By participating, you agree to assume all responsibility for safety precautions and risks. 🥽
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://play.robobattles.com/battle/rules/battle-rules.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.