> For the complete documentation index, see [llms.txt](https://unknown-development.gitbook.io/unknown-development/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unknown-development.gitbook.io/unknown-development/scripts/unknown_cargoheist/installation.md).

# Installation

**Installation difficulty**

**🟣⚫⚫⚫⚫** - very easy

***

### 1. Download Resource

To begin, download your recently purchased resource from [our store](https://corem.tebex.io/)

To do this, log in to your [cfx portal](https://portal.cfx.re/) account and navigate to the '**Asset Grants**' section, where you will find your owned resources.

***

### 2. Dependencies

Before installing **Cargo Heist**, you must ensure the following dependencies are installed:

<details>

<summary><a href="https://github.com/esx-framework/esx_core/tree/main">es_extended</a> | <a href="https://github.com/qbcore-framework/qb-core/tree/main">qb-core</a> | <a href="https://github.com/Qbox-project/qbx_core">qbx_core</a></summary>

The script supports **ESX, QBCore, and Qbox**, providing a flexible and versatile solution for different server setups.

</details>

<details>

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

A standalone library designed to offer reusable code through importable modules and exports.

</details>

<details>

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

A widely used MySQL wrapper for FiveM, trusted by servers around the world.

</details>

<details>

<summary><a href="https://github.com/overextended/ox_inventory">ox_inventory</a> | <a href="https://github.com/qbcore-framework/qb-inventory">qb-inventory</a> | <a href="https://github.com/esx-framework/esx_core">esx</a></summary>

Supports **ox\_inventory, qb-inventory, and ESX** for inventory management.

</details>

<details>

<summary><a href="https://github.com/overextended/ox_target">ox_target</a> | <a href="https://github.com/qbcore-framework/qb-target">qb-target</a></summary>

The script supports **ox\_target and qb-target**, offering a flexible solution for various server setups.

</details>

<details>

<summary><a href="https://codesign.pro/product/4206357">cd_dispatch</a> | <a href="https://tkscripts.com/product/dispatch">tk_dispatch</a> | <a href="https://store.rcore.cz/package/5789351">rcore_dispatch</a> | <a href="https://github.com/Project-Sloth/ps-dispatch">ps-dispatch</a></summary>

Compatible with **cd\_dispatch, tk\_dispatch, rcore\_dispatch, and ps-dispatch**, ensuring smooth and versatile dispatch integration.

</details>

<details>

<summary><a href="https://okok.tebex.io/package/4724993">okokNotify</a> | <a href="https://github.com/overextended/ox_lib">ox_lib</a> | <a href="https://github.com/qbcore-framework/qb-core/tree/main">qb-core</a> | <a href="https://github.com/esx-framework/esx_core/tree/main">es_extended</a></summary>

Compatible with **okokNotify,** **ox\_lib, QBCore and ESX**, providing clean and modern notification support.

</details>

***

### 3. Install Cargo Heist

* Add `unknown_cargoHeist` folder to your server `resources` folder and start them by adding the following to your `server.cfg`:\
  `ensure unknown_cargoHeist`

{% hint style="info" %}
Dependencies **must** be ensured before `unknown_cargoHeist`, otherwise the script may not function correctly.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://unknown-development.gitbook.io/unknown-development/scripts/unknown_cargoheist/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.