⬇️Installation

A step-by-step guide on how to install the script correctly corresponding to your framework, resources etc.

Welcome to the Bulgar Development Laundromat Heist 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.

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.

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

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.

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 Keymaster, 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
ox_lib	https://github.com/overextended/ox_lib
ox_target/qb-target/custom	https://github.com/overextended/ox_target
xsound (if using alarm in config)	https://github.com/Xogy/xsound
ox_doorlock/qb-doorlock/custom	https://github.com/overextended/ox_doorlock
bd-jobstatus	https://github.com/kristiyanpts/bd-jobstatus

---

Asset Positioning

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 computer resources.

-- 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 bd-computer here along with its dependencies
ensure [dependencies]

-- If you are using our computer system
ensure bd-computer

-- If you are using our laptop system
ensure bd-laptop

ensure [bd-heists]

---

Items

Our Ammunation Heist doesn't have any items that you must add at first (besides one that we recommend you use, but you can always change it). 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!

Item for ox_inventory

["coins"] = {
	label = "Coins",
	weight = 10,
	stack = true,
	close = false,
	description = "The best coins out there!",
},

Item for qb-core

coins = { name = 'coins', label = 'Coins', weight = 10, type = 'item', image = 'coins.png', unique = false, useable = false, shouldClose = true, description = 'The best coins out there...' },

---

Configuration

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.

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.

Basic framework configuration

The asset will work automatically if your framework is called es_extended or qb-core, it will automatically detect if any of them are started. In case your framework has been renamed, you can modify it in config.core.lua to edit the name of your framework.

Advanced framework configuration

If your framework is completely modified, both in events and name, you should access client/editable/framework or server/editable/framework to adapt the native events of your framework to the codes you have created. If this step doesn't work, we ask that you ask your framework modifier or trusted developer for help.

More general settings

This asset contains multiple configurations within the config folder. But you can also access more open source and configurations within client/editable or server/editable. We do not recommend using these configurations if you do not have the basics of programming.