Public hooks for integrating other resources — ambulance jobs, custom HUDs, scripted incidents.
Resource name is nexdev_crutchsystem.
Server exports
Client exports
Example — ambulance job auto-force after revive
In your ambulance job’s server script, after a successful revive:
The patient gets a crutch for 10 minutes, can’t manually unequip it, and shows up in /crutchadmin with EMS as the source label.
Example — read crutched state from another resource
Example — restore a custom walk style after unequip
Some scripts override SetPedMovementClipset. Tell the crutch system what to restore:
The next time the crutch is unequipped, the player’s clip-set is restored to that value instead of the default.
Net events
Only the events you’d reasonably trigger from another resource are listed. Prefer the exports above — they also keep the server’s equipped[] and forcedPlayers[] tracking tables in sync.
Server → client
Calling TriggerClientEvent('nexdev_crutchsystem:client:forceCrutch', src, 600) will visually equip the crutch on the client, but won’t register the player in the server-side tracking tables — IsPlayerCrutched, ListForced, and /crutchadmin won’t know about them. Always use the ForceCrutch export for force locks initiated outside the resource.
