Client-Side
This file documents all client-side exports and event wrappers provided by devm-bridge.
🔁 Framework Exports (Client)
GetPlayerData()
GetPlayerData()
DeleteVehicle(vehicle)
DeleteVehicle(vehicle)
GetClosestPed(coords, modelFilter)
GetClosestPed(coords, modelFilter)
GetClosestPlayer(coords)
GetClosestPlayer(coords)
GetClosestVehicle(coords)
GetClosestVehicle(coords)
GetVehicles()
GetVehicles()
SetVehicleProperties(vehicle, props)
SetVehicleProperties(vehicle, props)
🎯 Targeting System (Client)
addLocalEntity(object, data)
addLocalEntity(object, data)
addModel(model, data)
addModel(model, data)
addGlobalPlayer(data)
addGlobalPlayer(data)
disableTarget(state)
disableTarget(state)
👕 Clothing System (Client)
setPlayerComponentVariation(player, componentId, drawableId, textureId?, paletteId?)
setPlayerComponentVariation(player, componentId, drawableId, textureId?, paletteId?)
Unified method to set clothing based on the configured system:
Behavior:
illenium: Uses
setPedComponent()
native: Direct
SetPedComponentVariation
skinchanger: Uses native + triggers relevant
skinchanger:change
events
📣 Synced Events (Client)
These wrap base framework events and redirect them to devm-bridge
equivalents.
devm-bridge:onPlayerDeath
devm-bridge:onPlayerDeath
Framework
Original Event
ESX
esx:onPlayerDeath
QBCore
hospital:server:SetDeathStatus
devm-bridge:playerLoaded
devm-bridge:playerLoaded
Framework
Original Event
ESX
esx:playerLoaded
QBCore / QBX
QBCore:Client:OnPlayerLoaded
xPlayer
,isNew
, andskin
are only passed in ESX.
✅ Notes
Everything here is client-side only.
All systems auto-detect based on
Framework
,Target
, andClothing
values.Use
TriggerEvent('devm-bridge:...')
instead of framework-specific events.
Last updated