πŸ”—Using the Bridge

The NOVA Bridge (nova_bridge) provides compatibility with existing ESX, QBCore, vRPex, and Creative scripts.

What Does the Bridge Do?

The bridge intercepts calls to other framework APIs and translates them to NOVA's native API. This means you can use most existing scripts without modification.

Installation

git clone https://github.com/Buddhapt/nova-bridge.git nova_bridge

Add to server.cfg (after nova_core):

ensure nova_core
ensure nova_bridge

Configuration

Edit nova_bridge/config.lua:

Config = {}

-- Which framework to emulate
-- Options: 'esx', 'qb', 'vrpex', 'creative'
Config.Framework = 'esx'

ESX Compatibility

When Config.Framework = 'esx', the bridge provides:

Supported ESX Functions

ESX Function
Status

GetPlayerFromId

βœ… Full

GetPlayers

βœ… Full

getMoney / addMoney / removeMoney

βœ… Full

getJob / setJob

βœ… Full

getInventory / addInventoryItem / removeInventoryItem

βœ… Full

getGroup

βœ… Full

ShowNotification

βœ… Mapped to nova_notify

QBCore Compatibility

When Config.Framework = 'qb':

Supported QBCore Functions

QBCore Function
Status

GetPlayer

βœ… Full

GetPlayers

βœ… Full

AddMoney / RemoveMoney

βœ… Full

GetMoney

βœ… Full

SetJob

βœ… Full

AddItem / RemoveItem

βœ… Full

HasItem

βœ… Full

vRPex Compatibility

When Config.Framework = 'vrpex':

Creative Compatibility

When Config.Framework = 'creative':

Limitations

::: warning The bridge covers the most common API calls (~80% of scripts). Some edge cases may require manual adaptation:

  • Custom framework events specific to a particular script

  • Direct database queries that reference framework-specific table structures

  • UI elements that are tightly coupled to a specific framework :::

Running Both

You can technically run nova_bridge alongside ESX/QBCore scripts, but for best results:

  1. Start with Config.Framework = 'esx' (most common)

  2. Test your existing scripts one by one

  3. Gradually replace them with NOVA-native versions

Last updated