ev_pulsecheck

EV Pulse Check System

The EV Pulse Check System allows emergency responders (police and ambulance roles) to check the pulse of nearby players. The system includes animations, customizable interaction prompts, and dynamic responses based on the patient's current status.

---

System Features

Pulse Check Interaction

1. Initiating a Pulse Check:

   • Emergency responders can initiate a pulse check on nearby players.

   • An animation plays during the process for immersion.

2. Dynamic Pulse Responses:

   • Players being checked can select from predefined pulse options or respond with their current pulse value.

   • The system dynamically fetches and displays the pulse data from osp_ambulance.

3. Notifications:

   • Both the checker and the patient receive real-time notifications about the pulse check results.

---

Configuration

This system assumes emergency responder roles and integrates seamlessly with existing roleplay frameworks. No direct configuration file is provided; adjustments can be made in the script itself for role or interaction customization.

---

Client-Side Details

Pulse Check Logic

Initiating a Pulse Check

The system checks for nearby players and triggers the pulse check interaction:

AddEventHandler('ev:client:targetPulse', function()
    if not isPoliceOrAmbulance() then return end

    local coords = GetEntityCoords(cache.ped)
    local player = lib.getClosestPlayer(coords, 2.0, false)
    if not player then return DoNotification('Nobody close enough to pulse check.', 'error') end

    local id = GetPlayerServerId(player)
    lib.requestAnimDict('amb@medic@standing@tendtodead@base', 2000)
    TaskPlayAnim(cache.ped, 'amb@medic@standing@tendtodead@base', 'base', 8.0, 1.0, -1, 01, 0, 0, 0, 0)

    if lib.progressCircle({
        duration = 3000,
        position = 'bottom',
        label = 'Checking for a pulse..',
        useWhileDead = false,
        canCancel = false,
        disable = { move = false, car = true, mouse = false, combat = false, },
    }) then
        lib.callback.await('ev:server:checkPulse', false, id)
        ClearPedTasks(cache.ped)
    end
end)

---

Displaying Pulse Options

After the pulse check request, the patient is presented with pulse response options:

RegisterNetEvent('ev:client:displayPulse', function(senderId)
    local pulseCheck = 'pulse_check'
    local currentPulse = exports["osp_ambulance"]:GetAmbulanceData(GetPlayerServerId(PlayerId())).Pulse

    local pcMenu = {
        id = pulseCheck,
        title = 'Pulse Check',
        options = {
            { title = 'No Pulse', icon = 'fa-solid fa-heart-circle-xmark', serverEvent = 'ev:server:playerResponse', args = { response = 'NO PULSE.', id = senderId } },
            { title = 'Weak Pulse', icon = 'fa-solid fa-heart-circle-exclamation', serverEvent = 'ev:server:playerResponse', args = { response = 'a WEAK pulse.', id = senderId } },
            { title = 'Strong Pulse', icon = 'fa-solid fa-heart-circle-check', serverEvent = 'ev:server:playerResponse', args = { response = 'a STRONG pulse.', id = senderId } },
            { title = 'Current Pulse: ' .. currentPulse, icon = 'fa-solid fa-heart', serverEvent = 'ev:server:playerResponse', args = { response = 'a pulse of ' .. currentPulse, id = senderId } }
        }
    }

    lib.registerContext(pcMenu)
    lib.showContext(pulseCheck)
end)

---

Client Notifications

The pulse check result is displayed to the responder using qb-core notifications:

RegisterNetEvent('ev:client:notifyPulseResult', function(message)
    QBCore.Functions.Notify(message, "success")
end)

---

Server-Side Details

Pulse Validation

The server validates whether the target player is eligible for a pulse check:

lib.callback.register('ev:server:checkPulse', function(source, id)
    local src = source
    local Player = GetPlayer(src)
    local Target = GetPlayer(id)

    if not isPlyDead(Target) or not isPoliceOrAmbulance(Player) then return false end

    TriggerClientEvent('ev:client:displayPulse', id, src)
end)

---

Player Response Handling

Responses from the patient are handled and relayed to the responder:

RegisterNetEvent('ev:server:playerResponse', function(data)
    local src = source
    local Player = GetPlayer(data.id)

    if not isPoliceOrAmbulance(Player) then return end
    DoNotification(data.id, ('The Patient has %s'):format(data.response), 5000)
end)

A notification is sent to the responder with the pulse check results:

RegisterNetEvent('ev:server:playerResponse', function(data)
    local senderId = data.id
    local response = data.response

    if senderId then
        TriggerClientEvent('ev:client:notifyPulseResult', senderId, "Pulse check result: " .. response)
    end
end)

---

Example Scenarios

Scenario 1: Successful Pulse Check

1. An emergency responder initiates a pulse check.

2. The patient receives a menu to respond with their pulse status.

3. The responder receives a notification with the patient’s pulse response.

---

Scenario 2: No Player Nearby

1. An emergency responder attempts a pulse check.

2. No player is within range.

3. A notification appears: "Nobody close enough to pulse check."

---

Notes

1. Role Validation:

   • Ensure only designated roles (police/ambulance) can initiate pulse checks.

2. Integration:

   • Relies on osp_ambulance to fetch the player's current pulse.

3. Customization:

   • Adjust durations, labels, and localization for interaction prompts to suit gameplay requirements.