GFX Anti Meta

GFX Anti Meta - Magic Bullet & Ped Accuracy Detection

Cheaters ruin roleplay servers. Magic bullets that shoot through walls, aimbots with impossible accuracy - they kill the experience for legitimate players. GFX Anti Meta catches these specific exploits by monitoring bullet behavior and ped accuracy in real-time, then logs violations to Discord so you can take action before the damage spreads.

What It Does

This is focused anti-cheat targeting two common exploits that slip past basic protection: magic bullets (shooting through solid objects) and modified ped accuracy (aimbots that give perfect headshots every time). It watches for patterns that no legitimate player would create, logs them with player identifiers, and optionally kicks or bans based on your settings.

The magic bullet detection is clever - it knows when a bullet path should be blocked by geometry but somehow connects anyway. That's the signature of modified game files or injected code. The accuracy detection tracks headshot percentages and shot patterns that exceed human capability. Both systems run quietly in the background without affecting server performance.

Key Features

• Magic Bullet Detection - Monitors bullet trajectories for wall-penetration exploits. Flags when bullets connect through solid geometry they shouldn't
• Ped Accuracy Monitoring - Tracks accuracy patterns to identify aimbots and modified accuracy values that exceed realistic player performance
• Discord Logging - Real-time webhook integration sends detailed reports with player identifiers, detection type, and timestamp to your Discord
• Configurable Actions - Choose to kick, ban, or just log violations. Test mode lets you monitor without punishing players while tuning settings
• Bypass Whitelist - Exempt specific Steam IDs from checks (useful for admins testing, or trusted players if you get false positives)
• Framework Integration - Hooks into ESX or QBCore player loaded events to start monitoring at the right moment
• Test Command - Trigger detection manually to verify your webhook and logging systems are working correctly
• Color-Coded Discord Alerts - Red for detected violations, green for cleared checks, making triage faster in your moderation channel

Perfect For

• Servers tired of cheaters with modified game files slipping past basic anti-cheat
• Communities that need evidence logs for ban appeals and moderation decisions
• Admins who want real-time alerts when exploits are detected
• Roleplay servers where combat fairness directly impacts player retention

Technical Details

• Framework Support: ESX (esx:playerLoaded) and QBCore (QBCore:Client:OnPlayerLoaded) - configurable event triggers
• Detection Methods: Client + server-side validation for bullet paths and accuracy statistics
• Performance Impact: Minimal - checks run on specific events, not constant polling
• Discord Webhooks: Customizable bot name, avatar, and embed colors for branded logging
• Action Options: Kick with custom message, ban with custom message, or log-only mode

Installation

1. Extract GFX Anti Meta to your resources folder
2. Set up Discord webhook URL in config (create one in your Discord server settings)
3. Configure your framework's player loaded event (ESX or QBCore)
4. Set default spawn location for respawn after detection (if using kick/ban)
5. Choose action mode (kick, ban, or log-only) while you test thresholds
6. Add to server.cfg and restart

Configuration Breakdown

The config is straightforward but important to tune correctly. You'll want to start in log-only mode (kickActive = false, banActive = false) to see what gets flagged on your server. Some scripts or server modifications can trigger false positives, so monitoring first prevents wrongful bans.

Once you're confident in your thresholds, enable kicks for first offenses and bans for repeat violators. The bypass list lets you whitelist admins or trusted players by Steam ID if they trip detection during testing or legitimate gameplay.

How Magic Bullet Detection Works

When a player fires a weapon, the script traces the bullet path and checks if it should be blocked by world geometry. If the bullet connects with a target despite passing through walls, floors, or other solid objects, it's flagged as a magic bullet violation.

The system distinguishes between legitimate penetration (some weapons can shoot through thin materials) and exploit-based wall hacking. It logs the violation with Wall Magic Detected status and color-codes it red in Discord. Repeated violations within a session trigger your configured action (kick or ban).

Ped Accuracy System

This tracks shot statistics - hits vs misses, headshot percentage, rapid-fire accuracy patterns. Human players, even skilled ones, have variance. Aimbots don't. They maintain impossible consistency.

When accuracy patterns exceed realistic thresholds (configurable in the detection logic), it flags as Accuracy Detected and logs to Discord. Like magic bullet detection, you control the response: kick, ban, or just collect evidence.

Discord Integration

The webhook sends rich embeds with all relevant data: player name, Steam ID, detection type (magic bullet or accuracy), whether it was confirmed or ruled out, and timestamp. The bot avatar and name are customizable (default GFX Squad branding), and you can set custom footer/header URLs.

Color coding makes moderation easy at a glance: red (#FF0000) for confirmed violations, green (#00FF00) for cleared checks. Your moderation team can scan the channel and immediately see what needs attention.

Framework Compatibility

• ✅ ESX - Uses esx:playerLoaded event, works with all ESX versions
• ✅ QBCore - Integrates via QBCore:Client:OnPlayerLoaded event
• ✅ Custom Frameworks - Configurable player loaded event means you can adapt to any framework

Configuration Example

Config = {}

Config.PlayerCheck = true
Config.kickActive = true  -- Set false for log-only mode
Config.banActive = false  -- Enable for permanent bans

Config.PlayerLoadedEvent = esx:playerLoaded -- or QBCore:Client:OnPlayerLoaded
Config.DefaultSpawnLocation = vector3(323.65, -218.56, 54.09)
Config.magicTestCommand = magicTest

Config.BypassPlayerList = {
    [steam] = {
        -- Add Steam IDs here to bypass checks
    }
}

Config.LogMessages = {
    [magic] = {
        [message] = Magic Bullet Usage. %s,
        [detected] = Wall Magic Detected,
        [notdetected] = Wall Magic Not Detected,
        [detectedColor] = 16711680,  -- Red
        [notDetectedColor] = 65280,  -- Green
    },
    -- Accuracy config similar structure
    [magicKickMsg] = Citizen Modified Detected.,
    [magicBanMsg] = You are banned.,
}

Config.Discord = {
    LogActive = true,
    DiscordWebhook = YOUR_WEBHOOK_URL_HERE,
    BotName = GFX Log,
    BotAvatar = YOUR_AVATAR_URL,
}

Testing & Validation

Use the magic test command (default: /magicTest) to manually trigger detection and verify your webhook is receiving logs. This is crucial before enabling kicks or bans - you want to confirm the detection logic and logging pipeline work correctly on your specific server setup.

Run in log-only mode for 24-48 hours on a live server to establish baselines. Check the Discord logs for patterns. Are you seeing legitimate players flagged? Adjust thresholds. Only seeing actual cheaters? You're ready to enable enforcement actions.

What Makes It Stand Out

It's focused. Most anti-cheat systems try to catch everything and end up bloated or causing false positives. GFX Anti Meta targets two specific, common exploits and does them well. Magic bullets and accuracy manipulation are the cheats that ruin shootouts and roleplay combat, so stopping those protects your server's core experience.

The Discord integration is professional-grade too. Not just text logs - rich embeds with all the context your moderation team needs to make informed decisions. That evidence trail is invaluable when handling appeals or identifying repeat offenders across alt accounts.

Real-World Protection

A cheater joins your server with injected code that lets them shoot through walls. Within minutes, GFX Anti Meta logs the violation to Discord with their Steam ID. Your moderators see the red alert, spectate the player, confirm the exploit, and ban before they've even finished their first robbery.

That's the value - rapid detection and evidence collection. Most anti-cheat either misses these exploits entirely or catches them too late, after they've already ruined several players' experiences. This script catches them early and gives you the proof needed to act decisively.

Related Standalone Scripts

• VIEWPOINT V
• VIP System V2
• Izzy Spawn Selector
• Pickle’s Lottery System