The Hole in the Bukkit
As many of you are already aware, we may soon be in a world without Bukkit, the third-party version of the Minecraft server software. Yesterday, one of the developers for Bukkit announced the end of the project. This decision was quickly vetoed by Mojang, who revealed that they had bought Bukkit over two years ago. Dinnerbone, one of Minecraft’s lead developers and former Bukkit developer, announced that he would personally be updating Bukkit to 1.8, very shortly after announcing a prerelease version of Minecraft 1.8. Dinnerbone made it very clear that Bukkit will NOT be the official mod/plugin API that we’ve been promised for years, and hinted that the official API would be much better.
So what does this all mean? Well, the situation is still developing. The announcement from Bukkit was edited, striking out the entire statement and leaving us with cryptic messages such as “There’s more to come on this. Please stand by.” and “To be continued…” What we do know is that Bukkit will receive an update for 1.8, and Dinnerbone is currently working on it. However, anything after that remains unclear. Personally, I think it’s likely that Mojang will continue to update Bukkit until they release their official API. This will likely mean a complete restructure of the plugin system, forcing many plugin devs to rewrite their entire plugins with the new API. Will we lose a bunch of plugins? Probably. However the extent of the damages remains to be seen.
Meanwhile Spigot, popular Bukkit alternative (and all-around better choice, in my opinion), has yet to make an official statement, however they have stated that they “intend to continue Spigot for many Minecraft versions to come, whatever circumstances may unfold.”
The bottom line is we will probably be without Bukkit in the future, however we still have a while for events to unfold and things to change.