baseevents:onPlayerWasted

The reviewed implementation emits one argument: a death-coordinate array. It is a legacy fallback in the provider’s death-checking loop, not an alias with the same arguments as onPlayerDied, and not a reliable promise of one event per death.

The source contains both local TriggerEvent and TriggerServerEvent calls in this fallback branch. A listener’s shape is therefore:

-- client.lua: optional diagnostic only, not the primary death workflow.
AddEventHandler('baseevents:onPlayerWasted', function(deathCoords)
    if type(deathCoords) ~= 'table' then return end
    print('[Death observation] Legacy wasted fallback was emitted.')
end)

A server listener has the same single payload argument plus implicit source. Do not add a made-up killer type argument, shift array positions or forward this blindly to another handler expecting a different signature.

For a new feature, use the actual provider’s onPlayerDied and onPlayerKilled contracts, or your framework’s documented death/respawn lifecycle. Make presentation cleanup idempotent and keep rewards/penalties server-authoritative. Absence of this fallback is not evidence that death detection is broken.

Source: pinned baseevents death loop . The stock event directory distinguishes these resource notifications from engine events.