> For the complete documentation index, see [llms.txt](https://izzyshop-1.gitbook.io/izzyshop-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://izzyshop-1.gitbook.io/izzyshop-docs/izzyshop-resources/izzy-illegaljob/installation.md).

# Installation

Illegal jobs progression: heists, drug activity, robberies, and a black-market shop — configured in shared/cfg.lua.

{% hint style="info" %}
ESX, QBCore, and QBox with auto framework detection. Requires ox\_lib, oxmysql; ox\_target or qb-target optional for interactions.
{% endhint %}

```lua
author 'Izzy'
```

Dependencies

Ensure **ox\_lib**, **oxmysql**, and your framework core are running. Add **ox\_target** or **qb-target** if you use target interactions.

Place the resource

Copy izzy-illegaljob into your resources folder.

Server start

```lua
ensure izzy-illegaljob
```

Database

Import or run migrations so the tables in the [SQL tables](https://docs.izzyshop.info/izzy-illegaljob-installation#izzy-illegaljob-sql-tables) section exist (or let the resource create them if your build supports it).

Inventory images (PNG / job pack)

Custom item icons are usually shipped **separately** from the main resource folder. This documentation site does **not** host a direct PNG download URL; you get the archive with your purchase.

| Property    | Description                                                                                                                                                                                                                                        |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Tebex**   | Open [izzy.tebex.io](https://izzy.tebex.io/) → sign in → **Account** → **Purchases** → select **izzy-illegaljob** → download the package or **Extra files** and look for a `PNGs` / items archive (or the same files inside the full product zip). |
| **Discord** | Join [IzzyShop Discord](https://discord.gg/Jyg4RwNgJm), verify your **customer** role if required, then use the customer download / resources channel for the latest item icon pack.                                                               |

If items show without pictures, the PNG step was skipped.

1. Unpack the image archive from your purchase and copy every `.png` into your inventory’s image folder. File names must match item spawn names (for example `izzy_lockpick.png` for `izzy_lockpick`).
2. Typical targets: ox\_inventory/web/images/, qb-inventory/html/images/, or the equivalent path your inventory uses.
3. Set `cfg.inventoryImagePath` in `shared/cfg.lua` to the base URL or path your inventory expects for those images (see your inventory documentation).


---

# 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, and the optional `goal` query parameter:

```
GET https://izzyshop-1.gitbook.io/izzyshop-docs/izzyshop-resources/izzy-illegaljob/installation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.