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

# Admin events

Run a ring as staff. Pick the fighters, set the rules, start the match.

Perfect for fight nights and tournaments. While a ring is in **event mode**, players can't take corners themselves: an admin chooses who fights.

## Running an event

{% stepper %}
{% step %}

### Turn event mode on

Stand at the ring's join point and either:

* press **E** and click **Admin manage** in the menu header, or
* type **`/boxingevent`**.

Players' menus now say staff picks the fighters, and the prompt reads *Boxing event*.
{% endstep %}

{% step %}

### Pick the fighters

The admin panel lists every player within **15 m** of you (yourself included). Click **Red** or **Blue** next to a name. You can also **remove** or **swap** fighters. The chosen players get a notification.
{% endstep %}

{% step %}

### Set the rules and start

Choose rounds, round length, gloves, bets and purse, then press **Start the match**. From there it's a normal fight: betting window, walk-out, rounds and result.
{% endstep %}

{% step %}

### Next fight, or end the event

The rules stay set for the next match. Press **End event** between fights to give the ring back to the players.
{% endstep %}
{% endstepper %}

## Good to know

* A fighter can still step out with **Leave** before the match starts.
* **Stop the match** (in the same panel) ends a fight as a no contest and refunds everything.
* Event mode is kept in memory only: a resource restart (or deleting the ring) ends it.
* Every admin action is re-checked on the server: the admin permission, that you stand at the join point, and that the chosen player is nearby, alive and not in another fight.


---

# 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/admin-events.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.