> For the complete documentation index, see [llms.txt](https://docs.myarc.icu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.myarc.icu/en/configuration-and-administration/compatibility.md).

# Platform and plugin compatibility

ArcMenu integrates cleanly into modern server setups, working alongside popular server cores, custom item plugins, economy systems, and cross-version tools.

## Server platforms

Paper, Leaf, Folia, Purpur, and other Paper-based servers share the same plugin JAR and `plugins/ArcMenu/` directory and support the complete ArcMenu feature set. On Folia, ArcMenu automatically follows regionized multithreading rules, scheduling player and display-entity operations on their owning region threads.

| Feature area                                                                       | Paper / Leaf / Folia / Purpur                        |
| ---------------------------------------------------------------------------------- | ---------------------------------------------------- |
| Text, rectangles, borders, lines, vanilla items, and blocks                        | Supported                                            |
| Left-click, right-click, Shift-click combinations, command actions, and navigation | Supported                                            |
| Shift+F main menu shortcut and Space / Shift+F closing shortcuts                   | Supported                                            |
| Images, animated GIFs, and automatic resource pack generation                      | Supported                                            |
| Mouse mode, Vision mode, local cursor, and fixed FOV                               | Supported (Vision requires the companion Editor mod) |
| Hover tooltips, menu animations, and Effect cutscenes                              | Supported                                            |
| CraftEngine, Nexo, and ItemsAdder custom items and pack merging                    | Supported                                            |
| Visual editor, project manager, marketplace, and developer API                     | Supported                                            |

For server versions and Java requirements, see [Requirements](/en/getting-started/requirements.md).

## Custom item and resource pack plugins (CraftEngine / Nexo / ItemsAdder)

ArcMenu works natively with **CraftEngine**, **Nexo**, and **ItemsAdder**, letting you display their custom item models inside menus and automatically merge ArcMenu's generated assets into their resource packs.

### Displaying custom items in menus

In the `material` field of a frontend `type: item` element, enter the item identifier for your plugin:

* **CraftEngine**: Enter `namespace:item_id` (for example, `myitems:ruby_sword`) or use the explicit prefix `craftengine:namespace:item_id`. Unprefixed custom namespaced IDs resolve as CraftEngine items by default.
* **Nexo**: Enter `nexo:item_id` (for example, `nexo:magic_staff`).
* **ItemsAdder**: Enter `ia:namespace:item_id` or `itemsadder:namespace:item_id` (for example, `ia:custom:golden_key`).

If your server runs multiple custom item plugins that share similar item names, use the explicit prefix form. Pair the item with `context: GUI` to render it with its flat inventory icon orientation; see [Frontend element types](/en/menu-configuration/menus/frontend.md) for rotation and scale options. If custom items are still loading while the server starts up, ArcMenu automatically waits for the item plugin to finish initializing and then completes menu loading.

### Automatic resource pack merging

All three plugins can merge the images, GIFs, cursors, and shaders generated by ArcMenu without copying folders by hand or editing their configuration files:

* **Nexo** merges ArcMenu assets automatically during its pre-pack generation event.
* **ItemsAdder** receives ArcMenu assets during its pack merge event while preserving your existing pack metadata and `overlays` structure.
* **CraftEngine** merges ArcMenu's generated output directly whenever it builds its resource pack.

After adding or updating menu images or GIFs, first run `/arcmenu resources` or `/arcmenu reload all` to update ArcMenu's output, then run your item plugin's pack reload command to merge and distribute the updated pack:

* CraftEngine: `/ce reload pack` (or `/ce reload all`)
* Nexo: `/nexo reload pack`
* ItemsAdder: `/iazip`

When you import or modify workspace assets through the project manager, ArcMenu also requests a pack rebuild automatically (when multiple plugins are installed, automatic rebuild triggers prioritize CraftEngine, then Nexo, then ItemsAdder; running any plugin's reload command manually will always merge the assets). If your server has more than one custom content plugin installed, configure only one of them to send the final resource pack to players. In addition, enabling the `allowCe` option when exporting an ArcPack project also permits Nexo and ItemsAdder item references.

For full resource pack setup details, see [Images and resource packs](/en/feature-configuration/resource-packs.md).

## PlaceholderAPI

With PlaceholderAPI and the relevant expansions installed, you can use placeholders from other plugins—such as coin balances, points, levels, guild names, or quest progress—directly inside menu text, tooltips, image paths, item materials, conditions, and actions. ArcMenu's built-in placeholders for player info, coordinates, cursor preferences, and menu data work out of the box without extra dependencies.

## Vault and PlayerPoints

* **Vault**: When paired with any Vault-compatible economy plugin (such as EssentialsX or CMI), you can check player balances in conditions and add, deduct, or set money directly from menu actions.
* **PlayerPoints**: Lets you check, add, deduct, or set player points directly in conditions and actions.

Combining placeholder displays, conditions, and economy actions makes it easy to build shops, paid teleports, and upgrade menus; see [Advanced actions](/en/menu-configuration/menus/advanced-actions.md) for configuration examples.

## Cross-version connections and client rendering (ViaVersion and shaders)

When **ViaVersion** is installed so clients on different Minecraft versions can join, ArcMenu detects each player's actual client protocol version and serves the matching Mouse mode resources automatically.

Each input mode and cutscene renderer uses an approach suited to its visual requirements and shader compatibility:

* **Touch mode**: Requires no client mod and renders entirely with vanilla display entities, respecting the player's normal FOV and world block occlusion. It does not load or activate menu shaders, keeping gameplay rendering completely unchanged with any shader pack enabled.
* **Mouse mode**: Requires no client mod and uses the companion resource pack to provide a local client cursor, fixed FOV, menu depth, and flat lighting.
* **Vision mode**: Available whenever a player installs the matching **ArcMenu Editor** mod for their client version. Vision is built directly into the Editor mod, providing a responsive local cursor and a dedicated menu rendering pass with fixed FOV, bright item lighting, no occlusion from world blocks or entities, and full compatibility with shader packs and system IME text input.
* **Effect cutscenes**: Both live playback and editor previews use vanilla display entities and a native fixed camera without relying on Mouse shaders, so players can watch cutscenes without installing any client mod.

## Integrating with other gameplay plugins

Beyond running commands through `player:` (as the player) and `console:` (from the server console) to connect existing teleport, inventory, crate, or skill plugins to menu buttons, third-party plugins can also register native hosted applications through ArcMenu's developer API.

Once registered, a plugin interface can be opened directly on the current menu plane with the action `open-app: namespace:app-id`, sharing the same screen position, cursor control, and back-navigation history stack as standard YAML menus. See [Developer application API](/en/feature-configuration/application-api.md) for the integration guide.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.myarc.icu/en/configuration-and-administration/compatibility.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.