Introduction

FeloxAC is a modular anti-cheat system for FiveM. It combines client-side detection modules with a server-side authority layer and a web dashboard, protecting your server against cheats, injectors, and exploited resources.

These docs cover everything you need to get FeloxAC running and integrated with your own resources:

• Installation — license, resource placement, server.cfg, and the protection installer.
• ACE Permissions — staff permissions from server.cfg: every admin-menu feature, bypass and commands as separate ACE objects.
• Configuration — detections, punishment modes, and the Safe Events / Safe Scripts allowlists that stop false bans.
• False Bans — why they happen and how to fix them.
• Developer API (Exports) — every export FeloxAC provides to other resources.
• Ban Export — the banPlayer export in detail.
• Usage Examples — copy-paste integration recipes.

What FeloxAC protects against

How it works

1. Client detection modules watch for cheat behaviour on each player and report to the server.
2. The server layer is authoritative — it confirms detections, applies the configured punishment (ban / kick / log), and records evidence (screenshots and gameplay clips) to your Discord webhooks.
3. The dashboard is the single source of truth for configuration. Settings are synced to your running server automatically and can be reloaded live with fac reload.

Requirements

Installation

There are two ways in. The one-click installer does the whole setup for you, or you can follow the manual five-step route: get a license, add the resource, set your license.txt, update server.cfg, and run the protection installer.

Fast path — the one-click installer

feloxac-setup.exe automates steps 2 to 5 below: it extracts the resource, writes license.txt from your API token, configures server.cfg, and injects the third-party exports and guards. It runs locally on the machine that hosts the server. Get it from the Download page of your dashboard, together with the API token of the server you are installing on.

1

Put feloxac-setup.exe next to server.cfg

Drop the installer into your server folder — the same folder that holds server.cfg and resources/. Do not run it from your Downloads folder.

2

Open the program

Double-click feloxac-setup.exe. It detects the server folder on its own; if it shows the wrong path, use Change.

3

Paste your API token

Copy the token of your server from the dashboard and paste it into the FELOXAC API TOKEN field.

4

Press INSTALL

It extracts FeloxAC, writes license.txt, configures server.cfg and injects the exports. Restart your server when it finishes — you do not need to run fac install smart.

Prefer to do it by hand? The manual route is below.

Prerequisites

Step 1 — Get your license

1. Purchase a license at feloxac.com.
2. Your license is activated automatically after payment — there is no key to enter.
3. Open your dashboard and go to License. Under My Servers, enter your public server IP (the one in your connect address) and click Add server & get token. Your API token appears right there.

Step 2 — Add the resource

1. Download the FeloxAC resource from your dashboard's Download page.
2. Extract it into your server's resources/ folder.
3. Make sure the folder is named FeloxAC.

Step 3 — Configure license.txt

1. Open license.txt inside the FeloxAC folder and delete everything in it.
2. In your dashboard, go to Documentation → Replace license.txt.
3. Select your server, click Copy license.txt Content, and paste it into license.txt.
4. Save the file.

This file contains your API token. FeloxAC reads it at startup and validates it against feloxac.com for your server IP.

Step 4 — Configure server.cfg

Add OneSync near the top of your server.cfg:

set onesync on
set onesync_population false

Add these among your other permission lines:

add_unsafe_child_process_permission "FeloxAC"
add_ace resource.FeloxAC command allow

Add the ensure line at the very top of your ensure list, before every other resource:

ensure FeloxAC

Staff permissions (ACE) — optional

Staff permissions (admin menu, bypass, commands) are also given from server.cfg. They have their own section: ACE Permissions.

Step 5 — Run the protection installer

Copying the resource is not enough — you must run the installer once so FeloxAC protects your other scripts.

1. Start your server.
2. Open the Live Console (txAdmin or the server console) and run:

   fac install smart

3. Wait for the installation to finish.
4. Restart your server. FeloxAC is now active.

What fac install smart does

It scans every resource and installs FeloxAC protection only into scripts that use network events. Resources with no network events (vehicles, peds, maps, libraries) are skipped automatically, so the install stays fast and clean.

Other install modes

Verify the installation

• Run status (or check txAdmin) — FeloxAC should appear in the resource list.
• The server console prints FeloxAC's startup and license validation result.
• Connecting players are logged (join/leave) if connection logging is enabled.

Troubleshooting

License is invalid / players get kicked

• Confirm license.txt contains the exact token from your dashboard.
• Confirm your server's public IP matches the IP registered for the license.
• Make sure the server can reach https://feloxac.com (check firewall / hosts file). FeloxAC is fail-closed — if it cannot validate the license it stops and kicks players by design.

fac command not found

• Confirm the FeloxAC resource is running (status).
• The command prefix is fac, not feloxac. If you changed CommandPrefix in config, use your custom prefix.

Detections not firing after install

• Confirm ensure FeloxAC is at the top of your ensure lines.
• Confirm OneSync is on (set onesync on).
• Confirm your server build is 14317+.
• Re-run fac install smart and restart.

ACE Permissions

Staff permissions can be granted straight from server.cfg with FiveM's ACE system — the same add_ace / add_principal lines you already use for txAdmin and your other resources. Every part of the in-game /fac admin menu has its own permission, so a moderator can get bans and kicks without troll options or vehicle spawn.

All permissions

Objects are hierarchical, exactly like FiveM's own command / command.kick: allowing FeloxAC.AdminMenu allows everything under it, and a more specific deny beats a broader allow.

AdminMenu — the in-game /fac menu

Bypass

Commands

Shortcut — allow a whole group

You don't have to list every object. Allow the category and everyone in that group gets all of it:

add_ace group.admin FeloxAC.AdminMenu allow

Take one feature back from the same group with a more specific deny:

add_ace group.mod FeloxAC.AdminMenu allow
add_ace group.mod FeloxAC.AdminMenu.Troll deny
add_ace group.mod FeloxAC.AdminMenu.CarSpawn deny

Example server.cfg

# FELOXAC PERMISSIONS in server.cfg
# add_ace [principal] [object] [allow|deny]      -> grants (or denies) an object to a group / identifier
# add_principal [child_principal] [parent_principal] -> puts an identifier into a group
# Any FiveM identifier works: discord, steam, license, fivem, ip, xbl, live.
# Find someone's identifiers in txAdmin > Players, or on the FeloxAC dashboard > Players.

# SUPER ADMINS
add_principal identifier.discord:123456789012345678 group.superadmin

# ADMINS
add_principal identifier.discord:234567890123456789 group.admin
add_principal identifier.license:1a21a2380bca020822ad301eb4e579e00a7063f3 group.admin

# MODERATORS
add_principal identifier.discord:345678901234567890 group.mod

# PERMISSIONS GIVEN TO SUPER ADMINS
add_ace group.superadmin FeloxAC.AdminMenu allow
add_ace group.superadmin FeloxAC.Commands allow
add_ace group.superadmin FeloxAC.Bypass allow

# PERMISSIONS GIVEN TO ADMINS
add_ace group.admin FeloxAC.AdminMenu allow
add_ace group.admin FeloxAC.AdminMenu.Admins deny

# PERMISSIONS GIVEN TO MODERATORS
add_ace group.mod FeloxAC.AdminMenu.Players allow
add_ace group.mod FeloxAC.AdminMenu.Tools allow
add_ace group.mod FeloxAC.AdminMenu.Monitor allow
add_ace group.mod FeloxAC.AdminMenu.Bans allow
add_ace group.mod FeloxAC.AdminMenu.Kicks allow
add_ace group.mod FeloxAC.AdminMenu.Messages allow
add_ace group.mod FeloxAC.AdminMenu.Lookup allow
add_ace group.mod FeloxAC.AdminMenu.Logbook allow

Which one should I use — ACE or the panel?

• Panel (Admins page) — per person, changeable at any time without touching files, synced live to the server. Best for day-to-day staff management.
• ACE (server.cfg) — per group, lives with the rest of your server permissions, survives panel changes. Best for owners and for servers that manage every permission in server.cfg.
• Both can be used at once. A person who has both gets the union of the two.

Configuration

FeloxAC is configured from your dashboard. Everything is done through the panel — toggles, dropdowns, and list ("chip") inputs — so you never edit raw config files by hand.

Changes are synced to your running server automatically. To apply them immediately, run:

fac reload

How the panel works

• Toggles turn a detection on or off.
• Dropdowns choose the action for a detection (Ban / Kick / Log).
• Lists (chips) hold multiple values — such as Safe Events, Safe Scripts, and the white/black lists. To add an item, type it into the "New item, press enter to add…" box and press Enter. To remove one, click the ✕ on its chip.

Sections at a glance

Punishment modes (Ban / Kick / Log)

Safe Events — stop false bans from events

Where: Settings → Safe Events list.

Some legitimate scripts give a weapon or teleport a player through a network event. If that event trips a detection, honest players get false-banned. Add the offending event name to Safe Events and FeloxAC will skip weapon-give / teleport detection for it.

How to add one: type the event name into the Safe Events box and press Enter — for example job:teleportToWork or police:warpToStation. It appears as a chip in the list.

How to find the event name:

• Check the detection log / Discord evidence — the triggering event is included in the ban details.
• Or check the script's source for the TriggerServerEvent / TriggerClientEvent name it fires when teleporting or giving the weapon.

Safe Scripts — trust a whole resource

Where: Settings → Safe Scripts list.

Where Safe Events whitelists a single event, Safe Scripts trusts an entire resource. Add a resource here when it legitimately teleports players or gives weapons and you don't want to whitelist each event individually — for example job systems, rental systems, admin menus, or weapon shops.

How to add one: type the resource name into the Safe Scripts box and press Enter (for example my-rental-system). Matching is case-insensitive.

Ignored Scripts — fully exclude a resource

Where: Settings → Ignored Scripts list.

Ignored Scripts disables all FeloxAC checks for a resource — weapons, entities, events, everything. Use it only for a fully trusted resource that is otherwise incompatible with the anti-cheat.

Which one should I use?

White lists & black lists

Entities and weapons use the same chip inputs. Type a model name or hash (or weapon name) and press Enter.

Key detection toggles

Main

Weapons

Entities

False Bans

Almost every false ban comes from an object, a vehicle, or a ped. In the vast majority of cases it is not the detection that is wrong — it is one of two things:

1. The anti-cheat was not fully installed (the protection installer was never run), or
2. Your server basics are not set up correctly (OneSync / license), or
3. A legitimate resource keeps spawning the same entity, which just needs to be whitelisted.

Step 1 — Check your setup first

Most false bans disappear the moment the basics are correct:

• OneSync is ON — set onesync on
• OneSync population is OFF — set onesync_population false (this one is the most commonly forgotten)
• You have a paid FiveM (Keymaster) account — free / unlicensed setups cause detection problems
• You ran the installer — fac install smart, then restarted the server

If any of these is missing, fix it and test again before whitelisting anything.

Ban reason → what to fix

Look up the reason shown on the ban or on the detection log, and apply the fix next to it.

Illegal Object Spawn Detected

A resource spawned an object the anti-cheat does not recognise. If the object is legitimate and it is always the same one, whitelist it:

• Config → Entities → White Listed Objects — type the model name or hash, press Enter.
• Make sure Enable Objects White List is ON, otherwise the list is ignored.
• Run fac reload (or restart) to apply.

Exceeded Object / Vehicle / Ped Spawn Rate

This is a rate limit, not a model problem: a script spawned more entities within 5 seconds than the limit allows. In Config → Entities you can raise the limit or turn the limiter off:

• Objects — Objects Limit In5 Seconds / Enable Objects Limiter
• Vehicles — Vehicles Limit In5 Seconds / Enable Vehicles Limiter
• Peds — Peds Limit In5 Seconds / Enable Peds Limiter

Raise the limit first. Only turn a limiter off when a legitimate resource genuinely needs bulk spawning (map loaders, garages, event scripts).

Illegal Vehicle Spawn Detected

This almost always means the resource that spawns the vehicle does not have the FeloxAC include installed. Without it the spawn arrives unsigned, and the anti-cheat cannot tell it apart from an injected one.

• Find which resource spawns the vehicle, and make sure the include is installed in that resource.
• Run fac install smart and restart the server — it injects the include into eligible resources.

Resource Injection Detected

Read the detail line of the detection — it tells you which of the two fixes you need:

• The detail names an event → add that event to Config → Main → Safe Events.
• The detail shows a file path like @@Script/test.lua → add it to Config → Main → Anti Resource Injection Safe List, but without the @@: type Script/test.lua.

Entries match as a substring of the callsite path, so you choose how wide the exemption is:

• my-resource/client/cl-garage.lua — exempts that one file (preferred).
• my-resource — exempts every file in that resource (much wider; use only if you have to).

Ped false bans

If players are getting false-banned from a ped, it is almost always one of these:

• OneSync is not on
• No paid FiveM Keymaster account
• onesync_population is not set to false (the forgotten command)
• fac install smart was not run

Fix those first. If the ban always comes from the same ped, that ped is legitimate — add its model to the White Listed Peds list.

Object false bans

• If the anti-cheat keeps banning from objects in general, fac install smart was most likely not run, so the protection was never installed. Run it and restart.
• If the ban is always from the same object, that object is legitimate — add it to the White Listed Objects list.

Vehicle false bans

• Make sure fac install smart has been run and the server restarted.
• If a specific, legitimate vehicle is repeatedly flagged, add it to the White Listed Vehicles list.

How to whitelist a model

Whitelisting is done from the dashboard, using the chip inputs:

• White Listed Peds — for peds
• White Listed Objects — for objects
• White Listed Vehicles — for vehicles

Type the model (name or hash) into the "New item, press enter to add…" box and press Enter. Then run fac reload (or restart) to apply.

When it's a script, not an entity

If the false ban is caused by a resource that teleports players or gives weapons (not by a spawned entity), use Safe Events or Safe Scripts instead — see Configuration.

Developer API (Exports)

FeloxAC exposes exports so your resources can ban/kick players, read player state, and tell the anti-cheat when an action is legitimate (admin teleports, heals, weapon gives, and so on).

All exports are called on the FeloxAC resource:

exports['FeloxAC']:exportName(args)

Server exports

Moderation

-- Ban a player for 1 hour (3600 seconds)
exports['FeloxAC']:banPlayer(source, 'Aimbot', { by = 'Admin' }, 3600)

-- Unban by id
exports['FeloxAC']:unbanPlayer('BAN-ID-HERE', 'Appeal accepted', 'HeadAdmin')

-- Kick instead of banning
exports['FeloxAC']:kickPlayer(source, 'AFK too long', { by = 'Admin' })

-- Look up a ban, then lift every ban on the server
local found, banData = exports['FeloxAC']:getBanInfo('BAN-ID-HERE')
if found then print(banData.reason) end
exports['FeloxAC']:unbanAllPlayers('HeadAdmin')

-- Evidence straight to a Discord webhook
exports['FeloxAC']:screenshot(source, 'https://discord.com/api/webhooks/...')
exports['FeloxAC']:captureLastSeconds(source, 'https://discord.com/api/webhooks/...')

Player state

-- Everything FeloxAC knows about a connected player
local ids    = exports['FeloxAC']:getPlayerIdentifiers(source)
local tokens = exports['FeloxAC']:getPlayerTokens(source)
local score  = exports['FeloxAC']:getThreatScore(source)
local played = exports['FeloxAC']:getPlayTime(source)

print(ids.license, ids.discord, #tokens, score, played)

-- Skip your own admin checks for a player FeloxAC already exempts
if exports['FeloxAC']:hasBypass(source) then return end

Configuration

-- Apply config edits without restarting the resource (same as: fac reload)
if exports['FeloxAC']:ReloadConfiguration() then
    print('FeloxAC config reloaded')
end

Legitimate-action markers (server)

These tell FeloxAC that an action performed by your script is intentional, so a detection does not fire. They are not security bypasses — they scope an allowance to a specific action.

-- Admin teleports a player without a false ban
exports['FeloxAC']:markExternalTeleport(target)
SetEntityCoords(GetPlayerPed(target), x, y, z)

-- Heal a player from a server script
exports['FeloxAC']:markExternalHeal(target)

-- A job script hands out a weapon: register it, or the possession sweep bans
local weapon = GetHashKey('weapon_pistol')
exports['FeloxAC']:registerLegalWeapon(target, weapon)

-- ...and drop the registration when you take the weapon back
exports['FeloxAC']:unregisterLegalWeapon(target, weapon)
exports['FeloxAC']:clearLegalWeapons(target)   -- or drop every one at once

-- Ped model change (skin menu, job outfit). Pass nil to accept the current model.
exports['FeloxAC']:registerLegalPedModel(target, 'a_m_y_business_01')

-- Parkour / minigame super jump. durationMs is in MILLISECONDS.
exports['FeloxAC']:registerLegalSuperJump(target, 30000)
exports['FeloxAC']:unregisterLegalSuperJump(target)   -- end it early

-- Noclip from your own admin menu. Call it SERVER-side, after your own admin check.
-- durationMs is in MILLISECONDS (default 30000, capped at 600000 = 10 min).
exports['FeloxAC']:registerLegalNoclip(target)          -- when noclip is enabled
exports['FeloxAC']:registerLegalNoclip(target, 60000)   -- ...or ask for a longer window
exports['FeloxAC']:unregisterLegalNoclip(target)        -- when noclip is disabled

-- Megaphone / radio. Sticky: pair every true with a false.
exports['FeloxAC']:markVoiceOverrideActive(target, true)
exports['FeloxAC']:markVoiceOverrideActive(target, false)

-- Server-side spawn: create it pre-approved, or mark a handle you already hold
local veh = exports['FeloxAC']:CreateEntity(GetHashKey('adder'))
exports['FeloxAC']:MarkServerEntity(veh, GetHashKey('adder'))

Bypass & diagnostics (server)

-- Freeroam / event zone: lift detections, then always put them back
exports['FeloxAC']:toggleBypass(target, true)
-- ...
exports['FeloxAC']:toggleBypass(target, false)

-- Safer: a self-expiring window. duration is in SECONDS (capped at 43200 = 12 h).
exports['FeloxAC']:tempBypass(target, 60)

-- Is this event name already on FeloxAC's protected list?
if exports['FeloxAC']:IsEventProtected('myresource:giveMoney') then
    print('already protected')
end

Client exports

Client exports are markers: they tell FeloxAC that what your script is about to do is legitimate. Apart from banPlayer, kickPlayer, screenshot and captureLastSeconds, they do not perform the action for you. The pattern is always the same — mark first, then call the game native:

exports['FeloxAC']:markExternalTeleport()
SetEntityCoords(PlayerPedId(), x, y, z, false, false, false, false)

Legitimate-action markers (client)

-- Every marker below follows the same shape: mark first, then call the native.
exports['FeloxAC']:hasTeleported()          -- same marker as markExternalTeleport()
SetEntityCoords(PlayerPedId(), x, y, z, false, false, false, false)

exports['FeloxAC']:healthRefilled()         -- same marker as markExternalHeal()
SetEntityHealth(PlayerPedId(), 200)

exports['FeloxAC']:playerRevived()
exports['FeloxAC']:resettedStamina()        -- opens a ~10 s window
exports['FeloxAC']:hasAddedAmmo()           -- opens a ~5 s window

-- Declare the ped model before you apply it (name or hash). Returns true when the
-- call came from a resource; repeat refreshes are capped at one per 60 s.
exports['FeloxAC']:hasChangedPedModel('a_m_y_business_01')
SetPlayerModel(PlayerId(), GetHashKey('a_m_y_business_01'))

-- Right before an on-screen keyboard
exports['FeloxAC']:displayInputBox()
DisplayOnscreenKeyboard(1, 'FMMC_KEY_TIP8', '', '', '', '', '', 30)

-- Cuff / carry / cutscene / safezone. durationMs defaults to 5000, capped at 60000.
exports['FeloxAC']:allowImmortalityFlags(10000)

-- Mechanic script repairing a vehicle
exports['FeloxAC']:MarkVehicleRepair()
SetVehicleFixed(veh)

Godmode / player state (client)

These are state switches, not one-shot markers: whatever you turn on, you have to turn off again.

-- admin goes invisible, then comes back
exports['FeloxAC']:isVisible(false)
SetEntityVisible(PlayerPedId(), false, false)
-- ...
exports['FeloxAC']:isVisible(true)
SetEntityVisible(PlayerPedId(), true, false)

-- The rest of the switches follow the same on/off discipline
exports['FeloxAC']:proofsEnabled(false)
exports['FeloxAC']:canBeDamaged(false)
exports['FeloxAC']:isInvincible(true)
SetEntityInvincible(PlayerPedId(), true)
-- ...release everything you turned on
SetEntityInvincible(PlayerPedId(), false)
exports['FeloxAC']:isInvincible(false)
exports['FeloxAC']:canBeDamaged(true)
exports['FeloxAC']:proofsEnabled(true)

-- Ragdoll and spectate are declared the same way
exports['FeloxAC']:canRagdoll(false)
exports['FeloxAC']:setSpectatorMode(true)

Weapons & damage (client)

None of these give, remove or modify anything by themselves — they whitelist what your own script is about to do. Call the export, then the native.

kind is one of these strings (case-insensitive): weaponDamage, meleeDamage, vehicleDamage, weaponDefense, weaponDefense2, meleeDefense.

local weapon = GetHashKey('weapon_pistol')

-- give a weapon
exports['FeloxAC']:giveWeapon(weapon, 'my-weapon-shop')
GiveWeaponToPed(PlayerPedId(), weapon, 250, false, true)

-- take it back
exports['FeloxAC']:removeWeapon(weapon)
RemoveWeaponFromPed(PlayerPedId(), weapon)

-- per-weapon damage multiplier
exports['FeloxAC']:setDamageModifier(weapon, 1.5)
SetWeaponDamageModifier(weapon, 1.5)

-- ...and when the buff ends
exports['FeloxAC']:removeDamageModifier(weapon)
SetWeaponDamageModifier(weapon, 1.0)

-- player-wide melee buff (gym, PD, safezone...)
exports['FeloxAC']:setPlayerDamageModifier('meleeDamage', 1.8)
SetPlayerMeleeWeaponDamageModifier(PlayerId(), 1.8)

exports['FeloxAC']:removePlayerDamageModifier('meleeDamage')
SetPlayerMeleeWeaponDamageModifier(PlayerId(), 1.0)

-- Drop every weapon whitelist entry at once
exports['FeloxAC']:removeAllWeapons()
RemoveAllPedWeapons(PlayerPedId(), true)

-- Admin tool playing a scenario / animation
exports['FeloxAC']:markToolScenario('WORLD_HUMAN_WELDING', 'my-admin-menu')

-- setNewDamage is the legacy name for setDamageModifier -- identical behaviour
exports['FeloxAC']:setNewDamage(weapon, 1.5)
SetWeaponDamageModifier(weapon, 1.5)

Entities, camera & evidence (client)

exports['FeloxAC']:CreateVehicle(GetHashKey('adder'))
local veh = CreateVehicle(GetHashKey('adder'), x, y, z, heading, true, false)

exports['FeloxAC']:ChangeVehiclePlate(veh, 'FELOX01')
SetVehicleNumberPlateText(veh, 'FELOX01')

-- Peds and objects are declared exactly like vehicles
exports['FeloxAC']:CreatePed(GetHashKey('a_m_y_business_01'))
local ped = CreatePed(4, GetHashKey('a_m_y_business_01'), x, y, z, heading, true, false)

exports['FeloxAC']:CreateObject(GetHashKey('prop_barrier_work05'))
local obj = CreateObject(GetHashKey('prop_barrier_work05'), x, y, z, true, true, false)

-- Whitelist a texture dictionary by name
exports['FeloxAC']:allowTexture('mpleaderboard')

-- Legitimate freecam / admin camera
local cam = CreateCam('DEFAULT_SCRIPTED_CAMERA', true)
exports['FeloxAC']:createCam(cam)
-- ...when you are done
exports['FeloxAC']:destroyCam(cam)
DestroyCam(cam, false)
exports['FeloxAC']:destroyCams()   -- or drop every handle at once

-- Admin tool holding input: keep calling it while the tool stays open
exports['FeloxAC']:disableCamControls()
exports['FeloxAC']:disableAllControls()

Vehicle modifiers (client)

Call these when your script legitimately changes vehicle physics, so the speed-hack layer adopts the new values as its baseline instead of flagging them.

SetVehicleCheatPowerIncrease(veh, 1.6)
exports['FeloxAC']:newCheatPowerIncrease(1.6)
exports['FeloxAC']:registerLegalSpeedModifier()

-- Top speed and gravity are declared the same way
SetVehicleMaxSpeed(veh, GetVehicleModelMaxSpeed(GetEntityModel(veh)) * 1.4)
exports['FeloxAC']:newTopSpeedModifier(1.4)   -- values <= 1.1 are treated as 1.1

SetGravityLevel(2)
exports['FeloxAC']:newGravity(30.0)           -- values < 25.0 are treated as 25.0
exports['FeloxAC']:registerLegalSpeedModifier()

Moderation & diagnostics (client)

local alive, lastHeartbeat, lastLoopTime = exports['FeloxAC']:isRunning()
if not alive then print('FeloxAC is not running') end

exports['FeloxAC']:banPlayer('Custom client detection', { by = 'my-resource' }, -1)

-- Kick the local player instead
exports['FeloxAC']:kickPlayer('Custom client detection', { by = 'my-resource' })

-- Check an event name before you trigger it
if exports['FeloxAC']:IsEventProtected('myresource:giveMoney') then
    print('this event is protected by FeloxAC')
end

Ban Export

Use the banPlayer export to ban a player from any server-side script — your admin menu, a custom detection, a report system, and so on. The ban is applied through the same pipeline FeloxAC uses internally, so it is recorded in your ban list, synced to the dashboard, and logged to Discord.

Signature

exports['FeloxAC']:banPlayer(source, reason, details, duration)

Returns: a boolean indicating whether the punishment was applied.

Examples

Permanent ban

-- Omitting duration uses your configured BanDuration (default: permanent)
exports['FeloxAC']:banPlayer(source, 'Cheating')

-- Or be explicit
exports['FeloxAC']:banPlayer(source, 'Cheating', nil, -1)

Temporary ban

-- Ban for 1 day (86400 seconds)
exports['FeloxAC']:banPlayer(source, 'Toxic behaviour', { by = 'Moderator' }, 86400)

Ban with rich details

exports['FeloxAC']:banPlayer(source, 'Money exploit', {
    by       = 'AutoDetect',
    amount   = 500000,
    resource = GetCurrentResourceName(),
}, -1)

Ban from an admin command

RegisterCommand('myban', function(src, args)
    local target = tonumber(args[1])
    local reason = table.concat(args, ' ', 2)
    if not target or reason == '' then
        return print('Usage: myban [id] [reason]')
    end
    exports['FeloxAC']:banPlayer(target, reason, { by = GetPlayerName(src) }, -1)
end, true) -- restricted command

Ban from another resource via an event

-- In your other resource (server side)
RegisterNetEvent('myac:ban', function(targetId, reason, seconds)
    exports['FeloxAC']:banPlayer(targetId, reason, { by = 'myac' }, seconds or -1)
end)

Related exports

Usage Examples

Copy-paste patterns for the most common integrations. All exports are called on the FeloxAC resource.

Admin teleport without a false ban

Mark the teleport as legitimate right before you move the player.

Server side:

RegisterCommand('tp', function(src, args)
    local target = tonumber(args[1]) or src
    exports['FeloxAC']:markExternalTeleport(target)
    -- ... perform your teleport (SetEntityCoords on the target's ped) ...
end, true)

Client side (if you teleport locally):

exports['FeloxAC']:markExternalTeleport()
SetEntityCoords(PlayerPedId(), x, y, z, false, false, false, false)

Admin heal / revive without a false ban

-- Client side, before healing/reviving
exports['FeloxAC']:markExternalHeal()
SetEntityHealth(PlayerPedId(), 200)

-- After a revive
exports['FeloxAC']:playerRevived()

Give a weapon from a trusted script

The cleanest option is to add your resource to the Safe Scripts list in the dashboard, so its weapon gives are always trusted (see Configuration).

For a per-action allowance from client code instead:

exports['FeloxAC']:giveWeapon(GetHashKey('weapon_pistol'), 'my-weapon-shop')

Ban a cheater from your own detection

-- Server side
if isCheating then
    exports['FeloxAC']:banPlayer(source, 'Custom detection: money exploit', {
        by = GetCurrentResourceName(),
    }, -1)
end

See the Ban Export page for full details.

Gate content by threat score

-- Server side: deny a sensitive action to high-threat players
local score = exports['FeloxAC']:getThreatScore(source) or 0
if score > 75 then
    TriggerClientEvent('chat:addMessage', source, { args = { 'System', 'Action temporarily unavailable.' } })
    return
end

Collect evidence on demand

-- Server side: screenshot a suspicious player and post it to Discord
exports['FeloxAC']:screenshot(source, 'https://discord.com/api/webhooks/...')

-- Grab the last ~10 seconds of their gameplay
exports['FeloxAC']:captureLastSeconds(source, 'https://discord.com/api/webhooks/...')

Fix false bans from a job / rental script

If a specific event from a script teleports players or gives them items and causes false bans, add just that event to the Safe Events list in the dashboard (type the event name, press Enter). If the whole resource is trusted, use Safe Scripts instead.

Spawn entities that the anti-cheat trusts

-- Client side
local veh = exports['FeloxAC']:CreateVehicle(GetHashKey('adder'))

-- Server side
local ent = exports['FeloxAC']:CreateEntity(GetHashKey('prop_barrier_work05'))

Reload configuration after changes

exports['FeloxAC']:ReloadConfiguration()

Or from the console:

fac reload