On September 2nd 2014, Minecraft 1.8 was released to the general public. Since this date we have stated that our team will be updating Spigot to this version. Today, almost six weeks later, I am pleased to announce the first glimpse of where we’re at, what this process has entailed, and where we are headed.

Due to accusations and legal threats filed against both our source code and download repositories, we were unable to begin work as soon as we would have liked to; however after many weeks of advice, legal consultation, and your support, we have resolved to complete this Minecraft update as previously scheduled. This is an extremely complex and tedious process which takes a great deal of time; however it can be broken down into a series of about a half dozen steps.

As a point of interest, Minecraft 1.8 is one of the largest single updates ever made to the game, with 11 months spanning from the release of Minecraft 1.7 and numerous internal changes such as the much hyped “Block State” system as well as over 350 additional classes added.
  1. The first step in completing an update is to deobfuscate the Minecraft server jar. This is something which is aided through the use of a variety of public and private tools, however ultimately it boils down to painstaking, manual labour. Although some team members had begun dabbling with this process beforehand, official work on this started just over three weeks ago and it took about a week to finalize the first mappings draft. To give you an idea of how complex this is, the current mapping set which we are working with consists of around 4,700 unique entries, all reversed from obfuscated names such as aa.b(x, y, z, int, int) into usable namings.
    • As this is the first time we have completed such a task and other parties have all kept their tools quite close to their chest, we faced a variety of challenges in producing workable source code. In particular, we have begun a rewrite of SpecialSource into...
EDIT: Work has finished and everything looks great. If you notice any issues or oddities, please post them in the feedback section.

Tonight we plan to upgrade the forums to XenForo 1.4.1 along with our addons and custom style. Assuming no last minute issues we are planning to perform this upgrade in the timeslot mentioned below.

AEST (+11): Friday, September 19, 2014 at 7:30:00 PM
UTC: Friday, September 19, 2014 at 9:30:00 AM
EDT (-4): Friday, September 19, 2014 at 5:30:00 AM
PDT (-7): Friday, September 19, 2014 at 2:30:00 PM

It is estimated that this process will take 30 minutes and that things may look a little wonky for the next couple of hours as we clean up any issues that may arise.

Please let us know of any issues,

Thanks
~Spigot Team
Edit: I wish to make clear this is not the end for Spigot. We will keep on developing and we will keep on fighting. It is only a short matter of time before things will be sorted out. The Minecraft server community has not come this far over this many years to be killed by a single blow from a disgruntled developer.

It is with a heavy heart this morning that I announce that in response to the DMCA takedown notices issued by Wesley Wolfe (Wolvereness), a current [Craft]Bukkit developer, that we have removed downloads to Spigot from our public Jenkins build server located at http://ci.md-5.net/job/Spigot. Additionally access to the Spigot source code repository (formerly located at https://github.com/SpigotMC/) has been forcibly removed from GitHub following a similar DMCA takedown.

This decision is not one that has been made lightly, but is one which has been made based on a number of factors. Following extensive legal counsel and advice from our attorney we were presented with a number of options we could take, including issuing a series of DMCA counter notices which had been prepared. This morning an assembly of the extended Spigot team, including our forum moderators, developers and IRC staff took part in a vote to decide the appropriate course of action. I abstained from this vote, however the outcome was unanimous and we have decided not to issue this counter notice, and instead take down the allegedly infringing material. It is by taking these steps, we believe, that the Spigot project stands the best chance of continuing to operate long into the future.

Fighting a legal battle is all about risk, and no matter how solid we or our legal counsel believe our case to be, there is always the element of risk. A copyright lawsuit within the United States of America must be conducted within a Federal District Court, an activity which results in the potential for extreme risk and expense to all parties involved. A number of factors...
Normally a great deal of time and planning goes into posting front page notices, however this notice represents news which is currently breaking and as such we have had little time to review it. That being said we feel that making public our initial thoughts and intentions is far more beneficial than allowing speculation or other conclusions to be drawn. This is a brain dump of what has happened and what we intend to do, and is not indicative of anything else, nor should it be taken as gospel.

When I woke up just 30 minutes ago, I was alerted to the fact that downloads to CraftBukkit had been removed due to a DMCA request from former CraftBukkit developer Wesley Wolfe (Wolvereness). Upon scrolling through emails on my phone I found that approx 2:21AM (AEST) we received a similar DMCA report from the same user. It is attached below with personal information and contact details removed”
Reported URLs:
http://ci.md-5.net/job/Spigot/
http://ci.md-5.net/job/Spigot/lastS...Server/target/spigot-1.7.10-R0.1-SNAPSHOT.jar
http://ci.md-5.net/job/Spigot/lastSuccessfulBuild/artifact/Spigot-Server/target/spigot.jar
Original Work: Original content can be found at

https://github.com/Wolvereness/Bukkit-Bleeding/commits?author=Wolvereness
https://github.com/Wolvereness/Bukkit-Bleeding/commit/0a0fee8be25bf8a732abff2d66a89a64614b6327

and the appropriate license for previously mentioned content can be found at

https://github.com/Wolvereness/Bukk...e59275330f83b994e199c76f6abd41ee7/LICENCE.txt

The provided license requires the use of included or linking code to provide the original source under the GNU GPL license version 3, or any later version. An official notice has been sent to Mojang AB, whereas the Chief Operating Officer, Vu Bui, responded with the clear text:

> Mojang has not authorized the inclusion of any of its proprietary...
It’s been a while since anything new has graced the front page, so I thought we’d take this opportunity to liven it up and briefly discuss a few points.

RFC - Build Naming
Thanks to all those who participated in our previous discussion about build naming and distribution. We have collated all these comments and will be using them in the near future to help design and build our new distribution site. The first phase of actually building this site has been more or less completed by our designers, and we will be eager to start showing off the basic design to our donors once we receive it.

Wiki Team
Thanks to all of the wiki team who have been working hard on keeping the documentation up to date as well as adding new content. The addition of templates and other design tweaks have made a great improvement to accessibility and appearance - keep up the good work guys! Even if you are not an official wiki team member, you are still welcome to contribute and we encourage you to do so - check out the list of pages for stuff you can help improve.

Additional Staff Members
As many of you would have noticed by now, we have added @danjb2000 to our staff team as a “Junior Mod”. He will be spending the next few weeks getting to know all the ins and outs of being a staff member and hopefully we will eventually see him become a full fledged moderator. As always, please remember that everyone is still learning and sometimes people make mistakes, if you ever have any issues or complaints regarding any of our staff feel free to direct them to [email protected]. This transition to a Junior Moderator rank will be the way in which we select new forums staff from hereon in. As has always been the case, new staff members are selected on an as needed basis by us existing staff. Although there are no set requirements, the successful candidate will be an active and polite member...