like Bukkit eating your cake or your world. You have been warned.

---------------------------

Common Problems/Questions:
What's the first build that works with Minecraft 1.5_02
The first CraftBukkit build that works with Minecraft 1.5_02 was made available 2 days ago and is build #689. However, it is HIGHLY RECOMMENDED that if you are running the test builds, you always stay up to date as we usually fix bugs, exploits and improve stability.

I downloaded build 714 but got some other build!
You're probably reading the version string incorrectly.

Here's an example version string:
git-Bukkit-0.0.0-686-g71ef92a-b714jnks (MC: 1.5_02)

This version string is for build 714, as you can tell by the "b714jnks" at the end.

Whenever I use a plugin that changes blocks, I can't see the changes until I reconnect!
We had an issue with blocks not updating properly but this has since been fixed from build #707. This bug affected plugins that changed blocks in game, like WorldEdit.

Help! My console keeps getting spammed with this error whenever someone gets kicked or disconnects and it lags the server!

[SEVERE] java.lang.IllegalStateException: Failed to remove player

This is a bug we've fixed from build #701 onwards.

I can't build or destroy anything! Help!?
The common cause of this issue is a client mod called Single Player Commands, please try uninstalling all your client mods and seeing if this fixes the issue. If this is the case, then it isn't a Bukkit issue and you should contact the author of the mods you use.

Every time I connect to the server and load a sign, the client crashes. What's wrong?
Minecraft 1.5 has added limits for sign text. Plugin developers commonly used longer sign text to store extra data or add colours to signs. This is no longer possible, so we now cut off any line in a sign longer than 15 characters (as of build #712).

I get kicked when flying and am told that flying hasn't been enabled on this server. How do I enable flying?
Minecraft 1.5 added anti-flying checks. You can enable flying by setting allow-flight=true in server.properties.

Whenever I try to send a long message in chat, it gets cut off at roughly two lines.
A limit on chat has been added with Minecraft 1.5. This is one of the issues we're hoping to address before we promote a Recommended Build.

Help! When I use the CLI arguments to set ports (or any setting), the server always starts up on 25565 or ignores the setting!
There was a bug that prevented the server from reading settings passed through CLI arguments. This has since been fixed from build #706 onwards.

The easiest fix for most problems is to update to the latest Bukkit test build.

--------------------------------

As is the case with every Minecraft update, we saw our usual influx of extra traffic from people wondering if we have a build of CraftBukkit working with the Minecraft update seconds after release (seriously). Usually, you'd see a pretty standard post from me stating we're working on an update and providing the usual advice that you aren't forced to update. However, this time there was a distinct lack of communication from the team regarding the status of the update, other than the usual "we're working on it". Couple this with the slow development occurring lately and we can forgive people for posting the expected "is Bukkit dead?" or "what's going on?" posts. I hope this post will explain everything.

Will there be a CraftBukkit for Minecraft 1.5?
Given the reports of showstopping bugs present in 1.5, there's a high chance a new bugfix update for Minecraft will be out tomorrow or even several times this week. As a result, it is unlikely we will be releasing a 1.5 compatible build and, instead, will be waiting for something stable to work with.

Due to the nature of the project and the methods we use to provide Bukkit for Minecraft, any update - no matter how small - requires us to figure out the mapping of obfuscated classes and update our code. This takes a lot of time and work, so hopefully you understand our decision.

Having said all this, we recommend that you stay on 1.4 for a while until the patch storm subsides if your server depends on Bukkit.

Further, I wanted to apologise for the lack of communication regarding this update. I was really hesitant announcing this since it would only serve to disappoint and annoy people, however, I noticed quite a few supportive comments on here and IRC that pushed me to post this announcement because the people that have supported us through everything deserve it.

Why are things so quiet? Why is the update taking so long?
Before I answer this, I think it is appropriate to cover what usually happens when we're aware of an update coming soon. Whenever we recieve word of a Minecraft update (which, contrary to popular belief, is generally the same time as everyone else), we place all development in the Bukkit project under a code freeze to prepare for the update and make things easier. That being said, last week thursday we were expecting a Minecraft update and appropriately placed the project under a code freeze. Unfortunately, the update was delayed and pushed to the next week, resulting in a much longer code freeze than normally occurs. Naturally, this lead to activity within the project seeming critically lower than it really was and prompted some people to post the inevitable "what's going on?" thread.

On top of the code freeze, we're working on some larger changes to Bukkit or CraftBukkit that require quite a bit of time to complete and will only be commited to the public code when they are ready. Quite often you'll find that, while you don't see any updates, we definitely are still working hard programming awesome things and appreciate your patience and support.

So why is this update taking so long? After we had updated for Minecraft 1.4, we came across some annoying chunk related issues and bugs that were incredibly difficult to pinpoint due to confusion with the new obfuscated names mappings (d -> c and c -> d). Naturally, these kinds of issues were unacceptable for the project and we immediately got to work on improving our update process to avoid issues of this nature in the future. While I think we can all agree with this decision, the unfortunate result is the delay we're currently facing since we're not yet done improving the process. The good news is, we're nearly done improving our update handling process and the wait will definitely be worth it come future updates.

Thank you for your patience and understanding!