Talk:Plugin API

Github
Am I reading this wrong, or has no one added any code to that since August 2012? Are we sure that the purpose of the Git was to allow people to see the Plugins API while it was in development? Firebastard 00:36, 25 April 2013 (UTC)
 * We don't know what's going on with the repo, but rumors say that they plan to create a new repo and delete that one. Mojang have not released any official statements on it afaik, we're pretty much in the dark (except that Forge and Bukkit are like bright parallel universes). Hopefully we will see some development after 1.6 releases - currently it looks like they're using 1.6 for some general mass overhaul and refactoring of... well, everything.  LB ( T 01:49, 25 April 2013 (UTC)

Issues with the page
Uhh... The site is contradicting itself. In the first section, it says the Bukkit team is making the API, but down lower, it says they won't be... I don't have any information regarding whether the Bukkit team will make it, so can someone who knows more about it fix the self-contradictory statements? –Preceding unsigned comment was added by 17slim (talk • contribs)&#32;15:51, 17 October 2013&#32;(UTC). Please sign your posts with


 * Rewritten to make it clearer: the Bukkit team is working on the Plugin API, but it isn't going to be based on Bukkit itself. -- Orthotopetalk 02:53, 18 October 2013 (UTC)

General Talk/Questions
Does anyone know anything about the changes in 1.7 to start toward the API? What changed in the code?17slim (talk) 17:19, 26 October 2013 (UTC)

Development Hell
Considering that there haven't been any significant developments on the Plugin API since August 2012, and the only feedback we've received since then have been vague hints at it, I believe it may be time to remove Plugin API from upcoming features and reword the Plugin API page to show that development has halted on it, and shift it over to the unimplemented features page. Although it's not officially cancelled I believe it falls under the category of: "Development hell ADCK (talk) 03:05, 18 November 2013 (UTC)


 * On the contrary, I think 1.7 shows the most signs of progress toward the plugin API so far. Most visible is the shift to named identifiers, which will allow plugins to add new blocks and items without conflicting over hardcoded ID numbers. There's the ability to select multiple resource packs, which I suspect will eventually be turned into plugins. Also, there's been a huge amount of behind-the-scenes refactoring, which is why MCP is taking so much longer than usual to update. -- Orthotopetalk 17:37, 18 November 2013 (UTC)


 * Perhaps. It's been over a year since Plugin API was announced, if by this time next year it still hasn't been released, It would be safe to say it's not going to be released at all. ADCK (talk) 23:17, 18 November 2013 (UTC)


 * So true to my word, here I am one year later... and where is the plugin api? Still in development hell, that's where. It's now safe to say it's in limbo. Good too see it was moved from "Planned" to "Mentioned" features. I am curious though, has there been any mention of it at all since the takeover by microsoft? ADCK (talk) 23:45, 24 November 2014 (UTC)

I hope still for forge
The info relesed so far and how plugins for bukkit work and that the BUKKIT TEAM is most likely helping make it, I hope Forge will still exsist as plugins would SUCK. They would be just bukkits plugins system intergrated into MC, um, no! Restrictions, as said on the main page, would be not be able to add anything except commands and new functions to items. This is why I dont develop plugins 98.246.88.253 11:52, 29 December 2013 (UTC)


 * You misunderstand - you assume that they will affect the server-side only. THis is not true - they will affect both server and client and can do everything that Forge mods can.  LB ( T 21:44, 29 December 2013 (UTC)
 * Oh, ok. Considering the page says the bukkit team is developing it, I thought it would just be that. Okay, thanks. Nvm --01:47, 5 January 2014 (UTC)98.246.88.253