Installation

Installation Guide

Requirements

Required on every server

Pick one framework

Pick one phone

---

Step 1 — Database

Import the install schema once (HeidiSQL, phpMyAdmin, or CLI):

source sql/install.sql

Or import sql/install.sql in your SQL client. This creates all Chow Drop tables. You do not need separate migration files.

---

Step 2 — Install the resource

1. Place the folder as bs_chowdrop in your resources directory (path may vary, e.g. resources/[standalone]/bs_chowdrop).
2. Open config.lua and set framework / phone (or leave "auto" — see Config Guide).
3. Ensure dependencies start before Chow Drop.

---

Step 3 — server.cfg

QBX + lb-phone

ensure ox_libensure ox_targetensure oxmysqlensure ox_inventoryensure qbx_coreensure lb-phoneensure bs_chowdrop

QB-Core — use ensure qb-core instead of qbx_core. ESX — use ensure es_extended. CodeM — use ensure codem-phone instead of lb-phone.

Restart the server or ensure bs_chowdrop after a first-time install.

---

Step 4 — Inventory item

Chow Drop uses a food container for driver pickups.

1. Open items.lua in the Chow Drop resource (reference definition for cd_food_container).
2. Add that item to ox_inventory/data/items.lua.
3. Copy cd_food_container.png into ox_inventory/web/images/ (if provided with the package).

Restart ox_inventory (or the server) after adding the item.

---

Step 5 — Create businesses (required for player orders)

1. In-game, run /cd_admin (permissioned staff).
2. Create a business and set:
   • Display name
   • Job name (must match your framework job, e.g. burgershot)
   • Pickup coordinates (driver GPS for that restaurant)
3. Create a menu for that business.
4. Add menu items (ox inventory name, price, optional ox inventory image name).
5. Have a player with that job go on duty, open Chow Drop → Staff, and toggle the restaurant Open.

NPC deliveries work without a /cd_admin business (they use built-in NPC restaurant/delivery locations). Player ordering requires businesses + menus as above.

---

Step 6 — Verify

---

Post-install checklist

• sql/install.sql imported
• cd_food_container in ox_inventory
• Framework + phone ensured before bs_chowdrop
• Config.Framework / Config.Phone correct (or auto)
• Config.SoloTestMode = false on live
• At least one business + menu for player orders
• ESX: duty mode configured (see Config Guide)

---

Common install issues

---

Configuration Guide

All buyer-facing options live in config.lua (escrow-ignored). Do not replace the whole file with Config = {} — that wipes escrowed NPC restaurants/locations. The file correctly uses Config = Config or {}.

---

Framework & phone

Config.Framework = "auto" -- "qbx" | "qb" | "esx" | "auto"Config.Phone = "auto" -- "lb-phone" | "codem-phone" | "auto"Config.ESXDutyMode = "job" -- ESX only

ESX duty

• job — job.onDuty / job.onduty (common forks)
• metadata — xPlayer.get("duty") / meta
• always — any holder of the restaurant job counts as on duty (not for live)

Player IDs are stored in DB columns named citizenid (QBX/QB citizenid, or ESX identifier).

---

App listing (phone store / home)

Config.Identifier = "bs_chowdrop" -- unique app id (do not change after go-live)Config.Name = "Chow Drop"Config.Description = "Deliver food, earn money, climb the ranks!"Config.Developer = "Beetle Studios"Config.DefaultApp = true -- pre-installed on home when supported

---

General

Config.Debug = false -- verbose client/server/UI logs when trueConfig.SoloTestMode = false -- MUST be false on liveConfig.DistanceUnits = 'imperial' -- 'metric' | 'imperial'

---

XP & leveling (Config.XP)

• orderRadius — how far away a job can spawn relative to the driver (meters).
• maxDeliveryDistance — max restaurant → drop-off trip length for that level.

Raise radii if drivers see too few NPC jobs; lower if the map feels flooded.

---

Ratings (Config.Rating)

---

Payment (Config.Payment)

---

Orders (Config.Orders)

---

NPC locations (editable extras)

Escrowed NPC restaurants and delivery spots load automatically. Add more without editing escrowed files:

Config.ExtraRestaurants = {-- {-- name = "My Custom Spot",-- coords = vec4(x, y, z, heading),-- blipSprite = 106,-- blipColor = 1,-- items = { "Burger", "Fries" },-- pedModel = "s_m_y_busboy_01"-- },}Config.ExtraDeliveryLocations = {-- { name = "Custom Residence", coords = vec4(x, y, z, h), type = "house" },}

Also configurable:

• Config.CustomerNames — NPC customer name pool
• Config.DeliveryCustomerPeds — ped models for drop-off NPCs
• Config.DoorDeliveryChance — % chance of door drop vs ped (0–100)

---

Blips (Config.Blips)

Config.Blips = {Pickup = { sprite = 478, color = 5, scale = 1.0 },Delivery = { sprite = 501, color = 2, scale = 1.0 }}

---

Admin commands (Config.Admin)

Defaults (rename if they clash with other scripts):

Wire these to your ace/permissions system as you do for other admin tools.

---

Leaderboard (Config.Leaderboard)

---

What you should not edit

• Escrowed NPC location files (use ExtraRestaurants / ExtraDeliveryLocations instead)
• Core bridge logic unless you know your phone/framework fork needs it
• Do not reset Config = {} at the top of config.lua

---

Quick live-server defaults

Config.Framework = "qbx" -- or qb / esxConfig.Phone = "lb-phone" -- or codem-phoneConfig.Debug = falseConfig.SoloTestMode = falseConfig.Payment.CollectInApp = trueConfig.Payment.AccountType = "bank"