Bukkit plugin generator for plugins that move between servers

Bukkit started as an API: a set of Java interfaces under org.bukkit describing players, worlds, blocks, events and commands. CraftBukkit was the server that implemented those interfaces on top of vanilla Minecraft. Spigot grew out of CraftBukkit and Paper out of Spigot, and each kept the Bukkit API while adding its own features.

That history is why people still search for a "CraftBukkit plugin" when they mean a plugin for Spigot or Paper. The plugin talks to the Bukkit API; the server software underneath decides how it runs.

When you pick Bukkit on Spaleforce, the plugin is compiled against the Spigot API artifact, which contains the complete Bukkit API, so everything the plugin needs from Bukkit is available at build time.

Server owners switch software more often than they rewrite plugins. A network may start on Spigot, move to Paper for performance, then try Purpur for its gameplay settings. A plugin built on the Bukkit API usually follows along untouched, because each of those servers still implements it.

Staying on the common API also keeps the code familiar to any Bukkit developer: commands through a CommandExecutor, events through a Listener with @EventHandler methods, settings through config.yml, data attached to items through the persistent data container.

The Bukkit API is stable, not static. In 1.20.5, many EntityType constants were renamed: DROPPED_ITEM became ITEM and PRIMED_TNT became TNT. In 1.21.3, attributes lost their GENERIC_ prefix, so GENERIC_MAX_HEALTH became MAX_HEALTH. Code written for one side of those changes does not compile on the other.

The AI checks the version you selected before writing anything, so it uses the names that exist in that release and skips methods added later. If a mistake still gets through, the compiler catches it and the AI corrects the file.

The practical rule: generate for the version your server actually runs. When you upgrade the server, rebuild the plugin for the new version instead of assuming the old .jar still loads.

Some features need more than the shared API. Rich chat with hover and click actions is simpler with Paper's text components. Purpur exposes extra options of its own. Folia replaces the Bukkit scheduler with region-based schedulers and refuses plugins that are not marked as compatible.

In those cases, pick the matching server type instead of Bukkit. The generator offers Paper, Purpur, Pufferfish, Leaf, Folia, Spigot and Bukkit, so you can trade a little portability for the features you need.

After generation, the project opens in an online editor where every file is visible. Ask for adjustments in plain language, and each change is kept in the version history.

From the editor you can start a real Minecraft test server on the version you want and join it. Once the plugin behaves, download the .jar or publish it on the Spaleforce marketplace for other server owners.