Installation

Welcome to the Bablo Boosting installation guide! This guide will walk you through the complete installation process for our asset. By following each step carefully, you’ll ensure a smooth and hassle-free setup, provided that all instructions are followed thoroughly.

Download asset

To find the asset, you must have made the purchase using your own cfx account. Otherwise, you can use the transfer system to move the asset to a different cfx account.

After purchasing from our official website, the asset will be delivered directly to your CFX Portal. From your panel, you can download the asset and proceed with the installation using the provided documentation.

Setup CFG

To ensure everything functions correctly when you’re utilizing either the ESX framework or the QBCORE framework instead of the standalone version, it’s essential to adhere to the following steps carefully. Following these guidelines will help you achieve a seamless integration and maintain optimal performance across your systems.

When setting up your server environment, it is crucial to ensure that your core scripts are initialized before any additional resources. Specifically, the core resources such as es_extended or qb-core or qbx_core should be started first before you introduce other elements like the bablo-boosting resource. This order is essential for maintaining a stable and functional environment. Bablo Boosting only depends on ox_lib and oxmysql — it does not require xsound or any other sound resource.

LUA

-- First we will start the cores, never below
ensure es_extended or qb-core or qbx_core
ensure ox_lib
ensure oxmysql
 
-- Run bablo-boosting here
ensure bablo-boosting

Basic Configuration

Basic Framework Configuration

The asset will function automatically if your framework is named es_extended or qb-core or qbx_core, as it will detect either one when started (Config.Framework = "auto"). If your framework has been renamed, you can update its name in the config.lua file.

The same auto-detection applies to your inventory, target and dispatch resources — Config.Inventory, Config.Target and Config.Dispatch all default to 'auto'. Supported inventories are ox_inventory, qb-inventory, ps-inventory, qs-inventory, core_inventory, codem-inventory, origen_inventory and tgiann-inventory. Supported targets are ox_target and qb-target, with a standalone fallback if neither is running.

Setting up Items

To ensure the script functions correctly, follow this simple guide to add the necessary items.

To assist you in managing inventories, we’ve outlined the steps to create items for the supported inventories below. If you need guidance on creating items for other supported inventories not listed, please create a support ticket.

Navigate to your inventory resource (or item configuration), and add the following item:

LUA

['bboosting_tablet'] = {
    label = 'Boosting Tablet',
    weight = 1000,
    stack = false,
},

The essential item name must be bboosting_tablet — it is unique, useable and opens the boosting laptop when used. Add a matching bboosting_tablet.png image to your inventory’s images folder.

The default loot table also rewards metalscrap, copper, aluminum, plastic, rubber, iron, goldbar, rolex, cryptostick and diamond_ring. Most servers already have these standard items — add any that are missing to your inventory, or swap them for your own items in the Rewards tab of the in-game /boostingeditor.

Tablet Seller

The tablet is sold by a seller ped defined in Config.Seller. Players interact with the ped through ox_target / qb-target (or the standalone interaction), buy the bboosting_tablet item, and use the item to open the boosting UI — there is no command or keybind to open it.

LUA

Config.Seller = {
    enabled  = true,
    model    = 's_m_y_dealer_01',
    coords   = vector4(-1172.29, -1571.44, 4.66, 125.0),
    scenario = 'WORLD_HUMAN_SMOKING',
    price    = 5000,
    account  = 'cash',
    item     = 'bboosting_tablet',
    blip     = { enabled = false, sprite = 459, color = 27, scale = 0.7 },
}

You can freely change the ped model, coordinates, price and the account the purchase is charged to. Setting enabled = false removes the seller entirely — in that case, hand out the tablet item through your own shops or scripts instead.

Vehicle Keys

When a player steals a boost vehicle, the script hands over keys through Config.GiveVehicleKeys. This function must be adapted to match the key resource your server uses — the default targets qb-vehiclekeys:

LUA

-- Default (qb-vehiclekeys)
Config.GiveVehicleKeys = function(vehicle, plate)
    TriggerEvent('vehiclekeys:client:SetOwner', plate)
end
 
-- qs-vehiclekeys
exports['qs-vehiclekeys']:GiveKeys(plate, model, true)
 
-- wasabi_carlock
exports.wasabi_carlock:GiveKey(plate)

Replace the function body with the appropriate one-liner (or your own key logic) if you are not running qb-vehiclekeys.

Police & Dispatch

Each contract class requires a minimum number of police officers online before it can be started, configured in Config.Boosting.PoliceRequired:

LUA

PoliceRequired = { D = 0, C = 1, B = 2, A = 3, S = 4 }, -- min police online per class
PoliceJobs     = { 'police' },

Config.Boosting.PoliceJobs supports multiple LEO jobs — for example { 'police', 'sheriff' } — and every listed job counts towards the requirement.

Dispatch alerts are auto-detected (Config.Dispatch = 'auto') and support ps-dispatch, cd_dispatch, qs-dispatch, rcore_dispatch, tk_dispatch and lb-tablet, with a standalone fallback if none of these are running.

Database

Bablo Boosting stores player progression in the bablo_boosting_players table, which is created automatically on the first resource start — no SQL file needs to be imported. oxmysql is required for this, so make sure it is started before bablo-boosting as shown in the Setup CFG section.

Game build

The default vehicle pools in Config.Vehicles include Tuners-era models (such as calico, zr350, cypher and growler) which require game build 2372 or higher. Make sure your server is set to build 2372+ or replace those models with vehicles available on your build. All default vehicles are fixed-roof cars.