> 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/jobs/cuxial-diving.md).

# Cuxial Diving

Crew-based diving job for FiveM with regions, a work boat, oxygen gear, a market and progression.

Cuxial Diving is a diving job for one to four players. A crew picks a region, sails a work boat to the site, collects what lies on the seabed and brings the boat back to get paid.

## What it does

* **Crews of up to four.** The owner invites nearby players, picks the region and starts the job. A player who disconnects keeps their seat for a few minutes.
* **Regions with a minimum level.** Each region has its own tasks, reward, boat spawn points and drop-off point.
* **Four kinds of task.** Cut corals, collect trash, open and loot suitcases, and recover boxes with a lift bag and a rope thrown from the anchored boat.
* **Oxygen gear.** Three tank levels with different durations, a mask with a light, and an oxygen indicator on screen.
* **Work boat.** Spawned for the crew, with an anchor on a key and boxes stacking on deck as they are loaded.
* **Market at the job NPC.** Sells gear and buys what the divers bring back.
* **Progression.** Levels, daily tasks, job history and a ranking.
* **Payout modes.** Full reward to everyone, reward split between the crew, or a bonus per extra member. The owner can also share the money by percentage.
* **Discord logs** for jobs, daily tasks and market operations.

## How a job goes

1. Talk to the job NPC. The panel opens with your crew, the regions, your progress, the ranking and the market.
2. Invite nearby players, pick a region and start the job. Everyone is placed on the boat.
3. Sail to the marked site. Put on a tank, then the mask, and dive.
4. Complete the tasks. Corals and trash are required; suitcases and boxes are optional and give loot.
5. When the required tasks are done, take the boat to the drop-off point and deliver it. Everyone connected is paid.

## Requirements

| Resource               | Required                       | Used for                                                               |
| ---------------------- | ------------------------------ | ---------------------------------------------------------------------- |
| OneSync                | Yes                            | The boat is created by the server                                      |
| `ox_lib`               | Yes                            | Callbacks, commands, keybinds, notifications, locales                  |
| `oxmysql`              | Yes                            | Progress, history and audit                                            |
| `cuxial_bridge`        | Yes                            | Connects to your framework (QBox, QBCore or ESX) and to your inventory |
| `sleepless_interact`   | Yes                            | Interaction with the NPC and with the pieces on the seabed             |
| `cuxial_jobs`          | Yes, delivered with the script | Shared library of the Cuxial jobs                                      |
| `cuxial_diving_assets` | Yes, delivered with the script | Lift bag model                                                         |
| `cuxial_garages`       | No                             | Gives each crew member the keys of the boat                            |

{% hint style="warning" %}
The item file in `install/` is written for `ox_inventory`, and the market reads its pictures from the `ox_inventory` image folder. With another inventory, create the items in its own format.
{% 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 and start order.</td><td><a href="/scripts/jobs/cuxial-diving/installation.md">Installation</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/jobs/cuxial-diving/configuration.md">Configuration</a></td></tr><tr><td><strong>Commands &#x26; permissions</strong></td><td>Player and staff commands, keys and who can work.</td><td><a href="/scripts/jobs/cuxial-diving/commands.md">Commands &amp; permissions</a></td></tr><tr><td><strong>Exports &#x26; events</strong></td><td>Read a diver's level and react when a job is paid.</td><td><a href="/scripts/jobs/cuxial-diving/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/jobs/cuxial-diving/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/jobs/cuxial-diving.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.