> For the complete documentation index, see [llms.txt](https://quannsstudios.gitbook.io/quannsstudio-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quannsstudios.gitbook.io/quannsstudio-docs/packboyz-edibles-system-all-frameworks/installation.md).

# Installation

***

**Download the Resource**

Download the resource from the [Cfx.re Portal](https://portal.cfx.re/) after purchasing.

**Extract and Place into Resources**

Extract the downloaded file and place the <button type="button" class="button secondary" data-action="ask" data-query="how to add the box text" data-icon="book-open">QuannsStudios-packboyz-edibles</button> folder into your server's resources directory.

**Update server.cfg**

Add the following to your `server.cfg`. Start it after your framework and dependencies.

```
ensure ox_lib
ensure ox_inventory
ensure oxmysql
ensure QuannsStudios-packboyz-edibles
```

**Add Required Items**

Add the following items to your ox\_inventory items file:

lua

```lua
['packboyz_trop']           = { label = 'Packboyz Tropical',   weight = 100, stack = true, close = true },
['packboyz_trop_gummy']     = { label = 'Tropical Gummy',      weight = 10,  stack = true, close = true },
['packboyz_grape']          = { label = 'Packboyz Grape',      weight = 100, stack = true, close = true },
['packboyz_grape_gummy']    = { label = 'Grape Gummy',         weight = 10,  stack = true, close = true },
['packboyz_watermelon']     = { label = 'Packboyz Watermelon', weight = 100, stack = true, close = true },
['packboyz_watermelon_gummy'] = { label = 'Watermelon Gummy', weight = 10,  stack = true, close = true },
['packboyz_lemonade']       = { label = 'Packboyz Lemonade',   weight = 100, stack = true, close = true },
['packboyz_lemonade_gummy'] = { label = 'Lemonade Gummy',      weight = 10,  stack = true, close = true },
['packboyz_extreme']        = { label = 'Packboyz Extreme',    weight = 100, stack = true, close = true },
['packboyz_extreme_gummy']  = { label = 'Extreme Gummy',       weight = 10,  stack = true, close = true },
['packboyz_peach']          = { label = 'Packboyz Peach',      weight = 100, stack = true, close = true },
['packboyz_peach_gummy']    = { label = 'Peach Gummy',         weight = 10,  stack = true, close = true },
['packboyz_regular']        = { label = 'Packboyz Regular',    weight = 100, stack = true, close = true },
['packboyz_regular_gummy']  = { label = 'Regular Gummy',       weight = 10,  stack = true, close = true },
['packboyz_cola']           = { label = 'Packboyz Cola',       weight = 100, stack = true, close = true },
['packboyz_cola_gummy']     = { label = 'Cola Gummy',          weight = 10,  stack = true, close = true },
```

**Server Requirements**

Your server must be running artifacts version **17000 or higher**.

**Restart Server**

Restart your server. Packboyz Edibles will be ready to use immediately on boot.


---

# 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://quannsstudios.gitbook.io/quannsstudio-docs/packboyz-edibles-system-all-frameworks/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.