arc-trapphone includes bridge-based support for multiple frameworks, inventory systems, notifications, interaction methods, target systems, dispatch resources, and phone opening methods.
In most supported setups, no manual bridge edits are required. The resource is built to auto-detect supported integrations where possible, and you can still force a specific supported option in config if needed.
Core Detection
The resource supports auto-detection for the following config categories:
Config.Framework = 'auto' -- auto / esx / qb / qbox / standalone
Config.Notification = 'auto' -- auto / ox / esx / qb
Config.UI = 'auto' -- auto / ox / custom
Config.Inventory = 'auto' -- auto / ox / esx / qb / qbox
Config.Interact = 'auto' -- auto / target / textui / custom
Config.Target = 'auto' -- auto / ox_target / qb-target / qtarget / false
Auto-detect is the recommended default unless you need to force a specific supported setup.
Frameworks
| Framework | Status | Notes |
|---|
| Auto Detect | ✅ | Recommended default |
| ESX | ✅ | Supported |
| QBCore | ✅ | Supported |
| Qbox | ✅ | Supported |
| Standalone | ✅ | Supported |
Inventory
| Inventory | Status | Notes |
|---|
| Auto Detect | ✅ | Recommended default |
| ox_inventory | ✅ | Supported |
| ESX Inventory | ✅ | Supported through framework inventory functions |
| QBCore Inventory | ✅ | Supported through QB/Qbox player item functions |
| Qbox Inventory | ✅ | Supported through QB/Qbox player item functions |
Notifications
| Notification | Status | Notes |
|---|
| Auto Detect | ✅ | Recommended default |
| ox_lib | ✅ | Supported |
| ESX | ✅ | Supported |
| QBCore | ✅ | Supported |
| UI | Status | Notes |
|---|
| Auto Detect | ✅ | Recommended default |
| ox_lib | ✅ | Supported |
| Custom | ✅ | Manual implementation supported |
Context menus, alerts, progress handling, and text UI behavior are designed around the resource utilities. Custom UI implementations can still be added if you prefer to replace the default handling.
Interaction
| Interaction | Status | Notes |
|---|
| Auto Detect | ✅ | Recommended default |
| Target | ✅ | Supported |
| Text UI | ✅ | Supported |
| Custom | ✅ | Manual implementation supported |
Target
| Target Resource | Status | Notes |
|---|
| Auto Detect | ✅ | Recommended default |
| ox_target | ✅ | Fully supported |
| qb-target | ✅ | Supported |
| qtarget | ✅ | Supported |
| Disabled | ✅ | Supported by setting target off and using another interaction mode |
ox_target has the most complete target feature coverage in this resource.Full sphere-zone and model-target helpers are only available with ox_target. Standard target entity and global ped target flows are supported across ox_target, qb-target, and qtarget.
Dispatch
| Dispatch Resource | Status | Notes |
|---|
| none | ✅ | Default disabled state |
| cd_dispatch | ✅ | Supported |
| codem-dispatch | ✅ | Supported |
| kartik-mdt | ✅ | Supported |
| lb-tablet | ✅ | Supported |
| origen_police | ✅ | Supported |
| piotreq_gpt | ✅ | Supported |
| ps-dispatch | ✅ | Supported |
| rcore_dispatch | ✅ | Supported |
Dispatch alerts are optional and controlled through Config.Dispatch. You can also require active police and apply a dispatch chance before alerts are sent.
Additional Integrations
| Opening Method | Status | Notes |
|---|
| Command | ✅ | Supported |
| Framework usable item | ✅ | Supported on ESX / QBCore / Qbox |
| Standalone item registration | ⚠️ | Not applicable without a framework item system |
The trap phone can be opened by command, by usable item on supported frameworks, or both, depending on your config.
| Payment Type | Status | Notes |
|---|
| Account payout | ✅ | Supported |
| Item payout | ✅ | Supported |
The bridge supports both account-based payout handling and item-based payout handling, depending on your payment configuration.
If you are using a supported setup, it is recommended to leave the config on its default auto values unless you need to force a specific integration or add a custom implementation.