Skip to content
pluggy

The Minecraft plugin toolchain.

Build a Minecraft plugin without setting up Java.
Get started View on GitHub
Terminal window
curl -fsSL https://pluggy.sh/install.sh | sh
pluggy init my-plugin
cd my-plugin && pluggy dev

Pluggy installs the JDK, resolves dependencies, builds your plugin, and runs a live dev server. Useful from your first plugin to your hundredth.

What pluggy does

Provisions JDKs

pluggy init and pluggy build install the right Temurin JDK for your Minecraft version. You never set JAVA_HOME yourself.

Resolves dependencies

pluggy install <name> pulls from Modrinth and Maven. A pluggy.lock records exact versions so every machine builds the same jar.

Runs a live dev server

pluggy dev starts a local Paper, Folia, Velocity, or Sponge server and reloads your plugin on every save.

Generates IDE files

Open the project in IntelliJ, VS Code, or Eclipse. The .classpath is written on every build. No import wizard.

Builds for every platform

One project.json targets Paper, Folia, Spigot, Bukkit, Velocity, BungeeCord, Waterfall, and Sponge.

Ships as one binary

Install pluggy with curl on macOS or Linux, brew on either, or PowerShell on Windows. No JDK, Maven, or Gradle required to run pluggy itself.

Why pluggy exists

Building a Minecraft plugin still requires installing a JDK, picking a build tool, configuring Maven or Gradle, and importing the result into an IDE. For a newcomer that is a weekend before any code runs. For an experienced developer it is recurring tax on every new project.

Pluggy collapses every step into a single binary. You run pluggy init and pluggy dev, and your plugin compiles, loads, and reloads while you write code.

Install

Terminal window
curl -fsSL https://pluggy.sh/install.sh | sh

After install, pluggy doctor reports your install method and any environment issues. Then head to Getting started.