Edit: Several candidates have been selected and are hard at work with their new role. Thanks to all those that applied and remember that the wiki is still free to edit.

Hi all!

We're currently looking for a small team of helpers to join the wiki team and assist us with overhauling the SpigotMC Wiki.
Both the Spigot and BungeeCord project have grown tremendously in terms of features since the wiki was first written and thus with this is the need for better documentation that is both highly accurate and up to date.

The ideal candidates for the position must have very good English, a professional attitude, attention to detail as well as sound knowledge of the associated projects.

As a member of the wiki team you will be expected to contribute on a regular basis, both maintaining existing articles and creating new ones, as well as ensure that the wiki is not vandalised or misinformative; in return you will receive a shiny wiki badge as well as being responsible for the wiki content.

If you are interested in this position, please send an email to [email protected] preferably attaching existing content that you have worked on whether it be here or elsewhere and a small paragraph as to why you should be a wiki team member.

Just to add, everyone is free to contribute to the wiki, however our goal here is to recruit several passionate volunteers with a focus on producing content. As a reminder, when editing articles you will often find a discussion thread linked and therefore we ask that you use it to keep other members informed of proposed changes or suggestions. You can also discuss within the #wiki channel on our IRC network.

Looking forward to your applications,

The upgrade has been completed, there may be a few issues which we haven't seen yet, please reply to this thread if you experience any.

Known issues:
In ~two days time we will be upgrading the forums to XenForo 1.3.2 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): Sunday, June 8, 2014 at 3:00:00 PM
UTC: Sunday, June 8, 2014 at 5:00:00 AM
EDT (-4): Sunday, June 8, 2014 at 1:00:00 AM
PDT (-7): Saturday, June 7, 2014 at 10:00:00 PM

It is estimated the initial downtime will be 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 that arise,

~Spigot Team
Hey guys,

Hope all is well - activity has been a bit sparse as of late due to the usual mid term lull and impending / in progress final exams (good luck to all of those involved). I thought I’d spice up the front page by bringing forth the following question to all within our community:

How best can we identify versions of Spigot, BungeeCord and potentially other projects?

In the near future we plan on completely revamping the way we distribute our projects (goodbye Jenkins, welcome super awesome easy-to-use and attractive custom site!). This little mini series of posts will focus on gaining input from the community with regards to how things should operate.

Naturally the most important thing about a download site is the downloads themselves, which begs the question, how can they be uniquely named and identified? Jenkins uses an ever increasing (monotonic) build number system. This is good as it gives an indication of the relative freshness of the build and allows easy version comparisons, however it’s also bad as it doesn’t allow much more than this. Additionally it makes it very hard to compare binaries generated from the same revisions. I believe there are two ways of addressing this issue:
  • Version builds based on their timestamp
  • Version builds based on their source code revisions
Comparing and finding a suitable variant of these two combinations will be the focus of discussion in this thread. I’ll kick start it by weighing up some pro’s and con’s of each of the options as well as providing my choice:

  • What format should we use? spigot-yyyymmdd-hhmmss seems like the only canonical choice (eg: spigot-20140524-213612.jar)
  • What about unix time? spigot-1400931609.jar, 5 digits shorter, comes in at only 10 digits rather than 15. Con: Not human readable.
  • Is a long file name really an issue?
  • Timezone? UTC makes sense.
  • Con: Quite long, multiple dashes involved.
  • Pro: Gives indication of...
I'd like to draw your attention to two things which we have added to the forums recently. One of these is two factor authentication with Google Authenticator, the other is premium resources.

For some users here, their Spigot account is quite a valuable thing as it is used for offering goods & services, releasing plugins used by thousands of users, and representing their server. We don't want to skimp on the security of these accounts, and as such we now have the option for all accounts to enable two factor authentication. This means that you will require a code from your mobile device each time you log in.

From your account menu, click the two factor authentication button:
Ensure that the use two factor authentication button is ticked, then save and click add new key:

Enter a name for your device, and follow the instructions listed to enable two factor authentication:
Now whenever you log in, you will be prompted to enter a code from one of your devices, enjoy the enhanced security!

Premium resources are an addition to the XenForo resource manager, coded specifically for SpigotMC. They enable you to create paid resources with barely any work on your end. Simply enter your PayPal email, cost and upload a file, everything else is handled automatically.
When choosing a category for your resource, you must place it in the premium category:

From here, simply create the resource as you normally would, making sure you enter the cost, currency and your PayPal email address:
Now, before anyone gets access to your resource downloads, they must send the cost of the resource to you via PayPal.

We hope you enjoy...
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...