Documentation

Set up CoreAC

Install the resource, connect it to your panel, and wire up the few scripts that move or heal players so nobody honest is ever flagged.

Quick start (one-click installer)

  1. Get a licence key — see how to buy — and add your server under My Servers → New server.
  2. Open Download, reveal the server token and download the installer.
  3. Put CoreAC-Installer-….bat next to your server.cfg and double-click it. Paste the token when asked.
  4. Restart the server. It shows Online in the panel within a minute.

The installer checks your licence, installs the resource (under a random folder name unless you turn that off), writes the server.cfg lines above your other resources, and keeps a backup as server.cfg.coreac.bak. Running it again updates the same folder.

Manual install

Download the resource zip from the Download page, extract it into resources/ (you may rename the coreac folder) and add these lines above your other ensure lines:

set coreac_api "https://YOUR-PANEL/api/v1"
set coreac_token "coreac_srv_…"
add_ace resource.coreac command allow
ensure coreac

add_ace lets the web console run server commands. Live screen, screenshots and the videos before a ban / kick are captured by CoreAC itself; screencapture (or screenshot-basic) is only an optional fallback — ensure it exactly once.

Integrating your scripts

Recognised automatically, no changes needed: teleports done behind a screen fade (almost every QBCore/ESX apartment, house, elevator, hospital, prison and spawn script), QBCore /tp /tpm, txAdmin teleport/bring/spectate/noclip/god mode and qb-adminmenu goto/bring/spectate.

For anything else that legitimately teleports, revives or protects players, tell CoreAC first — these events work whatever your resource folder is called:

Teleports (garages, houses, jobs, spawn selectors)

-- server
TriggerEvent('coreac:markTeleport', source)
-- client (before SetEntityCoords)
TriggerEvent('coreac:markTeleport')

Revives and heals

TriggerEvent('coreac:markRevive', source)   -- server
TriggerEvent('coreac:markRevive')           -- client

Safe zones, cutscenes, admin god mode (server)

TriggerEvent('coreac:markImmune', source, 30000)  -- ms

Death/last-stand states from QBCore, QBox and the common medical scripts are recognised automatically. Server staff (txAdmin admins, QBCore/ESX admins, ACE command, in-game admins added in the panel) are never auto-kicked or banned while Settings → Never punish server staff is on — their detections are still logged with a Staff tag. Turn it off to test the anti-cheat with your own admin account. The old aeigs:markTeleport / aeigs:markRevive event names still work.

Only needed if you enable the matching option: exports['<folder>']:giveWeapon(hash) (Anti Weapon Spawn), exports['<folder>']:canRagdoll(false) (Anti No-Ragdoll) and exports['<folder>']:newCheatPowerIncrease(x) for nitro scripts that use engine power over 3×.

Console commands

Type these in the server console, or in the panel's Console page (the output shows up there too):

ac players                          list online players and their IDs
ac kick <id> <reason>               kick an online player
ac ban <id> [hours] <reason>        ban (no hours = permanent)
ac unban <Ban ID>                   lift a ban, e.g. ac unban AC-7K3QP9
ac baninfo <Ban ID>                 who, why and until when
ac announce <message>               banner on every player's screen
ac clear <peds|vehicles|objects|all> delete world entities (never players or occupied cars)
ac reload                           pull the configuration from the panel now
ac shield [status]                  Event Shield: watched events, traps, protected resources
ac shield install <resource|all>    protect resources against events fired by executors
ac shield uninstall <resource|all>  remove the Event Shield include again

Convars

coreac_apiPanel API URL (…/api/v1). Must be public for screenshots.
coreac_tokenThe server token from the Download page.
coreac_detections"false" pauses every detection (test mode).
coreac_menu_keyOptional key that opens /core (e.g. F6). Empty by default.
coreac_logoPublic logo URL for the connect/ban card.
coreac_ss_uploadCustom screenshot upload URL (optional).

Servers installed under the old name keep working: every aeigs_* convar is still read as a fallback.

How punishments work

Every detection type has a confidence level. It sets what a fresh install does — only checks the server confirms itself can ban, signals that come from the player's own game kick at most, noisy signals are only logged — and the “recommended up to” hint next to each type. You choose Log / Kick / Ban per type in Configuration → Punishments, and the action you pick is the one that runs, for every report of that type. Picking above the recommendation is allowed and marked, because it means a legitimate player who trips the check gets punished.

Three things still override a choice: a player on the Trust Whitelist, server staff (Never punish server staff), and Log-Only Mode / Enable Bans off. A Ban on a licence without the Auto Ban feature is applied as a Kick, and the Punishments page says so.

Rolling out a new protection? Turn on Log-Only Mode under Configuration → Settings: everything is recorded, nobody is kicked or banned.

Configuration → Settings

The Settings tab holds the rules around the anti-cheat rather than single detections. What you type there stays in the panel or on your game server; none of it is sent to your players' game clients.

  • Safe Guard — keeps your own scripts from being flagged. Safe Events are never used as cheat-menu traps; Safe Scripts are trusted (what they spawn skips the spawn checks, and a teleport or revive they hand to CoreAC gets a longer grace); Ignored Scripts are left completely alone; the Anti Resource Injection Safe List names resources the injection check never flags.
  • Connection & Identity — who may join, checked on the connection card before the player loads in: name rules, required Steam / Discord, duplicate sessions, VPN / proxy (looked up at proxycheck.io and cached for 24 hours), a network-reputation gate and a threat score built from recent automatic kicks. Staff and Trust-whitelisted players skip these checks; bans always apply. If the panel or the VPN lookup cannot be reached the player is let in, unless Block Joins When Verification Fails is on.
  • Bans & Evidence — Enable Bans is the master switch (off = detections are only recorded). Ban Duration sets how long automatic bans last, Ban Message and Ban Video URL decide what a banned player sees, and Screen Shots / Gameplay Record keep proof — the record is a short sequence of screenshots, not a video. Ban Ip Address also blocks the banned player's IP; leave it off on servers where players share networks.
  • Logs & Webhooks — one Discord channel per kind of event (bans, warns, kicks, joins, leaves, silent-aim warns, staff actions) plus switches for the console output. Webhook URLs live in the panel only: the panel posts to Discord itself, so your game server never holds them.
  • Framework & API — the resource names of your ESX / QBCore / Qbox core, the txAdmin data folder (admins listed in its admins.json count as staff the moment they connect), the prefix of the admin commands, and the settings of the HTTP API below.

Game server HTTP API

The resource answers HTTP requests on your game server's own port, under its folder name: http://YOUR-SERVER:30120/<resource folder>/status. Every request needs Authorization: Bearer <coreac_token> — the token from your server.cfg. Requests are limited to 60 a minute per address, and X-Forwarded-For is ignored.

GET/status

Server version, player count and whether the panel is reachable.

GET/players

Online players and their identifiers (IP addresses only when writing is enabled).

GET/bans

Active bans (IP addresses only when writing is enabled).

POST/unban

Lifts a ban: {"code":"AC-7K3QP9"}. Needs write access.

POST/screenshot

Captures a player's screen: {"id":12}. Needs write access.

POST/reload

Pulls the configuration from the panel right now. Needs write access.

Allowed IPs limits every endpoint to the listed addresses (IPv4, IPv6 or an IPv4 range such as 203.0.113.0/24). The write endpoints need the HTTP API — Allow Write Endpoints switch and at least one allowed IP, and they only work for callers on that list. Every write is recorded in the logs and posted to the Admin Logs webhook as "HTTP API".

curl -H "Authorization: Bearer $COREAC_TOKEN" http://YOUR-SERVER:30120/coreac/status

curl -X POST -H "Authorization: Bearer $COREAC_TOKEN" \
     -d '{"code":"AC-7K3QP9"}' http://YOUR-SERVER:30120/coreac/unban

API reference

Every request needs an Authorization: Bearer <server-token> header. The resource handles all of this for you — the list is here for reference.

POST/api/v1/heartbeat

Keeps the server online and returns its configuration.

POST/api/v1/players/sync

Syncs the list of online players.

POST/api/v1/detections

Reports a detection; the answer says whether to kick or ban.

GET/api/v1/actions/pending

Punishments issued from the panel, waiting to be applied.

POST/api/v1/actions/ack

Confirms punishments that were applied.

GET/api/v1/bans

Active bans, checked when a player connects.

GET/api/v1/commands/pending

Console commands queued from the web console.

GET/api/v1/install/resource

Downloads the protected resource (used by the installer).

Stuck on something? Ask the team on Discord.

discord.gg/coreac