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

# Troubleshooting

Fixes for the most common problems.

{% hint style="info" %}
First step, always: look at the **server console** and the player's **F8 console**. Most problems print a clear message there, starting with `[Chapo_BoxingCreator]`.
{% endhint %}

## Startup

<details>

<summary>"You lack the required entitlement" / the resource won't start</summary>

See [Escrow and common errors](/visionstore-docs/getting-started/escrow-and-common-errors.md). The server key must belong to the account that bought the script.

</details>

<details>

<summary>The console says <code>framework: standalone</code> but I use QBCore / ESX</summary>

The script started before your framework. Move `ensure Chapo_BoxingCreator` **below** your framework in `server.cfg`, or set `Config.Framework` to `'qb'`, `'qbx'` or `'esx'` explicitly.

</details>

<details>

<summary><code>could not create chapo_boxing_stats</code></summary>

Your database user can't create tables. Run `sql/chapo_boxing.sql` manually, then restart.

</details>

## In game

<details>

<summary>/boxingcreator says I don't have permission</summary>

Your account needs the ACE `command.boxingcreator`. Check that you are in `group.admin` (or the group in `Config.Admin.Principal`) and that `server.cfg` contains `add_ace group.admin command allow`.

</details>

<details>

<summary>Punches don't do any damage, or every punch knocks people down</summary>

Tune `Config.Combat.Damage.Scale`. Turn on `Config.Debug`, fight, and read the numbers in the console. See [Tuning damage](/visionstore-docs/scripts/boxing-creator/configuration/combat-and-knockdowns.md#tuning-damage-for-your-server).

</details>

<details>

<summary>Punches aren't counted at all</summary>

* **OneSync must be on**: hits arrive as OneSync damage events.
* Both players must be the two fighters of the same ring, in a **live** round (not the countdown or a break).
* Another anticheat or "safe zone" script may be cancelling melee damage in that area.

</details>

<details>

<summary>Notifications don't show</summary>

Check `Config.Notify` matches a resource you actually run, and that it's started before this script. Use `'gta'` to test: it needs no resource.

</details>

<details>

<summary>The gloves item does nothing</summary>

* ox\_inventory: the item entry must have `client = { export = 'Chapo_BoxingCreator.useGloves' }` and the folder name must be exactly `Chapo_BoxingCreator`.
* QBCore / ESX / qs: the item must exist in your items list. The script registers it as usable on start. Restart the script after adding the item.

</details>

<details>

<summary>The ring prop is invisible or players fall through it</summary>

* Don't rename or remove anything in `stream/`.
* The model shows within 220 m (`Config.RingPropStream`).
* After placing a ring, make sure the canvas isn't under the ground: use **Move it** and PgUp to raise it.

</details>

<details>

<summary>My HUD stays visible during fights</summary>

By default only the minimap is hidden. Name your HUD's exports in `Config.HideHud.Resource`, or edit `Bridge.setHudHidden`. See [Framework, notify & inventory](/visionstore-docs/scripts/boxing-creator/configuration/framework-notify-inventory.md#hiding-the-players-hud-during-fights).

</details>

<details>

<summary>Players lost money in a fight that crashed</summary>

They didn't: anything at stake is refunded on resource stop, and winnings for offline players are paid to their character in the database. Check their bank / cash after they log back in.

</details>

Still stuck? [Open a ticket on our Discord](https://discord.gg/ZvHtyhyBp4) with your console errors (see [Support](/visionstore-docs/getting-started/support.md) for what to include).


---

# 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/troubleshooting.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.