Please make sure both your BuildTools and Java versions are up to date. In order to get 1.17.1, simply run the latest BuildTools with the required arguments. 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. Closing NotesĮach 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. We ask you to please keep all this in mind in all your interactions over the coming weeks, and thank those that are already doing so. An update is a large commitment and unimaginably stressful period for everyone which lasts for weeks and severely disrupts normal life. Please remember that an update is not a singular thing that begins or ends with this post. I just wanted to draw attention to that post again, first to say thank you for the many kind messages then (they really mean a lot), and secondly to say thank you for the improvements in behaviour this time round. Re: Expectations & EntitlementĪlmost a year ago I wrote in the 1.16 release thread about how disappointed we were in the attitude displayed by many users. So please, if for whatever reason you are distributing Spigot, please ensure it is kept up to date. It is detrimental to users of those builds who experience bugs and crashes it is detrimental to plugin developers who cannot take advantage of new API and it is detrimental to us who have to deal with the consequences. This is detrimental to the entire community. Too often we see users running the first build of Spigot for a particular Minecraft version when it is dozens-hundreds of builds and several months out of date. Whilst we do not and cannot condone Spigot jars other than those officially sourced via BuildTools, this is a plea to those who do distribute jars to please ensure that they are kept up to date. Please report bugs, or issues you think might be bugs, to JIRA and not in this thread. 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.16.5 versions before reporting - this speeds up the process for us immensely during this stressful time. This means that you should first upgrade your world completely on 1.16.x using the -forceUpgrade server argument, and then do the same on 1.17. UpgradingĪlthough upgrades from between any two version pairs are technically possible, it is recommended that all upgrades are conducted from 1.16.x. As always it is not possible to downgrade your server to an earlier version. Please make sure you have recent and tested backups for your server before upgrading. You also cannot remove the experimental datapack once it has been added to a world. There is every chance a world created with the experimental datapack will not be able to be upgraded to 1.18 when it is released. You are welcome to test them, report Spigot bugs, and contribute API, but be cautious and wary of bugs and the potential for future incompatible changes. Although most of these features are still accessible in 1.17 through the use of either the experimental datapack or commands, and Spigot provides APIs for them, it must be remembered that these features are experimental/disabled for a reason. Mojang has delayed many features, including extended world heights, generation changes, and certain blocks/items to Minecraft 1.18. Please note however that this is a temporary workaround and might not work in future Java versions. If you have problems with plugins after updating Java you may be able to temporarily work around this by adding -illegal-access=permit straight after java in your command line. If you are using a shared host you should contact your host for instructions on how to do this, otherwise if you are hosting yourself you can check your java version with java -version. your Java version is incompatible and you will need to upgrade. This version of Minecraft requires at least Java 16. If you see an error message that looks similar to Unsupported Java detected (55.0). You may therefore have to manually install it from a third party such as Azul Zulu. As this is not an LTS version, it is not available by default in the repositories of some popular Linux distributions. Mojang has decided to make Minecraft 1.17 require Java 16 or later. Although this is a moderately sized update overall there are some major changes and very important points to note, so please read the following carefully. We are pleased to announce the first builds of Spigot for Minecraft 1.17 are now available. Update 6 July 2021: We have updated to 1.17.1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |