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

# Backpacks

Backpack/item system with stash support, props, and configurable weight/slots.

## MRC Backpacks

### Quick links

* [Install Instructions](/docs/scripts/backpacks/install-instructions.md)

### What is MRC Backpacks?

MRC Backpacks is a backpack/item system for FiveM.

It can display props or clothing based on items in inventory.

Backpacks can act as a stash.

### Main features

#### Visual + functional backpacks

* Show props or clothing based on items.
* Turn the displayed item into a usable stash.
* Choose from multiple models and props.

#### Real gameplay interactions

* Backpacks can be dropped.
* Backpacks can be transferred.
* Backpacks can be stolen.

#### Configurable

* Configure max weight and slot count.
* Restrict or whitelist items allowed in the backpack.

### Dependencies

#### Framework

* QBCore / QBox
* ESX

#### Inventory

* `qb-inventory` (or derivatives)
* `ox_inventory`

### TL;DR

* Backpack/items show props or clothing based on inventory.
* Backpacks can be a stash.
* Backpacks are droppable, transferable, and stealable.
* Configurable slots/weight.
* Restrict or whitelist backpack contents.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://mrcscripts.gitbook.io/docs/scripts/backpacks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.