Rules
Settings → Rules is separate from Detections. It requires resource 1.8.34 or later to apply saved rules. Rules belong to one server and require permission to edit that server's settings. They can be prepared while the server is offline.
Choose a name and a supported event, then add conditions using the searchable field picker. Choose whether all conditions or any condition must match. The expression is a preview of structured conditions, not executable Lua.
For example, an entityCreating rule can match data.model == 4222310262 and data.entityType == 2, then block that vehicle and send a Discord log. Available fields depend on the event. You can also use a per-player event limit, with or without additional conditions.
Actions include Block event, Ban player, Kick player, Warn player, Discord log and a custom Trigger event action. Custom action names must start with voidac:rules:; server actions run locally and client actions target only the matching player. This prevents the rule editor from calling unrelated privileged framework events. Add your own trusted handlers for these names.
Block a license when connecting
Choose On connection: block ID and log. Paste the full license: identifier from Lookup, including its 40 hexadecimal characters, and save the rule. The license2: fallback is supported when that is the account identifier supplied by the resource. This is not the temporary in-game player number.
The verified server sends its account identifier to the central connection check. Matching accounts are blocked with a server-rule message; other accounts continue through the normal checks. This does not create a permanent ban. Turn off or remove the rule to allow that account again. These ID rules support Block and Log, plus optional name conditions; they do not support event rate limits. Use the ban list if you want a persistent ban.
Open Configure Discord logs on the Rules page to set the webhook. Rule logs share the Ban webhook, so changing it here changes the Ban logging destination too. Webhook credentials are encrypted in the database. Connecting rule logs are recorded before rejecting the connection. Repeated matching join attempts are coalesced for 30 seconds; blocking remains active throughout.
Patterns
The pattern operator supports an intentionally limited regex subset: anchors, literals, character classes, \d, \w, \s, and at most one repetition operator. Patterns must start with ^ and stay within 64 characters. Groups, alternatives, backreferences and repeated optional/unbounded wildcards are rejected. Escape literal hyphens outside a character class. Input matching is bounded. This is not a full PCRE engine.
What blocking means
Only cancellable FiveM events can actually be stopped. A notification such as entityRemoved describes something that already happened; blocking it cannot restore the entity. Connecting-player rules use the connection deferral instead of cancelling the handshake, preserving the custom rejection card. Screen captures cannot be taken from a player who has not joined.
Connecting-player rules support Block, Kick, Ban and Log. Warn and custom actions are offered for in-game events only; they cannot operate on a client that has not joined yet.
Start unfamiliar rules with Discord log. Broad rules can block legitimate gameplay. Notification throttling does not stop blocking: an event that matches a block rule remains blocked during a flood.
