Minecraft plugin maker with an editor, a test server and version history

A tool that hands you a file and forgets about it leaves you stuck at the first bug or the first "can it also do this?". Server plugins evolve: players find edge cases, staff ask for a new permission, an event needs a different reward.

Spaleforce keeps each plugin as a project. The files stay in your dashboard, you reopen them whenever you like, and every request builds on what already exists instead of starting from zero.

The first version comes from a description. You choose the server type, pick a Minecraft version between 1.16 and 26.3, and explain what the plugin should do.

Once generated, the plugin opens in an online editor listing its files: main class, commands, listeners, plugin.yml and config.yml. You can read all of it, even if you never intend to write Java.

To change something, type it the way you would explain it to a developer: "add a 30-second cooldown to /kit", "store balances in a file instead of memory", "show the reward message in the action bar". The AI edits the relevant files and leaves the rest alone.

Each change becomes a new version in the project history. If an idea does not pan out, you go back to an earlier version instead of trying to undo it by hand.

No-code here means you never write the Java yourself. The AI writes it, our servers compile it with Maven, and any compile error goes back to the AI, which fixes it. You end up with a working .jar, not a file that fails the first time it meets a compiler.

The AI also stays within the version you chose, so it does not call APIs your server lacks, and the plugin is compiled with the matching Java level. Popular dependencies such as Vault, PlaceholderAPI, WorldEdit and PlotSquared are resolved during the build.

Knowing what you want still matters. The more precisely you describe commands, permissions and messages, the fewer rounds of edits you need.

From the editor, start a real Minecraft test server, choose its version and connect with your own client. Run the commands, trigger the events and read the messages exactly as a player would.

When something feels off, go back to the editor, describe the fix and test again. That loop of describe, test, adjust is what turns a rough first draft into a plugin you can trust on a live server.

When you are happy with it, download the compiled .jar and drop it into your server's plugins folder. You can also publish it on the Spaleforce marketplace, which lists more than 3,100 public plugins and models, and pick up ideas from what others have built.

Plugins made on the free plan keep an embedded "Powered by Spaleforce" credit. With Pro or Ultimate, plugins carry no Spaleforce mention and can be used commercially, with no royalties.