About
About PluginForge
An AI plugin creator for Minecraft server owners who want a working plugin, not a research project.
PluginForge Team
Plugin tooling for server owners
We build PluginForge, the AI Minecraft plugin creator. The guides come from what we see when plugins are generated, compiled and installed on Paper and Spigot servers.
Why PluginForge exists
Running a Minecraft server means constantly missing small things: a command that does one specific job, a join message in your own words, a kit with the cooldown you want. Finding a public plugin that does exactly that is hit and miss, and hiring a developer for a twenty-line idea is rarely worth it. PluginForge was built for that gap. You describe the small thing in plain language and you get a plugin that does it, with the source so you are never locked in.
How a request is processed
- You write what the plugin should do and pick the Minecraft version your server runs.
- The AI is briefed with the rules of that version: the API it may use, the Java level and which items and blocks exist.
- It returns the Java files, plugin.yml and config.yml. A safety scan checks the code before anything is built.
- Maven compiles the project against the real Paper or Spigot API. If the compiler complains, the errors go back to the AI, which repairs the code. This repeats a limited number of times.
- You download the jar and the source. Further requests change the existing code instead of starting over.
- How it works
- You describe a plugin. An AI model writes the Java and the plugin.yml. Maven compiles it against the API of your Minecraft version. If the compiler reports errors, the AI repairs the code and tries again.
- What you get
- A compiled .jar and the complete source as a Maven project. There is no PluginForge code inside the jar and it never contacts us.
- Privacy
- Your plugins are visible only to your account. We do not publish them.
- Safety
- A scan blocks code that runs system commands, opens raw sockets, loads remote code, shuts down the JVM or grants operator status, before anything is built.
- Limits
- AI-written code can contain bugs, so test on a copy of your server. Fabric, Forge, Velocity and BungeeCord are not supported, and neither is NMS.
What it is good at
PluginForge works well for commands, menus, cooldowns, kits, homes and warps, simple economies, join and chat features, scoreboards and small minigames. These are jobs with clear rules that can be written down in a few sentences, which is exactly what an AI model needs to produce reliable code. It also works with Vault, LuckPerms and PlaceholderAPI when you ask for them, and treats them as optional so the plugin still starts without them.
What it is not for
It is not a tool for anti-cheat, custom world generation, deep changes to the server internals through NMS, or anything that has to be perfect without testing. Code that is meant to harm a server or hide what it does is refused. AI can also misread a description, so every plugin should be tested on a copy of your server before it goes live.
Credits and fairness
Credits measure the AI work of a request: a typical plugin uses about two, a small change less, a large one more, and each request shows what it used. Compiling, automatic repairs and downloads are free, and a request that fails on our side costs nothing. Packs are one-time purchases that never expire, and every new account starts with five free credits so you can judge the result before paying. The details are on the pricing page.