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

# Gardener \[V2]

This category is for our Gardener \[V2]

**Gardeners who design gardens.** Gardener V2 is a job for crews of up to four players at EcoGreen Landscaping. Crews mow lawns, trim hedges, blow leaves and pull weeds, and on design jobs they place trees, flowers, paths, benches and fountains from a catalog within the client's budget, install them in short minigames and get a rating from the client.

**Gardens stay on the map.** A finished garden is saved, stands on the map after a restart, overgrows with time and comes back as an upkeep job. Players can order a garden on a plot themselves, and the order becomes a job for the crews.

**Everything is set in game.** Plots, the depot, the catalog, client briefs, the economy and permissions are set in the admin panel (`/gardenadmin`). The config file only starts the resource, and the database is created and repaired by itself on every start.

**Drop-in replacement for V1.** The resource provides `qf_gardener`, and levels from V1 are imported with one click.

<figure><img src="https://511863936-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBSud7PQu51IKAxzl2VLS%2Fuploads%2Fgit-blob-a1d7fe8b859770357ece09fd469a30de84de1215%2Fqf_gardener_v2.png?alt=media" alt=""><figcaption></figcaption></figure>


---

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