Would be nice if anyone official could create a... - - - - - Topic: Official information about the status of the Bukkit-Project Contents: This is the official thread for what is going on with Bukkit during the current times / through the Mojang take-over. Subscribe here to get informed about any official changes and announcements regarding the operation of the project.- - - - - ...thread, and lock it so only officials can post in it. The idea being that currently lots of people are confused and it would be good to send a clearer message to all the community members that here is where you should look for your answers - this one spot is where the answers to your questions will (eventually) appear. What we know thus far EvilSeph made an announcement about Bukkit shutting down. This created a lot of turmoil and confusion as rumor and misinformation spread that all of Bukkit would shut down due to legal uncertainties regarding Mojangs "evil EULA". EvilSeph was removed from the Bukkit forums as Administrator after Grum and Dinnerbone seized control of the Bukkit forums and GitHub repository. Mojang has taken over many aspects of Bukkit. They own the Bukkit-projekt. Dinnerbone sold Bukkit to Curse a long time ago when Bukkit had major hosting problems. (Curse offered to hire him, host Bukkit, and not to interfere in the project itself.) Mojang bought it from Curse ~2 years ago to prevent any potential legal issues with the EULA and ensure Bukkit was safe. Dinnerbone will personally update Bukkit to 1.8 He has also clarified that Bukkit is not the official Minecraft Modding API. (We have every reason to expect a great API once it comes out since Dinnerbone is one of the original creators of Bukkit and his goal has always been to make something that will outdo it. ) They have locked the GitHub-repository. Dinnerbone said in the BukkitDev IRC that this is until they have sorted out what to do next / how to best proceed. He also said that they do not intend to stop any forking. Bukkit is GPLv3 CraftBukkit is LGPLv3 TnT has stepped down and is no longer working on Bukkit. He was next in line to take over after EvilSeph, but since Mojang has promised to take care of Bukkit he feels he can finally allow himself to step down and spend some time with his family. (You deserve it TnT! ) He still encourages people to create pull requests in the simple hopes that Bukkit and Minecraft will become more awesome than ever (once Mojang unlocks commits to the repository again). Download of the craftbukkit software on http://dl.bukkit.org/downloads/craftbukkit/ has been disabled due to a DMCA takedown request by Wolvereness- (a staff member and top10 code contributor to CB). Simply put this means that the possible legal issues with the various software licenses that should probably best have been resolved a very long time ago, but never was, has been forced from heated arguments into legal domain. It also means that there is a code-freeze... Also there is now an official post by Mojang!!! Many additional staff-members are stepping down... mbaxter has retired. evilmidget38 has retired. lukegb has retired. feildmaster has retired. and many, many more... a long list can be found here. Plugin submissions / files are not currently processed! (see the post below this one) > If I've missed anything important post it in the thread! < Ok.... so bukkit as a live project looks rather fucked by now: ...and (Sept 8 - 2014) (trimmed away some messages): Read the whole unedited chat-log here - with many former staff joining in.Bonus: "[21:29] <BlizzardFyre> What's going on with the next Bukkit release?" "[21:31] <MeltedLux> BlizzardFyre, its done" My hope at this point is that somehow 1.7.9 will stay alive, and the bukkit site will "resurrect" and still accept plugin submissions. So it's not on the latest version - I can deal with that - forge has been behind practically forever... it's community doesn't need to shrivel up and die, just change the goals and direction. It can still be re-purposed and remain an amazing site with an awesome creative community. (Admittedly it would shrink a lot - but that's not necessarily a bad thing either.) (Oh... and it would be a good idea to remove the restriction on mentioning other server software - at this point in time I strongly believe the community would benefit from an as open discussion as possible. The original reasoning behind that rule is suddenly outdated is it not?) EDIT by Moderator: merged posts, please use the edit button instead of double posting.