> For the complete documentation index, see [llms.txt](https://striga.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://striga.gitbook.io/docs/striga-inventory/troubleshooting-and-faq.md).

# Troubleshooting & FAQ

Common Striga Inventory problems and how to fix them.

<details>

<summary>The inventory does not open / qb scripts give errors</summary>

* Check the `qb-inventory` folder is **out of** `resources`. Look for a red `[striga-inventory]` line in the console.
* Check `ensure striga-inventory` comes **after** `ensure striga-core` in `server.cfg`.
* Check `"inventory": "auto"` in `striga-core/config.json`.

</details>

<details>

<summary>Striga Inventory does not start</summary>

`striga-core` is missing or too old. Install or update `striga-core` (0.1.0 or newer) and start it **before** Striga Inventory. Look for a red striga-core error in the server console.

</details>

<details>

<summary>I added new files / updated and something is missing</summary>

Run `refresh` and then `ensure striga-inventory` in the server console (or restart the server). New files in the resource are only seen after a `refresh`.

</details>

<details>

<summary>The inventory does not open while a progress bar runs</summary>

This is on purpose. While another script sets `inv_busy` (progress bars, qb-drugs...), the inventory stays closed.

</details>

<details>

<summary>My old stashes, trunks and gloveboxes are empty</summary>

Move them over with `strigaconvert`. See [Converting from another inventory](/docs/striga-inventory/converting-from-another-inventory.md). Player inventories on QBCore are safe (they stay in the `players` table).

</details>

<details>

<summary>A character has the clothes of another character</summary>

Run `/clothesreset <id>` (admin). It empties that character's clothing slots. Put the right look on the character (clothing shop or appearance menu), then open the inventory: the slots are read again from the character.

</details>

<details>

<summary>Weapons do nothing / qb-weapons still handles them</summary>

The weapon pack turns on only when `qb-weapons` is **not** running (`Weapons.Enabled = 'auto'`). Move `qb-weapons` out of `resources`, or set `Weapons.Enabled = true` in `editable/weapons.lua`. See [Weapons](/docs/striga-inventory/weapons.md).

</details>

<details>

<summary>My weapon cannot be drawn</summary>

Its quality is 0: it is broken. Repair it at a gunsmith. See [Weapons](/docs/striga-inventory/weapons.md#gunsmith).

</details>

<details>

<summary>The console says a player holds a weapon the inventory did not give</summary>

The weapon guard saw a weapon that is not in the player's inventory (spawn menu or cheat). If one of your scripts gives weapons on purpose, add it to `Weapons.GuardIgnore`. `Weapons.Guard = 'remove'` also takes such weapons away.

</details>

<details>

<summary>I cannot take my backpack off</summary>

The extra backpack slots still hold items, or the weight does not fit without it. Move those items first.

</details>

<details>

<summary>An item shows no image</summary>

Put the `.png` in `striga-inventory/images/` with the same name as the item's `image` field.

</details>

<details>

<summary>Every shop shows twice on the map</summary>

`qb-shops` is still running. Move it out of `resources`, or remove the shops from `editable/shops.lua`.

</details>

<details>

<summary>A shop from another script does not open with E</summary>

On purpose. Shops other scripts add open only through that script, so its own checks stay. The script can pass `interact = true` to allow `E`.

</details>

<details>

<summary>How do I stop players from changing the look?</summary>

Set `Config.Ui.Settings = false` in `editable/config.lua`. Everyone then sees your config values, and the `/hud` section is read only.

</details>

<details>

<summary>A bike or a train has no trunk</summary>

That is the default. Set a size for it in `Config.VehicleTypes` or `Config.VehicleModels`.

</details>

<details>

<summary>A sports car trunk only has 5 slots</summary>

`Config.VehicleClasses` makes sports cars and supercars small on purpose. Change or remove the class entry, or give the model its own size in `Config.VehicleModels`.

</details>

<details>

<summary>Does it work on Qbox or ESX?</summary>

The inventory side is ready (the ox\_inventory mode). It waits for a striga-core update that loads and saves player inventories on Qbox and ESX. See [Qbox & ESX](/docs/striga-inventory/qbox-and-esx.md).

</details>

{% content-ref url="/pages/l5wN7F8ApRvA4hIyq5me" %}
[Introduction](/docs/striga-inventory/introduction.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://striga.gitbook.io/docs/striga-inventory/troubleshooting-and-faq.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 `automate deployments from our CI pipeline` 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.