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

# Fighting (player guide)

Everything a player needs to know to fight, bet and climb the leaderboard.

{% hint style="info" %}
This page is written for **players**. Feel free to link it in your server's Discord.
{% endhint %}

## Joining a fight

1. Find a ring on the map (🥊 blip) and walk to the **marker** at the ring.
2. Press **E** to open the ring menu.
3. Take the **Red** or **Blue** corner and wait for an opponent.
4. Either fighter can set the rules: **rounds**, **round length**, **gloves**, **spectator bets** and the **purse**. Any change clears both "Ready".
5. Both press **Ready**.

Closing the menu before the fight starts takes you out of the lobby.

## The walk-out

Your clothes come off for a shirtless fight (they all come back afterwards). A camera shows both fighters and the **tale of the tape** compares your records and ratings. Then: **3 · 2 · 1 · FIGHT!**

## Controls

| Key                    | Action                   |
| ---------------------- | ------------------------ |
| **R**                  | Light punch              |
| **Left Mouse**         | Heavy punch              |
| **Right Mouse** (hold) | Lock on to your opponent |
| **Space** (locked on)  | Dodge                    |
| **Backspace** (hold)   | Throw in the towel       |
| **A / D** (alternate)  | Get up after a knockdown |

Weapons, vehicles, cover and stealth takedowns are disabled in the ring.

## Winning

* Every clean punch takes **ring HP** off your opponent. Big punches are **power punches**.
* Landing punches in a row builds a **streak** (3, 5 and 8 hits get called out).
* At 0 HP your opponent is **knocked down**. Keep them from beating the count to win by **K.O.**
* Three knockdowns in one fight = **T.K.O.**
* Still standing after the last round? Three judges decide, based on damage, punches landed and power.

{% hint style="warning" %}
**Stay inside the ropes!** Outside the ring for more than 6 seconds during a round and you're disqualified.
{% endhint %}

## Getting knocked down

1. You fall and the referee starts counting.
2. Alternate **A** and **D** as fast as you can to fill the bar.
3. You can't get up before the count of 3, however fast you tap.
4. Make it before 10 and you're back with some HP. The second knockdown needs more taps.

## Betting as a spectator

When both fighters are ready, a **30-second betting window** opens for everyone near the ring:

1. Open the ring menu (**E** at the marker).
2. Pick a fighter and an amount. The odds update live.
3. If your fighter wins, you share the losing side's pool.

A draw, a no contest or a fighter disconnecting refunds every bet.

## Records and leaderboard

Every fight updates your **record** (W-L-D, KOs, streaks, earnings) and your **rating**. Climb from **Rookie** through Amateur, Contender, Pro and Elite to **Champion**. Check the **Leaderboard** tab in the ring menu.


---

# 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://visionstore.gitbook.io/visionstore-docs/scripts/boxing-creator/guides/fighting.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.