The long awaited CraftBukkit recommended build is upon us, along with a swathe of other new announcements which I suggest you check over at the Bukkit forums.

The big points in this commit, especially for Spigot are:
  • Asynchronous chunk loading -> reduce toll chunk loading has on the server
  • Optimized tick loop -> perfect for GSPs, reduces idle load to nearly 0%
  • Nerfing of maps in item frames -> Only update once on chunk load, causes huge TPS increases
  • Chunk garbage collector -> remove chunks which have been left around for some reason, ensures RAM usage is consistent.
You can checkout the full Bukkit changelog here http://dl.bukkit.org/downloads/craftbukkit/view/01707_1.4.5-R1.0/

Important: As of this release, Spigot will be moving to a new patch based system. This means we can easily keep track of changes we apply to the source code, allowing for easy tracking of bugs, and ensuring a more stable server by only using select CraftBukkit commits. We will likely still have a branch with bleeding edge CraftBukkit commits for those of you who want it. Early 1.4.6 builds will still be applied with the old system.

Special thanks to ammar2 who was the driving force in implementing async chunkloading.

I don't know if this will be the last post from us before Christmas, but in any case, happy holidays to you all!

~Spigot Team
Channel: #spigot
Server: irc.esper.net
Link: http://www.spigotmc.org/pages/irc/

Thought I would take this opportunity in time to give our IRC channel a bit of a plug.
If you are not familiar with what IRC (internet relay chat), its basically retro Skype (text only chat), but for cool people. If you join us on #spigot, you can get immediate help and advice on any issues you may be having, general support about your server, or just stop to say hi and have a chat with other server admins.

Use the direct link if you want to say hi, you are welcome to stick around for as long as you like!

~Spigot Team
Hey everyone! I would like to make a post today which is not based on the Spigot project itself but rather an area that is lacking in both our new community as well as myself: attitude. It has been brought to my attention that my behavior, and the behavior of others, does not reflect too kindly on this project. There are a few things I would like to discuss; most importantly beginning with a very important and sincere apology.

I would like to apologize first and foremost for my own actions. There have been misdirected comments made by myself which were incorrect as well as looked to lay the blame elsewhere. Comments which inspired people who read them to take an attitude different to that which they may have taken otherwise, some of which were not even relevant to the context in which they were presented. I truly apologize for the lost time and effects caused as a result of these comments and the ramifications to those who read and acted upon them.

To you, the Spigot community, I would like to say thank you for the wonderful support you have continued to provide here while this project grows. This post serves to remind you all that once you are involved with Spigot, the way you behave does reflect on the project and on our team. Spigot is not an excuse or reason for anything and it should stay that way. We do not promote attacking other projects and decisions based on what you might think may happen here, and neither should you. We highly support and respect the work of others.

Now since it is pretty obvious to what the above is apologizing for, I would like to go out and address these issues, and why the reasoning is flawed, as well as why Spigot will not be reverting or altering what is a perfectly good commit. The commit I am referring to is “Refactor all OBC, libs, and NMS into versioned packages.”, and of course my previous discussion on breaking API changes. The paramount thing to remember is that all these changes occurred in development builds....
These changes only affect development builds. Spigot build 249 is based on the latest CraftBukkit Beta and as such is the build which should be used.
Plugins will update and these changes will be better for everyone in the long run.

Sorry guys, but I need to do this too keep myself sane, and to stop you from spamming the forums.
Over the last few builds there have been at least three breakages in the Bukkit API. These breakages are controlled completely by Bukkit, so there is nothing we can do about it. Your best defence is to update your plugins or downgrade to a build prior to the 1st of December 2012.

The first change which can be found at: https://github.com/Bukkit/Bukkit/commit/49690f9620b7ed1ed9769cec35d095a3cac33ab0
Details with the changing of the BlockFace / Direction enum. The fact that these directions, well point to the wrong directions, has been a common law feature pretty much since Bukkits inception. You may experience symptoms of this breakage if stuff is rotated oddly, or shop signs, and Lockette / Deadbolt locks do not function.
All plugins known to be affected by this breakage have updated.

The second change is affecting the most users, found at https://github.com/Bukkit/Bukkit/commit/e468a8b391336f292d3642ffa4c45b4600e91b64:
This change alters the return type of the EntityBlockChange event. Any plugin using this simply needs a recompile. There are only about 60 plugins which will be affected by this change.
You can be reasonably sure any block logging plugin will be broken, as well as any protection plugin (WorldGuard)
The error will look something like: Caused by: java.lang.NoSuchMethodError: org.bukkit.event.entity.EntityChangeBlockEvent.getEntity()Lorg/bukkit/entity/LivingEntity;

The third change: https://github.com/Bukkit/CraftBukkit/commit/8f12382e8efc8c39a919af9180dd884caf3720ff
Only affects plugins which...
UPDATE: Server is back!

At this point in time, the Jenkins server appears to be down.
The host is showing no issues on their status page, so at this time I am thinking a malicious attack of some sort (DDOS, although that seems odd on a Jenkins server).
Hopefully it will come back some time whilst I am sleeping, but I'll make enquiries just in case.