All,

A short while ago Mojang released Minecraft 1.16.2 and we have now also updated.
Although this is a 'minor' release insofar as it is 1.16.x, it does contain a reasonable amount of internal changes, so please be patient whilst we polish things up.

It has also come to our attention that a number of mirror sites have been advertising severely outdated builds of Spigot as the 'latest' version. This caused significant issues for many users when 1.16.1 launched as users were reporting critical bugs for weeks after they were fixed. Please ensure you use the /version command to check your server version before reporting any bugs. BuildTools is the only official source of Spigot builds.

In order to get 1.16.2, simply run the latest BuildTools with the required arguments. 1.16.2 will become the default version in the coming days/weeks.
Code (Text):
java -jar BuildTools.jar --rev 1.16.2
If you haven't used BuildTools to create a server jar yet, it is suggested you first read the 1.8 announcement and the additional BuildTools info thread.

BungeeCord is also updated and can be found on Jenkins.

Enjoy,
~md_5
Dear SpigotMC Community,

The first builds of our software for Minecraft 1.16.1 have now been released. Although this is a minor update for plugin developers it is a relatively large update overall. In particular multi-world support was rewritten several times relatively late in the snapshot cycle, so extra caution is recommended if your server has more than the three default worlds (world, world_nether, world_the_end). Although this now means that the Vanilla server (in theory) has (experimental) multi-world support, we have retained the existing Spigot structure and approach for various reasons. Accordingly, you should continue to use your existing plugins and folders for multi-world management and not the Vanilla system.

Upgrading
Although upgrades from between any two version pairs are technically possible, it is recommended that all upgrades are conducted from 1.15.2. This means that you should first upgrade your world completely on 1.15.2 using the --forceUpgrade server argument, and then do the same on 1.16.1.

Bug Reports
If you are reporting a bug to JIRA, please make sure that you read the guidelines and have compared the results between Vanilla & Spigot, and also the 1.15.2 versions before reporting — this speeds up the process for us immensely.

Developers
Please see below post.

Expectations & Entitlement
I'm not sure if the addition of a Discord server has caused this behaviour to become more visible or whether it is a new phenomenon within the community, but in either case I am writing this message to make both my stance and the stance of the rest of the SpigotMC Team clear. We love SpigotMC. We love Minecraft (yesterday was my nine year anniversary). We love that you're all excited for new releases. What we don't love is entitlement and demands — something we have seen a lot of in the last two days. SpigotMC is not our life. SpigotMC is not even our...
Despite all the bad news as of late, to mark the start of April I have some good news to share with you all: as of right now we are launching the official SpigotMC Discord™ Server. Although we will still be keeping IRC as a first-class option for those who prefer the community/experience there, Discord™ will be an additional place to hang out with the SpigotMC community and seek interactive help/support. We know that many of you are already avid Discord™ users so quite frankly you would be foolish to not join our server right away.


Of course with synchronous communication, especially when it is persistent, there are additional moderation challenges. I would therefore like to remind everyone who joins that they will be held to the same high standard as on these forums (if not higher). All the existing IRC and General rules (as well as bans) still apply, and we have also developed some additional guidelines to ensure a pleasant experience for all.
  • Please make use of the nickname feature to align with your Forums nickname.
  • Please keep help requests simple and consider whether the Forums are not more appropriate to resolving your issue.
    • Posting issues on the forums makes it easier for more people to see your issue, and also creates knowledge which is easily accessible in the future. If you need to share more than a few lines of code or you expect the answer to be longer than a few sentences, then the forums are probably a more appropriate venue.
    • Although we can sometimes help with plugins, often the best thing to do is contact the author in their resource discussion thread. This is because there are thousands of plugins and we do not know everything about them all....
If your recent experience has been anything like mine, it has probably been filled with a frenzy of COVID-19 news, toilet paper shortages, and an inbox full of companies promising to help you with their products in these uncertain times. I cannot communicate anything which governments and experts have not already, nor is it appropriate/necessary for me to let you know we still exist (not that I have anything to sell you). And no, you cannot have my toilet paper either. Instead I thought I might use this opportunity and platform to communicate a message which although not revolutionary is a far cry from almost everything else I have encountered recently. Those of you who have been with me since the beginning (nearly a decade ago!) might recall a predilection for long form content, and to either your disdain or delight this post marks a brief return to that: MD's soapbox if you will.

Although I have had the great pleasure of meeting hundreds of you in person, the reality is that most of us only know each other through our online interactions. The situation which we are all facing right now is not confined to, or indeed even a product of these interactions. As such in writing this post, I wanted to try and break through this virtual barrier that divides us and address you all at a level that, at least on this platform, is not the norm. In doing so I recalled the phrase ‘Remember the Human’. In another time and place this phrase might be one of chastise — a reminder to all be civil to each other — but today I instead use it thematically, as a guide for what I am to write next, and I hope as a guide to all of you dealing with this situation, whether online here or back in the ‘real world’.

On the Internet, nobody knows you're a dog.’ Whilst I must confess that I am not in fact a dog, the comic nevertheless again illustrates...
This is to advise that the rules regarding obfuscation have been changed. These changes have been extensively reviewed by staff and are aimed at reducing the instances of unnecessary obfuscation making it difficult for staff to perform their duties. All resources and resource updates posted after today must comply with the new rules or risk being removed. If you use an obfuscator which is not allowed by the rules and wish to gain an exemption you must contact us.

Rules: https://www.spigotmc.org/wiki/spigot-rules/
Premium Guidelines: https://www.spigotmc.org/threads/31667/

---------------------------------------

4.1.6: You are allowed to obfuscate your resources, however the decompiled code must be somewhat legible by staff and is subject to the following limitations:
  1. Free resources may only use basic name obfuscation (ie what Mojang does with Minecraft).
    1. This limits you to certain free publicly available obfuscators (eg Proguard, yGuard).
      1. See https://www.spigotmc.org/threads/420746/ for a complete list of approved obfuscators and settings.
    2. Do not use string obfuscation or anything that hides code flow.
    3. In exceptional circumstances exceptions to this rule may be granted.
  2. All resources must retain an unobfuscated package root and main class name.
    1. com.example.myplugin.MyPlugin is an acceptable main class name, com.example.myplugin.a, a.a.a.MyPlugin or a.a.a.a. are not.
    2. com.example.myplugin.a.a is an acceptable secondary class name, a.a.a.SecondaryClass or a.a.a.a are not.
  3. Obfuscation designed to crash inspection tools is not allowed.
  4. All parts of a class must be visible when decompiled and it must be clear what all parts of the code is supposed to do.
    1. Class encryption is not allowed. It does not add meaningful security anyway.
  5. Obfuscated class or member names should not be unnecessarily long or difficult to inspect....