Setup

Configuration

twisteAC is configured in two places: a tiny set of server.cfg convars (credentials and global mode) and the panel (detection thresholds, blacklists and per-module toggles). Start with defaults - they're tuned for a typical RP server - and only adjust when you have a concrete reason.

Panel first, convars second
Almost everything you'll want to tune lives in the panel and hot-reloads to your live server in ~3 seconds - no restart needed. Reserve server.cfg for credentials and the global enforcement mode.

#Enforcement modes

The single most important setting. It controls whether twisteAC only watches, or actually acts.

ModeBehaviourUse it when
observeDetects and logs everything. Never kicks or bans.First launch, or while calibrating thresholds.
enforceDetections can kick/ban per your module settings.You trust the signal and want active protection.
server.cfg
setr ac_mode "observe"        # or "enforce"
setr ac_enable_actions 1      # master switch for kick/ban actions
setr ac_grace_period 300      # seconds before a freshly-connected player is checked
Recommended rollout
Run in observe for at least one busy session. Watch the alerts, confirm there are no false positives on your legitimate players, then switch to enforce. Going straight to enforce on day one risks kicking real players over an untuned threshold.

#server.cfg convar reference

These are the convars a client typically touches. Anything not listed is best left at its default.

Credentials & connection

ConvarDefaultPurpose
ac_server_idfreeYour Server ID from the panel. Set this.
ac_api_keyemptyAPI Key from the panel. Set this.
ac_backend_endpointofficial APIAPI base URL. Leave default.
ac_persist_events1Persist important events to disk so nothing is lost on a crash.

Enforcement

ConvarDefaultPurpose
ac_modeenforceobserve (log-only) or enforce (act).
ac_enable_actions1Master switch for local kick/ban actions.
ac_grace_period300Seconds before enforcement applies to a new connection.
ac_allow_bypass0Leave 0 in production.

Player verification

On connect, twisteAC can verify players (including an optional VPN/proxy check) before they fully load.

ConvarDefaultPurpose
ac_verification_enabled1Enable connect-time verification.
ac_verify_vpn_check1Flag connections from VPNs/proxies.
ac_verify_fail_open0If 1, let players in when the check service is unreachable.
ac_verify_timeout5000Verification timeout in milliseconds.

Auto-update

On by default. twiste_AC checks for new versions hourly and downloads them to disk; they apply on the next restart. The resource never restarts itself, so no ACE permission is required.

ConvarDefaultPurpose
ac_autoupdate_enabled1Enable version checks.
ac_autoupdate_apply1Auto-download new versions. Set 0 to be notified only.
ac_autoupdate_interval3600000Check interval in ms (default 1 hour).
ac_autoupdate_notify1Notify in-game admins (command.ac ACE) when an update is available.

#Tuning detections in the panel

Detection behaviour is organised into module groups by cheat domain, configurable per server from Servers → your server → Settings:

  • Combat - aimbot, rapid-fire, headshot ratio, forbidden weapons/ammo.
  • Movement - teleport, speedhack, super-jump, physics exploits.
  • Health & Armor - godmode, instant heal, unauthorized armor.
  • Economy / VORP - item dupe, money spawn, XP gain, desyncs.
  • Entity spawn - mass spawning, blacklisted models/weapons, explosions.
  • Abuse - chat/sound spam, ragdoll, spectate, command brute-force.
  • Menu / client - mod-menu, noclip, freecam, invisibility, NUI hooks.
  • System integrity - resource heartbeat, anti-dump, HWID spoof.

Each group can be toggled on/off and most expose thresholds, blacklists and cooldowns. Save as a draft, then deploy to push it live to your running resource. See the full list of what each group catches in Detections.

Changes are hot
Deploying module settings from the panel hot-reloads your live resource in ~3 seconds. You only need a server restart for server.cfg changes (credentials, mode, load order).

#Exempting staff & trusted players

Two ways, depending on whether you want it in config or in the panel:

  • By ACE group - anyone in group.admin or group.moderator is auto-exempt. Add staff with add_principal identifier.steam:… group.admin.
  • By Steam hex - add individual players to the exemption list from the panel, no restart needed.
Use exemptions sparingly
Every exempt player is a blind spot. Exempt staff accounts that genuinely need to fly/teleport for events - not your whole community. A compromised exempt account is invisible to the anticheat.

#A safe way to make changes

  • Change one parameter at a time.
  • Note the timestamp and your reason.
  • Observe the panel for a full gameplay cycle.
  • Keep it or roll it back based on what the data shows - not a hunch.

If your server stays noisy after defaults plus one controlled pass, open support with your startup logs and the last parameters you changed. See Troubleshooting.