> ## Documentation Index
> Fetch the complete documentation index at: https://docs.archonexe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Archon Trap Phone System Integrations

> Supported frameworks, inventory systems, notifications, UI handling, interaction methods, target systems, dispatch integrations, and opening methods for arc-trapphone.

`arc-trapphone` includes bridge-based support for multiple frameworks, inventory systems, notifications, interaction methods, target systems, dispatch resources, and phone opening methods.

<Info>
  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.
</Info>

## Core Detection

The resource supports auto-detection for the following config categories:

```lua theme={null}
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
```

<Note> Auto-detect is the recommended default unless you need to force a specific supported setup. </Note>

## 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

| UI          | Status | Notes                           |
| ----------- | ------ | ------------------------------- |
| Auto Detect | ✅      | Recommended default             |
| ox\_lib     | ✅      | Supported                       |
| Custom      | ✅      | Manual implementation supported |

<Note> 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. </Note>

## 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 |

<Warning>
  `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`.
</Warning>

## 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              |

<Note> Dispatch alerts are optional and controlled through `Config.Dispatch`. You can also require active police and apply a dispatch chance before alerts are sent. </Note>

## 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 |

<Info> The trap phone can be opened by command, by usable item on supported frameworks, or both, depending on your config. </Info>

| Payment Type   | Status | Notes     |
| -------------- | ------ | --------- |
| Account payout | ✅      | Supported |
| Item payout    | ✅      | Supported |

<Note> The bridge supports both account-based payout handling and item-based payout handling, depending on your payment configuration. </Note>

<Note>
  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.
</Note>