# Dependencies

> **Need Help?** If you're unsure whether this script will work with your custom resources or have compatibility questions, feel free to contact us on [Discord](https://discord.gg/xZZu23AcpP) for support.

<details>

<summary><a href="https://github.com/esx-framework/esx_core/releases">es_extended</a> or <a href="https://github.com/qbcore-framework/qb-core">qb-core</a></summary>

This script works with both **ESX** and **QB-Core**, providing flexibility and full compatibility with your chosen framework.

</details>

<details>

<summary><a href="https://github.com/overextended/ox_lib">ox_lib</a></summary>

**ox\_lib** provides essential tools, utilities, and user interface options for a smoother script experience.

</details>

<details>

<summary><a href="https://github.com/overextended/oxmysql">ox_mysql</a></summary>

**oxmysql** is a modern and reliable SQL wrapper for FiveM, ensuring fast and optimized database queries.

</details>

<details>

<summary><a href="https://github.com/bohous04/bhd_bridge">BHD Bridge</a></summary>

**BHD Bridge** is a core dependency that connects script with multiple resources.

***

### **To install the BHD Bridge for your server, follow these steps:**

#### **1. Ensure All Dependencies Are Installed**

Before installing the BHD Bridge, make sure the following dependencies are downloaded and added to your `resources` folder:

* **ox\_lib**
* **oxmysql**

Ensure these dependencies are started **before** the BHD Bridge in your `server.cfg`:

```plaintext
plaintextZkopírovat kódensure ox_lib
ensure oxmysql
```

***

#### **2. Add BHD Bridge to Resources**

1. **Download the BHD Bridge**: Obtain the latest version of the BHD Bridge from your source.
2. **Place in Resources**: Move the `bhd_bridge` folder into your server's `resources` directory.
   * **Important**: To avoid boot order issues, do not place the bridge within a subfolder.

***

#### **3. Configure Server Startup Order**

In your `server.cfg`, ensure that the BHD Bridge is started **after** your framework and target scripts, but **before** any scripts that depend on it:

* **For ESX Framework**:

  ```plaintext
  plaintextZkopírovat kódensure es_extended
  ensure ox_target  # or your target script
  ensure bhd_bridge
  ```
* **For QB-Core Framework**:

  ```plaintext
  plaintextZkopírovat kódensure qb-core
  ensure qb-target  # or your target script
  ensure bhd_bridge
  ```
* **Note**: Start the bridge after any scripts it may use exports from, such as inventories or targets.

***

#### **4. Verify Installation**

After configuring your `server.cfg`:

1. **Restart Your Server**: Apply the changes by restarting the server.
2. **Check Console for Errors**: Monitor the server console to ensure there are no errors related to the BHD Bridge or its dependencies.

***

By following these steps, the BHD Bridge should be correctly installed and operational on your server.

</details>

<details>

<summary>Billing System</summary>

Supports the following billing systems:

* [**esx\_billing**](https://github.com/esx-framework/esx_billing)
* **okokbilling**
* [qb-banking](https://github.com/qbcore-framework/qb-banking)

Choose one and configure it in `bhd_bridge/society/server.lua`

</details>

***

#### **Support and Compatibility**

If you have any questions regarding script compatibility or need further assistance, join our [**Discord Server**](https://discord.gg/xZZu23AcpP).\
Our support team is ready to help with installation, configuration, and custom integrations.


---

# 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://docs.bhdscripts.com/scripts/bhd-bossmenu/dependencies.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.