QBCore Frameworkqbcore.netCommunity docs
On this page

Updated 2026-10-11 · 2 min read

qb-weed: plant growth and persistence

qb-weed manages persistent house plants, growth stages, feeding and harvesting. The implementation is pinned to commit 318b5b1.

Install and data storage

  • Start qb-core, oxmysql and any inventory/housing dependencies used by your installation before qb-weed.
  • Import the official qb-weed.sql into a backup/staging database and check that house_plants exists.
  • Verify house identifier and plant data consistency with your own housing resource. Do not treat client-reported building names as proof of access.

Configuration uses QBWeed, not Config

The upstream config defines the top-level QBWeed table:

KeyMeaning
QBWeed.Progress.min / maxAmount of growth progress per tick
QBWeed.GrowthTickMinutes between growth updates (default 9.6)
QBWeed.FoodUsagePlant nutrition used per tick
QBWeed.ShowStagesWhether to display stage changes
QBWeed.StageLabelsVisible lifecycle labels
QBWeed.DefaultPropsGTA prop models for plant stages
QBWeed.PlantsPlant types including ogkush and amnesia
QBWeed.Progress = { min = 1, max = 3 }
QBWeed.GrowthTick = 9.6
QBWeed.FoodUsage = 1

These are entries to modify in the original config, not a complete replacement file.

Source event map

The server source registers callback qb-weed:server:getBuildingPlants plus events placePlant, removeDeathPlant, removeSeed, harvestPlant and foodPlant under the qb-weed:server: prefix.

These events are internal to the gameplay script. In particular, placePlant accepts client-supplied coordinates, plant type and building name and inserts a database row; it does not independently establish ownership of that house in the reviewed handler. Production usage needs a validated server-side placement and harvest authorization boundary.

Troubleshooting

SymptomFirst check
Plants disappear on restartCorrect house_plants table and database connection
Growth never advancesServer timer, QBWeed.GrowthTick and plant stage data
Plant model doesn't appearDefaultProps and client streaming errors
Plants appear in someone else's houseHouse identifier, caller authorization and client-submitted building
Missing seeds or harvest itemsQBCore shared items, qb-inventory and event errors

Update checklist

  1. Pin the source version and back up house_plants before any schema migration.
  2. Test planting, growth, watering, harvest and reconnect with different house owners.
  3. Enforce server-side house access, permitted item types, positions and cooldowns.
  4. Validate failures and item removal/addition against your inventory version.

Sources

Repository · SQL · Config · Server

Found an issue in this guide?

Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.

On this page

Leonida RP server website built with RPWebsite
RPWebsite

Advertisement · RPWebsite

Want a website for your server?

Launch a site with live player status, rules, and a join button in minutes.

Build your website