What is Bukkit doing?

In case you’re not familiar with Minecraft servers, it’s a bit of an odd dynamic. In the vast majority of multiplayer games, there are one of two things: dedicated servers, or console-hosted rounds. In Call of Duty (in the past, this is changing now), one of the consoles in the multiplayer lobby would be chosen, based on ping speed, location, and latency. That console would host the match. It puts that particular console under more stress, but it ensures everyone else runs at a faster pace. Or, there are dedicated servers. Built for only that game, they are the fastest and most reliable way to play online. Problem is, dedicated servers aren’t cheap, so services like Xbox Live have to be made to pay for that.

Then there is Minecraft. Since there aren’t rounds or matches, the server has to be online 24/7. Mojang can’t possibly hope to create enough dedicated servers to house them all, and no one wants to sacrifice their computer’s RAM and never reboot it for a console-hosted server. Both of those, interestingly enough, are in the works or are in use, but are not the most popular option. The most popular option is to purchase a server through a hosting service, like MC Pro Hosting or Fragnet. And unless you want a totally vanilla, no plugins, no modifications server, you’ll probably want Bukkit. Bukkit is a free software that allows plugins, modifications, and easy API for developers to use. It’s a super slick piece of software, and is most commonly used by servers. Sure, there’s Tekkit and Feed The Beast, but they are significantly less popular and serve a different purpose.

With the recent release of 1.7.2, Bukkit hasn’t been getting on the development train like most people want them to. In fact, they’re still releasing and working on 1.6.4 versions instead of 1.7.2. Why is that? Keep reading to hear my speculation.

1.7.2 has some massive changes. Aside from the biome generator, the entire multiplayer system has been rewritten, along with the sound engine, and lots of other behind the scenes details. These could be delaying Bukkit longer than previous versions of Minecraft. But that still doesn’t account for why they’re making new 1.6.4 builds. They released an official Recommended Build (a stable, complete version) shortly before 1.7.2 was officially launched. Unless there are some absolutely gamebreaking glitches, why are they still updating for 1.6.4?

There’s an odd issue between 1.6.2 and 1.7.2. All dungeons, villages, nether fortresses, and generated buildings will all be lost and deleted! That’s a bit of a big problem. That’s the key reason that Mojang released 1.6.4, because that will prevent the loss of buildings and make a bit smoother transition to the new 1.7.2 generation engine. Alright, that makes sense. Even though many servers (mine included) are going to be making a new world using only the 1.7.2 generation engine, it’s good to keep old structures around.

But Bukkit seems far over-concerned with this. They released the first recommended build of 1.6.4, told everyone to install it, and run a custom plugin to absolutely guaranty that you wouldn’t lose any structures. That’s convenient, and fairly helpful. But why create a second recommended build? And, if I’m reading their Twitter correctly, they’re working on yet another build. Seriously? Everyone is anxiously waiting to play 1.7.2 with their friends online, and Bukkit is dropping the ball. My server has been an empty land since 1.7.2 launched. Fixing the 1.6.4 build will not bring them back.

So, in short, Bukkit should seriously get to work on the 1.7.2 build. Get a dev build out at least, something that is quality enough to make the transition to 1.7.2. We’ve waited almost a week, and they keep making 1.6.4. 1.6.4 is already obsolete, it’s time to move on.