Installation
A step-by-step guide on how to install the script correctly corresponding to your framework, resources etc.
Welcome to the Bulgar Development installation guide, here you can learn how to completely install our asset, following each step we will achieve a clean and fluid installation where you will not find any problems, as long as the documentation has been completed in full.
Warning
If you do not have programming experience, we recommend that you read each step completely without skipping any lines, since all documentation is important and should not be ignored under any circumstances. If you have a trusted developer, you can install this quickly, easily and safely if you complete this documentation step by step.
Information
If at the end of this documentation you still have any problems, review each step again, after having checked that everything is correct, you can obtain more information about common errors in the Common Problems section within this same documentation to seek help independently.
Asset Download
Warning
To find the asset, you must have made the purchase using your own keymaster account. Otherwise, you can use the transfer system to move the asset to a different keymaster account.
Success
If you need to make an update you must also do this step again, download the asset and you will get the complete update.
Once the purchase is made on our official website, you will receive your asset directly in your Portal, in your own panel you can download the asset and install it following the following documentation.
Asset Dependencies
This asset has some dependencies that are completely mandatory and important for the operation of the asset. If you do not have these dependencies, your asset will probably start and have some error or message in its command console.
| Resource Name | Resource Download |
|---|---|
| qb-core/es_extended/custom | Open |
| ox_inventory/qb-inventory/custom | Open |
| ox_target/qb-target/custom | Open |
| bd-jobstatus | Open |
Asset Positioning
Warning
Correctly position the assets by following this step, if something goes wrong you will probably get errors about exports not found, do not skip this step.
For the execution of this asset, we will respect the respective order mentioned below. The dependencies should be ensured before the resource.
-- First we will start the cores, never below
ensure es_extended or qb-core or your-custom-core
-- Your inventory system, always on top
ensure [inventory]
-- Run all the dependencies here
ensure [dependencies]
ensure bd-tuningItems
Information
Our Tuning job doesn’t have any items that you must add at first (besides a couple that we use for our own server, but you can always change them). But that doesn’t mean it doesn’t require items and other things. Go through the next page, where the configuration is, and you will configure the required items and the reward items depending on your server!
Items for ox_inventory
["tuning_part"] = {
label = "Vehicle Part",
weight = 100,
stack = false,
close = true,
description = "Vehicle parts",
client = {
image = "tuning_part.png",
event = "bd-tuning:installPart"
}
},Items for qb-core
['tuning_part'] = {['name'] = 'tuning_part', ['label'] = 'Vehicle Part', ['weight'] = 100, ['type'] = 'item', ['image'] = 'tuning_part.png', ['unique'] = true, ['useable'] = true, ['shouldClose'] = true, ['combinable'] = nil, ['description'] = 'Vehicle parts'},Configuration
Information
We do not recommend editing frameworks unnecessarily, since almost all assets depend exclusively on your framework and exports on the name of your framework. Otherwise and if you edited your framework, read these steps carefully.
Success
If you still require more open codes for the configuration, you can check within client/editable and server/editable to adapt the asset to your personal taste.
Please expand each part to see information about the configuration of the asset, this way you will understand the general operation of the asset on the framework and editable files side.