> For the complete documentation index, see [llms.txt](https://pintux.gitbook.io/pintux-support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pintux.gitbook.io/pintux-support/addons.md).

# Addons

Addons take another plugin's GUIs and serve them to Bedrock players as native forms. You install one, enable what you need, and get working forms without designing a single menu. Java players keep the original GUIs.

Every addon needs **BedrockGUI 2.0.12+**, **Floodgate**, and the plugin it wraps, all on the same Paper server. All four JARs are on [GitHub Releases](https://github.com/pintux98/BedrockGUI/releases/latest).

### Available addons

| Addon                                                                  | Wraps                                                        | Covers                                           |
| ---------------------------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------ |
| [**Essentials Addon**](/pintux-support/addons/essentials-addon.md)     | EssentialsX, CMI, HuskHomes, ShopGUI+, EconomyShopGUI, MyPet | Warps, kits, homes, TPA, shops, pets, death menu |
| [**Bedwars Addon**](/pintux-support/addons/bedwars-addon.md)           | BedWars2023, BedWars1058, ScreamingBedWars                   | Shop, upgrades, arena, stats, spectator, party   |
| [**Homestead Addon**](/pintux-support/addons/homestead-addon.md)       | Homestead                                                    | All 27 region, sub-area, flag and member GUIs    |
| [**PhoenixDuels Addon**](/pintux-support/addons/phoenixduels-addon.md) | PhoenixDuels / PhoenixDuelsLite                              | Queues, duel builder, parties, stats, spectating |

### Two ways to use an addon

**Integrated (default)** — the addon intercepts the wrapped plugin's GUIs. A Bedrock player who opens a shop or a region menu simply gets a form. Nothing to configure beyond enabling the modules you want.

**Actions-only** — the addon stops intercepting and instead just registers its actions, which you call from your own menus. Set `integrated-gui: false` and keep `register-actions: true`:

```yaml
integrated-gui: false
register-actions: true
```

Then call an action from your own YAML:

```yaml
onClick:
  - |
    essentials_hub {
      - ""
    }
```

The Essentials Addon can also do this per module with `actions-only`, so you can keep the built-in warps form while designing your own shop.

### Admin commands

| Addon        | Command                                                         | Permission               |
| ------------ | --------------------------------------------------------------- | ------------------------ |
| Essentials   | `/essentialsaddon reload`                                       | `essentialsaddon.reload` |
| Bedwars      | `/bedwarsaddon reload` (alias `/bwaddon`)                       | `bedwarsaddon.admin`     |
| Homestead    | `/homesteadaddon <reload\|open\|openfor>` (alias `/hsaddon`)    | `homesteadaddon.admin`   |
| PhoenixDuels | `/duelsaddon <reload\|open\|openfor\|menus>` (alias `/pdaddon`) | `duelsaddon.admin`       |

{% hint style="info" %}
Writing your own addon? [Building an Addon](/pintux-support/developers/building-an-addon.md) walks through how these four are made, from project setup to testing, and the [BedrockGUI API](/pintux-support/developers/bedrockgui-api.md) is the reference.
{% endhint %}