OnPlayerWeaponChangeResult

onPlayerWeaponChangeResult

Since 0.1.4. Requires a compatible client and server.

Server event delivered only to the resource that requested the weapon change.

onPlayerWeaponChangeResult(playerId, itemKey, ok, reason, requestId)

• playerId: the player whose request finished.
• itemKey: the requested catalog key, or "none" for clearing both weapon slots.
• ok: whether native completion passed server validation.
• reason: "confirmed" for success, or a failure reason such as "superseded", "native-equip-not-allowed", "readback-timeout" or "client-confirmation-timeout".
• requestId: the identifier of this request, useful for correlating results.

A successful clear requires empty native inventory slots and completed carry-visual cleanup. The updated server commits the confirmed empty equipment to replication/late-join state. Request identity, current life revision and deadline are checked; failed, expired, superseded or cancelled requests cannot commit a successful clear.

This event is not an acknowledgement from every remote renderer. A later manual change may already be reflected by getPlayerWeaponState when a script handles the result. Failure/timeout is not rollback; inspect current state before retrying. Stopping the owning resource discards pending result delivery, while an already issued native operation may finish.

addEventHandler("onPlayerWeaponChangeResult", resourceRoot,
    function(playerId, itemKey, ok, reason, requestId)
        if not ok then
            outputDebugString("Weapon request failed: " .. tostring(reason))
            return
        end
        local state = getPlayerWeaponState(playerId)
        if state and state.fresh then
            -- Use current state.melee and state.ranged for persistence.
        end
    end)

See Weapon control and setPlayerWeapon.