Mentioned features/Plugin API

From Minecraft Wiki
< Mentioned features(Redirected from Plugin API)
Jump to: navigation, search

The Plugin API,[1][2] dubbed "Workbench", is a feature that allows mod developers to easily add more content to the game. In contrast to mods, plugins will not require any alteration of the minecraft.jar file itself, although they will also be slightly limited in their feature set.[3][4] The Bukkit team will help make the official Plugin API.[5]

Features[edit | edit source]

It is planned that plugins shall be as easy as possible to find, download, and install.[6][7][8] Although the Bukkit team will help make the API, it will not be based on Bukkit.

The following features are planned as part of the Plugin API:

  • Plugins will be targeted at multiplayer, eventually extending into singleplayer as well.
  • It aims to support directly adding plugins by allowing installation directly in the game, reducing time and effort to install modifications, and making them less prone to accidentally destroying the game.
  • The Minecraft website will be revamped, helping to bring the most interesting community plugins and custom maps to the surface.
  • It will be easier to add and animate models.
  • It will change the way the game stores data regarding its many materials and items.
  • A way for mod/plugin makers to implement new commands and register them in a simple way.[9][10][11]

Resource packs were added in 1.6, and the release of a self-updating launcher for running newer versions of the game and allowing for more functionality makes it a step closer to the incorporation of the Plugin API. However, resource packs are not to be used for adding plugins, a separate API is to be used to accomplish this. Rather, resource packs simply modify the look and feel of the game, while plugins aim to change how the game functions.

At MineCon 2012, Mojang shared their vision for the future of the Plugin API.

Development[edit | edit source]

Initially called the Modding API, it has been planned in some capacity since at least July 5, 2010, shortly after the release of Alpha 1.0.1_01.[12] It was then stated to be released in Beta 1.8.[13] The Modding API was then rebranded as the Plugin API, with the release originally stated to be planned for 1.3, then for 1.4, and then it was accidentally stated by Curse that it would be implemented in 1.5, but has since been delayed.[14][15]

As of October 26, 2013, the Plugin API cannot be found on its GitHub page. Furthermore, the developer website has also been taken offline ( However, Dinnerbone has mentioned that many changes made in the past few years have been preparation for the Plugin API.[16]

On July 5th 2015, Grum briefly commented on the plugin API following a question at the "The Minecraft Team - Behind the Scenes" panel.[17] He explained the team didn't think they could produce anything better than what Forge offered with the current codebase and as such it didn't make sense to do exactly the same as Forge. He reiterated what had been said about past changes to the code being preparation for the API.

When Dinnerbone was working on the loot tables for 1.9, he tweeted on October 19, 2015: "And all I'm saying is that these very things that make the game so much easier to modify are huge steps towards an API."[18] A user replied "I think an official "we're working on it" would really help a lot"[19] to which Dinnerbone replied "We're working on it."[20]

On August 12, 2016, Searge tweeted: "There will be news about the API at Minecon. I'll talk about the things I'm working on and what our plans are. But no more details for now."[21] The next day it was confirmed by Grum to be for Pocket Edition.[22]

References[edit | edit source]

  4. Modding API: Modding API
  5. Modding API: Bukkit Developing API
  7. Modding API: Curse Interview with Jeb (Part 1)
  8. Modding API: Curse Interview with Jeb (Part 2)
  12. Server scripting