> For the complete documentation index, see [llms.txt](https://five-customs.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://five-customs.gitbook.io/docs/troubleshooting/framework-compatibility.md).

# Framework Compatibility

Several resources in this bundle include configuration options for automatic or manual framework selection. The exact supported combinations vary by script.

## Framework selection

Where available, set the resource's framework option to one of the values documented in its configuration. Common values in this bundle include `auto`, `esx`, `qbcore`, and `qbox`. Some resources support standalone/native mode; do not assume every resource does.

Use automatic detection only when a single intended core is running. If multiple cores are installed or detection is ambiguous, choose the correct framework explicitly.

## Integration layers

Some resources provide bridge or custom integration files for framework, inventory, target, banking, notification, or voice systems. Prefer editing the intended bridge/configuration layer over modifying core gameplay files.

## Inventory and target systems

Inventory options differ between resources. If an item-based feature does not work:

* Confirm the item is registered in the inventory being used.
* Use the supplied SQL or Lua item definitions when provided.
* Confirm the configured inventory matches the running inventory.
* Check item names for exact spelling and case.
* Verify the target resource is started before the script.

## Voice, database, and other dependencies

Use the per-script dependency list and the original manifest as the source of truth. A dependency may be required by a particular feature or integration even if it is not required by every server setup.