How to Properly Set Up Anti-Cheat on Your FiveM Server

Official VenusAC Installation (2025)

This article mirrors the official documentation so you can install VenusAC correctly the first time. For the canonical guide, see VenusAC Installation Guide.

System Requirements

• Server artifacts version ≥ 5181
• OneSync enabled
• MySQL database access
• screenshot-basic resource installed

Required Resources

• Download screenshot-basic
• Latest server artifacts
• OneSync setup guide

Installation Steps

Step 1: Download VenusAC

1. Open your FiveM Keymaster dashboard.
2. Locate Venus AntiCheat in purchased assets.
3. Download and extract the venusac_anticheat.pack file.

Step 2: Server File Structure

1. Go to your server's resources directory.
2. Unzip and place the venusac_anticheat folder directly in resources.
3. Add this line to your server.cfg:

ensure venusac_anticheat

Important: Do not rename the resource folder. It must remain venusac_anticheat.

Step 3: Database Setup

Import the provided SQL schema into your MySQL database (file name: venusac_anticheat.sql). Example (excerpt):

CREATE TABLE IF NOT EXISTS `venusac_anticheat` (
  `ban_id` varchar(9) NOT NULL,
  `ban_reason` varchar(255) DEFAULT NULL,
  `banned_at` datetime NOT NULL DEFAULT current_timestamp(),
  `player_name` varchar(25) DEFAULT NULL,
  `steam_id` varchar(40) DEFAULT NULL,
  `ip_address` varchar(40) DEFAULT NULL,
  `license` varchar(100) DEFAULT NULL,
  `discord_id` varchar(100) DEFAULT NULL,
  `hwid_1` varchar(130) DEFAULT NULL,
  `hwid_2` varchar(130) DEFAULT NULL,
  `hwid_3` varchar(130) DEFAULT NULL,
  `hwid_4` varchar(130) DEFAULT NULL,
  `hwid_5` varchar(130) DEFAULT NULL,
  `cfx_id` varchar(100) DEFAULT NULL,
  `xbox_id` varchar(100) DEFAULT NULL,
  `live_id` varchar(100) DEFAULT NULL,
  `license_2` varchar(100) DEFAULT NULL,
  UNIQUE KEY `venusac_anticheat_index_1` (`ban_id`),
  UNIQUE KEY `venusac_anticheat_unique_identifiers` (`license`, `steam_id`, `discord_id`, `cfx_id`, `license_2`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin;

Step 4: Configuration Overview

Open the main config file inside the VenusAC resource (configs/anticheat_config.lua) and review the core options:

venusac.Debug = false
venusac.Locale = "en"
venusac.txAdminAuthentication = true
venusac.screenshotModule = "screencapture"
venusac.antiCheatName = "VenusAC AntiCheat"
venusac.adminMenu = true
-- During testing, prefer logs only:
venusac.detectionHandler = "log" -- "log" | "kick" | "ban"

Basic detection toggles (excerpt):

venusac.Detections.Client = {
  blacklistedPeds = true,
  blacklistedWeapons = true,
  godMode = true,
  noclip = true,
  modMenus = false,
}

Step 5: Final Verification

1. Fully restart the server (not just a resource refresh).
2. Watch the console for errors while VenusAC loads.
3. Verify with: refresh; ensure venusac_anticheat.
4. If enabled, open the admin menu using your txAdmin-authenticated account.

Post‑Installation Checklist

• Database tables created successfully
• Config customized (detectionHandler, webhooks, language)
• txAdmin authentication working (if enabled)
• Discord webhooks configured (optional)
• Test environment verified before production

Troubleshooting

Connection Problems

• Artifacts version ≥ 5181
• OneSync enabled
• DB credentials correct and reachable

Resource Loading Errors

• Dependencies installed (screenshot-basic)
• Folder name is exactly venusac_anticheat
• No conflicting resource names

Detection False Positives

• Start with venusac.detectionHandler = "log" for initial tuning
• Gradually tighten detections after reviewing logs