Documentation › Hunting System › Integrations

Integrations

Connect your own permissions, license system, dispatch, tablet or MDT.

Everything a server usually wants to swap lives in bridge/ and config/config_bridge.lua. Both stay readable and editable after escrow, so you can connect the script to any ESX, QBCore or QBox setup.

File What you can change
bridge/server/framework.lua Identifiers, names, money, jobs
bridge/server/inventory.lua Item counts, add / remove, carry checks
bridge/server/permissions.lua Who is an admin, who is police
bridge/server/license.lua Where hunting licenses are stored
bridge/server/hooks.lua React to hunts, sales, poaching, legends and more
bridge/client/framework.lua Notifications, callbacks
bridge/client/dispatch.lua Police dispatch for poaching reports
bridge/client/tablet.lua Opening the tablet from phones, radial menus, keys
bridge/client/target.lua Target interactions (ox_target, qb-target, TextUI)
bridge/client/progress.lua Progress bars
mermaid
flowchart LR
    Hunt[Player skins an animal] --> Core[Hunting core]
    Core --> Hooks[bridge/server/hooks.lua]
    Core --> License[bridge/server/license.lua]
    Core --> Dispatch[bridge/client/dispatch.lua]
    Hooks --> Your[Your resources]
    License --> Store[(Database / item / esx_license / QB metadata)]
    Dispatch --> Police[ps / cd / core / qs / rcore dispatch]

The Admin → Integrations screen shows what the bridge detected: framework, inventory, target, license storage, dispatch, commands and which webhooks are set.