Edit (9 December): 1.18 is now the default version. Edit: 1.18 release is now available. Dear All As we mark the 9-year anniversary of SpigotMC.org, it is my pleasure to announce that development/preview builds of Spigot for Minecraft 1.18 are now available. Owing to the shorter interval between 1.17 and 1.18 this is a smaller update than previous major releases. There are however still some significant changes, particularly around world generation and biomes, so some initial caution is advised. Plugin Updates With the exception of plugins referencing removed biomes/particles and changes to third-party libraries (especially MySQL), there are no breakages expected. As a server owner, if a plugin is breaking on Minecraft updates, you should be encouraging developers to code their plugin in a way that it does not break (read: use the API). Doing this once is much more efficient than depending on an update every release. As a developer you should use the API wherever possible — a stable API is what distinguishes plugins from mods. If you cannot use the API, then you should contribute one, or at least open a feature request stating the API desired and why you need it. This will prevent you needing to update your plugin each release and will cumulatively save server owners and the community thousands of hours each year. You should consider it your duty to the community to do this. Java Version Mojang has decided to make Minecraft 1.18 require Java 17 or later. You can install this from a third party such as Azul Zulu or your Linux package manager. Please note that the --illegal-access=permit workaround is no longer possible on this version. Please also note that current versions of Java 17 have a bug which may affect users on single-core systems. If you have such a system consider adding -Djava.util.concurrent.ForkJoinPool.common.parallelism=1 as a Java argument. Backups Please make sure you have recent and tested backups for your server before upgrading. As always it is not possible to downgrade your server to an earlier version. This is especially important for this release due to the permanent alterations to older worlds. World Upgrading Although upgrades from between any two version pairs are technically possible, it is recommended that all upgrades are conducted from 1.17.x. This means that you should first upgrade your world completely on 1.17.x using the --forceUpgrade server argument, and then do the same on 1.18. 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.17.1 versions before reporting — this speeds up the process for us immensely and ensures more bugs get fixed more quickly. Please report bugs, or issues you think might be bugs, to JIRA and not in this thread, Discord, or any place other than JIRA. We prefer good quality but uncertain reports over no reports at all. Developers Please see the below post(s). Downloading / Installing In order to get 1.18, simply run the latest BuildTools. Please make sure both your BuildTools and Java versions are up to date. There may be mandatory BuildTools updates throughout the 1.18 release cycle, so it is good practice to ensure that you are always using the latest version. You can download the latest BuildTools from this link. Code (Text): java -jar BuildTools.jar If you haven't used BuildTools to create a server jar yet, it is suggested you first read the 1.8 announcement and the BuildTools Wiki. BungeeCord is available in the usual location: https://ci.md-5.net/job/BungeeCord/ Closing Notes Each release represents the culmination of hundreds of hours of effort, so if SpigotMC has helped you in any way, shape, or form we encourage you to leave a donation, contribution, or nice message. If nothing else, at least please make sure that any bug reports you may open are polite, clear, specific, and have been tested thoroughly both without plugins and on Vanilla. Enjoy, ~Spigot Team PS: Join our Discord.