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

# Installation

Page dedicated to how to install our Gardener \[V2]

## Step #1 - Drag & Drop

Just Drag & Drop the `qf_gardener_v2` folder into your `resources` folder.

{% hint style="warning" %}
Keep the folder name **`qf_gardener_v2`**. It is used for events, NUI paths, exports and table names, so the resource stops on start when the folder is renamed.
{% endhint %}

If you ran our Gardener Multiplayer Job (`qf_gardener`), remove its `ensure` line. Gardener V2 provides `qf_gardener`, so scripts that depend on the V1 name keep working. See [Moving from V1](https://wiki.qfdevelopers.com/scripts/gardener-v2/additional-informations.md#moving-from-v1).

## Step #2 - SQL Installation

{% hint style="info" %}
There’s no need to manually insert any SQL file into your database. On every start the script creates its tables (`qf_gardener_v2_*`), checks every table and column and adds whatever is missing. Updates only ever add, so restarting or updating the resource never drops your data.
{% endhint %}

On the first start six upkeep plots are added on the V1 work places (Rockford Hills, Mirror Park, Davis, East Mirror Drive, Paleto Bay and Grapeseed), so upkeep jobs run right away. A default plot you delete does not come back.

## Step #3 - Items

Gardener V2 uses no inventory items. Tools, garden bags and catalog items are props handed out and taken back by the script.

## Step #4 - Script start

Make sure `oxmysql` and your framework start before Gardener V2:

```
ensure oxmysql
ensure es_extended        # or qb-core / qbx_core
ensure qf_gardener_v2
```

On start the console prints the version, the framework and the target it found, followed by missing hooks and outdated editable files, if any.

## Step #5 - Admin access

The admin panel opens with `/gardenadmin` for the groups `superadmin`, `admin` and `god`, or for anyone with the ace below. Add it to your `server.cfg` if you use aces:

```
add_ace group.admin qf_gardener.admin allow
```

Then join the server and run `/gardenadmin`. The dashboard lists what still blocks the first design job (plots, work spots, van parking, catalog, client briefs, a test run) with a button to each page, and hides the list once everything is done.

{% hint style="info" %}
Design jobs and garden orders need a design plot. Open **Admin → Plots → New plot → Draw in the world** and walk around the garden. See [Admin Panel](https://wiki.qfdevelopers.com/scripts/gardener-v2/admin-panel.md#plots).
{% endhint %}

## Requirements

* ESX, QBCore or QBox, detected automatically
* `oxmysql`
* OneSync

Optional:

* `ox_target`, `qb-target` or `qtarget`. Without one, every spot has a ground ring, an arrow and a key prompt (E by default, rebindable in Settings → Key Bindings → FiveM).
* `ox_lib` for notifications, when you do not use the built-in QF notifications.
* A vehicle key script for the work van: qbx\_vehiclekeys, qb-vehiclekeys, Renewed-Vehiclekeys, MrNewbVehicleKeys, wasabi\_carlock, qs-vehiclekeys, Jaksam's vehicles\_keys, mk\_vehiclekeys, t1ger\_keys, cd\_garage, okokGarage or your own.
* A fuel script: ox\_fuel, LegacyFuel or cdn-fuel. Without one, the native fuel level is set.
* Our [Banking \[V2\]](https://wiki.qfdevelopers.com/scripts/banking-v2.md) for payouts to the bank account and income tax.
* A housing script (qs-housing, ps-housing, loaf\_housing or your own) when garden orders should be limited to the owner of a property.


---

# 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://wiki.qfdevelopers.com/scripts/gardener-v2/installation.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.
