Common false bans

Aimbot / Silent Aim

EZAC uses strict heuristics (instant snap, flick pattern). Very low sensitivity or scripted camera movement can occasionally trigger. If you see false positives:

• Ensure the detection is not firing during loading or pause (EZAC skips during those).
• Set the action to Log first in dashboard Configuration → Actions to confirm before enabling ban.
• Whitelist trusted staff or testers via Dashboard → Admins (grant In-game admin menu so they are whitelisted), or use the whitelist exports from script (see References).

Teleport / Speed

Legitimate teleports (e.g. admin menu, job scripts) or very fast vehicles can trigger movement-based detections. Options:

• Add admins in Dashboard → Admins with In-game admin menu (staff) — they are often excluded from movement checks.
• Adjust Teleport cooldown (ms), Max speed on foot, or Vehicle max speed multiplier in dashboard Configuration → Thresholds if your server allows high mobility.
• Set action to Log first and check the dashboard Console for frequency and context.

Entity spawn / Blocked models

If a job or script spawns props/peds that EZAC blocks by default, you will see "Blocked entity" or "Entity limit". Fixes:

• Add allowed models in the dashboard under Configuration → Entities (blocked models / spawns) or adjust the lists.
• Increase entity limits (amount per time window) in config if players legitimately spawn many objects.
• Use the detection whitelist on the main config page: expand the arrow next to the toggle and add event names or reason substrings that should not trigger the action.
• For specific players who need to spawn more (e.g. admins), add them in Dashboard → Admins with the appropriate permissions so they are whitelisted in-game.

Event abuse / Lua injection

Some resources trigger many events or use loadstring in a way that can look like abuse. If legitimate scripts are flagged:

• Increase Event abuse window (sec) or related limits in Configuration → Thresholds if your server has event-heavy resources.
• Add the event or reason to the detection whitelist for that feature (expand the whitelist with the arrow next to the toggle on the main config page).
• Set the action to Log and check the dashboard Console for the reason string before enabling ban.

General tips

• Whitelist — Manage whitelist through Dashboard → Admins (server owner and admins with In-game admin menu are whitelisted). See References for export-based whitelist if needed.
• Actions — Prefer Log for new detections until you're confident thresholds are right, then switch to Kick or Ban in Configuration → Actions.
• Unban — From the dashboard Bans page you can remove a ban by ID. In-game, staff can use ezac unban [banId]. See References.