> 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/readme.md).
# ArcMenu Premium
Build an interface that truly belongs to your Minecraft server.
ArcMenu brings text, images, GIFs, item models, and animations together into custom in-game interfaces. Whether you are building server navigation, shops, daily check-ins, and quest boards, or login screens, guilds, story cutscenes, and music players, everything can share a cohesive visual style and interaction model. Players can use Touch and Mouse modes without any client mods, or install the ArcMenu Editor mod to unlock Vision mode.
## What you can do with it
* **Freeform layouts and reusable components**: Arrange text, images, items, blocks, rectangular backgrounds, borders, and lines on a single canvas, with multi-level nested groups and reusable component templates.
* **Three input modes**: Touch mode aims with the crosshair while keeping vanilla world lighting and block occlusion intact, so gameplay looks natural even with shader packs enabled. Mouse mode uses the server resource pack to provide a locked camera view and a local cursor. Vision mode is built into the ArcMenu Editor mod, offering a shader-compatible native cursor, fixed FOV, and dedicated menu rendering.
* **Multi-button clicks and hover feedback**: Every button region can respond independently to left, right, middle, and Shift-modified clicks, and can display custom tooltips and play hover animations when pointed at.
* **Menu navigation and conditional logic**: Clicking a button can run commands, open another menu, or return to the previous page, while permissions, economy balances, or math expressions decide what content appears and where navigation leads.
* **Dynamic content and custom assets**: Render live player heads and PlaceholderAPI values, display custom item models directly from CraftEngine, Nexo, or ItemsAdder, tint images, and play animated GIFs.
* **Keyframe animations and cutscenes**: Set up entry, transition, and exit animations for menus, or use Effect to build cutscenes complete with audio waveform previews, cubic Bézier curves, keyframes, and event tracks.
* **In-game WYSIWYG editing**: Administrators with a matching ArcMenu Editor build for their client version can drag and arrange elements right beside a live 16:9 game viewport, manage layers, browse resource pack images, undo changes, and save immediately.
* **Project packaging and marketplace**: Bundle menus, templates, images, and Effects into ArcPack archives from your workspace, and browse the marketplace inside the editor to download community creations or publish your own designs.
* **Open application API**: Developers can connect custom inventories, card games, music players, social systems, or login flows to ArcMenu, keeping business data in their own plugin while ArcMenu handles the screen, pointer input, text input components (Arcitx), and page history stack.
## Getting started
Before starting your server, check [Requirements](/en/getting-started/requirements.md) to review the server environment, client input modes, and optional companion plugins, then follow [Installation and updates](/en/getting-started/install.md) to drop the plugin into your server and set up the resource pack.
If you prefer learning the structure from configuration files first, follow [Your first menu](/en/getting-started/first-menu.md) to write a welcome screen with a working button, and refer to [Menu document structure](/en/menu-configuration/menus.md) for the full YAML reference.
For day-to-day layout and design work, we recommend pairing the server with the **ArcMenu Editor** client mod so you can drag and adjust elements directly in-game. See [Visual editor](/en/feature-configuration/editor.md) and [Project manager](/en/feature-configuration/projects.md) for details.
---
# 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/readme.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.
