WP Bridge

Current version: 1.2.6

WP Bridge is the central integration layer required by WaCKPaCK Development Studios resources.

It allows supported WaCKPaCK resources to work across multiple frameworks, inventories, target systems, fuel systems, vehicle-key resources, and dispatch systems without requiring separate versions of each resource.

Features

WP Bridge provides:

Framework integration
Inventory integration
Target-system integration
Vehicle fuel integration
Vehicle-key integration
Dispatch integration
Automatic framework detection
Optional provider auto-detection
Startup validation
Runtime diagnostics
Centralized version checking
Custom-provider support

Requirements

WP Bridge requires:

A supported FiveM framework
The provider resources selected in config.lua
Correct server start order
Any dependencies required by your selected providers

WaCKPaCK resources that depend on WP Bridge must start after it.

Supported Providers

Frameworks

Provider	Configuration value	Default resource name
Qbox	`qbx`	`qbx_core`
QBCore	`qb`	`qb-core`
ESX Legacy	`esx`	`es_extended`
Custom	`custom`	Customer configured

Inventories

Provider	Configuration value	Default resource name
ox_inventory	`ox_inventory`	`ox_inventory`
qb-inventory	`qb_inventory`	`qb-inventory`
ESX default inventory	`esx_default`	`es_extended`
Custom	`custom`	Customer configured
Disabled	`none`	None

Target Systems

Provider	Configuration value	Default resource name
ox_target	`ox_target`	`ox_target`
qb-target	`qb_target`	`qb-target`
Custom	`custom`	Customer configured
Disabled	`none`	None

Fuel Systems

Provider	Configuration value	Default resource name
ox_fuel	`ox_fuel`	`ox_fuel`
LegacyFuel	`legacy_fuel`	`LegacyFuel`
CDN Fuel	`cdn_fuel`	`cdn-fuel`
TAM Fuel	`tam_fuel`	`TAM_Fuel`
LC Fuel	`lc_fuel`	`lc_fuel`
Custom	`custom`	Customer configured
Disabled	`none`	None

Vehicle-Key Systems

Provider	Configuration value	Default resource name
Wasabi Carlock	`wasabi_carlock`	`wasabi_carlock`
MrNewbVehicleKeys	`mrnewb_vehiclekeys`	`MrNewbVehicleKeys`
QBCore Vehicle Keys	`qb_vehiclekeys`	`qb-vehiclekeys`
Qbox Vehicle Keys	`qbx_vehiclekeys`	`qbx_vehiclekeys`
Renewed Vehiclekeys	`renewed_vehiclekeys`	`Renewed-Vehiclekeys`
Custom	`custom`	Customer configured
Disabled	`none`	None

Dispatch Systems

Provider	Configuration value	Default resource name
LB Tablet	`lb_tablet`	`lb-tablet`
rcore_dispatch	`rcore_dispatch`	`rcore_dispatch`
ps-dispatch	`ps_dispatch`	`ps-dispatch`
Codesign Dispatch	`cd_dispatch`	`cd_dispatch`
Codesign Dispatch 3D	`cd_dispatch3d`	`cd_dispatch3d`
core_dispatch	`core_dispatch`	`core_dispatch`
Custom	`custom`	Customer configured
Disabled	`none`	None

Installation

Place the wp_bridge folder inside your FiveM resources directory.

Example:

resources/
└── [wackpack]/
    └── wp_bridge/

Add WP Bridge to your server.cfg after its selected providers.

Example:

ensure ox_lib
ensure qbx_core
ensure ox_inventory
ensure ox_target
ensure ox_fuel
ensure wasabi_carlock
ensure lb-tablet

ensure wp_bridge

WaCKPaCK resources must start after WP Bridge:

ensure wp_bridge
ensure wp_moneywash
ensure wp_underworld
ensure wp_missions

Important

Starting a dependent WaCKPaCK resource before WP Bridge may cause missing exports, failed integrations, or startup errors.

Basic Configuration

Provider selections are located near the top of config.lua.

Config.Framework = 'auto'
Config.Inventory = 'ox_inventory'
Config.Target = 'ox_target'
Config.Fuel = 'ox_fuel'
Config.Keys = 'wasabi_carlock'
Config.Dispatch = 'lb_tablet'

Explicit provider selection is recommended for production servers.

The framework may normally remain set to:

Config.Framework = 'auto'

because most servers run only one supported framework.

Framework Configuration

Config.Framework = 'auto'

Available values:

auto
qbx
qb
esx
custom

Examples:

Config.Framework = 'qbx'

Config.Framework = 'qb'

Config.Framework = 'esx'

Inventory Configuration

Config.Inventory = 'ox_inventory'

Available values:

ox_inventory
qb_inventory
esx_default
custom
none

Examples:

Config.Inventory = 'qb_inventory'

Config.Inventory = 'esx_default'

Use none only when the WaCKPaCK resource does not require inventory support.

Target Configuration

Config.Target = 'ox_target'

Available values:

ox_target
qb_target
custom
none

Examples:

Config.Target = 'qb_target'

Config.Target = 'none'

Use none only when the dependent WaCKPaCK resource supports a non-target interaction mode.

Fuel Configuration

Config.Fuel = 'ox_fuel'

Available values:

ox_fuel
auto
legacy_fuel
cdn_fuel
tam_fuel
lc_fuel
custom
none

Examples:

Config.Fuel = 'legacy_fuel'

Config.Fuel = 'cdn_fuel'

Config.Fuel = 'none'

Vehicle-Key Configuration

Config.Keys = 'wasabi_carlock'

Available values:

wasabi_carlock
auto
mrnewb_vehiclekeys
qb_vehiclekeys
qbx_vehiclekeys
renewed_vehiclekeys
custom
none

Examples:

Config.Keys = 'qb_vehiclekeys'

Config.Keys = 'qbx_vehiclekeys'

Config.Keys = 'renewed_vehiclekeys'

Dispatch Configuration

Config.Dispatch = 'lb_tablet'

Available values:

lb_tablet
auto
rcore_dispatch
ps_dispatch
cd_dispatch
cd_dispatch3d
core_dispatch
custom
none

Examples:

Config.Dispatch = 'ps_dispatch'

Config.Dispatch = 'rcore_dispatch'

Config.Dispatch = 'none'

Use none only when dispatch support is not required.

Automatic Detection

Supported providers may be selected automatically.

Example:

Config.Dispatch = 'auto'

WP Bridge checks providers in the order listed under:

Config.AutoDetect

Example dispatch detection order:

dispatch = {
    'lb_tablet',
    'rcore_dispatch',
    'ps_dispatch',
    'cd_dispatch3d',
    'cd_dispatch',
    'core_dispatch'
}

Explicit selection is recommended because it prevents the wrong provider from being selected when multiple supported resources are installed.

Resource Folder Names

Provider resource names are configured under:

Config.Resources

Example:

Config.Resources = {
    qbx = 'qbx_core',
    qb = 'qb-core',
    esx = 'es_extended',

    ox_inventory = 'ox_inventory',
    qb_inventory = 'qb-inventory',

    ox_target = 'ox_target',
    qb_target = 'qb-target',

    ox_fuel = 'ox_fuel',
    wasabi_carlock = 'wasabi_carlock',
    lb_tablet = 'lb-tablet'
}

The configured value must exactly match the resource folder name.

For example, when the folder is renamed from:

lb-tablet

to:

my-lb-tablet

update:

Config.Resources.lb_tablet = 'my-lb-tablet'

Startup Validation

Startup validation is enabled with:

Config.StartupValidation = true

Strict provider validation is enabled with:

Config.StrictMode = true

Recommended production settings:

Config.Debug = false
Config.StrictMode = true
Config.StartupValidation = true

When strict mode is enabled, invalid or missing provider configurations are reported more clearly during startup.

Startup Console Output

A successful startup should display a block similar to:

[wp_bridge] --> resource [wp_bridge] started successfully.
[wp_bridge] --> version: 1.2.6
[wp_bridge] --> created by: WaCKPaCK Development Studios © 2026
[wp_bridge] --> website: https://wackpackstudios.com
[wp_bridge] --> documentation: https://docs.wackpackstudios.com
[wp_bridge] --> customer support: https://discord.gg/wackpack

[wp_bridge] --> Active Providers:
[wp_bridge]     Framework: qbx
[wp_bridge]     Inventory: ox_inventory
[wp_bridge]     Target: ox_target
[wp_bridge]     Fuel: ox_fuel
[wp_bridge]     Keys: wasabi_carlock
[wp_bridge]     Dispatch: lb_tablet

Review the active providers after every configuration change.

A provider showing none or an unexpected value normally means:

The provider is not selected in config.lua
The selected resource is not started
The resource starts after WP Bridge
The resource folder name does not match Config.Resources
Automatic detection selected another installed provider

Account Configuration

WP Bridge uses normalized account names for supported frameworks.

Config.Accounts = {
    cash = {
        qbx = 'cash',
        qb = 'cash',
        esx = 'money'
    },

    bank = {
        qbx = 'bank',
        qb = 'bank',
        esx = 'bank'
    },

    crypto = {
        qbx = 'crypto',
        qb = 'crypto',
        esx = 'crypto'
    }
}

Most server owners should leave these values unchanged.

Only modify them when your framework uses custom account names.

Inventory Defaults

Default inventory values are configured under:

Config.InventoryDefaults = {
    stashSlots = 50,
    stashMaxWeight = 100000,
    shopId = 1
}

These values are used when a WaCKPaCK resource does not define its own stash or shop settings.

Fuel Defaults

Config.FuelDefaults = {
    minimum = 0.0,
    maximum = 100.0,
    mirrorNative = true,
    replicateState = true
}

Recommended settings:

minimum = 0.0
maximum = 100.0
mirrorNative = true
replicateState = true

These values normally do not need to be changed.

Vehicle-Key Defaults

Config.KeyDefaults = {
    skipNotification = false
}

Set skipNotification to true only when:

The selected key provider supports notification suppression
Duplicate key notifications are appearing
WaCKPaCK Development Studios support instructs you to enable it

Dispatch Defaults

Default dispatch values are used when a dependent WaCKPaCK resource does not provide its own alert settings.

Config.DispatchDefaults = {
    jobs = {
        'police'
    },

    code = '10-31',
    codeName = 'suspicious_activity',
    title = 'Suspicious Activity',
    message = 'Suspicious activity reported.',
    priority = 2,
    duration = 60,

    blip = {
        sprite = 161,
        colour = 1,
        scale = 1.0,
        flashes = false,
        radius = 0
    }
}

Commonly edited values include:

jobs
code
title
message
priority
duration

LB Tablet Configuration

LB Tablet-specific options are configured under:

Config.LBTablet = {
    mdts = {},
    notificationTime = 10,
    sound = nil,
    randomCoords = false,
    shortRange = false
}

Job-Based Routing

Leave the MDT list empty:

mdts = {}

WP Bridge will route calls based on the jobs supplied by the dependent WaCKPaCK resource.

Fixed MDT Routing

Route all supported calls to one MDT:

mdts = {
    'Police'
}

Route to multiple MDTs:

mdts = {
    'Police',
    'Ambulance'
}

MDT identifiers are case-sensitive.

They must match the identifiers configured in LB Tablet.

Notification Time

notificationTime = 10

This controls the LB Tablet notification duration where supported.

Sound

Use the LB Tablet default sound:

sound = nil

Disable notification sounds:

sound = false

Version Checking

WP Bridge checks the centralized WaCKPaCK Development Studios version manifest.

Config.VersionCheck = {
    enabled = true,
    resourceKey = 'wp_bridge',

    url = 'https://raw.githubusercontent.com/wackpack-studios/resource-versions/refs/heads/main/versions',

    releaseUrl = 'https://docs.wackpackstudios.com/resources/wp-bridge/',

    command = 'wpbridgeversion'
}

Run a manual check from the server console:

wpbridgeversion

Possible results include:

Up to date
Update available
Development version
Version check unavailable
Invalid version response

A failed version check does not stop WP Bridge from starting.

Diagnostics

Run the diagnostics command from the server console:

wpbridgecheck

This checks:

Active framework
Active inventory
Active target system
Active fuel system
Active vehicle-key system
Active dispatch system
Configured provider resource names
Provider resource states

To allow administrators to use the diagnostics command in-game:

add_ace group.admin wp_bridge.diagnostics allow

Restart the server after changing ACE permissions.

Editable Files

Most server owners only need to edit:

config.lua

Additional custom integration files may be included for advanced setups:

custom/shared.lua
custom/client.lua
custom/server.lua

Do not modify protected provider files.

Custom integrations should only be added when instructed by WaCKPaCK Development Studios support or by an experienced FiveM developer.

Troubleshooting

Provider Shows `none`

Confirm the provider is selected:

Config.Dispatch = 'lb_tablet'

Confirm the provider starts before WP Bridge:

ensure lb-tablet
ensure wp_bridge

Confirm the folder name matches:

Config.Resources.lb_tablet = 'lb-tablet'

Provider Shows the Wrong Integration

Avoid automatic detection and select the provider explicitly.

Instead of:

Config.Dispatch = 'auto'

use:

Config.Dispatch = 'lb_tablet'

Restart WP Bridge after changing the configuration.

Provider Resource Is Reported as Missing

Check:

The provider is installed
The provider folder name is correct
The provider is started in server.cfg
The provider starts before WP Bridge
The name in Config.Resources exactly matches the folder name

Resource names are case-sensitive on some server operating systems.

WP Bridge Starts Before Its Providers

Incorrect:

ensure wp_bridge
ensure ox_inventory
ensure ox_target

Correct:

ensure ox_inventory
ensure ox_target
ensure wp_bridge

A WaCKPaCK Resource Fails to Start

Confirm WP Bridge starts first:

ensure wp_bridge
ensure wp_resource_name

Run:

wpbridgecheck

Review the WP Bridge startup output for missing or stopped providers.

Version Check Returns HTTP 404

Confirm the URL uses the raw GitHub address:

url = 'https://raw.githubusercontent.com/wackpack-studios/resource-versions/refs/heads/main/versions'

Do not use:

A GitHub blob URL
The documentation website
A changelog page
A GitHub repository page

Version Check Returns `invalid_version_format`

Confirm the resource key is:

resourceKey = 'wp_bridge'

Also confirm the version in fxmanifest.lua uses semantic version formatting:

version '1.2.6'

Valid examples:

1.0.0
1.2.6
2.0.1

Dispatch Shows `none`

Add an explicit dispatch selection:

Config.Dispatch = 'lb_tablet'

Confirm the resource name:

Config.Resources.lb_tablet = 'lb-tablet'

Confirm start order:

ensure lb-tablet
ensure wp_bridge

Recommended Production Configuration

Config.Debug = false
Config.StrictMode = true
Config.StartupValidation = true

Config.Framework = 'auto'
Config.Inventory = 'ox_inventory'
Config.Target = 'ox_target'
Config.Fuel = 'ox_fuel'
Config.Keys = 'wasabi_carlock'
Config.Dispatch = 'lb_tablet'

Recommended Qbox start order:

ensure ox_lib
ensure qbx_core
ensure ox_inventory
ensure ox_target
ensure ox_fuel
ensure wasabi_carlock
ensure lb-tablet

ensure wp_bridge

Then start dependent WaCKPaCK resources:

ensure wp_moneywash
ensure wp_underworld
ensure wp_missions

Getting Support

Before opening a support ticket, collect:

WP Bridge version
Your selected providers
Your config.lua
WP Bridge startup console output
The output from wpbridgecheck
Exact provider resource folder names
Any related server or client console errors

Support:

Website: https://wackpackstudios.com
Documentation: https://docs.wackpackstudios.com
Discord: https://discord.gg/wackpack

WP Bridge

Features

Requirements

Supported Providers

Frameworks

Inventories

Target Systems

Fuel Systems

Vehicle-Key Systems

Dispatch Systems

Installation

Basic Configuration

Framework Configuration

Inventory Configuration

Target Configuration

Fuel Configuration

Vehicle-Key Configuration

Dispatch Configuration

Automatic Detection

Resource Folder Names

Startup Validation

Startup Console Output

Account Configuration

Inventory Defaults

Fuel Defaults

Vehicle-Key Defaults

Dispatch Defaults

LB Tablet Configuration

Job-Based Routing

Fixed MDT Routing

Notification Time

Sound

Version Checking

Diagnostics

Editable Files

Troubleshooting

Provider Shows none

Provider Shows the Wrong Integration

Provider Resource Is Reported as Missing

WP Bridge Starts Before Its Providers

A WaCKPaCK Resource Fails to Start

Version Check Returns HTTP 404

Version Check Returns invalid_version_format

Dispatch Shows none

Recommended Production Configuration

Getting Support

Provider Shows `none`

Version Check Returns `invalid_version_format`

Dispatch Shows `none`