Logging

wlabs_handcuff can send action logs through ox_lib when logging is enabled.

Use this page if you want to know which handcuff actions are logged and what kind of information each log contains.

Enable Logging

Logging is controlled in shared/config.lua:

Config.Logging = true

• true: send handcuff logs through ox_lib
• false: disable logging

How ox_lib Logger Is Used

Each log entry includes a source player or identifier, an event name, a message, and optional tags for filtering.

In wlabs_handcuff, the message is built as a structured line with the acting player, the target player when there is one, and extra details such as cuff type or restraint type.

Logged Actions

Cuff

Written when a player is cuffed successfully.

Includes:

• acting player
• target player
• cuffType
• restraint
• aggressive
• bypassChecks=true when bypass exports are used
• bypassItems=true when item checks are skipped

Uncuff

Written when a player is uncuffed successfully.

Includes:

• acting player
• target player
• cuffType
• restraint
• reason
• instant=true for instant uncuff
• bypassChecks=true when bypass exports are used
• bypassItems=true when item checks are skipped

Current reasons:

• uncuff: standard uncuff flow
• admin: bypass/admin uncuff flow

BreakCuffs

Written when a break attempt succeeds.

Includes:

• acting player
• target player
• method
• cuffType
• restraint

PutInVehicle

Written when a cuffed player is placed into a vehicle.

Includes:

• acting player
• target player
• vehicleNetId
• seat
• cuffType
• restraint

RemoveFromVehicle

Written when a player is removed from a vehicle.

Includes:

• acting player
• target player
• cuffType
• restraint

CombatLog

Written when a cuffed player disconnects while combat log protection is enabled.

Includes:

• acting player
• reason
• cuffType
• restraint

CombatLogRestore

Written when a saved cuffed state is restored after the player reconnects.

Includes:

• acting player
• cuffType
• restraint