AFK Kick System | AFK Detection, Return Transport & Admin Kick Scene for FiveM

The AFK Kick System automatically detects inactive players based on movement, heading and freely configurable tolerance values. Affected players first receive a two-stage warning – via a random-key check, screen flicker and an optional siren – before being teleported automatically to a dedicated AFK zone if they remain inactive. There, a robust, self-healing return-transport NPC can take them back to their last position at the press of a key; positions are stored persistently per player identifier. Admins also have two commands: an instant manual AFK teleport and a dramatic abduction scene with a guard and vehicle, after which the player is automatically removed from the server. Thanks to the integrated framework bridge, the script runs automatically with ESX or QBCore/QBox – configurable via a single, clearly labeled setting in config.lua. Admins manage permissions via ACE permissions or framework groups, and an optional Discord webhook logs every action with full player identifiers.

What’s included

• Automatic AFK detection (movement, heading, configurable tolerance values)
• Optionally ignores players in vehicles, in the pause menu, when dead or in animations/scenarios
• Freely definable safe zones where monitoring does not apply
• Discord ID exception list for team/VIP members
• Two-stage warning system with a random-key check against auto-clickers/macros
• Visual flicker (yellow/red) plus optional warning siren via NUI
• AFK zone with an interactive, self-healing return-transport NPC
• Return points stored persistently per player identifier, surviving restarts
• Admin command for manual AFK teleport (/kickafk) with automatic return point saving
• Admin command for a cinematic abduction kick scene (/kicknew) with guard, vehicle and synchronized animation
• Clean entity cleanup without server ghosts (network control, mission entity flags, delete fallbacks)
• Framework bridge for ESX and QBCore/QBox (automatic detection or fixed selection)
• Either ACE permissions or framework groups for permission checks
• Standalone-capable with native fallback notifications without a framework
• Optional Discord webhook for all actions (disabled by default, own link required)
• All texts centralized in Config.Locale, fully translatable and customizable
• All important settings centralized and labeled in config.lua