Main / Event protection
Server event protection
events.server_protectserverDefault: banA server event of a protected script arrived without the matching call from that script's client code.
How ByteAC finds it
Protected scripts (the ByteAC protect wrapper) send a small stamp right before each server event. Net events arrive in order, so a real call always has its stamp. An event without one was sent by an executor.
Measured by the server. The player cannot fake or block it.
What the numbers mean
These are the values shown under the detection in the Threat feed and on the player page.
- event
- Name of the server event.
- resource
- The protected script it belongs to.
Can also be caused by
Events that are also triggered from server code or from an unprotected client script. Add them to the exceptions list.
What to do
Ban once exceptions are set up. In Log mode the event still reaches the script.
The action (Off, Log, Kick, Ban) is set per detection on the Protection page. It only applies when Enforcement is on Custom. See Actions, modes & numbers.
Related settings
- Max events per seconddefault 80 /s
- -
- Event protection exceptionsdefault 0 entries
- Events that skip token validation.
- Honeypot event namesdefault 4 entries
- -