Minecraft 1.6 Breaks the Game, Mojang Fixes It

| 27 May 2011 18:58

The latest patch for indie sensation Minecraft is out, and so is the patch fixing everything that the patch broke.

Patching a game as intricate and complex as Minecraft isn't easy. Still, creator Notch and his team at Mojang do their best with regular updates to the game, and patch 1.6 hit servers yesterday, adding maps - among other things - to the addictive build-a-thon.

Unfortunately, Patch 1.6 brought with it a host of nasty bugs and potentially-crippling performance issues. So, Mojang released not one, not two, but four bug fixes in an attempt to set right what had been set wrong, by themselves, not a day before. And then, setting right the things that they'd said they'd set right, but that actually hadn't been set right at all.

The full Beta 1.6 patch notes can be found here, if you're curious. The best part, though, is the notes for Beta 1.6.1 through 1.6.4. Somebody was feeling a little irritated at this point:

Update 1.6.1
-Fixed a visual item duplication bug when trying to pick up items while the inventory is full

Update 1.6.2
-Fixed an ACTUAL item duplication bug while picking up some items

Update 1.6.3
-The renderer is now capped at 100 fps while there are chunks to be generated. The excess time will be spent generating chunks instead of rendering frames
-The "limit framerate" option now limits the game to 40 fps and will spend at least 10 ms per frame sleeping
-The "limit framerate" option has been reset to "off" for all players, enable it again if you want it
-Fixed some block updates not updating lighting properly under some circumstances by reverting the "don't always send block data" fix in 1.6
-Fixed a major CPU load issue in the server where a very tight loop would starve all other threads
-Fixed furnaces dropping/duplicating their contents when they change state from lit to unlit or back

Update 1.6.4
-Fixed 1.6.3 using more CPU despite it claiming to use less
-Totally professional

I bet Obsidian and Bethesda wish they could fix their own patch screwups this quickly.

(Via Joystiq)

Comments on