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

# Troubleshooting & FAQ

Common problems and questions for ace\_deployables.

## Troubleshooting

<details>

<summary>generated_items.txt is for the wrong inventory (or says STANDALONE)</summary>

The inventory is detected when the resource starts, about 0.5 s after start. If your inventory starts **after** `ace_deployables`, it isn't detected. Move `ensure ace_deployables` below your inventory and framework in `server.cfg`, then restart.

</details>

<details>

<summary>Using the item does nothing (ox_inventory)</summary>

* The item must use `client.export = 'ace_deployables.deploy_<key>'`, where `<key>` is the table key in `ItemList.lua` (for example `deploy_skidChair`), **not** the item name.
* The folder must be named `ace_deployables`.

</details>

<details>

<summary>"You cannot place that here." / "You are not allowed to deploy here."</summary>

* With `UseZones = true`, check `Config.Zones`, including each zone's `allowedDeployables` and `allowedPlayers`.
* Check `MaxPlacementDistance` and `maxPlacementHeight`.

</details>

<details>

<summary>"You are too far away to place this object."</summary>

Placement is further away than `MaxPlacementDistance` (default `10.0`).

</details>

<details>

<summary>"Your inventory is too heavy!" when picking up</summary>

The inventory bridge checks whether the player can carry the returned item. Free up inventory space.

</details>

<details>

<summary>Errors mentioning `lib` when using ox notifications</summary>

With `Config.NotificationType = 'ox'`, uncomment `'@ox_lib/init.lua'` in `fxmanifest.lua` and make sure `ox_lib` starts first.

</details>

<details>

<summary>Objects disappear after a restart</summary>

Check that `EnablePersistence = true` and that the server can write to `ace_deployables/db/deployables.json`. Deployables with a `lifeTime` also remove themselves over time.

</details>

## FAQ

<details>

<summary>Which inventories are supported?</summary>

ox\_inventory, qs-inventory, codem-inventory, tgiann-inventory, qb-inventory, ps-inventory, lj-inventory, and ESX's built-in inventory. Without any of these, the resource runs in standalone mode.

</details>

<details>

<summary>Can anyone pick up a deployable?</summary>

Per deployable, `ownership = false` lets anyone interact and `ownership = true` restricts it to the owner. `Config.lua` also has a global `DeployableOwnerShip` setting (default `true`).

</details>

<details>

<summary>Can I add storage to the cooler?</summary>

Not out of the box. The cooler has no interactable. You can write one. See [Custom Interactables](/docs/inventory-and-items/deployables/custom-interactables.md).

</details>