LowThela - Server-Side Anticheat for FiveM
Most cheats are cancelled on the server before other players ever feel them. What FiveM can't block, LowThela detects and punishes, with evidence you can read.
WHAT IT STOPS
Combat
• God mode: lethal hits that do nothing, invincibility, damage-resistance tricks, bullet/melee proofs
• Magic bullet & shooting through walls: hits from guns the player doesn't own or isn't holding, from beyond weapon range, or through walls (confirmed by the victim's game)
• Silent aim: hits far off the crosshair and stretched hitboxes (male and female models)
• Rapid fire: hits faster than the weapon can physically fire
• Damage boost: native multipliers AND spoofed damage. The server learns each gun's real damage, addon guns included
• Punch player: one-hit and long-range melee
Players & vehicles
• Launch player: invisible explosions, thrown cars and objects, entities spawned onto players
• Vehicle kick: remote task clearing, forced exits and animation hijacks are cancelled; the victim stays in their seat
• Vehicle delete: an occupied car that gets deleted is respawned and its passengers are put back in
• Vehicle explode: blowing up someone else's car is blocked
• Fire troll: fake molotovs, flame jets, fires started from far away, fire spam, burning animals attached to players
Server & network
• Explosion, projectile and entity spam; blacklisted explosions and vehicles (tanks, jets, weaponized vehicles)
• Giving or removing weapons on other players
• Resource stops on a player's game (kick or ban), plus alerts when a resource stops server-side
• Tamper protection: a changing-code heartbeat removes players who stop or freeze the anticheat
BUILT NOT TO BAN INNOCENT PLAYERS
• Evidence scoring with decay: most removals need repeated proof, not one odd hit
• Instant action only for things legit play can't produce
• Victim reports need 2 different victims, so one player can't get another banned
• Lag and frozen games never count as a missed heartbeat
• Observe mode: keeps every block but only logs, so you can watch it on your server first
YOUR RULES
• Ban, kick or log only, per cheat, with ban length
• Choose whether players see the ban/kick reason or only a reference ID
LOGS & EVIDENCE
• Discord embeds: player identifiers, reasons in plain words, the latest evidence and a screenshot
• Screenshot before every kick and ban (screencapture or screenshot-basic)
• SQL records table: every kick and ban with its reason, evidence, identifiers and screenshot
• Staff commands: /acinfo, /acstatus, /acclear, /acunban
• In-game staff alerts
COMPATIBILITY
• Qbox (qbx_core + qbx_medical): bans go straight into Qbox's own bans table
• Standalone on any framework: built-in bans, ACE staff checks, console + Discord logs
• Custom frameworks: plug your own ban, log and staff functions into the config
• ox_inventory aware, addon weapons supported
• Restart-safe with players online
PERFORMANCE
• No per-frame loops on the server or the client
• Client checks run every 2 seconds; everything else runs only on game events, with early exits
• Heavy handlers can be switched off one by one
REQUIREMENTS
• OneSync
• FXServer artifact 7290 or newer
• oxmysql (for the records table)
• Optional: ox_lib (staff alerts), ox_inventory, screencapture or screenshot-basic (screenshots)
WHAT YOU GET
• Escrow-protected code with a fully open config
• SQL file included
NOT COVERED (YET)
Teleport, noclip, aimbot snapping, and hardware-ID ban evasion.
Made in Bangladesh.