Minecraft Bukkit began in September 2010 with the development of a modification called hMod by developer hey0 and other programmers. This mod served to improve Minecraft Server with additional functions and features. This laid the foundation stone for a possibility of server modification. Bukkit, the plugin development framework. The documentation is for developing plugins and is split into the respective packages for each subject matter. This documentation does not cover running a server, contributing code back to the project, or setting up a workspace. Working knowledge of the Java language is a prerequisite for developing.

• Bukkit Server Gui
• Bukkit Server Plugin
• Bukkit Server Spigot

• Set up a Bukkit server such as Spigot or Paper (Paper is recommended over Spigot). Download WorldEdit from this page (see the Files tab above for all versions). Put the WorldEdit plugin file into your plugins folder. Check YouTube for tutorials, or read the official documentation. We also recommend WorldGuard and CraftBook!
• Create your own Minecraft Bukkit server! By purchasing a Minecraft Hosting from us and following several steps you can host a Minecraft Bukkit server.

Bukkit, the plugin development framework.

The documentation is for developing plugins and is split into therespective packages for each subject matter. This documentation does notcover running a server, contributing code back to the project, or settingup a workspace. Working knowledge of the Java language is a prerequisitefor developing plugins.

For basic plugin development, see the pluginpackage. It covers the basic requirements of a plugin jar.

For handling events and triggered code, see the event package.

Bukkit Server Gui

Note: While the Bukkit API makes every effort to ensure stability, this isnot guaranteed, especially across major versions. In particular thefollowing is a (incomplete) list of things that are not API.

Bukkit Server Plugin

Bukkit Server Spigot

• Implementing interfaces. The Bukkit API is designed to only beimplemented by server software. Unless a class/interface is obviouslydesigned for extension (eg BukkitRunnable), orexplicitly marked as such, it should not be implemented by plugins. Althoughthis can sometimes work, it is not guaranteed to do so and resulting bugswill be disregarded.
• Constructing inbuilt events. Although backwards compatibility isattempted where possible, it is sometimes not possible to add new fields toevents without breaking existing constructors. To ensure that the APIcontinues to evolve, event constructors are therefore not plugin API.
• Implementation classes. Concrete implementation classes packaged withBukkit (eg those beginning with Simple) are not API. You should access themvia their interfaces instead.