Frameworks and inventories

Qbox (qbx_core), QBCore (qb-core) and ESX Legacy (es_extended) are detected automatically, in that order. set meridian_framework "qbox" (or "qbcore", "esx") picks one explicitly, and "standalone" turns framework support off.

Jobs, duty and callsigns

A player’s job gives them an agency while they’re on duty. Agencies from ACE and Discord roles are added on top.

set meridian_jobs "police=lspd,sheriff=bcso,ambulance=fire"   # job=agency pairs
set meridian_require_onduty "true"                            # off-duty players get no job agency
set meridian_duty_power "true"                                # radio switches on when going on duty, off when going off duty
set meridian_item "radio"                                     # optional: must carry this item; using it toggles the radio

Radios start switched off. Players turn them on and off with the power key. With meridian_duty_power on, a player in one of the meridian_jobs jobs also has the radio switched on when they go on duty and off when they go off duty. ESX versions without a duty flag count everyone in a job as on duty.

The radio alias is the player’s callsign, if the framework has one, plus their last name.

Radio item

With meridian_item set, players need that item to use the radio, and the radio turns off within a few seconds of the item leaving their inventory. The item is checked in ox_inventory when it’s running (with any framework, and on standalone servers too), otherwise in qb-inventory or the framework’s own inventory.

With ox_inventory, add the item to ox_inventory/data/items.lua so using it toggles the radio (use your folder name instead of meridian if you renamed the resource):

['radio'] = {
    label = 'Radio',
    weight = 500,
    stack = false,
    client = { export = 'meridian.useItem' },
},

Without ox_inventory, Meridian registers the usable item with QBCore or ESX itself.