ESX and Qbox scripts

Status: shipped in 1.1.0 as a first, partial layer. Off by default. BS19 is not compatible with ESX or Qbox scripts in general. Many scripts will not work yet. Test every script on a test server before you put it on a live one.

The aim is to run some scripts written for ESX Legacy or Qbox on a standalone BS19 server. Scripts that only need player, money, item or notification calls have the best chance. Scripts that depend on their framework’s jobs, inventory, targeting, menus, database tables or client modules need more than this layer gives them.

Turning it on

Both bridges ship in the release but are not started. In server.cfg find these lines and remove the ## in front of the one you need:

# Compatibility bridges for ESX and Qbox scripts. First compatibility layer, partial: remove ## to try them.
## ensure bs_esx_bridge
## ensure qbx_core

Start the bridge before the third-party script, restart the server, and test one script at a time. bs_esx_bridge lives in resources/[beyond], qbx_core in resources/[compat].

Never run a bridge next to the real framework it stands in for. No real es_extended or qbx_core on the same server.

What it covers

• ESX (bs_esx_bridge): answers the es_extended resource name with a limited getSharedObject() and imports.lua. The player object covers basic identity, cash and bank, item counts and changes, metadata and callbacks, and lookup by BS19 character. Jobs, societies, black money and full ESX weapon loadouts are not supported yet.
• Qbox (qbx_core): answers the qbx_core resource name. It covers a small set of player, money, metadata and notification calls, passes BS19 character load and logout on to Qbox script events, and provides the playerdata.lua import some client scripts use. The wider Qbox lib module, the qb-core bridge, jobs, gangs and the ox resources are not covered.

Checking a script

1. Read its fxmanifest.lua dependencies and install notes. Write down every framework, inventory, target, menu and database dependency.
2. Start the matching bridge before the script and check that the script starts and its main actions work.
3. Check identity, money, items, permissions and reconnecting. A menu that opens is not proof that its transactions work.
4. Keep backups of your server files and database while you test.

Found a script that works, or one that almost does? Tell us on the Discord. The layer will grow over the next versions.