Skip to Content

Framework Bridge

Flux Radial Menu includes full backward-compatible bridges for QBCore and QBox. These bridges provide all the features from the original qb-radialmenu and qbx_radialmenu resources.

QBCore Bridge

When Config.Framework = 'qb', the bridge in bridge/qb-radialmenu/ is loaded. This includes:

  • Vehicle doors — Open/close individual vehicle doors
  • Vehicle extras — Toggle vehicle extras
  • Vehicle seats — Switch between vehicle seats
  • Job interactions — Per-job radial items (ambulance, taxi, tow, mechanic, police, hotdog)
  • Clothing toggles — Toggle jackets, hair, bags, visors, gloves with male/female variations and animations
  • Trunk system — Get in/out of trunk, kidnap trunk, camera system
  • Stretcher system — Ambulance stretcher spawn, push, and lay-on

All QB bridge features use QBRadialConfig in bridge/qb-radialmenu/config.lua.

QBox Bridge

When Config.Framework = 'qbx', the bridge in bridge/qbx_radialmenu/ is loaded. Features are identical to the QB bridge but adapted for QBox APIs:

  • Uses cache.ped, lib.playAnim, lib.getClosestVehicle
  • Uses exports.qbx_core:Notify for notifications
  • Uses lib.callback.await for server callbacks
  • Uses lib.addCommand for commands
  • Handles death state via qbx_medical:deathState state bag

ESX

When Config.Framework = 'esx', only the core Config.MenuItems are used. No bridge is loaded — define all your menu items directly in config.lua.

Migrating from qb-radialmenu

  1. Remove qb-radialmenu from your resources
  2. Install flux-radialmenu
  3. Set Config.Framework = 'qb'
  4. Your existing QB radial config is loaded from the bridge — no migration needed

Migrating from qbx_radialmenu

  1. Remove qbx_radialmenu from your resources
  2. Install flux-radialmenu
  3. Set Config.Framework = 'qbx'
  4. Your existing QBX radial config is loaded from the bridge — no migration needed
Last updated on
ConfigurationExports