Bridge

Bridge System Documentation

Complete guide to the Bridge compatibility system for iSanz Labs

---

Table of Contents

• Introduction

• Bridge.Core

• Bridge.Gangs

• Bridge.Inventory

• Bridge.Interaction

• Bridge.MenuInput

• Bridge.Notify

• Bridge.Progressbar

• Bridge.Dispatch

• Bridge.MiniGames

• Custom Bridge Systems

• Popular System Examples

• Troubleshooting

---

Introduction

The Bridge system is a compatibility layer that allows iSanz Labs to work with different framework systems without code modifications. It automatically adapts to your server's configuration based on Config.Base settings.

How It Works

The Bridge system:

1. Detects which resources are installed on your server

2. Routes function calls to the appropriate system based on Config.Base

3. Provides a unified API for all systems

4. Handles system-specific differences automatically

Configuration

All Bridge systems read from Config.Base in shared/config.lua:

Config.Base = {
    core = 'qb-core',              -- Framework
    menu = 'iSanz-menu',           -- Menu system
    input = 'iSanz-input',         -- Input system
    interact = 'interact',         -- Interaction system
    inventory = 'qb-inventory',    -- Inventory system
    progressbar = 'qb',            -- Progressbar system
    notify = 'qb',                 -- Notification system
}

---

Bridge.Core

File: bridge/core.lua

Purpose: Core framework detection and player object retrieval.

Functions

Bridge.GetCore()

Returns the core framework object and framework name.

Returns:

• Core (table) - Framework core object

• Framework (string) - Framework name ("qb" or "qbx")

Example:

local Core, Framework = Bridge.GetCore()
print(Framework) -- "qb" or "qbx"

Bridge.GetPlayer(src)

Gets player object by server source ID.

Parameters:

• src (number) - Player server source ID

Returns:

• Player object or nil

Example:

local Player = Bridge.GetPlayer(source)
if Player then
    print(Player.PlayerData.citizenid)
end

Supported Frameworks

• QB-Core (qb-core)

• QBX-Core (qbx_core)

Auto-Detection

The Bridge automatically detects which framework is running:

if GetResourceState("qbx_core") == "started" then
    Framework = "qbx"
    Core = exports["qb-core"]:GetCoreObject()
elseif GetResourceState("qb-core") == "started" then
    Framework = "qb"
    Core = exports["qb-core"]:GetCoreObject()
end

---

Bridge.Gangs

File: bridge/gangs.lua

Purpose: Gang system integration for gang-based access control.

Functions

Bridge.Gangs.GetPlayerGang()

Gets current player's gang name (client-side).

Returns:

• string - Gang name or nil

Example:

local gangName = Bridge.Gangs.GetPlayerGang()
if gangName == "mafia" then
    print("Player is in mafia gang")
end

Bridge.Gangs.GetServerGang(source)

Gets player's gang name (server-side).

Parameters:

• source (number) - Player server source ID

Returns:

• string - Gang name or "none"

Example:

local gangName = Bridge.Gangs.GetServerGang(source)
if gangName == "mafia" then
    -- Allow access
end

Bridge.Gangs.GetPlayerGangData()

Gets full gang data object (client-side).

Returns:

• table - Gang data object or nil

Example:

local gangData = Bridge.Gangs.GetPlayerGangData()
if gangData then
    print(gangData.name)    -- Gang name
    print(gangData.label)   -- Gang label
    print(gangData.grade)   -- Player's grade
end

Bridge.Gangs.GetServerGangData(source)

Gets full gang data object (server-side).

Parameters:

• source (number) - Player server source ID

Returns:

• table - Gang data object or nil

Bridge.Gangs.IsPlayerInGang(source, gangName)

Checks if player is in a specific gang.

Parameters:

• source (number) - Player server source ID

• gangName (string) - Gang name to check

Returns:

• boolean - true if player is in gang

Example:

if Bridge.Gangs.IsPlayerInGang(source, "mafia") then
    -- Player is in mafia
end

Bridge.Gangs.GetAllGangs()

Gets list of all gangs in the framework.

Returns:

• table - Array of gang objects {key = "gang_key", name = "Gang Name"}

Example:

local gangs = Bridge.Gangs.GetAllGangs()
for _, gang in ipairs(gangs) do
    print(gang.key, gang.name)
end

Bridge.Gangs.SetCustomGangSystem(customSystem)

Sets a custom gang system for non-standard implementations.

Parameters:

• customSystem (table) - Custom system with functions:

  • GetPlayerGang() - Client-side gang name

  • GetServerGang(source) - Server-side gang name

  • GetPlayerGangData() - Client-side gang data

  • GetServerGangData(source) - Server-side gang data

  • GetAllGangs() - All gangs list

Example:

Bridge.Gangs.SetCustomGangSystem({
    GetPlayerGang = function()
        -- Your custom code
        return exports['custom-gangs']:GetPlayerGang()
    end,
    GetServerGang = function(source)
        return exports['custom-gangs']:GetServerGang(source)
    end
})

Supported Systems

• QB-Core Gangs - Uses Core.Shared.Gangs

• QBX-Core Gangs - Uses exports.qbx_core:GetGangs()

• Custom Systems - Via SetCustomGangSystem()

---

Bridge.Inventory

File: bridge/inventory.lua

Purpose: Inventory system integration for item management.

Configuration

Set Config.Base.inventory to your inventory system:

• qb-inventory

• ox_inventory

• ps-inventory

• qs-inventory

Functions

Bridge.Inventory.Search(item)

Searches for item in player inventory (client-side).

Parameters:

• item (string) - Item name

Returns:

• number - Item count

Example:

local count = Bridge.Inventory.Search('bud_bluedream')
if count >= 5 then
    print("Player has enough buds")
end

Bridge.Inventory.GetItemCount(source, item)

Gets item count from player inventory (server-side).

Parameters:

• source (number) - Player server source ID

• item (string) - Item name

Returns:

• number - Item count

Example:

local count = Bridge.Inventory.GetItemCount(source, 'bud_bluedream')
if count >= 10 then
    Bridge.Inventory.RemoveItem(source, 'bud_bluedream', 10)
end

Bridge.Inventory.AddItem(source, item, quantity, metadata)

Adds item to player inventory (server-side).

Parameters:

• source (number) - Player server source ID

• item (string) - Item name

• quantity (number) - Quantity to add

• metadata (table, optional) - Item metadata

Example:

Bridge.Inventory.AddItem(source, 'bluedream_bag', 1, {
    uses = 3,
    quality = 100
})

Bridge.Inventory.RemoveItem(source, item, quantity, slot)

Removes item from player inventory (server-side).

Parameters:

• source (number) - Player server source ID

• item (string) - Item name

• quantity (number) - Quantity to remove

• slot (number, optional) - Specific slot to remove from

Example:

Bridge.Inventory.RemoveItem(source, 'bud_bluedream', 5)

Bridge.Inventory.GetItemMetadata(source, item, slot)

Gets item metadata from specific slot.

Parameters:

• source (number) - Player server source ID

• item (string) - Item name

• slot (number) - Slot number

Returns:

• table - Metadata or empty table

Example:

local metadata = Bridge.Inventory.GetItemMetadata(source, 'rolling_paper', 1)
if metadata.uses then
    print("Rolling paper has " .. metadata.uses .. " uses left")
end

Bridge.Inventory.UpdateItemMetadata(source, item, slot, metadata)

Updates item metadata in specific slot.

Parameters:

• source (number) - Player server source ID

• item (string) - Item name

• slot (number) - Slot number

• metadata (table) - New metadata

Example:

local metadata = Bridge.Inventory.GetItemMetadata(source, 'rolling_paper', 1)
metadata.uses = (metadata.uses or 3) - 1
Bridge.Inventory.UpdateItemMetadata(source, 'rolling_paper', 1, metadata)

Bridge.Inventory.OpenStash(stashName, options)

Opens a stash inventory (client-side).

Parameters:

• stashName (string) - Stash identifier

• options (table, optional) - Stash options:

  • maxWeight (number) - Maximum weight

  • slots (number) - Number of slots

Example:

Bridge.Inventory.OpenStash("lab_stash_1", {
    maxWeight = 1000000,
    slots = 50
})

Bridge.Inventory.Stash(gang)

Opens lab stash for specific gang (client-side).

Parameters:

• gang (string) - Gang name

Example:

local gangName = Bridge.Gangs.GetPlayerGang()
Bridge.Inventory.Stash(gangName) -- Opens "mafia_weedlab" stash

Bridge.Inventory.CreateUsableItem(item, callback)

Registers a usable item with callback.

Parameters:

• item (string) - Item name

• callback (function) - Callback function function(source) end

Example:

Bridge.Inventory.CreateUsableItem('weed_joint', function(source)
    -- Player used weed_joint
    TriggerClientEvent('iSanz_Labs:client:SmokeJoint', source)
end)

System-Specific Implementations

QB-Inventory / PS-Inventory

Uses QB-Core player objects and exports:

exports['qb-inventory']:AddItem(source, item, quantity, nil, metadata)
exports['qb-inventory']:RemoveItem(source, item, quantity)

OX Inventory

Uses OX Inventory exports:

exports.ox_inventory:AddItem(source, item, quantity, metadata)
exports.ox_inventory:RemoveItem(source, item, quantity)
exports.ox_inventory:Search('count', item)

QS Inventory

Uses QS Inventory exports:

exports['qs-inventory']:AddItem(source, item, quantity)
exports['qs-inventory']:getUserInventory(source)

---

Bridge.Interaction

File: bridge/interaction.lua

Purpose: World interaction system integration (E key interactions, targeting, etc.).

Configuration

Set Config.Base.interact to your interaction system:

• interact - Custom interaction system (default)

• qb-target - QB-Target

• ox_target - OX Target

Functions

Bridge.Interaction.AddInteraction(data)

Adds an interaction point in the world.

Parameters:

• data (table) - Interaction data:

  • id (string) - Unique interaction ID

  • coords (vector3) - World coordinates

  • distance (number, optional) - Detection distance (default: 2.0)

  • interactDst (number, optional) - Interaction distance (default: 1.5)

  • interactionType (string, optional) - Type for sprite (default: 'key')

  • options (table, optional) - Interaction options

  • entity (number, optional) - Entity handle

  • ignoreLos (boolean, optional) - Ignore line of sight check

Options Format:

{
    {
        label = "Interact",
        icon = "fas fa-circle",
        action = function() end,      -- Direct function
        event = "event:name",         -- Event name
        isServer = false,             -- Server event (if event used)
        args = {},                    -- Event arguments
        job = {"police"},             -- Required job
        gang = {"mafia"},             -- Required gang
        canInteract = function()      -- Can interact check
            return true
        end
    }
}

Example - Custom System:

Bridge.Interaction.AddInteraction({
    id = "lab_door",
    coords = vector3(100.0, 200.0, 30.0),
    distance = 3.0,
    interactDst = 2.0,
    interactionType = "door",
    options = {
        {
            label = "Open Door",
            icon = "fas fa-door-open",
            action = function()
                OpenLabDoor()
            end
        }
    }
})

Example - QB-Target:

-- Automatically converted to QB-Target format
Bridge.Interaction.AddInteraction({
    id = "lab_table",
    coords = vector3(150.0, 250.0, 30.0),
    options = {
        {
            label = "Use Table",
            icon = "fas fa-table",
            event = "iSanz_Labs:client:UseTable",
            gang = {"mafia"}
        }
    }
})

Example - OX Target:

-- Automatically converted to OX Target format
Bridge.Interaction.AddInteraction({
    id = "lab_stash",
    coords = vector3(200.0, 300.0, 30.0),
    options = {
        {
            label = "Open Stash",
            icon = "fas fa-box",
            event = "iSanz_Labs:client:OpenStash"
        }
    }
})

Bridge.Interaction.RemoveInteraction(id)

Removes an interaction point.

Parameters:

• id (string) - Interaction ID

Example:

Bridge.Interaction.RemoveInteraction("lab_door")

System-Specific Details

Custom Interaction System (interact)

Uses custom sprite rendering and E key detection:

• Requires Config.Interactions configuration

• Uses DrawInteractionSprite() function

• Shows sprites based on interactionType

• Supports entity-based interactions

QB-Target (qb-target)

Converts to QB-Target format:

exports['qb-target']:AddCircleZone(id, coords, distance, options)

OX Target (ox_target)

Converts to OX Target format:

exports.ox_target:addBoxZone({
    coords = coords,
    size = vector3(distance, distance, height),
    options = options
})

---

Bridge.MenuInput

File: bridge/menu_input.lua

Purpose: Menu and input dialog system integration.

Configuration

Set Config.Base.menu and Config.Base.input:

• Menu: iSanz-menu, qb-menu, ox_lib

• Input: iSanz-input, qb-input, ox_lib

Functions

Bridge.MenuInput.OpenMenu(menu, menuId)

Opens a menu dialog.

Parameters:

• menu (table) - Menu items array

• menuId (string, optional) - Menu ID for tracking

Menu Format:

{
    {
        header = "Menu Title",
        isMenuHeader = true  -- First item is header
    },
    {
        header = "Option 1",
        txt = "Description",
        icon = "fas fa-icon",
        params = {
            event = "event:name",
            args = {},
            isServer = false,
            isAction = false,
            action = function() end
        }
    }
}

Example:

local menu = {
    {
        header = "Lab Menu",
        isMenuHeader = true
    },
    {
        header = "Open Shop",
        txt = "Browse lab products",
        icon = "fas fa-shopping-cart",
        params = {
            event = "iSanz_Labs:client:OpenShop"
        }
    },
    {
        header = "Manage Plants",
        txt = "View and manage plants",
        icon = "fas fa-seedling",
        params = {
            event = "iSanz_Labs:client:ManagePlants"
        }
    }
}

Bridge.MenuInput.OpenMenu(menu, "lab_main_menu")

Bridge.MenuInput.OpenInput(inputData, inputType, inputContext)

Opens an input dialog.

Parameters:

• inputData (table) - Input configuration

• inputType (string) - Input type identifier

• inputContext (table, optional) - Context data

Input Format:

{
    header = "Input Title",
    submitText = "Submit",
    inputs = {
        {
            text = "Label",
            name = "input_name",
            type = "text",        -- text, number, password, etc.
            isRequired = true,
            default = "",
            disabled = false
        }
    }
}

Example:

local inputData = {
    header = "Enter Password",
    submitText = "Confirm",
    inputs = {
        {
            text = "Password",
            name = "password",
            type = "password",
            isRequired = true
        }
    }
}

Bridge.MenuInput.OpenInput(inputData, "password_input", {gang = "mafia"})

Handling Input Response:

Set callback before opening input:

Bridge.MenuInput.OnInputSubmit = function(data, inputType, inputContext)
    if inputType == "password_input" then
        local password = data.password
        -- Handle password
    end
end

Bridge.MenuInput.OnInputCancel = function(inputType, inputContext)
    -- Handle cancellation
end

Bridge.MenuInput.CloseMenu()

Closes the current menu.

Example:

Bridge.MenuInput.CloseMenu()

Bridge.MenuInput.CloseInput()

Closes the current input dialog.

Example:

Bridge.MenuInput.CloseInput()

System-Specific Implementations

QB-Menu / QB-Input

Menu:

exports['qb-menu']:openMenu(menuOptions)

Input:

exports['qb-input']:ShowInput(inputData, callback)

OX Lib

Menu:

lib.registerContext({
    id = menuId,
    title = title,
    options = options
})
lib.showContext(menuId)

Input:

local result = lib.inputDialog(title, inputs)

iSanz-Menu / iSanz-Input

Uses NUI-based system:

• Sends NUI messages

• Uses SetNuiFocus() for focus control

• Requires HTML/JS implementation

---

Bridge.Notify

File: bridge/notify.lua

Purpose: Notification system integration for player messages.

Configuration

Set Config.Base.notify:

• qb - QB-Core notifications

• ox_lib - OX Lib notifications

Functions

Bridge.Notify.Client(text, notifyType, duration)

Sends notification to local player (client-side).

Parameters:

• text (string) - Notification message

• notifyType (string, optional) - Type: success, error, primary, info, warning

• duration (number, optional) - Duration in milliseconds (default: 5000)

Example:

Bridge.Notify.Client("Plant watered successfully!", "success", 3000)
Bridge.Notify.Client("Not enough items!", "error")
Bridge.Notify.Client("Processing...", "primary")

Bridge.Notify.Server(source, text, notifyType, duration)

Sends notification to specific player (server-side).

Parameters:

• source (number) - Player server source ID

• text (string) - Notification message

• notifyType (string, optional) - Notification type

• duration (number, optional) - Duration in milliseconds

Example:

Bridge.Notify.Server(source, "Lab hacked successfully!", "success")
Bridge.Notify.Server(source, "Insufficient funds!", "error", 5000)

Bridge.Notify.All(text, notifyType, duration)

Sends notification to all players.

Parameters:

• text (string) - Notification message

• notifyType (string, optional) - Notification type

• duration (number, optional) - Duration in milliseconds

Example:

Bridge.Notify.All("Server maintenance in 5 minutes", "warning")

Notification Types

QB-Core:

• success - Green success message

• error - Red error message

• primary - Blue primary message

• info - Info message

OX Lib:

• success - Success message

• error - Error message

• inform - Info message (converted from primary/info)

• warning - Warning message

System-Specific Implementations

QB-Core

Core.Functions.Notify(text, notifyType, duration)
TriggerClientEvent('QBCore:Notify', source, text, notifyType, duration)

OX Lib

lib.notify({
    description = text,
    type = notifyType,
    duration = duration
})
exports.ox_lib:Notify(source, {...})

---

Bridge.Progressbar

File: bridge/progressbar.lua

Purpose: Progress bar system integration for timed actions.

Configuration

Set Config.Base.progressbar:

• qb - QB-Core progressbar

• ox - OX Lib progressbar

Function

StartProgressbar(progressType, callback, cancelCallback, customLabel, customDuration)

Starts a progress bar with animation and props.

Parameters:

• progressType (string) - Predefined progress type

• callback (function, optional) - Function to call on completion

• cancelCallback (function, optional) - Function to call on cancellation

• customLabel (string, optional) - Custom label text

• customDuration (number, optional) - Custom duration in milliseconds

Predefined Types:

• lab_hack_prep - Lab hack preparation (2 seconds)

• lab_hack_finish - Lab hack completion (3 seconds)

• laptop_hack_prep - Laptop hack (2 seconds)

• deal_items - Item dealing (5 seconds)

• collect_items - Item collection (3 seconds, with animation)

• smoke_joint - Smoking joint (3 seconds, with joint prop)

• water_plant - Watering plant (3.5 seconds, with watering can)

• fertilize_plant - Fertilizing (3.5 seconds, with fertilizer)

• harvest_plant - Harvesting (3.5 seconds, with animation)

• plant_seed - Planting seed (5 seconds, with trowel)

• craft_baggy - Bagging buds (5 seconds)

• craft_baggy_seated - Seated bagging (8 seconds)

• craft_doll - Crafting doll (8 seconds)

• rolling_joint - Rolling joint (8 seconds)

Example:

StartProgressbar("water_plant", function()
    -- Plant watered successfully
    WaterPlant()
end, function()
    -- Cancelled
    Bridge.Notify.Client("Cancelled", "error")
end)

Custom Progress Bar:

StartProgressbar("plant_seed", function()
    PlantSeed()
end, nil, "Planting Blue Dream Seed...", 10000) -- 10 seconds

Progress Bar Configuration

Each progress type has:

• name - Internal identifier

• label - Display text

• duration - Default duration (milliseconds)

• disableMovement - Disable player movement

• disableCarMovement - Disable vehicle movement

• disableMouse - Disable mouse input

• disableCombat - Disable combat

• anim - Animation dictionary and clip

• prop - Prop model and attachment

Animation Format:

anim = {
    animDict = "anim@dict",
    anim = "animation_name",
    flags = 49  -- Animation flags
}

Prop Format:

prop = {
    model = "prop_model",
    bone = 57005,  -- Bone ID
    pos = vec3(0.0, 0.0, 0.0),  -- Position offset
    rot = vec3(0.0, 0.0, 0.0)   -- Rotation offset
}

System-Specific Implementations

QB-Core

Core.Functions.Progressbar(name, label, duration, useWhileDead, canCancel, {
    disableMovement = true,
    disableCarMovement = true,
    disableMouse = false,
    disableCombat = true
}, animData, propData, {}, callback, cancelCallback)

OX Lib

lib.progressBar({
    label = label,
    duration = duration,
    disable = {
        move = true,
        car = true,
        mouse = false,
        combat = true
    },
    anim = {
        dict = animDict,
        clip = anim,
        flag = flags
    },
    prop = {
        model = propModel,
        bone = propBone,
        pos = {x, y, z},
        rot = {x, y, z}
    },
    onFinish = callback,
    onCancel = cancelCallback
})

---

Bridge.Dispatch

File: bridge/dispatch.lua

Purpose: Police dispatch system integration for alerts.

Configuration

Configure in Config.Dispatch:

Config.Dispatch = {
    system = "qb",  -- qb | ps | cd | custom
    title = "Suspicious Sale",
    code = "10-90",
    message = "Suspicious street sale reported.",
    blip = {
        sprite = 161,
        color = 1,
        scale = 1.2
    }
}

Function

Bridge.Dispatch.PoliceAlert(coords)

Sends police dispatch alert.

Parameters:

• coords (vector3) - Alert location coordinates

Example:

local coords = GetEntityCoords(PlayerPedId())
Bridge.Dispatch.PoliceAlert(coords)

Supported Systems

QB-Core (qb)

TriggerEvent("police:server:policeAlert", coords, title)

Project Sloth (ps)

TriggerEvent('ps-dispatch:server:notify', {
    coords = coords,
    message = message,
    code = code,
    title = title,
    blip = {sprite, color, scale}
})

Core Dispatch (cd)

TriggerEvent('cd_dispatch:AddNotification', {
    job_table = {"police"},
    coords = coords,
    title = title,
    message = message,
    flash = false,
    unique_id = unique_id,
    blip = {sprite, scale, colour, text}
})

Custom (custom)

No implementation (requires custom code).

---

Bridge.MiniGames

File: bridge/minigames.lua

Purpose: Minigame system for hacking challenges.

Function

PlayHackGame(type, options)

Plays a hack minigame.

Parameters:

• type (string) - Minigame type: digit, minesweeper, custom

• options (table, optional) - Minigame options

Returns:

• boolean - true if completed successfully

Example:

local success = PlayHackGame("minesweeper")
if success then
    print("Hack successful!")
else
    print("Hack failed!")
end

Supported Types

Digit (digit)

Uses bl_ui resource:

exports.bl_ui:DigitDazzle(1, {
    length = 1,
    duration = 1000000
})

Minesweeper (minesweeper)

Uses bl_ui resource:

exports.bl_ui:MineSweeper(1, {
    grid = 3,
    duration = 10000,
    target = 2,
    previewDuration = 2000
})

Custom (custom)

Requires custom implementation in bridge/minigames.lua:

function PlayHackGame(type, options)
    if type == "custom_type" then
        return exports['your_minigame']:Start(options)
    end
    return false
end

Configuration

Set in Config.MiniGames:

Config.MiniGames = {
    LabHack = 'digit',
    LaptopHack = 'minesweeper'
}

---

Custom Bridge Systems

You can extend the Bridge system for custom implementations:

Custom Gang System

-- In your resource's client/server script
Bridge.Gangs.SetCustomGangSystem({
    GetPlayerGang = function()
        return exports['custom-gangs']:GetPlayerGang()
    end,
    GetServerGang = function(source)
        return exports['custom-gangs']:GetServerGang(source)
    end,
    GetAllGangs = function()
        return exports['custom-gangs']:GetAllGangs()
    end
})

Custom Dispatch System

Modify bridge/dispatch.lua:

elseif system == "custom" then
    -- Your custom dispatch code
    exports['custom-dispatch']:SendAlert({
        coords = loc,
        title = dispatchCfg.title,
        message = dispatchCfg.message
    })
end

---

Popular System Examples

Example 1: QB-Core + QB-Inventory + QB-Menu

Config:

Config.Base = {
    core = 'qb-core',
    menu = 'qb-menu',
    input = 'qb-input',
    interact = 'qb-target',
    inventory = 'qb-inventory',
    progressbar = 'qb',
    notify = 'qb'
}

Usage:

• Uses QB-Core player objects

• QB-Inventory exports

• QB-Menu for menus

• QB-Target for interactions

• QB-Core notifications and progressbars

Example 2: QB-Core + OX Inventory + OX Lib

Config:

Config.Base = {
    core = 'qb-core',
    menu = 'ox_lib',
    input = 'ox_lib',
    interact = 'ox_target',
    inventory = 'ox_inventory',
    progressbar = 'ox',
    notify = 'ox_lib'
}

Usage:

• QB-Core for framework

• OX Inventory for items

• OX Lib for menus, inputs, progressbars, notifications

• OX Target for interactions

Example 3: QBX-Core + OX Inventory

Config:

Config.Base = {
    core = 'qbx_core',
    menu = 'ox_lib',
    input = 'ox_lib',
    interact = 'ox_target',
    inventory = 'ox_inventory',
    progressbar = 'ox',
    notify = 'ox_lib'
}

Usage:

• QBX-Core framework (detected automatically)

• Full OX Lib integration

• OX Inventory for items

Example 4: Custom Interaction System

Config:

Config.Base = {
    core = 'qb-core',
    menu = 'iSanz-menu',
    input = 'iSanz-input',
    interact = 'interact',  -- Custom system
    inventory = 'qb-inventory',
    progressbar = 'qb',
    notify = 'qb'
}

Usage:

• Custom sprite-based interactions

• Requires Config.Interactions configuration

• Uses NUI-based menu/input system

---

Troubleshooting

Bridge System Not Working

Problem: Bridge functions return nil or don't work.

Solutions:

1. Check resource names match Config.Base exactly

2. Ensure resources are started before iSanz_Labs

3. Verify resource names in fxmanifest.lua dependencies

4. Check server console for Bridge errors

Inventory Functions Not Working

Problem: Items not adding/removing correctly.

Solutions:

1. Verify Config.Base.inventory matches your inventory resource name

2. Check item names exist in your inventory database

3. Ensure inventory resource exports are working

4. Test inventory exports directly in server console

Interaction System Not Showing

Problem: Interactions don't appear.

Solutions:

1. Check Config.Base.interact setting

2. For custom system, ensure Config.Interactions is configured

3. Verify interaction coordinates are correct

4. Check if target system (qb-target/ox_target) is running

Menu/Input Not Opening

Problem: Menus or inputs don't open.

Solutions:

1. Verify menu/input resource names in Config.Base

2. Check if resources are started

3. For NUI systems, verify HTML files are loaded

4. Check browser console (F8) for NUI errors

Notifications Not Showing

Problem: Notifications don't appear.

Solutions:

1. Check Config.Base.notify setting

2. Verify notification resource is running

3. Test notification exports directly

4. Check for console errors

---

Summary

The Bridge system provides a unified API for multiple framework systems:

• Bridge.Core - Framework detection and player objects

• Bridge.Gangs - Gang system integration

• Bridge.Inventory - Item management

• Bridge.Interaction - World interactions

• Bridge.MenuInput - Menus and inputs

• Bridge.Notify - Notifications

• Bridge.Progressbar - Progress bars

• Bridge.Dispatch - Police alerts

• Bridge.MiniGames - Hacking minigames

All systems automatically adapt based on Config.Base settings, providing seamless compatibility across different server setups.

---

Support

• Documentation: This file

• Version: v3.0.0-BETA

• Last Updated: 2025

---

Note: Always test Bridge configuration changes on a development server before applying to production. Resource names must match exactly (case-sensitive).