> 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/getting-started/requirements.md).
# Requirements
Before deploying ArcMenu Premium, review the server requirements below and see how the client input modes and optional companion plugins fit together.
## Server and Java
| Server generation | Java requirement |
| ------------------- | ---------------- |
| Paper 1.21.x series | Java 21 or later |
| Paper 26.x series | Java 25 or later |
Paper forks such as Leaf, Folia, and Purpur run the same plugin JAR with full feature support. On Folia, the plugin automatically handles display entities and interactions on each player's owning region thread.
## Player clients and input modes
Players can interact with menus using three modes. You can let players switch freely between them or configure a default mode on the server:
* **Touch mode**: Needs no client mod and does not use ArcMenu shader resources. Menus render with vanilla display entities, scale naturally with the player's FOV, and follow normal world lighting and block occlusion, preserving normal gameplay visuals when players use shader packs.
* **Mouse mode**: Needs no client mod. Once the client loads the companion ArcMenu resource pack, it gets a fixed-FOV view, flat item lighting, and a smooth local cursor. When used alongside ViaVersion, the server automatically matches resources to each player's actual client protocol version.
* **Vision mode**: Requires Fabric, the matching Fabric API for the game version, and the **ArcMenu Editor** mod matching the client version. Vision is built right into the Editor mod, and regular players can use it without administrator permissions. It runs a zero-latency native cursor locally, fixed-FOV projection, independent depth occlusion, and bright UI item rendering while staying compatible with third-party shader packs. For text fields, it also lets players type directly through native text input and their system IME without opening a vanilla anvil screen.
Click detection, hover checks, and menu actions for all three modes are processed uniformly by the server.
## Optional companion plugins
All of the following plugins are optional and can be installed based on what your server needs:
| Plugin | Role in ArcMenu |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
| PlaceholderAPI | Read player counts, levels, stats, and other placeholders inside text, image paths, player head textures, or conditions. |
| Vault (with an economy plugin) | Check currency balances in menu conditions, or charge and reward money in click actions. |
| PlayerPoints | Check point balances, or deduct and grant points. |
| CraftEngine | Display custom CE items in menus, and automatically merge ArcMenu images and font assets when building the resource pack. |
| Nexo | Display custom Nexo items, and automatically merge ArcMenu assets into the Nexo resource pack during pack generation. |
| ItemsAdder | Display custom ItemsAdder items with their original metadata and overlays intact, and automatically merge ArcMenu assets when packaging. |
## Client editor and Vision mod
[ArcMenu Editor](https://github.com/FENTAIIII/ArcMenu-Editor/releases) is the companion client-side Fabric mod. Users with administrator permissions can use it to open the visual menu editor, Effect cutscene workspace, project manager, and menu marketplace, as well as preview menus with dedicated rendering inside the editor. Regular players can install the same mod to enable Vision mode.
The releases page provides separate builds for each Minecraft version (1.21.x clients require Java 21+, and 26.x clients require Java 25+). To install it, pick the single JAR whose `mc` version in the filename matches your game client, place it into your client's `mods/` folder alongside the matching Fabric API, and make sure you do not keep multiple Editor JARs in `mods/` at the same time. When upgrading or troubleshooting, update both the server plugin and the client Editor to the latest release together.
---
# 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/getting-started/requirements.md?ask=&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.
