QB-Drugs - Substance System - QBCore Guide for FiveM

Introduction

This tutorial turns QB-Drugs - Substance System into a clean, developer-friendly guide for QBCore/FiveM. You will follow a step-by-step flow, copy the relevant code patterns, and learn the “why” behind the setup.

Requirements

• QBCore installed and running on a dev server
• Basic Lua knowledge and comfort reading FiveM patterns
• A test workflow for iterating safely (dev server, not production)
• Optional: a code editor with Lua/FiveM helpers (VS Code recommended)

Step-by-Step Guide

Step 1: Overview

In this step, you will apply the overview concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 2: Key Features

In this step, you will apply the key features concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 3: Installation

In this step, you will apply the installation concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 4: Prerequisites

In this step, you will apply the prerequisites concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 5: Installation Steps

In this step, you will apply the installation steps concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 6: Configuration

In this step, you will apply the configuration concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 7: Basic Configuration

In this step, you will apply the basic configuration concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 8: Law Enforcement Integration

In this step, you will apply the law enforcement integration concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Code Example

cd resources/[qb]
git clone https://github.com/qbcore-framework/qb-drugs.git

Tips & Best Practices

• Keep authority on the server: validate inputs before money/database operations.
• Start with one resource/module at a time, then refactor after you verify it works.
• Use callbacks for request/response flows and events for push/UX updates.
• When you run loops, avoid freezes: always yield with Wait() (client/server) and cache hot values.