Events

Server-side events XeroShield triggers after a server ban, global ban, kick, or warning has been successfully recorded. Use them for your own logging and integrations.

Each event provides the player server ID, a token, and a data table. Check the token against the xerotoken convar before processing the payload. Register handlers in a server-side script with AddEventHandler.

Optional drop delay

The server ban, global ban, and kick events provide delayDrop as a fourth argument. Call delayDrop(4000) to delay the player drop by 4 seconds. The maximum accepted value is 20000 ms (20 seconds).

Call it directly in the event handler, before any Wait, Citizen.Await, or asynchronous callback. If multiple handlers request a delay, the largest valid value is used; delays are not added together. Values outside 0–20000 and non-number values are ignored.

The warning event has no delayDrop argument because a warning does not drop the player.

On Player Server Banned

Fired after a ban on this server has been successfully recorded.

On Player Global Banned

Fired after a global ban has been successfully recorded.

On Player Kicked

Fired after a kick has been successfully recorded, before the player is dropped.

On Player Warned

Fired after a warning has been successfully recorded. A warning does not drop the player.