> 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-gardener.md).

# Cuxial Gardener

Team gardener job for FiveM: mowing, pruning, branch cutting from a ladder, planting and watering.

Cuxial Gardener is a legal job played alone or in a crew of up to four. The crew picks a region at the job NPC, drives out with a truck and a lawn mower, clears every task on the map and brings the trucks back to get paid.

## What it does

* **Four tasks per job.** Mow weeds by driving the lawn mower over them, prune bushes, cut branches from a ladder with a timing minigame, and plant flowers with a placement preview.
* **Two bonus tasks.** Watering the planted flowers and loading the cut branches into the truck. They are optional and are counted separately.
* **Crews.** Invite nearby players, kick, leave, and keep your seat for a while if you disconnect in the middle of a job.
* **Tools live in the truck.** Hedge trimmer, ladder, watering can and flowers are taken from the truck and returned to it. No inventory items are needed.
* **Regions with a minimum level.** Each region has its own reward, task amounts and flower area.
* **Levels and XP**, daily tasks with their own rewards, a ranking and a personal job history.
* **Money split.** The crew owner can share the money by percentage. XP is always full for everyone.
* **Job panel** with four tabs: home, progress, ranking and an in-game guide. First-time tips and an end-of-job summary.
* **Work clothes** (optional) applied when the job starts and removed when it ends.
* **Discord logs** and an audit table in the database.
* **Server-side checks** on distance, timing and tool in hand for every action.

## Requirements

| Resource                         | Required | Used for                                                      |
| -------------------------------- | -------- | ------------------------------------------------------------- |
| OneSync                          | Yes      | Server-side vehicles and state                                |
| `ox_lib`                         | Yes      | Callbacks, commands, keybinds, locales                        |
| `oxmysql`                        | Yes      | Profiles, history and audit                                   |
| `cuxial_bridge`                  | Yes      | Connects to your framework (QBox, QBCore or ESX)              |
| `cuxial_jobs`                    | Yes      | Shared library of the Cuxial jobs. Delivered with the script  |
| `sleepless_interact`             | Yes      | Interaction options on the NPC, the truck and the work points |
| `cuxial_gardener_assets`         | Yes      | Truck and branch models. Delivered with the script            |
| `cuxial_garages`                 | No       | Gives the crew the keys of the job vehicles                   |
| `ox_inventory` or `qb-inventory` | No       | Only for the optional item rewards in `reward.items`          |

{% hint style="info" %}
The branch ladder is a game model added in game build 2944. On an older build the script uses a shorter ladder instead. See [Installation](/scripts/jobs/cuxial-gardener/installation.md).
{% 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, convars and start order.</td><td><a href="/scripts/jobs/cuxial-gardener/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-gardener/configuration.md">Configuration</a></td></tr><tr><td><strong>Commands &#x26; permissions</strong></td><td>Player and staff commands, default keys.</td><td><a href="/scripts/jobs/cuxial-gardener/commands.md">Commands &amp; permissions</a></td></tr><tr><td><strong>Exports &#x26; events</strong></td><td>Read a player's gardener profile and react when a job is paid.</td><td><a href="/scripts/jobs/cuxial-gardener/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-gardener/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-gardener.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.