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

# Cuxial Gym

Gyms for FiveM with real equipment, minigames per rep, strength and agility stats, memberships and player-run businesses.

Cuxial Gym adds working gyms to your server: players train on equipment, pass a minigame on each rep and raise two stats that change their character. Each gym can sell memberships and be run as a business by players.

## What it does

* **22 exercises** on machines, benches, bars, mats and a punching bag, with their own props, animations and sounds.
* **13 minigames** with 8 difficulty levels. Difficulty rises along the set.
* **Strength and agility.** Strength raises maximum health; agility adds stamina regeneration. Both are levelled by training.
* **Fatigue per muscle group.** Seven body parts tire with each rep and recover over time. A tired muscle cannot be trained.
* **Streaks and achievements.** Training on consecutive days gives an XP bonus; 45 achievements in five tiers.
* **Supplements.** Eight inventory items with timed bonuses to XP, fatigue or minigame auto-pass.
* **Memberships.** Each gym can require a pass, sell packages by days and give members a daily reward.
* **Gym panel** on a physical screen in the world, or as a regular full-screen interface.
* **Businesses.** Owner, grades with permissions and hourly wage, employees, finances with taxes, warehouse with supplier orders, public shop, automatic workers, levels and missions.
* **Spotters.** An employee can help a player who is training and earn them free reps.
* **In-game editors.** Staff build gyms without touching files: zones, equipment, interaction points, minigame presets, balance, supplements and businesses.
* **API for other resources**: exports, server events and editable hooks.

## Requirements

| Resource             | Required    | Used for                                                     |
| -------------------- | ----------- | ------------------------------------------------------------ |
| OneSync              | Yes         | Synced equipment and exercise sessions                       |
| `ox_lib`             | Yes         | Callbacks, keybinds, locales                                 |
| `oxmysql`            | Yes         | Players, zones, businesses and settings                      |
| `cuxial_bridge`      | Yes         | Connects to your framework, inventory and target             |
| `sleepless_interact` | Yes         | Interaction on equipment and points                          |
| `cuxial_gym_assets`  | Yes         | Props, animations, map and sounds. Delivered with the script |
| `ox_inventory`       | Recommended | Supplements, daily reward, shop, lockers and stashes         |
| `cuxial_appearance`  | No          | Wardrobe opened from a cloakroom point                       |

{% hint style="warning" %}
Lockers and business stashes require `ox_inventory`.
{% endhint %}

## Pages

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Installation</strong></td><td>Dependencies, items, convars, permissions and start order.</td><td><a href="/scripts/leisure/cuxial-gym/installation.md">Installation</a></td></tr><tr><td><strong>Features guide</strong></td><td>How training, memberships, businesses and the editors work in game.</td><td><a href="/scripts/leisure/cuxial-gym/features.md">Features guide</a></td></tr><tr><td><strong>Configuration</strong></td><td>Every option in <code>shared/config.lua</code> and the editable data files.</td><td><a href="/scripts/leisure/cuxial-gym/configuration.md">Configuration</a></td></tr><tr><td><strong>Commands &#x26; permissions</strong></td><td>Staff commands, keys and who can do what.</td><td><a href="/scripts/leisure/cuxial-gym/commands.md">Commands &amp; permissions</a></td></tr><tr><td><strong>Exports &#x26; events</strong></td><td>Read stats, grant memberships and work with businesses from your own resources.</td><td><a href="/scripts/leisure/cuxial-gym/developers.md">Exports &amp; events</a></td></tr><tr><td><strong>Troubleshooting</strong></td><td>Common problems and how to fix them.</td><td><a href="/scripts/leisure/cuxial-gym/troubleshooting.md">Troubleshooting</a></td></tr></tbody></table>


---

# 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://docs.cuxial.com/scripts/leisure/cuxial-gym.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.