Info

• Deploy bait-car trackers on automobiles and place them in locations where they are susceptible to theft. The bait-car can be operated from a remote location, enabling the toggling of the engine, securing the doors to prevent the suspects from entering or exiting the vehicle, and observing the interior of the vehicle through a concealed camera. The system is fully SERVER synchronized with a comprehensive configuration file, which enables integration with various frameworks.

Features

• Incredibly extensive configuration file allowing great control over the resource and its functionality
• QBcore, ESX, OR Standalone (Framework Independent)!
• Ability to use different permission systems: Ace permissions, Discord roles, command, QBCore jobs, custom or no authentication at all!
• Ability to choose between NativeUI menu, ESX menu, QBCore menu, or add your custom menu yourself (RageUI Menu Update Coming Soon)
• Ability to choose from different notification systems: GTAV, VCore-Noti 2, OkOkNotify, T-Notify 1, skeexsNotify 1, Infinity Notify 1, B-Notify 1, Atom Notify 1, Mythic Notify 1, QBCore, ESX, or add your custom notification calls! If you don’t know how, make a request and I’ll add it in for you!
• Everything is Server-Synced! all online LEO officers are able to view and control the bait-cars
• an Infinite number of bait-cars possible! Or restrict the number via the config on a server bases and/or a player bases
• Easy-to-use menu for controlling the bait-cars with keybinds and remapping
• COMPLETE REWRITE OF first attempt, more safely and efficiently written
• Included languages: English, *Spanish, *French, *Dutch, *Russian, *Bulgarian, *German : (*AI Generated) (Hungarian, Italian, Polish, Swedish Updates Coming Soon)
• Translatable language file, easy to change language file add your own if needed

Menu Options

• Set Vehicle As Bait-Car : Toggle’s the current vehicle that you’re in as a bait-car. If the current vehicle is set as a bait-car already, it will remove it as a bait-car
• Toggle Engine : Toggle’s the selected bait-cars engine on / off
• Toggle Vehicle Locked : Toggle’s the vehicle’s doors locking them trapping all people inside and preventing anyone from entering from the outside
• Toggle DashCam : Peek inside the bait-car vehicle
• Toggle Notification : Toggle a notification to appear when suspects enter the bait-car (client only)
• Toggle Blip : Toggle the bait-car blip to turn it on or off (client only)
• Bait-Car Selector : Select the bait-car you want to control

Requirements

NOTE: not all of these requirements are required, only install the resources that you need. If you are using QBCore or ESX frameworks then you will not need any Discord Permission resources or NativeUI for the menu - unless you want to use those options!

If you are confused about which files you need, please refer to the Installation Guide and Customization Guide found below!

For Discord Permissions

1. [discordroles 1] : Discord permission checking

2. [hqly_perms] : wrapper for discordroles

OR alternatively,

1. [Badger Discord API] : Discord permission checking with built-in caching negating the need for the combination of hqly_perms and discordroles resources together.

For NativeUI Menu

1. [NativeUI] : Menu API.

For QBCore

1. [QBCore Framework 5] : QBCore framework

For ESX

1. [ESX Framework 1] : ESX framework

Supported Notification Frameworks

Installation Guide

1. make sure you have NativeUI installed and running
2. install hqly_baitcar_v2 into your resources folder
3. edit fxmanifest.lua and uncomment line #25: '@NativeUI/NativeUI.lua',
4. edit config.lua

• change menuType to nativeui
• change notificationFramework to gtav
• change permissionType to either ace, command, or none
• change itemFrameWork to none
• ensure requireItem is set to false

1. Follow the specific permissions framework guide found below

1. make sure you have QBCore installed and running
2. install hqly_baitcar_v2 into your resources folder
3. edit fxmanifest.lua and comment line #25: '@NativeUI/NativeUI.lua',
4. edit config.lua

• change menuType to qbcore
• change notificationFramework to qbcore
• change permissionType to either qbcore, ace, command, or none
• change itemFrameWork to qbcore
• ensure requireItem is set to false
• edit allowedRoles and put any job names you wish to be able to open the menu

If you wish to require an item to use with the bait-car:

1. install baitcar.png into qb-inventory/html/images
2. edit config.lua

• ensure requireItem is set to true

1. item name is: baitcar_tracker

1. make sure you have ESX installed and running
2. install hqly_baitcar_v2 into your resources folder
3. edit fxmanifest.lua and comment line #25: '@NativeUI/NativeUI.lua',
4. edit config.lua

• change menuType to esx
• change notificationFramework to esx
• change permissionType to either esx, ace, command, or none
• change itemFrameWork to esx
• ensure requireItem is set to false
• edit allowedRoles and put any job names you wish to be able to open the menu

If you wish to require an item to use with the bait-car:

1. run hqly_baitcar.sql on your SQL server, replacing DBNAME with the database associated with your ESX server
2. edit config.lua

• ensure requireItem is set to true

1. item name is: baitcar_tracker

Ace Permissions

1. edit config.lua

• change permissionType to ace

1. in your server.cfg add the appropriate ace permissions.

• IE: add_ace group.police command.baitcar allow (make sure the command matches the command you have set in the config)

Discord Permissions

1. install & configure discordroles and hqly_perms: refer to Requirements section found above
2. edit config.lua

• change permissionType to discord

1. place any desired Discord role IDs into allowedRoles

Discord BADGER Permissions

1. install & configure badger_discord_api
2. edit config.lua

• change permissionType to discord-badger

1. place any desired Discord role IDs into allowedRoles

Command Permissions

1. edit config.lua

• change permissionType to command
• change commandPassword to your own password

1. authenticate in-game via /bc_onduty <password> (if you didnt change the default onDuty command)

QBCore Permissions

1. install & configure QBCore
2. edit config.lua

• change permissionType to qbcore
• edit allowedRoles to include any job roles names you wish to be able to open the menu

ESX Permissions

1. install & configure ESX
2. edit config.lua

• change permissionType to esx
• edit allowedRoles to include any job roles names you wish to be able to open the menu

No Permissions

1. edit config.lua

• change permissionType to none

ADVANCED

Custom Permissions

1. edit config.lua

• change permissionType to custom

1. find function canAccessMenu in client/auth.lua

• find line: elseif config.permissionType == 'custom' then and add your verification call there, return true if can access menu

GTAV

1. edit config.lua

• change notificationFramework to gtav

OkOkNotify

1. install & configure OkOkNotify
2. edit config.lua

• change notificationFramework to okok

VCore-Noti

1. install & configure VCore-Noti
2. edit config.lua

• change notificationFramework to vcore

T-Notify

1. install & configure T-Notify
2. edit config.lua

• change notificationFramework to tnotify

B-Notify

1. install & configure B-Notify
2. edit config.lua

• change notificationFramework to bnotify

Infinity Notify

1. install & configure Infinity Notify
2. edit config.lua

• change notificationFramework to infinity

Atom-Notify

1. install & configure Atom-Notify
2. edit config.lua

• change notificationFramework to atom

skeexsNotify

1. install & configure skeexsNotify
2. edit config.lua

• change notificationFramework to skeexs

Mythic Notify

1. install & configure Mythic Notify
2. edit config.lua

• change notificationFramework to mythic

QBCore

1. install & configure QBCore
2. edit config.lua

• change notificationFramework to qbcore

ESX

1. install & configure ESX
2. edit config.lua

• change notificationFramework to esx

ADVANCED

Custom Notifications

1. edit config.lua

• change notificationFramework to custom

1. find function doNotification in config.lua

• find first instance of if config.notificationFramework == 'custom' then and add your success notification call under hat line using variable msg as the message text
• find second instance of if config.notificationFramework == 'custom' then and add your error notification call under that line using variable msg as the message text

Config File Explained

NOTE: if an option is left blank, that means that you can change it to anything!

Commands (How to OPEN the menu)

Note: commands are modifiable through the config

Preview

Video:

NOTE: this is a an older video, but the functionality is more or less the same.

• Preview Video

Images:

• QBCore Menu:

Screenshot 2023-01-22 134550313×507 101 KB

• QBCore Menu - Selecting Bait-Car

• ESX Menu:

• ESX Menu - Selecting Bait-Car

• NativeUI Menu: (NOTE: Menu Banner will be the default commonmenu.ytd texture)

• NativeUI Menu - Selecting Bait-Car: (NOTE: Menu Banner will be the default commonmenu.ytd texture)

Support & Other Work

You can find live support on our Discord: https://discord.gg/UwH68aHMPn

Don’t hesitate to report any issues, offer any constructive criticism, or leave a suggestion!
If you have an idea you’d love to see come to life, don’t be afraid to get in touch!
Check out my other work:
[Player Worlds] | [X-Priorities] | [Play-Time] | [Ground]