Death Event Parameters Synchronization Fix

[MohabCodeX]

This PR fixes issues #2312 and #2273 where onPlayerWasted and onClientPlayerWasted events received inconsistent parameters when players died via setElementHealth or vehicle explosions.

Root Cause: Race condition between health RPC packets and client-side death events caused DoWastedCheck() to fire with stale damage data, resulting in inconsistent parameters between server and client death events.

Solution: Added client-side flag m_bServerProcessedDeath to prevent stale data usage and implemented dynamic weapon data retrieval.

Results

-- Client

function onClientPlayerWasted(...)
	local t = {...}

	iprint("Client: "..inspect(t))
end
addEventHandler("onClientPlayerWasted", root, onClientPlayerWasted)

-- Server

function onPlayerWasted(...)
	local t = {...}

	iprint("Server: "..inspect(t))
end
addEventHandler("onPlayerWasted", root, onPlayerWasted)

crun setElementHealth(localPlayer,"0")

[13:15:37] [debug] mark\client.lua:4 - "Client: { false, 0, 3, false, 0, 15 }"
[13:15:37] [debug] mark\server.lua:4 - "Server: { 0, false, 0, 3, false, 0, 15 }"

Vehicle Explosion

mark\client.lua:4 - "Client: { false, 51, 3, false, 0, 15 }"
mark\server.lua:4 - "Server: { 2972, false, 51, 3, false, 0, 15 }"

This also incidentally fixed an additional bug:

The inconsistent value of 63 that appeared when dying from a vehicle explosion. It was hardcoded and unrelated to the correct ID, which is 51. Please note that the information on the wiki will need to be updated accordingly. I will provide the full list of damage types later.

[MohabCodeX]

This is likely to be backward-incompatible because of the explosion type ID change.

[Fernando-A-Rocha]

Perfect fix for 1.7 😄