Exports & Events

• Server Exports: Revive, injure, query state, pull medical records, register drugs.
• Client Exports: Player state, injuries, impairment, opening UI.
• Events & State Bags: Everything the script fires, and the state bags it keeps.

🎯 The two you will actually useCopy Anchor Link

Slow down your script for injured playersCopy Anchor Link

duration = 5000 * exports['kartik-ambulancejob']:getActionSpeed()

Hook your drug items into addictionCopy Anchor Link

-- once, on resource start
exports['kartik-ambulancejob']:RegisterAddictiveDrug('oxy', {
    class = 'opioid',
    addiction = { type = 'opioid', gain = 20 },
    overdose = { doses = 3, window = 900, disease = 'opioid_overdose' },
})

-- every time the item is used
exports['kartik-ambulancejob']:RecordDrugUse(source, 'oxy')

See Addictions & Overdoses.

🔄 Legacy compatibilityCopy Anchor Link

If your script already talks to qbx_medical, qb-ambulancejob or esx_ambulancejob, you do not need to change anything. Those exports and events are answered by the compatibility layer.

Supported:

• qbx_medical exports and events, and its isDead / qbx_medical:deathState state bags, pma-voice, phones and appearance menus that check them keep working
• qb-ambulancejob, esx_ambulancejob and wasabi_ambulance exports
• hospital:client:Revive, hospital:client:HealInjuries, esx_ambulancejob:revive and friends

The full list is in Events & State Bags → Legacy events.

Setting up an admin menu (919Admin, vMenu, EasyAdmin…)? Its revive hook is in Events & State Bags → Admin menus.

See Config.Compat in General & Compatibility.