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

# Features

Page dedicated to what our Gardener \[V2] does in game

## Job Center and Crew

Players come to the EcoGreen depot and talk to the foreman. The conversation works like the bank tellers in Banking V2: jobs are offered as answers with the details and the pay, and the foreman answers questions about levels, the crew, work clothes, garden orders and the tablet.

A crew has one to four players with a leader. The leader invites players nearby and sets the payout split, which cannot change once the job starts. Every member needs the level the job asks for, and the job page names who is too low.

* A member who loses connection keeps their place for 5 minutes and is back with the same share after reconnecting.
* When the leader leaves, the next member leads.
* A member who is offline when the job ends is paid on their next login.

## Getting Ready

Before leaving the depot each member changes at the locker room, someone takes the van from the van ped and the whole crew gets in. The HUD lists these steps and the GPS points to the plot only after them.

At the warehouse a worker hands the tools out one at a time. The crew carries them to the van and places each one in the hold with a ghost that shows where it fits. The job offer lists the tools it needs, and a tool left on the shelf is missing on the plot: the tasks that need it are dropped and the pay is cut.

On the plot the crew takes the tools from the back of the van, one per person. Tools can be put down on the lawn and picked up by anyone in the crew. The mower and the blower are started with three pulls of the cord.

## Upkeep Jobs

| Task   | How it works                                                                                                                |
| ------ | --------------------------------------------------------------------------------------------------------------------------- |
| Mowing | A push mower or a ride-on mower over a grid of lawn cells. Grass tufts disappear under the mower with a burst of clippings. |
| Hedges | Hold the key and walk along the hedge with the trimmer running. Trimmed hedges leave clippings on the ground.               |
| Leaves | Blow the scattered leaves into a heap, then kneel and pack the heap into a garden bag armful by armful.                     |
| Weeds  | Pull each weed kneeling and toss it into the bag in hand or standing nearby.                                                |

Every crew member takes their own empty bag off the roll in the van, so two players can work in two corners of the garden. A full bag goes back into the van and the next one comes off the roll. The players around see the tools run, the heaps grow and the bags fill.

## Design Jobs

The client has a brief, a budget and a plot. The leader opens the catalog (F6) and places trees, shrubs, flowers, paths, benches, lights and fountains:

* the ghost has a red outline on collision, outside the plot and over budget,
* plants get a random rotation, path pieces join the previous piece,
* the brief checklist updates live for the whole crew.

Every placed item is a sketch first. The crew carries it from the van and installs it in a minigame that fits the work:

| Work             | Minigame                  |
| ---------------- | ------------------------- |
| Trees and shrubs | Rhythm while digging      |
| Flowers          | Timing while planting     |
| Paths and paving | Arrows for each slab      |
| Benches, lights  | A measured squeeze to fix |

## Review and Payout

When the work is done the leader calls the client. The review screen shows the rating from 0 to 100, the score breakdown and the crew split.

The server computes everything: the rating from the brief, the budget, the coverage, the variety and the minigames, and the pay from the rating, the job rate and the level bonus. The client never sends an amount. With Banking V2 the money goes to the bank account and income tax is taken.

## Gardens That Stay

A finished design garden is saved and stands on the map after a restart. Its props spawn only near players. After a set time the garden overgrows, weeds come back and the garden is offered as an upkeep job.

## Garden Orders

Players order a garden on a plot from the tablet (**Orders**). The fee and budget are taken at once, crews online get a notification and the order appears as a job. An order nobody has taken yet can be cancelled for a full refund, and the unused budget returns to the client when the garden is done.

A plot with a property ID can only be ordered by the owner of that property, through the `GetOwnedProperties` hook. Examples for qs-housing, ps-housing and loaf\_housing are in [Additional Informations](https://wiki.qfdevelopers.com/scripts/gardener-v2/additional-informations.md#owned-properties-for-garden-orders).

## Work Tablet

The tablet (F7) shares the frame of the QF MDT \[V2] tablets: address bar with the clock, sidebar with a grouped menu and a settings page.

| Page         | What the player does there                       |
| ------------ | ------------------------------------------------ |
| **Jobs**     | Job offers with the plot, the tools and the pay. |
| **Crew**     | Members, invites and the payout split.           |
| **Progress** | Level, experience and finished jobs.             |
| **Orders**   | Their own garden orders.                         |
| **Help**     | How the job works.                               |
| **Settings** | Theme and window size, saved for the player.     |


---

# 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/features.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.
