Help

Troubleshooting

Find your symptom below. Each entry pairs the most likely cause with the concrete fix. Still stuck after the relevant section? Jump to Contacting support.

#Installation & startup

Symptom

The resource doesn't start / isn't found

Likely cause

A double-nested folder (twiste_AC/twiste_AC) or a renamed folder means the server can’t find fxmanifest.lua.

Fix

Make sure the path is resources/[twiste]/twiste_AC and that fxmanifest.lua sits directly inside twiste_AC. The folder must be named exactly twiste_AC.

Symptom

Server boots, but twiste_AC errors or loads in the wrong order

Likely cause

Load order - twiste_AC started before oxmysql / vorp_core.

Fix

Put the ensures in this order in server.cfg:

server.cfg

ensure oxmysql
ensure vorp_core
ensure twiste_AC

#Server not reporting

Symptom

Server shows offline in the panel / no data appears

Likely cause

Missing or mismatched credentials: ac_server_id doesn’t match the Server ID in the panel, or ac_api_key is wrong/empty. Also check the server was actually created on Servers.

Fix

Confirm the server exists on Servers, then verify both convars match it exactly:

server.cfg

setr ac_server_id "my-server-01"   # must equal the panel Server ID
setr ac_api_key   "YOUR_API_KEY"   # must equal the panel API Key

If you ever rotated keys, the old key stops working - paste the new one and restart.

Symptom

It was online, then went offline after a key rotation

Likely cause

Rotating keys invalidates the previous pair immediately.

Fix

Copy the freshly generated API Key into ac_api_key and restart the server. The HMAC Secret is handled by the panel automatically.

#Detections & false positives

Symptom

Legitimate players (or staff) are being flagged

Likely cause

A threshold is too tight for your server’s style, or staff who fly/teleport for events aren’t exempt.

Fix

Exempt staff by adding them to group.admin / group.moderator, or per-player by Steam hex from the panel. For genuine threshold noise, loosen that one module in Servers → Settings and observe for a session. See Configuration.

Symptom

Detections appear but nobody is ever kicked/banned

Likely cause

You’re in observe mode (log-only), or ac_enable_actions is off - both are normal during calibration.

Fix

Once you trust the signal, enable enforcement:

server.cfg

setr ac_mode "enforce"
setr ac_enable_actions 1

Restart, and confirm the relevant module's action is enabled in the panel.

Symptom

Too many alerts to keep up with

Likely cause

Either real abuse, or a single noisy module. Repeat detections of the same rule increment an occurrence count rather than creating new alerts.

Fix

Sort Alerts by severity, use bulk actions to clear noise, and group related alerts into a case. If one rule dominates, tune that module in the panel.

#Auto-update

Symptom

A new version was downloaded but isn't active yet

Likely cause

twiste_AC stages updates to disk; it never restarts itself.

Fix

Restart the server (or run ensure twiste_AC) and the staged version applies. Nothing else to configure.

No special permissions needed

Auto-update writes new files to disk and applies them on the next restart - it does not run a self-restart, so you don’t need any add_ace lines for updates. To stage without auto-applying, set ac_autoupdate_apply 0.

#Account & billing

Symptom

I paid but my license still shows inactive

Likely cause

Payment confirmation can take a moment to sync.

Fix

Wait a short interval and refresh Profile. If it’s still wrong, contact support with the payment timestamp and your account email.

Symptom

Dashboard pages look empty even with an active license

Likely cause

Full access requires both an active license and at least one configured server.

Fix

Create your server on Servers and set its keys in server.cfg.

#Contacting support

If the relevant section above didn’t solve it, reach out - and bring this with you so we can help fast:

Include	Why it helps
What failed + exact timestamp (with timezone)	Lets us line up your report with backend logs.
Your account email / Discord ID	Identifies your account and license.
Your Server ID	Scopes the issue to the right server.
What you did and what you expected	Separates a bug from a config gap.
A screenshot or console log of the error	Often pinpoints the cause immediately.

Where to reach us

Join the Discord or use the contact page. For investigation help on a specific player, request an expert review from the case itself.

PreviousBilling Next FAQ