# Installation

#### 📦 Installation Instructions for Black market Script System

To ensure the proper functioning of the Black market Script System, you need to follow these installation instructions carefully. This system has some essential dependencies that must be installed first.

***

#### 🛠️ Asset Dependencies

This asset has some mandatory dependencies that are crucial for its operation. If you do not have these dependencies, your asset may start with errors or fail to function correctly.

***

#### Dependencies & Direct Links

| **Dependency** | **Direct Link**                                                      |
| -------------- | -------------------------------------------------------------------- |
| **oxmysql**    | [Download oxmysql](https://github.com/overextended/oxmysql/releases) |
| **qbcore**     | [Download qbcore](https://github.com/qbcore-framework/qb-core)       |
| ps-zone        | [Download ps zone](https://github.com/Project-Sloth/ps-zones)        |
| PolyZone       | [Download polyzone](https://github.com/mkafrin/PolyZone)             |

Alternatively, for **ESX**, use the following dependencies:

* [**es\_extended (ESX Base)**](https://github.com/esx-framework/esx_core)
* [**ox\_target**](https://github.com/overextended/ox_target)

***

🗄️ Database Setup

Run the following SQL command inside your database to set up the necessary table for the Black market System. This step is crucial for the proper functioning of the asset, so please do not skip it.

<details>

<summary>Click to view SQL Code</summary>

```sql
CREATE TABLE IF NOT EXISTS `evo_blackmarket_profiles` (
  `citizenid` varchar(255) NOT NULL,
  `playername` varchar(255) NOT NULL,
  `rep` int(11) DEFAULT 0,
  PRIMARY KEY (`citizenid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci;
```

</details>

***

#### 📦 Install Items in inventory

This system includes areas for dog-related activities, which will require specific items to be added to your inventory. Below is the code snippet to add the necessary items for the Black market Script System.

<details>

<summary>Click to view Items for qb-inventory Code</summary>

```lua
evo_delivery_box = { 
    name = 'evo_delivery_box', 
    label = 'Delivery Box', 
    weight = 0, 
    type = 'item', 
    image = 'evo_delivery_box.png', 
    unique = false, 
    useable = false, 
    shouldClose = false, 
    combinable = nil, 
    description = 'Delivery Box' 
},
```

</details>

<details>

<summary>Click to view Items for ox_inventory Code</summary>

```lua
["evo_delivery_box"] = {
    label = "Delivery Box",
    weight = 0,
    stack = true, -- Assuming you can stack more than one box
    close = false, -- Assuming you don't want to close the inventory when using the box
    description = "Delivery Box",
    client = {
        image = "evo_delivery_box.png",
    }
},
```

</details>

***

#### 🖼️ **Images Installation**

To ensure your items display correctly in the inventory, follow these steps to install the images:

1. **Navigate to the Images Directory**:\
   In your project folder, go to:\
   `evo-blackmarket/ui/items`.
2. **Install Item Images**:\
   Place your item images (e.g., `evo_delivery_box.png`) into the `items` directory to make them appear in the UI.

Make sure all images are correctly named to match their corresponding items in your code!

***

#### 📌 Final Steps

Make sure you follow these instructions carefully to ensure the Black market Script System is installed correctly on your server.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://evo-development.gitbook.io/evo-development-docs/products/advanced-blackmarket/installation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.