> For the complete documentation index, see [llms.txt](https://simple.superiormc.cn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://simple.superiormc.cn/arcmenu-wiki/configuration-and-administration/compatibility.md). # Platform and plugin compatibility This page covers feature availability across servers and considerations for using menus with other plugins. Minecraft, Java and client version requirements are listed in [Requirements](/arcmenu-wiki/getting-started/requirements.md). ## Server features Paper, Folia, Leaf and compatible servers support the full menu feature set. Spigot supports basic menus; check that the features you need are available before configuring them. | Feature | Paper, Folia, Leaf and compatible servers | Spigot | | --------------------------------------------------- | ----------------------------------------- | -------------------------------------------- | | Text, rectangular backgrounds and borders | Supported | Supported | | Vanilla item and block displays | Supported | Supported | | Crosshair or view-based interaction | Supported | Supported | | Mouse mode | Supported | Unavailable | | Menu navigation, back and close | Supported | Supported | | Permission checks and basic conditions | Supported | Supported | | Messages, player commands and console commands | Supported | Supported | | Custom images and CraftEngine items | Supported | Unavailable | | Tooltips and animations | Supported | Unavailable | | Reusable templates | Supported | Unavailable | | PlaceholderAPI, Vault and PlayerPoints integrations | Supported | Unavailable | | ArcMenu Editor visual editing | Supported | Unavailable | | Configurable plugin message language | Supported | Supported through the root language settings | Menu text and custom messages remain editable on Spigot. Its supported conditions and actions are more limited, so Paper menus containing advanced features cannot be used unchanged. Menu directories also differ between server types. When changing server software, place files according to [Configuration files](/arcmenu-wiki/configuration-and-administration/configuration-files.md) and check the features used by each menu. ## Optional plugin integrations The direct integrations below apply to Paper, Folia, Leaf and compatible servers. Restart the server after installing optional plugins and confirm that they are enabled successfully. ### PlaceholderAPI Use PlaceholderAPI to display information provided by other plugins. Check that the required placeholders resolve correctly before using them. Missing plugins or placeholder support prevent the corresponding data from appearing. ArcMenu's built-in player name, UUID and coordinate placeholders do not require PlaceholderAPI. Spigot supports these basic placeholders but does not support additional placeholders supplied by PlaceholderAPI. ### Vault and PlayerPoints Vault connects menus to server economy features and requires a compatible economy plugin. PlayerPoints provides player point features. Before using balance or point operations in menus, confirm that the relevant plugins work correctly. Installing Vault alone does not provide balances or turn a menu into a shop; transactions and button actions still require configuration. ### CraftEngine CraftEngine integration supports custom item displays and merging ArcMenu assets into the CraftEngine resource pack. Ensure that custom items are correctly configured in CraftEngine before using them. After changing menu images, reload ArcMenu resources, rebuild the CraftEngine pack and have players load the updated pack. See [Resource pack configuration](/arcmenu-wiki/getting-started/install.md#resource-pack-configuration). ArcMenu images can also be used without CraftEngine, but the resource pack must be distributed separately. ### ViaVersion When using ViaVersion to allow other client versions to connect, check that those clients still meet ArcMenu's mouse-mode requirements. Being able to join does not establish compatibility with every menu feature. Check menu appearance, mouse clicks and resource-pack loading with the client versions allowed on your server. See [Client requirements](/arcmenu-wiki/getting-started/requirements.md#client-requirements). ## Connecting other plugins through commands A menu button can run another plugin's command even without a dedicated ArcMenu integration. This also works on Spigot. Before configuring a button, confirm that: * The target plugin is installed and its command works. * Players have the required permission when executing the command as a player. * Console commands support console execution and include any required player arguments. Running a plugin's command from a button does not mean ArcMenu supplies all of that plugin's features. Consult the target plugin's documentation for arguments, permissions and restrictions. ## Resource packs and the editor ### Server resource packs Custom images require players to accept and load a resource pack. If the server already uses a pack, include ArcMenu assets in the merged pack distributed to players. If menu images or mouse visuals appear incorrectly, check that players have loaded the updated pack. Rebuilding a pack on the server alone does not update the assets players are using. ### ArcMenu Editor The editor is for administrators designing menus; ordinary players do not need it. Choose an editor compatible with the administrator's client and the ArcMenu plugin. Spigot does not support the editor. When transferring an editor-created menu to another server, confirm that the destination supports its features and provides the required resource pack. ## Compatibility checks When first enabling a menu or changing server software, plugins, clients or resource packs, check that: 1. Configuration validation and reload succeed. 2. Menu text, items and images appear correctly. 3. Hit regions, navigation and third-party commands work. 4. Placeholders, economy and point operations behave as configured. 5. Ordinary players have the required permissions and can load the resource pack. Include an ordinary player account in permission checks rather than testing only as OP. Relevant commands are listed in [Commands and permissions](/arcmenu-wiki/configuration-and-administration/commands-permissions.md). ## Next step Read [Menu document structure](/arcmenu-wiki/menu-configuration/menus.md) for a hierarchical introduction to menu configuration.