Yesterday marked the fourth anniversary of these forums.

We've come a long way in those last four years (as I write this there are over 1000 people browsing this site), and I'd like to thank everyone from server owners, to developers, to players, to staff, who have supported us throughout this time - especially those who have been around since the very beginning.

See you in another four years,
Long Live Spigot!

[email protected]_MC

Our software for Minecraft 1.11 has been released for general usage. For a brief summary of API changes, you should please see the draft API thread. For server owners, you should please note that the packaged SQLite version has been upgraded from 3.7.x to 3.15.x. This means (like your worlds), your databases may also not be backwards compatible if you downgrade - so please back them up. It should also be noted that the current jar releases have an expiry of 3 days ± 1 day, so you will be required to update them frequently to ensure you have the latest and greatest.

It is also a good time to point out that when seeking support from us or the community, the only supported server versions are recent CraftBukkit & Spigot 1.10.2 / 1.11 versions. Any other version puts you at risk of already fixed bugs, and exploits. Additionally as per the, the server software is open source and we welcome good quality code contributions, especially during this busy time.

If you are reporting a bug to JIRA, please make sure that you have compared the results between Vanilla, CraftBukkit & Spigot, and also the 1.10 versions before reporting - this speeds up the process for us immensely.

I’d also like to personally thank the testers on their help on the SpigotCraft server, especially @cindy_k, @ScruffyRules & @ssamjh - we’ve managed to fix a heap of issues including several crashes and duplications, which should make this one of the most stable releases yet.

In order to get 1.11, simply run the latest BuildTools with the required arguments. 1.11 will become the default version when we are confident that most bugs are ironed out.
Code (Text):
java -jar BuildTools.jar --rev 1.11
If you haven't used...

The draft Bukkit API for 1.11 has been published. You can review the changes, and if desired compile your plugin against it to be sure that it will be ready for 1.11. Changes of note include:
  • Removal of assorted deprecations - especially classes and event constructors. These removals have been deprecated since 1.7 and have replacements implemented.
  • Refactoring of Entity classes: Guardian, Horse, Skeleton, Zombie. These entities are special in that they have different variants. In previous Minecraft versions these variants were all the same actual entity, however in 1.11 they are not. We have tried to keep the implementation as compatible as possible with old plugins, but some differences are irreconcilable and plugins will need to be updated. Expect all deprecated methods to be removed in 1.12!
    • We’ve made some last minute changes to the Horse hierarchy in particular. It’s slightly less compatible than before, but more correct in terms of matching the implementation and allowing for future expansion. Stuff like LlamaInventory would not be able to work without these changes.
  • Addition of new Sounds, Statistics, Particles & Materials. It is interesting to note that the different colours of Shulker Boxes are all their own Material - this is corresponding with the way it has been done by Mojang.
  • Remapping EntityType names to Mojang names. This shouldn’t be an issue since they have already been deprecated for being magic values, but EntityType string names now correspond exactly with the ones used by Mojang for consistency. Enum names are still the same as before if you wish to implement conversion in your plugin.
  • For NMS Developers: We don’t normally do release notes here, but there is a change that I must stress greatly. net.minecraft.server.ItemStack may no...
Today Mojang announced final details of Minecraft 1.11. In particular, Minecraft 1.11 Pre-Release 1 has been released, and the final version is scheduled for Monday the 14th of November. Accordingly we must decide on our own gameplan and release schedule, which is anticipated to be as follows:

Wednesday 9th

  • No more changes to any SpigotMC repositories.
Monday 14th
  • BungeeCord support for 1.11 added.
  • Mojang releases Minecraft 1.11.
Tuesday 15th
  • Draft Bukkit 1.11 API released.
Wednesday 16th
  • Test servers for Spigot 1.11 go up.
Saturday 19th | Sunday 20th
  • Release of Bukkit, CraftBukkit & Spigot 1.11.
Subtract one day (more or less) if you’re American.

Now I can already anticipate the question “But md_5, wasn’t Spigot 1.9 / 1.10 released just after Vanilla? Why not is it not the same this time around?”. The answer to this is as follows: SpigotMC is a gigantic software community / project with a very small development team. Accordingly releases have to be made in such a way which ensures the best possible product for the users (that’s you guys). In planning out this roadmap, we have taken many things into account, including, but not limited to (in order of relevance):
  1. Personal Reasons - Staff Availability: A new release takes many many hours of work, both beforehand, and also immediately afterwards. Sometimes other unavoidable things come up which limit our ability to put in the time beforehand, and also prevent us from having a contiguous space of free time afterwards. This is one of those times.
  2. Previous Releases - Quality: Whilst I won’t disagree that the 1.9 / 1.10 releases were fantastic to get out with the speed they did; both of them had several major flaws initially - Magma Block, Elytra &...
All those attending MINECON,

We are going to be having a casual dinner at the California Pizza Kitchen tomorrow night. It's a short walk from the convention centre and reasonably priced (expect about $30 for pizza, dessert and drink). It's not a formal event so you will need to handle the bill for your respective party. Numbers are quite limited so please see us IN PERSON tomorrow to confirm your attendance.

Please follow us @spigot_mc on Twitter for all further information.

See you soon,
~Spigot Team