Gardening by HypnoticGD is an archived QBCore mowing job at the golf club. Its manifest declares version 1.0.1. Players start a route, use a spawned mower and receive in-game cash per marker; the supplied server handler needs additional validation before use in a public economy.
Configure dependencies and the route
Keep fxmanifest.lua, client.lua, server.lua and config.lua together in the Gardening resource folder and start qb-core before ensure Gardening. The code defaults to cdn-fuel and also contains x-fuel and LegacyFuel branches. Match Config.FuelSystem to your installed resource. The vehiclekeys:client:SetOwner event requires a compatible key system; it is not provided by this package.
The default configuration has 25 ordered markers, four mower spawn points, vehicle model mower and rewardPerMarker=10. After the last marker the client starts the route again. Finishing manually at JobEndCoords removes the mower and route blip. Configure start/end points and the separate hardcoded Greenkeeper blip together when moving the job.
Validate server rewards and cleanup
The client checks marker distance and whether the player is in its mower. The server payment event only checks that a QBCore player exists, then adds the configured cash reward. It does not track active jobs, marker order, mower ownership, distance or payment timing. Store route state on the server and pay each eligible marker once.
Spawn selection is random and does not check whether the chosen bay is occupied. The supplied code has no resource-stop cleanup handler; normal clock-out cleanup does not prove reconnect or restart behavior. Test blocked spawn bays, fuel/keys, wrong vehicles, repeated markers, early finish and disconnects. Adapt the hardcoded German UI text and notification arguments to your QBCore version.
Reviewed on 10 September 2026 at revision ab49d46f629948392370aef0ed5ff4755afd1836. All supplied Lua, configuration, manifest and README were read; GitHub still reports the repository archived. No mower, route or payment was executed.