On this page
Setup

Configuration

Baobab AC 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 Baobab AC 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.
Set this from the panel
Mode, actions, grace period and report-only all live on the Servers page, on the Enforcement module. Changes apply in about three seconds, with no restart and nothing to edit in server.cfg.
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_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.
ac_frameworkautoForce a framework instead of auto-detecting it: vorp, rsg, qbr, redemrp or standalone.
Everything else is configured from the panel
Enforcement, pre-join verification and auto-updates used to be convars. They are modules on the Servers page now: you get every option with its description, a safe default, and a hot reload instead of a server restart. The convars above are the only ones left, because they are read before the panel configuration can arrive.

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 - 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.

Still stuck?

If this page did not answer your question, ask on Discord or write to us. Both reach the people who build Baobab AC.

New to the product? Start with the overview: anticheat RedM, detections and panel on a single page.