Advanced Discord Queue with Boarding Pass UI

Advanced Discord Queue with Boarding Pass UI

Enhance your FiveM server's queue system with this professional and feature-rich resource. This script offers seamless Discord integration, role-based priority, username validation, and a stunning adaptive card UI, providing a premium and clean queue experience for your players.

Features

• Discord member verification before queue entry
• Optional required-role access control
• Whitelist support for specific Discord IDs
• Queue priority based on Discord roles
• Username blacklist protection
• Duplicate session protection for Rockstar license and Discord
• Webhook alerts for failed checks
• Adaptive-card loading and queue UI
• Local boarding pass ticket image support
• Customizable loading text, queue labels, buttons, and status messages

Installation

1. Put the tech_queue folder inside your server resources folder.
2. Add the following lines to your server.cfg, replacing the placeholders with your actual values:
   • set queue_discord_bot_token "YOUR_BOT_TOKEN"
   • set queue_discord_server_id "YOUR_DISCORD_SERVER_ID"
   • set queue_webhook_url "YOUR_DISCORD_WEBHOOK_URL"
3. Add ensure tech_queue to your server.cfg.
4. Restart your server, or run ensure tech_queue in the server console.
5. Open config.lua and configure your settings, including:
   • Discord role IDs
   • Whitelist IDs (if needed)
   • Queue priority roles
   • Queue texts and button links
   • Loading image and boarding pass image
6. Ensure any local images are included in fxmanifest.lua.
7. Test the resource by joining the server with a Discord account that matches your setup.

Configuration Highlights

• Config.General: Runtime convars, max slot fallback, locale, debug
• Config.Security: Duplicate session checks and bypass behavior
• Config.Roles: Whitelist, required roles, queue priority roles
• Config.Queue: Min/max wait time, refresh interval, halt duration
• Config.UI: Loading screen, queue card, buttons, and boarding pass ticket
• Config.Logging: Console logging behavior