Installation

Beetle Studios · FiveM weed cultivation script (genetics, breeding, drying, processing, skill tree, reputation)

This guide walks server owners through installing bs_weed on a typical FiveM server. Adjust paths if your folder layout differs.

What you need first

Before installing, confirm you have:

---

Required prop packs (Bzzz / BPB Mods)

bs_weed uses Bzzz weed and grow props. Stream these on your server per each pack’s instructions so props load correctly.

Store: bzzz.tebex.io

---

Installation steps

1. Add the resource

1. Copy the bs_weed folder into your server’s resources directory (for example resources/[standalone]/bs_weed).
2. Do not rename the resource folder unless you know how to update every reference and Tebex escrow expectations; keeping the folder name bs_weed avoids confusion.

2. Start order in server.cfg

Ensure dependencies load before bs_weed. Typical order:

ensure oxmysqlensure ox_lib# your target resource, e.g.:ensure ox_target# your inventory, e.g.:ensure ox_inventory# your framework core if applicable, e.g.:ensure qb-coreensure bs_weed

Add object_gizmo only if you use precision placement (see Optional section).

3. Database

• Tables are created automatically on first start when your MySQL resource matches Config.Database in shared/config.lua (default oxmysql).
• For a manual reference or DBA review, use schema.sql in the resource root.

4. Configure the script

Edit shared/config.lua (this file is intended to stay editable; it is listed in escrow_ignore in fxmanifest.lua for Tebex builds).

Set at minimum:

• Config.Framework — 'qbcore', 'esx', or 'standalone'
• Config.Database — 'oxmysql' or 'mysql-async'
• Config.Target — 'ox_target', 'qb-target', or 'standalone'
• Config.Inventory — 'ox_inventory', 'qb-inventory', or 'custom'

Tune economy, plant caps, theft, indoor unlocks, drying times, and debug there as needed for your server.

5. Items and inventory

ox_inventory

1. Open items/ox_inventory_items.lua inside bs_weed.
2. Merge those item definitions into your inventory’s items file (commonly ox_inventory/data/items.lua).
3. Item names must match Config.Items in shared/config.lua.

qb-inventory

Use the same item names and logic as a reference; adapt the item definitions to your qb-inventory format so keys still match Config.Items.

Important — weed_seed

If another resource registers the same item name with a different server export, players can see “Invalid seed item!” or wrong behavior. The weed_seed definition should use bs_weed’s server export (as in items/ox_inventory_items.lua). Merge after conflicting packs so bs_weed wins, or rename the conflicting item in the other resource.

6. Admin permissions (ACE)

For admin commands such as /setrep and /givexp, add:

add_ace group.admin cultivationrp.admin allow

Adjust group.admin to match your admin group in server.cfg.

---

Optional (but recommended): precision placement (object_gizmo)

If Config.UseObjectGizmoForPlacement is true in shared/config.lua, start the object_gizmo resource before or with your placement workflow so placeables (indoor pot, grow light, weed table, drying rack, rosin press) can use the 3D gizmo. Outdoor seed placement is unchanged. https://github.com/dodibanScripts/object_gizmo

---

After install — quick checks

1. Start the server with no script errors referencing bs_weed, ox_lib, or oxmysql.
2. Join in-game and confirm Bzzz props appear (no invisible/missing models near plants or placeables).
3. Open Pete’s (or your configured shop) and confirm shop items appear after the ox_inventory merge.
4. Use weed seed from inventory and confirm planting flow works.
5. Try /skilltree to confirm the NUI loads.

---

Useful reference (not full install)

---

Troubleshooting

Shop shows no items

• Items must exist in ox_inventory’s definitions. Re-merge items/ox_inventory_items.lua and restart ox_inventory or the server. Check Config.PedStoreItems and Config.PedStoreBeginnerOnly in shared/config.lua.

“Invalid seed item!”

• Another resource may own weed_seed. Ensure server = { export = 'bs_weed.seedItemCallback' } (or equivalent) wins for that item name.

Database errors

• Confirm oxmysql (or mysql-async) is running and connection string is correct. Confirm Config.Database matches what you use.

---

Version note

Script version is declared in fxmanifest.lua (version field). After Tebex updates, compare that version with your docs when reporting issues.