Configuring the resource
We've aimed to make the configuration file for Smart Bollards as straightforward as possible, in order for it to work straight out of the box for you.
Developer Mode
The first configuration value is enableDeveloperMode. This is relevant for adding new locations using the /bollards create <Set Name> command on the next page, so enable that if you're planning on adding new locations (but remember to turn it off again after).
You can also see all the locations of the bollards by enabling the blips. If you don't want blips around the map, make sure to disable blips set.
Adding new Permission Sets
Smart Bollards works on permission sets, which may be 'police', 'fire' or 'ambulance' for example. Each permission set can have a combination of ace permissions, job types and permitted vehicles models. These permission sets are configured beforehand in the config.lua file and then easily specified when adding new bollard locations around the map, offering access to one permission set or multiple.
When adding new permission sets, whether this is for one of the supported frameworks or standalone, you want to copy an existing set from the config.lua file before changing the name as this will be used when you are setting the permissions name on the bollard group shown on the next page.
Permitted Vehicles
You are able to specify any permitted vehicles for that permission set, using the vehicle model in backticks - ``. Please note, this is different to the usual quotation mark, and backticks allow model hashing at runtime for efficiency.
Permitted Jobs
We've added support for QBCore, ESX, vRP and QBX straight out of the box. To enable permissions for any of these sets, navigate to the CheckJob = { section of the permission set and enable your relevant framework. You are also able to specify job names, for example:
Ace Permissions
You are able to specify any ace permissions that a player can have access to.
Last updated