When a player breaks server rules, the standard options are a kick or a ban. Neither one gives staff a proportionate middle-ground response for minor violations. An admin jail fills that gap: a staff-controlled, timed confinement that keeps the player on the server and on record without permanently removing them.

How Admin Jail Works

Authorised staff select a player, assign a jail location from the configured list, set the duration, and add a reason. The player is teleported immediately. While confined, escape prevention blocks movement outside the designated zone — teleport-back triggers if they try to leave, and vehicles are blocked within the area. Weapons and attacks are disabled for the duration. When the timer expires, the player is released automatically and returned to their prior location.

• Command-based jailing with player selection, reason, location, and duration inputs
• Multiple configurable jail locations across the map
• Anti-escape: teleport-back on zone breach, vehicle blocking inside the zone
• Weapons and attack actions disabled for jailed players
• Database-persisted jail time — counts only while the player is online
• Force release / immediate unjail override for staff
• Optional mute: chat and voice muting during confinement
• Permission-controlled access so only designated staff ranks can jail

Framework Compatibility

The script runs on both ESX and QBCore. Permission checks hook into each framework’s native ace/group system, so your existing staff rank hierarchy carries over without extra configuration. Jail locations are defined in config, meaning you can place confinement zones wherever makes sense for your server’s map layout — a police cell block, a dedicated holding area, or anywhere else.

Why Staff Need This

Database-persisted time is the detail that matters most. Jail time only ticks down while the player is actively connected — they can’t log out to wait it out. That makes admin jail a genuinely effective deterrent rather than an inconvenience players can sidestep in thirty seconds. Combined with a reason log and force-release capability, it gives your moderation team a tool with actual accountability on both ends.