Skip to content

Kivo Weedshop

Kivo Weedshop adds a player run dispensary job to your server. Employees of the SkyHigh Dispensary (job name skyhigh) grow plants in plots, dry the harvest on racks, roll pre-rolls, sell them and run restock missions. A management computer inside the shop shows stats, pay rates, the team and the shop finances.

The script works with ESX, QB-Core and QBX, with ox_inventory, qb-inventory or the ESX default inventory, and with ox_target or qb-target. It detects what you run at startup.

You need all of the following on your server.

Requirement Supported options
Database library oxmysql
Utility library ox_lib
Framework (one) es_extended (ESX Legacy), qb-core, or QBX with its QB-Core compatibility bridge enabled
Inventory (one) ox_inventory, the ESX default inventory, or qb-inventory
Target (one) ox_target or qb-target
Shop interior The shop interior (map) that the default coordinates are set for. See the note below.

The script creates its own database tables on the first start. You do not import a SQL file for the script itself. You only add the job and the five items to your framework (see Installation).

Start the libraries first, then the framework, inventory and target, then the script.

ensure oxmysql
ensure ox_lib
ensure es_extended # or qb-core / qbx_core
ensure ox_inventory # or qb-inventory (or the ESX default inventory)
ensure ox_target # or qb-target
ensure kivo-weedshop

The script waits up to 10 seconds for a supported framework and target to appear, but the correct order is still recommended.

What Detection order
Framework es_extended first, then qb-core. If both are running, ESX is used.
Inventory ox_inventory first (on any framework). Otherwise qb-inventory on QB-Core and QBX, or the ESX default inventory on ESX.
Target ox_target first, then qb-target.

This is the loop a player sees. Every step needs the skyhigh job, and the grade needed for each step is set in the configuration.

  1. Grab a tool. At the supply zones the employee picks up a water sprayer or a fertilizer bag. The tool appears in their hands and can be put back.
  2. Plant. At an empty plot the employee plants seeds. Planting uses 6 weed_seed.
  3. Tend the plant. The employee waters and fertilizes the plant with the matching tool and can inspect it. A floating board above each pot shows the stage (Empty, Seed, Growing, Mature), health, water and fertilizer.
  4. Harvest. When the plant is ready, harvesting with weed_shears gives 6 wet_weed_plant. The shears are not used up.
  5. Dry. At one of the 3 drying racks the employee puts in 6 wet_weed_plant. After a set time the rack is ready and gives back 6 dried_weed_plant.
  6. Roll. In the rolling area the employee presses E, a progress bar runs, and 6 dried_weed_plant become 6 weed_preroll (the amounts are configurable).
  7. Sell. In the selling area the employee presses E, a progress bar runs, and every weed_preroll they carry is sold in one go.
  8. Get paid. Each completed step pays the employee a share of a fixed amount and gives the rest to the business.
  9. Restock. Employees of the right grade start a restock mission from the computer. They drive a van to a pickup point, collect a supply box, bring it back and store it. Each mission raises the shop stock level.
  10. Manage. At a shop computer employees see their stats and the leaderboard. Higher grades hire, promote and fire staff, see the finances and set how much of each payout goes to employees.
  • 6 plant plots with floating status boards (two display modes, can be turned off).
  • 3 drying racks with visible full or empty rack props in the interior.
  • Rolling and selling areas with progress bars.
  • Restock missions with a mission vehicle, a carried box, map blips and a time limit.
  • Employee computer with Overview, Activity, Leaderboard, Operations, Team, Financials and Config tabs.
  • Five job grades with a per-action permission table.
  • Per-action payouts split between employee and business, with admin-set limits for the boss.
  • Optional daily or weekly salary.
  • Optional Discord avatars in the computer.
  • Custom props that stream automatically with the script.
  • Works with ESX, QB-Core and QBX, three inventories and two target systems.
Page What it covers
Installation Step by step setup, job and item definitions for every framework, server.cfg
Configuration Every option in the editable config files
Exports and integration Reading plant and rack data from other scripts, and adapting the bridge to another framework, inventory, target or key script
Examples and troubleshooting Ready-made config changes, edge cases, common mistakes

The script registers no exports. Other scripts read its data through two sets of state bags, described on the integration page.

Back to the scripts index.