Some exciting news this month, for the last few weeks we have been working hand in hand with Facebook™ to arrange an acquisition deal.

We started Spigot with the mission of creating a bleeding edge, optimized version of the Minecraft Server, to allow everyone to experience the joy of running a Minecraft Server without having unrealistically high end hardware. When Facebook first approached us about partnering, we were skeptical. As we learned more about the company and its vision and spoke with Mark, the partnership not only made sense, but became the clear and obvious path to furthering Spigot’s cause. Facebook was founded with the vision of making the world a more connected place. Minecraft is a medium that allows us to share experiences with others in ways that were never before possible.

Facebook is run in an open way that’s aligned with Spigot’s culture. Over the last decade, Mark and Facebook have been champions of open software and hardware, pushing the envelope of innovation for the entire tech industry. As Facebook has grown, they’ve continued to invest in efforts like with the Open Compute Project, their initiative that aims to drive innovation and reduce the cost of computing infrastructure across the industry. This is a team that’s used to making bold bets on the future.

In the end, I kept coming back to a question we always ask ourselves every day at Spigot: what’s best for the future of Spigot? Partnering with Mark and the Facebook team is a unique and powerful opportunity. The partnership accelerates our vision, allows us to execute on some of our most creative ideas and take risks that were otherwise impossible. Most importantly, it means a better Spigot with fewer compromises and an even faster development cycle.

Suffice it so say, social network integration will be but an obvious path for the future of Spigot, including the ability to link your Facebook account with your Spigot account, sharing your server’s daily moments on Facebook and...
There was a time based bug in spigot, this has been fixed in the latest builds.

Download: http://ci.md-5.net/job/Spigot/lastSuccessfulBuild/artifact/Spigot-Server/target/spigot.jar

Backports to older versions:

1.7.2: http://dl.thinkofdeath.co.uk/spigot/spigot-1.7.2-R0.4-SNAPSHOT.jar
Mirror: http://dl.gunfighterj.com/spigot-1.7.2-R0.4-SNAPSHOT.jar
Mirror: http://solderrepo.rainbowcode.net/spigot-1.7.2-R0.4-SNAPSHOT.jar

1.7.2 (Protocol Update): DMCA Removal

1.6.4: http://dl.thinkofdeath.co.uk/spigot/spigot-1.6.4-R2.1-SNAPSHOT.jar
Mirror: http://dl.gunfighterj.com/spigot-1.6.4-R2.1-SNAPSHOT.jar
Mirror: http://solderrepo.rainbowcode.net/spigot-1.6.4-R2.1-SNAPSHOT.jar

1.5.2: DMCA Removal
More info (by md_5)
Early Wednesday night (Australian time), we received our first reports of this issue occurring. A user's server had crashed with the now widely known stack trace (this user was from New Zealand, which becomes important later). The apparent cause of this was unknown, somehow the currentTick variable had become negative (how exactly can the server be currently at a negative tick!). Whilst I was not awake at the time, the issues became more and more apparent as clocks started to roll over. @Thinkofdeath quickly prepared a fix and the bug was resolved from our point of view. Unfortunately not everyone updates to every new build instantly, so the bug persisted, and eventually almost every server was affected as time went on.

The actual cause
This issue is a combination of two factors, the way in which CraftBukkit keeps track of the current tick (https://github.com/Bukkit/CraftBukkit/commit/c1a47990408eda27f985c79e7ad6fbeadc8fc338) and the way in which our enhanced tab ping code (which enables latency updates for the tab list) works: https://github.com/SpigotMC/Spigot/commit/fdfc07bd39322ece7c9700b46578e591115a34e5

We use this...
Good afternoon Spigot Community,

Its been nearly a month since we last caught up! I’d like to take this opportunity to update you on a few things that have been happening within the community lately. As I’m sure you have all noticed by now, we are running the latest version of XenForo, featuring a shiny new skin by @Audentio. I’d like to take this time to thank all of our wonderful supporters who donated to make this theme possible! I am sure it will serve us well into the future and continue to be our own special splash of uniqueness. If you do encounter any issues with it, please do let us know in the feedback section. The forums as a whole have also continued to grow immensely these past few weeks, with a large increase in both active users and content generated. I’d especially like to thank the developers who have taken the time to upload and maintain their resources in the resources section, it is great to see a swathe of Bungee, Bukkit and Spigot plugins up for download.

With all this growth, there have also been some growing pains, especially within the services and recruitment section. We would like to take this opportunity to remind you of the rules and general decency which we expect all members of the community to adhere to, regardless of their position anywhere else; you are not exempt from the rules just because you own a 1500 player server or hold some other high ranking position within the Minecraft community. Before I go into specific detail about a couple of rules, I would like to draw to your attention this post made earlier last week by cupcake, one of the administrators of reddit:

Tomorrow we will be upgrading the forums to XenForo version 1.2 as well as implementing our new forum theme and ensuring that all our plugins and features are up to date. Assuming no last minute issues we are planning to perform this upgrade in the timeslot mentioned below.

Start Times:
UTC+11 (AEDT, Melbourne): Monday, 20 January 2014 at 4:00:00 PM
UTC+0 (UTC, London): Monday, 20 January 2014 at 5:00:00 AM
UTC-5 (EST, New York): Midnight between Sunday, 19 January 2014 and Monday, 20 January 2014
UTC-8 (PST, Los Angeles): Sunday, 19 January 2014 at 9:00:00 PM

Maximum Duration: 4 hours

Estimated Impact:
1 hour full outage - forums will not be accessible during this time
3 hours sporadic outage - forums may be slightly broken or not load for some users during this time.
Following days - there may be some bugs present, please report this to the feedback section and we will look into them ASAP.

Thanks for your support, and it will be great to finally get our brand new custom theme from Audentio launched.
~Spigot Team
As most of you would have gathered by now, we do not often promote recommended builds of our projects. In general we expect all builds to be equally as stable, and by having a constantly rolling release, it ensures that no one is left behind. Over the last year there have been a few times that we released recommended builds of Spigot and Bungee. These recommended builds occur immediately preceding points where we feel that instability, or an otherwise poorer user experience will occur. Examples of these events have included the BungeeCord API, updating Spigot to use a patch based system, and updating both of these programs to use a new IO backend based on Netty. Today I would like to announce that the current Bungee build, #788, has been marked as recommended.

Our coming Bungee plans have been Inspired by the way large, long running programs (such as IRCDs) are broken up into a core feature set followed by modules containing specific features and commands. The first port of call for doing this will be making each command its own module, downloaded and updated automatically from Jenkins. The biggest benefit of this is that internal Bungee commands can be enabled/disabled at will, and we can also add more functionality which wouldn’t otherwise be a part of BungeeCord, such as MySQL reconnect location saving.

Rewriting these commands to be their own modules also gives us the opportunity to clean up their output. I am no designer, and this is evident through the hodge-podge of colours and layouts used within the BungeeCord commands and message outputs. Just like all Essentials commands are standardised in terms of arguments and colour scheme, we wish to do the same for Bungee, ensuring that users have a consistent and easy experience across all servers which they join. If you wish to help out redesigning the existing commands, as well as the upcoming new commands, please express your interest in the form below. A GitHub account is required to take part in this...