trt_lockdown by t0r3tto is a server-side FiveM resource for scheduled connection restrictions. The inspected version 1.1.0 requires ox_lib; it is not a standalone script with no dependencies. Place the resource in resources and start ox_lib before ensure trt_lockdown. Back up configuration before changing access to a live server.
Set the schedule in config/server.lua. Startup reads the host’s local time with os.date. Its initial check compares the current time against a same-day start and end; a window crossing midnight needs corrected startup logic and a restart test. The daily cron transitions do not make that initial check correct. Test both transitions and a restart during the restricted period.
Bypass can come from the lockdown.bypass ACE permission, an allowed identifier or a configured Discord role. With kickAllPlayers enabled, the closing transition also kicks whitelisted players; disabling that option preserves whitelisted players. Test access using an ordinary account and a bypass account before the first scheduled closure.
Discord role lookup needs a private server-side bot token and the correct guild. The inspected code assumes the API response contains roles: failed requests or malformed responses can raise an error before the pending permission check resolves. Add status checks, response validation and bounded failure handling before relying on Discord access. Keep bot credentials out of client files, screenshots and public repositories.
Source reviewed at commit 12334d79de38e3bcbdfd9c917aff38e5ffacb94d. This is a source-based configuration review; scheduled closure, reconnection and Discord failure recovery still require testing on your server.