Exceptions and compatibility

How to make oxb live with your scripts: ignored scripts, ignored events, execution patterns, escrow resources and scripts that heal, teleport or give weapons.

oxb is made to live with a real roleplay server. These are the tools, from the gentlest to the most drastic:

Tool	Where	When to use it
*Action on warn***	Configuration, next to each detection	To investigate without punishing anyone.
Ignored events	Main → Events	An event of your server that the event protections block by mistake.
Execution pattern exceptions	Beta	A specific execution that the injection detection flags and is legitimate.
Ignored scripts	Settings → System	An incompatible resource: oxb will not install itself in it.
`BYPASS` permission	Admins	A player who must not receive detections (for example your test team).

Scripts that heal, teleport or give weapons#

If the resource is installed with oxb (it installs itself on the first start), oxb sees when that script heals, moves, arms or creates entities and does not mistake it for a cheat. If an escrow script does those things, oxb cannot see it from the inside and you must tell it. The families are health (heals, max health), movement (teleports, cameras), weapon, vehicle, explosion and spawn.

In a client script

-- right before or after the action
exports.oxb:noteScriptAction("health")

In a server script

-- playerId is the affected player; 0 is valid for everyone (global spawns)
TriggerEvent("__oxb_internal:scriptAction", playerId, "health")

Last updated: November 11, 2026