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

# Admin Panel

Page dedicated to the admin panel of our Gardener \[V2]

Everything a server owner sets in Gardener V2 is set here, in game, and saved to the database. Open it with `/gardenadmin`. Changes apply at once, without a restart.

Each settings page has one **Save** for all its groups. The server checks every value, so an invalid one (for example a rate of -5) is refused with a message. Every change is written to **History** with the value before and after and, when set, to the `admin` Discord webhook.

{% hint style="info" %}
Places (the job center, locker room, van ped, warehouse, van spawn and return) are set with **Set here**: the point goes where you stand, facing where you face. Each point shows how far it is from you, with **Teleport** and the coordinates on demand.
{% endhint %}

## Overview

### Dashboard

What still blocks the first job (plots, work spots, van parking, catalog, client briefs, a test run), with a button to each page. The list hides once everything is done.

### Players

Players with their level and experience, their face and whether they are online. **Import levels from V1** copies levels and experience from the V1 table `gardener_cache`. It can run more than once and never lowers progress a player already has in V2.

### History

Every admin change, with who made it, when, and the value before and after.

## Server

### General

Language, accent colour (`#8cc63f` by default), currency and its position, number and date format, interface scale, the framework job required to work (empty for everyone), work clothes on or off, the map blip and debug.

### Base and vehicles

* The job center: the foreman ped, his name, position and whether the camera turns to him while you talk.
* The locker room and the van ped, each as an NPC or a marker, with their models.
* The warehouse point and the warehouse worker (NPC or marker).
* The van spawn and return points, set by standing there.
* The van and mower models, the plate prefix and the vehicle keys resource.
* The mower drawn per job: `random`, `push` or `ride`, with the ride-on chance (30% by default).
* The prop models of the tools and the world (folded by default).

### Economy

Upkeep and design rates, the level bonus, the minimum rating for pay, the allowed overspend on design jobs, the pay cut for every tool missing on the plot (10% by default), bank or cash, income tax through Banking V2 and the experience curve. The page shows what a job pays with the values being edited.

### Jobs

Number of offers, refresh time, time limit, the mowing grid, leaves and weeds per plot, the garden bag capacity (12 by default), spare bags on the roll, loading the van at the warehouse and the warehouse radius, crew size and invites, how the pay is split (by the leader's shares or by the work each member does), how long a disconnected member keeps their place (5 minutes by default) and taking jobs from the tablet anywhere.

### Permissions

Access to single modules for other groups. The page suggests the admin groups of your framework. Full admins are set in `Config.AdminAccess`.

## Work

### Plots

Plots are drawn in the world. **New plot → Draw in the world** starts the tool:

* E adds a point of the outline,
* H marks a hedge line,
* G sets the door point,
* Enter finishes.

Undo is available, and a self-crossing outline or a plot that is too small is refused with a message. Each plot has a type (upkeep, design or both), mowing on or off, a minimum level, a photo and an optional property ID for garden orders.

**Work layout** sets the rest in game:

* weed and leaf spots, placed by aiming,
* lawn zones left uncut (paths, pools, flower beds),
* van parking (the GPS target and the arrival point) and the ride-on mower spot,
* how many weeds and leaf spots a job on this plot asks for.

The list warns about a plot with missing spots, van parking or entrance. **Test run** starts an unpaid job on the plot for your crew with the tools already in the van, without experience, history or a saved garden.

{% hint style="warning" %}
The six default plots have mowing off, because the V1 places only record the work spots and not where the lawn is. Turn mowing on for a plot after checking that its outline covers only the lawn.
{% endhint %}

### Catalog

The items crews place on design jobs: model, price, radius, install minigame, level and tags. Each item is previewed in the world, where the mouse wheel fits the radius to the prop.

### Client briefs

The templates design jobs are drawn from: a name shown to players, the budget per m² and the requirements (for example at least three trees, a path to the door, no fountain). Each brief shows a preview of the offer.

### Gardens

Gardens standing on the map, with teleport, remove and **Mark overgrowing**, which brings weeds back at once and offers an upkeep job for the garden.

| Setting              | Default | Meaning                                         |
| -------------------- | ------- | ----------------------------------------------- |
| Gardens stay         | on      | Finished design gardens are saved on the map.   |
| Items per garden     | 60      | Most items one garden can hold.                 |
| Gardens on server    | 150     | Most gardens saved at once.                     |
| Spawn distance       | 150 m   | Garden props spawn only for players this close. |
| Overgrows after      | 72 h    | Time until a garden needs upkeep again.         |
| Weeds when overgrown | 6       | Weeds that come back on an overgrown garden.    |

### Orders

Garden orders filtered by status.

| Setting       | Default           | Meaning                                                     |
| ------------- | ----------------- | ----------------------------------------------------------- |
| Orders on     | on                | Players can order gardens from the tablet.                  |
| Fee           | 30%               | Paid on top of the budget and kept when the garden is done. |
| Budget        | 10 000 to 300 000 | The range a player can order with.                          |
| Open orders   | 1                 | Orders one player can have open at once.                    |
| Expires after | 72 h              | An order nobody takes is closed and refunded.               |


---

# 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/admin-panel.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.
