Config with an AI Assistant
The Config Editor contains a ready prompt for AI assistants. It makes the assistant read your own scripts first and then set detections, whitelists and staff permissions for your server, so you get a configuration built for your server without going through every setting by hand. You stay in control: the result only changes your configuration after you review it and press save.
Why There Is No Ready-Made Config
CXA does not sell configs, and anyone selling "ready CXA configs" is a scammer. Every server has its own framework, scripts, events, vehicles and weapons, so a copied config either punishes your own scripts or leaves gaps. No server is fully protected by a copied config. This page shows you how to build one for your server.
How It Works
- You give an AI assistant access to your server files.
- You paste the CXA prompt and your current configuration.
- The assistant reads your scripts, changes the values that need changing and explains every change.
- You paste its answer into Import code, read the change list and save.
The prompt and your configuration are copied to your clipboard. CXA never receives your server files, and nothing is sent anywhere until you paste it yourself.
Setting It Up
Open your license in the panel, go to Configuration and switch to Code view. The Build your config with an AI assistant card is at the top. In the visual editor, the link Build a config for your server with your AI assistant takes you there as well.
Step 1 — Show Your Server to the Assistant
Open your AI assistant inside your server folder, or upload your resources folder and server.cfg to it. The more of your scripts it sees, the more accurate the settings.
Assistants that can open a folder on your computer work best, because they can read every fxmanifest.lua and script on their own. If yours can only take uploads, give it at least server.cfg, the fxmanifest.lua files, your admin menu and your framework's permission setup.
Remove Secrets Before You Share Files
server.cfg usually contains secrets. Before you give it to an assistant, remove or blank out these lines: set cxa_license, sv_licenseKey, your database connection string, steam_webApiKey and rcon_password. Never share sv_config.lua, because it holds your license key, webhooks and API keys. The assistant needs none of them.
Step 2 — Paste the Prompt and Your Config
- Press Copy prompt + config. The panel copies the prompt and your current configuration in one go.
- Paste it into the assistant and send it.
Copy prompt + config includes your unsaved changes. If you prefer to paste the config yourself, press Copy prompt only, paste the prompt, then paste your config right under it.
The prompt follows the panel language. Switch the panel to EN or TR before you copy it to get the prompt in that language.
Step 3 — Import the Result
- Copy the complete
config.luathe assistant returns. - Press Import code and paste it.
- Press Validate and read the change list.
- Press Apply to draft, check the changes in the visual editor and press Save changes.
Config Editor explains the import window in detail.
The Buttons
| Button | What it does |
|---|---|
| Copy prompt + config | Copies the prompt and your current configuration, including unsaved changes, as one text. |
| Copy prompt only | Copies only the prompt, without your configuration. |
| Import code | Opens the import window for the assistant's answer. Only shown when you can edit the configuration. |
| Show prompt / Hide prompt | Shows the full prompt text in the card, so you can read it or select it by hand. |
What the Prompt Tells the Assistant
You can read the whole prompt with Show prompt. In short, it tells the assistant to:
- Read your server folder (
resources,server.cfg) before changing anything. If it cannot see your files, it must tell you exactly which files it needs and wait, instead of guessing what your scripts do. - Check your framework and set
Config.Framework. - Find your staff groups and ACE permissions and set
Config.Permissions.RolesandConfig.Bypass. - Find scripts that legally do what a cheat would do, and adjust the detections they affect:
- teleport, spectate, noclip and invisibility (admin menus, character creation, spawn selectors, jail, apartments)
- god mode, health and armor changes (safe zones, hospitals, EMS revive, arenas)
- speed, super jump, vehicle boost, vehicle god mode and plate changes (races, drift, tuning, job vehicles)
- weapons given by scripts and weapons with custom damage
- explosions used by scripts (heists, robberies, fireworks, mining) in
Config.ServerDetections.Explosions.Types - vehicles, peds and props spawned by scripts, for the blacklists and
Config.EntityLockdown - server events that give money, items or rewards, for
Config.EventGuard.StrictEvents - events that fire very often by design, for
Config.EventGuard.IgnoredEvents - commands your scripts register, for
Config.BlacklistedCommands
- Never put a weapon, vehicle, ped, object, event or command into a blacklist if one of your scripts uses it.
- Keep settings marked
[PERF]on only if your server needs them, and ask you for your usual player count if it matters.
It also sets strict rules for the answer:
- Change values only. Keep every key, its name and its type. Entries may be added to or removed from lists such as whitelists, blacklists and
Config.Rules. - Punishment is one of
ban,kick,warn,log,none.BanDurationis in hours,0means permanent. - Plain values only: no functions, no
require, no loops, no other Lua code. - No webhooks, tokens or API keys. They stay in
sv_config.luaon your server. - If a detection could hit innocent players, prefer
logorwarnoverbanand explain why. - If it is not sure about a value, keep the current one and say so.
The assistant has to answer with three parts:
ANSWER WITH
1. The complete config.lua in a single code block, ready to paste.
2. A list of every change: setting -> new value -> the file or resource that made it necessary.
3. Questions about anything you could not find in my files.Why Your Server Files Matter
Many legitimate scripts do something a cheat would also do: an admin menu that teleports, a race script that boosts cars, a heist that spawns explosions. A detection cannot tell them apart from a cheat unless the configuration allows them, and the assistant can only allow them if it sees them.
- With your files, it can name the exact event, weapon or vehicle a script uses and keep it out of the blacklists.
- Without your files, it can only guess. A guess either leaves a detection too strict, so your players get punished, or too loose, so cheaters get through.
- The change list ties every change to the file that caused it, so you can check each one.
Reviewing the Answer
Never save an assistant's answer without reading it. Before you press Save changes:
- Compare the assistant's change list with the panel's change list in the import window. Every key in the panel's list should be explained by the assistant.
- Answer the assistant's questions. Paste the answers back and ask for an updated config if something important was unclear.
- Check every detection the assistant set to
ban. If you are not sure, set it tologfirst. - After saving, watch the Detections tab for a few days and adjust what still triggers on innocent players.
The card itself reminds you: "Always read the change list before you save what an assistant wrote."
Privacy
- Webhooks and API keys are never part of the copied text. They are not in the configuration at all.
- The panel only copies text to your clipboard. Your server files go only to the assistant you choose; CXA never receives them.
- What you share with an assistant is handled under that assistant's own terms. Remove secrets from files first, as shown in Step 1.
Recommendations
Recommended:
- Give the assistant as many of your scripts as you can, especially admin menus, job scripts and anything that spawns entities or gives items.
- Run it again after you add new scripts, with your current config, so it only adds what is new.
- Keep a downloaded copy of your config before you import, so you can go back.
Avoid:
- Using a config someone else's assistant made for their server.
- Saving without reading the change list.
- Sharing
sv_config.luaor an uneditedserver.cfg.
Related Features
Config Editor
- The prompt card, Import code and the change list all live in the Code view. See Config Editor.
- A partial answer works too, for example only
Config.EventGuard = { ... }. Lists in it replace the whole list.
Detections & Punishments
- Detections & Punishments explains what
ban,kick,warn,logandnonedo, and how tolerance avoids false positives. - All Detections lists every detection key the assistant may change.
Event Guard and Staff Bypass
- Reward events end up in
Config.EventGuard.StrictEvents. See Event Guard. - Staff found in your files end up in
Config.Bypassand the staff roles. See Staff Bypass and Staff Roles & Command Access.
Common Problems
The Assistant Did Not Look at My Files
What you see: The answer changes values without naming any of your scripts.
How to fix it:
- Open the assistant inside your server folder, or upload the files it asks for.
- Tell it to follow the MY SERVER FILES part of the prompt and list the files it read.
- If it says it cannot read files, send
server.cfg(without secrets) and yourfxmanifest.luafiles first.
"Could not copy, open the prompt and select it manually."
What you see: The copy buttons do not work in your browser.
How to fix it:
- Press Show prompt, select the text and copy it with
Ctrl C. - For the config, press Copy all in the code view, or Download and open the file.
Validate Shows a Parse Error
What you see: The import stops with a message like Line 12: Variables and function calls are not allowed ('GetConvar').
How to fix it:
- The assistant added Lua code. Ask it again for plain values only, as the prompt says.
- Make sure you pasted only the code block, not the assistant's explanation around it.
Validate Lists Invalid Values
What you see: The import window shows 2 invalid value(s): with keys and reasons.
How to fix it:
- Paste the error lines to the assistant and ask it to fix exactly those values.
- Keys the assistant invented are ignored, they do not cause errors. If a change you expected is missing from the change list, the key name was probably wrong.
Players Get Punished After the Import
What you see: Normal players are kicked or banned by a detection the assistant changed.
How to fix it:
- Set that detection to
login the visual editor and save. - Tell the assistant which script triggers it and paste the detection from the Detections tab. Ask for a corrected value.
- Unban the affected players, see Bans & the CXA Network.
© 2026 CodeXart Studios · CXA Anticheat