Compatibility and prerequisites
Choose an agent that matches your runtime and understand what it can manage.
Choose the runtime, then the artifact
Open a server's Setup page for the current downloads. Do not use a Bukkit jar on a proxy or a native executable on another operating system.
| Target | Agent | What to prepare |
|---|---|---|
| Paper, Purpur, Folia, Spigot, Bukkit | EnderDash-Bukkit.jar | Access to the plugin directory, console, and runtime restart |
| Velocity | EnderDash-Velocity.jar | Proxy plugin directory and console |
| BungeeCord or Waterfall | EnderDash-Bungeecord.jar | Proxy plugin directory and console |
| Hytale | EnderDash-Hytale.jar | Hytale plugin installation and data directory |
| Linux x64 or ARM64 | Matching standalone executable | Writable agent directory and supported system libraries |
| macOS Apple Silicon | Standalone macOS ARM64 executable | Local permission to run the downloaded executable |
| Windows x64 | Standalone Windows executable | Writable executable and configuration directories |
| Docker, Podman, Kubernetes | Standalone container image | Platform access, socket or cluster credentials, and required RBAC |
Intel macOS and Windows ARM64 do not have standalone downloads. Linux builds use glibc, not musl. See standalone installation for library requirements.
For game runtimes, use the Java version required by the runtime and the selected agent release. The repository builds JVM agents with Java 25. Check the download and runtime release requirements before upgrading a production server.
Features follow the connected runtime
The agent reports capabilities when it connects. A proxy does not supply a game world's metrics. A standalone host does not supply a Minecraft console or players.
Some panels require a companion plugin, such as LuckPerms, EssentialsX, or Chunky. Some also require a plan feature. Server panels lists these requirements.
A working agent connection does not install Docker, Podman, Helm, or kubectl for you. Container platforms explains which tools each action needs.
Account and organization prerequisites
An owner or admin creates the server record and installs its key. Members need an explicit server grant. The organization must have an active subscription and an available server slot.
Each agent uses the key for one server record. Use distinct records and keys for separate runtimes. Never reuse a production key in the demo or share it in support messages.
Next: connect a Paper server or choose another installation.
Was this page helpful?
Send a quick note if anything is missing or unclear.
Last updated on