esx_ambulancejob

esx_ambulancejob adds a playable EMS job to ESX Legacy: paramedics can revive dead players, heal injured ones, take medical supplies from the hospital pharmacy and buy ambulances and helicopters. Death itself (death screen, bleedout, respawn) is handled by esx_death; this resource only adds the medic side.

OverviewCopy Anchor Link

In-game features:

• F6 menu (/ambulance command, rebindable key mapping): revive, small heal (bandage), big heal (medikit), put a patient in the closest vehicle, search a nearby dead player.
• Hospital markers: cloakroom (go on and off duty in uniform), boss actions, pharmacy, vehicle and helicopter garages, fast-travel elevators.
• Dead player blips for on-duty medics, plus a distress blip when a downed player sends a distress signal through esx_death.
• Usable items: medikit restores full health, bandage restores one eighth of max health.

InstallationCopy Anchor Link

ensure esx_lib
ensure es_extended
ensure esx_skin
ensure esx_vehicleshop
ensure esx_death
ensure esx_society
ensure esx_ambulancejob

ConfigurationCopy Anchor Link

All keys live in config.lua.

Config.HospitalsCopy Anchor Link

Each hospital has these fields:

Config.AuthorizedVehiclesCopy Anchor Link

Keyed by vehicle type (car, helicopter) and then by job grade name:

Config.AuthorizedVehicles = {
    car = {
        ambulance = { { model = 'ambulance', price = 5000 } },
        boss = { { model = 'ambulance', price = 2000 } },
    },
    helicopter = {
        doctor = { { model = 'buzzard2', price = 150000 } },
    },
}

An entry can also carry a props table; it is merged into the vehicle properties saved in owned_vehicles. Purchased vehicles get an AMB plate prefix and are stored with job = 'ambulance'.

Server eventsCopy Anchor Link

These are net events, so any client can trigger them. Each one validates the caller on the server, which is why custom scripts should not bypass them.

esx_ambulancejob:reviveCopy Anchor Link

TriggerServerEvent('esx_ambulancejob:revive', targetServerId)

esx_ambulancejob:healCopy Anchor Link

TriggerServerEvent('esx_ambulancejob:heal', targetServerId, healType)

On-duty medics only, 3 second rate limit. On success the server sends esx_ambulancejob:heal to the target client.

esx_ambulancejob:putInVehicleCopy Anchor Link

TriggerServerEvent('esx_ambulancejob:putInVehicle', targetServerId)

Warps the target (within 8 m) into the closest free seat of the nearest vehicle. On-duty medics only, 3 second rate limit.

esx_ambulancejob:giveItemCopy Anchor Link

TriggerServerEvent('esx_ambulancejob:giveItem', itemName, amount)

esx_ambulancejob:svsearchCopy Anchor Link

TriggerServerEvent('esx_ambulancejob:svsearch')

Sends esx_ambulancejob:clsearch to every dead player within 3 m of the medic. esx_death handles that client event.

Client eventsCopy Anchor Link

Sent by the server; listen to them if you build a custom MDT or HUD.

RegisterNetEvent('esx_ambulancejob:PlayerDistressed', function(playerId, coords)
    print(('Distress call from %s at %.1f, %.1f'):format(playerId, coords.x, coords.y))
end)

Server callbacksCopy Anchor Link

Registered with xLib.callback.registerCompat, so they work with xLib.callback and ESX.TriggerServerCallback.

CommandsCopy Anchor Link

Integration tipsCopy Anchor Link

• Revive from other scripts: use the esx_death export on the server.

  Copy Text

  local ok = exports.esx_death:Revive(playerId, 'admin')
  if ok then
      print(('Revived %s'):format(playerId))
  end

• Duty: the server checks xPlayer.job.onDuty ~= false. If you use a duty script, set ESX duty through it so medics who are off duty cannot revive.

• Uniforms come from the skin_male / skin_female columns of job_grades and are applied through esx_skin.

• Society money: the resource registers society_ambulance with esx_society when that resource is present.

Common issuesCopy Anchor Link

• Duplicate column is_dead when importing the SQL: the column already exists (esx_death). Skip the ALTER TABLE statement.
• Revive or heal does nothing: the player is not on duty, has no medikit/bandage, is too far away, or hit the rate limit. Turn on Config.DebugDeath.
• F6 does nothing: the key was rebound in the FiveM settings, or ESX.PlayerData.dead is true.
• Pharmacy returns nothing: you added an item to Config.PharmacyItems that is not medikit or bandage, or requested more than Config.MaxPharmacyTake.

RelatedCopy Anchor Link

• esx_death
• esx_society
• esx_vehicleshop
• Create a job
• Add items

Frequently asked questions