Hey, its that time again, and I am quickly dropping a new recommended build so that you guys have a stable platform whilst we build out next changes.

Promoted Build: 485
Spigot Changes:
  • Enhanced timings command
  • Inbuilt anti xray
  • Fix for massive lightning storms
  • Half a dozen minor performance boosts
Bukkit Changes:
  • Entity portalling
In this next development phase, our primary goal will be the implementation of a new network engine based on Netty. This will be released very soon to our dev builds, we are just waiting for TagApi to become compatible without the use of ProtocolLib (which has already updated).
This new networking engine is a godsend as it reduces a huge amount of load on the server used for costly IO operations.

Thanks as always for supporting Spigot, we are pleased to announce that approximately 4% of CraftBukkit servers now run Spigot. A big shoutout for MCPC-Plus / Tekkit for choosing Spigot as the platform to build their server / modpack, keep spreading the word!

~Spigot Team
ATTN: Anyone using build 389 or above please upgrade to 396 or above, fixes crucial crash bug.

I know there was no announcement for 1.4.6, but you guys all seemed to find it pretty well :), but I would like to use this post to promote both builds 387 and 396 as our 'recommended builds'.
Build 387 is based on the same codebase you have seen in all prior builds, whilst 396 introduces fixes for two things which have plagued Spigot for a while:
  • Growth
  • Mob Spawning
Thanks a heap to Aikar for these fixes.

The Future
The other reason I am promoting these builds now is so that you can have a stable build to stick to for as long as need be. Tomorrow the mainline Spigot repo will be transformed into a patch based repository, enabling you to see exactly what changed each and every Spigot commit, and enabling us to apply small fixes to the Bukkit codebase to where necessary (no new API functionality is planned).
This change is expected to be messy and no doubt there will be some hiccups, but it is for the better.

A huge thanks to Aikar whom is assisting us with this process, normal Spigot builds will be resumed and announced ASAP.

I hope all of you and your communities had a great festive season / break, and together in 2013 we can help make Spigot even better!

md_5 & the Spigot team

PS: Inbuilt anti-xray is looking really efficient and nice, hope to have it up shortly after our patch migration is complete.
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....