Logging

wlabs_gopostal can send job logs through ox_lib.

Use this page if you want a quick overview of what gets logged during normal job flow and which anti-exploit actions are reported separately.

Enable Logging

Normal job logs are controlled in shared/config.lua:

Config.logging = true

• true: enable normal GoPostal job logs
• false: disable normal GoPostal job logs

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.

wlabs_gopostal uses readable text messages for normal job logs with small tag sets. Anti-exploit logs use a dedicated GoPostal:AntiExploit event.

Logged Actions

GoPostal:JobStarted

Written when a player starts a postbox or delivery job.

Examples:

• Started Postbox Job
• Started residential Delivery Job with 10 locations
• Started commercial Delivery Job with 10 locations

GoPostal:DeliveryCompleted

Written after a successful delivery.

Includes:

• delivered item name
• payout amount
• job tag

GoPostal:TimerExpired

Written when the delivery timer runs out.

Includes:

• delivery job id

GoPostal:JobFinished

Written when a player finishes a postbox or delivery job.

Postbox finish logs include:

• total payout
• letters handed in
• penalty amount

Delivery finish logs include:

• completed deliveries
• total deliveries
• total paid
• vehicle return bonus
• whether the vehicle was returned
• whether the timer expired

GoPostal:JobStopped

Written when a player stops the current job manually.

GoPostal:AntiExploit

Written when the server detects invalid or suspicious job interaction.

Current checks include things like:

• trying to start a second job while already on one
• rate-limited actions
• invalid job ids or delivery amounts
• invalid delivery indexes
• interacting without an active job
• trying to deliver after the timer expired
• being too far from the required interaction point
• trying to return a vehicle twice