Installation

The complete install workflow, fully explained. In one sentence: active license → download the resource → drop it into your server → create the server in the panel → set your keys + load order in server.cfg → restart and validate.

#Prerequisites

• An active Baobab AC license on your account (check Profile).
• A RedM server with oxmysql already installed and working, on any RedM framework.
• Access to your server files and the ability to edit server.cfg and restart.
• Outbound HTTPS from your server to the Baobab AC API (api.twiste-services.net) - Baobab reports detections and validates players over this connection, so a restrictive egress firewall will block it.

#1 · Verify your license

1. 1
   Open your profile

   Go to Profile and confirm your subscription shows as Active.

2. 2
   No active license yet?

   Choose a plan on Pricing and complete checkout. Access unlocks once payment is confirmed.

#2 · Download the resource

From Profile, click Download. This downloads baobab.zip - the same package for everyone; your credentials are configured separately in server.cfg (step 5), not baked into the download.

#3 · Place the files

1. 1
   Extract into your resources folder

   For example: resources/[twiste]/baobab.

2. 2
   Keep the structure intact

   The folder must contain fxmanifest.lua plus the client/, server/ and shared/ folders at its root.

#4 · Create your server in the panel

1. 1
   Open Servers → New server

   Go to Servers and create a new entry.

2. 2
   Choose a Server ID

   A short, unique identifier such as my-server-01. It labels the server in the panel only - it never goes into server.cfg. Your API key alone identifies the server. Name, IP and port are optional metadata.

3. 3
   Copy your keys

   On creation the panel shows an API Key and an HMAC Secret. Copy them immediately - for security they are shown only once. Lost them? Use Rotate keys on the server card to generate a fresh pair (this invalidates the old ones).

#5 · Configure server.cfg

Two things matter here: your credentials and your load order. Add your keys, then ensure baobab loads right after oxmysql.

# ── Baobab AC credentials (from the panel) ─────────────────
set ac_api_key "YOUR_API_KEY"             # API Key shown on server creation

# Optional (recommended from day one): identify players by Steam; omit and Baobab uses the Rockstar license
set steam_webApiKey "STEAM_WEB_API_KEY"

# ── Load order (critical) ─────────────────────────────────
ensure oxmysql
ensure your_framework_core                # your framework core, whichever it is
ensure baobab

# ── Everything else after ─────────────────────────────────
ensure your_other_resources

#6 · Exempt your staff (optional)

Admins testing the server can trip detections. baobab automatically exempts anyone in the group.admin or group.moderator ACE groups. Add your staff as principals and grant the /ac admin commands:

# Make your staff members part of an admin group
add_principal identifier.steam:110000100000000 group.admin

# Let that group use /ac admin commands and receive update notices
add_ace group.admin command.ac allow

#7 · Restart and validate

1. 1
   Restart the server

   A full restart picks up the new resource and your server.cfg changes.

2. 2
   Read the console

   baobab logs its startup and version. No errors = good. If it doesn't start, see Troubleshooting.

3. 3
   Check the panel

   Your server shows online on Servers, and Dashboard begins populating as players join.

#About auto-updates

baobab keeps itself current. It checks for new versions about once an hour and downloads them straight to disk. The new files apply on your next server restart - the resource never restarts itself, so there’s nothing to configure and no special permission to grant.

#Go-live checklist