okokVehicleShop
Installation Guide
Execute the following SQL code in your database:
Importing vehicles to the Vehicle Shop
If importing from the shared/vehicles.lua
for QBCore, you must make sure that the "shop" is set as the vehicle shop "type". Here's an example:
You need to check through the config.lua
that the Config.Stands section as well as the Config.VehicleshopsCategories also has their "type" set the same. In this case "pdm", like so:
The vehicle "categories" are also important, as these need to be the same in your okokvehicleshop_vehicles
table as well, otherwise the shop won't sync the vehicles with their respected categories.
As you can see from the above screenshots, in the okokvehicleshop_vehicles
table, there is a category called "supers", and in the config.lua
, there is a category called "supercars". This is an example to show that these vehicles will not sync because they are not identical. Whereas if you look at "motorcycles", it's the same in both, so they will work perfectly.
Optional okokScripts that are configured to be used with okokVehicleShop
These do not come included with the script, they are only configured to be used alongside the script, if you have them.
okokTextUI, okokRequests and okokNotify (these are not required, so if you do not wish to use them, look for the setting within the config and set it to false).
For okokNotify it won't be in the config, but in the cl_utils.lua
file instead. Change the notification system to the one you use within your server.
Adding vehicle images
To add images to the vehicles, simply drop them in the web/img folder with the same id as the vehicle (the images should be in the PNG format).
Setting the Discord Webhook URL (to enable logs)
Navigate to the sv_utils.lua
file and paste the webhook URL in the line 5.
How to create a Discord Webhook URL
Server artifacts
Make sure your server artifacts version is above the 5181.
Last updated