Dear excited players,
Despite our excitement earlier this year with Minecraft 1.14 we're still on version 1.13.2, and without going into details: It's because of the pretty serious bugs that remained in 1.14.
But we aren't giving up hope, and we've invested our time and money yet again to prepare for the next upgrade option: 1.15
Today's not that day. Sorry. What will happen today: Mojang releases Minecraft Vanilla 1.15.0 to Java players.
What we have done so far: Reviewed snapshots, pre-releases, updated and upvoted 1.14 and 1.15 bug reports on MOJIRA that are in the way of us upgrading. And we've increased the system memory to 64gb to help speed up world conversions using ramdisks and other tricks.
What we've found is that we're confident to conclude that 1.14 is not worth the upgrade, and that 1.15 is potentially worth the upgrade. A lot of our concerns have been addressed in 1.15.
And yes, early 2020 the Nether Update might be right around the corner, but we still want to upgrade to 1.15 before going to 1.16 and 1.17, etc.
<insert huge but here> BUT, we do what we can do. And we care about you as a player. We won't RESET any perm-worlds, and we are not interested in you losing your items and builds, or your inventories. And this means we are going to spend a lot of our free time trying and testing and running 1.15 upgrades, converts, patches, and all sorts of stuff to try and make that happen.
And if 1.15 has corruption issues, chunks disappearing, items disappearing from armor stands and item frames, and weird stuff like that: We will just wait for 1.15.1 or 1.15.2, .. before trying again.
So what's next?
First, we are going to play around with Spigot 1.13.2 to Vanilla 1.15.0's final version and see what our first impressions are and learn major concerns. While internally prepping our plugins and resources and figuring out what we want to convert with, and what stuff we put on hold for a later date.
Then, we wait for Spigot and Paper to upgrade to a stable enough release of 1.15.0, and do all the testing all over again. While keeping an eye on all these plugins and features, etc. that we believe we should have when we convert. Guaranteeing that your fireplace isn't suddenly taking down your build. Or that your armor stands aren't suddenly all at level 300 or nonsense like that.
When we have a stable core engine, with stable core plugins, and we have converted from 1.13.2 to 1.15.0 (or .1) and are confident after some internal beta testing we can publicly test it. Then we will run it live for about a week. This is our 'buffer' period. If nobody comes and reports issues with their build areas and stuff, then we will keep what we have and more forward. If there's a reason to rollback, we will do so as soon as possible.
SO MUCH TEXT: I AM LAZY
I am sorry you're lazy, we're a community, I put multiple hours per day into this community to make it fun for you all. I think reading for 5 minutes in return to let you enjoy 1.15 as soon as we can is the least I can ask. Oh, and to come online to help test.
Summery:
Mojang has to release Vanilla 1.15 for Java: DONE
SpigotMC has to release Spigot 1.15 for Java: Pre-X is out internally, we're waiting for a download to become available (I suspect it won't be stable, and is considered a dev build)
Spigot Plugin Authors have to upgrade their plugins to the new API so it works with Spigot 1.15 releases.
When the above conditions are done, and we're done testing: We will do a public test that you can join.
Again, if it all fails, and the CPU runs at 100% all the time, and nobody can play because the TPS is dropping to 15 or lower every hour etc .. We're canning the idea of upgrading and will stick to 1.13.2
As with every grace period between versions, as soon as ViaVersion supports 1.14.4 and 1.15.0 clients to connect to 1.13.2 servers, we will install it and help everybody play a little easier. We strongly suggestion to use 1.13.2 client to connect to 1.13.2 server.
Despite our excitement earlier this year with Minecraft 1.14 we're still on version 1.13.2, and without going into details: It's because of the pretty serious bugs that remained in 1.14.
But we aren't giving up hope, and we've invested our time and money yet again to prepare for the next upgrade option: 1.15
Today's not that day. Sorry. What will happen today: Mojang releases Minecraft Vanilla 1.15.0 to Java players.
What we have done so far: Reviewed snapshots, pre-releases, updated and upvoted 1.14 and 1.15 bug reports on MOJIRA that are in the way of us upgrading. And we've increased the system memory to 64gb to help speed up world conversions using ramdisks and other tricks.
What we've found is that we're confident to conclude that 1.14 is not worth the upgrade, and that 1.15 is potentially worth the upgrade. A lot of our concerns have been addressed in 1.15.
And yes, early 2020 the Nether Update might be right around the corner, but we still want to upgrade to 1.15 before going to 1.16 and 1.17, etc.
<insert huge but here> BUT, we do what we can do. And we care about you as a player. We won't RESET any perm-worlds, and we are not interested in you losing your items and builds, or your inventories. And this means we are going to spend a lot of our free time trying and testing and running 1.15 upgrades, converts, patches, and all sorts of stuff to try and make that happen.
And if 1.15 has corruption issues, chunks disappearing, items disappearing from armor stands and item frames, and weird stuff like that: We will just wait for 1.15.1 or 1.15.2, .. before trying again.
So what's next?
First, we are going to play around with Spigot 1.13.2 to Vanilla 1.15.0's final version and see what our first impressions are and learn major concerns. While internally prepping our plugins and resources and figuring out what we want to convert with, and what stuff we put on hold for a later date.
Then, we wait for Spigot and Paper to upgrade to a stable enough release of 1.15.0, and do all the testing all over again. While keeping an eye on all these plugins and features, etc. that we believe we should have when we convert. Guaranteeing that your fireplace isn't suddenly taking down your build. Or that your armor stands aren't suddenly all at level 300 or nonsense like that.
When we have a stable core engine, with stable core plugins, and we have converted from 1.13.2 to 1.15.0 (or .1) and are confident after some internal beta testing we can publicly test it. Then we will run it live for about a week. This is our 'buffer' period. If nobody comes and reports issues with their build areas and stuff, then we will keep what we have and more forward. If there's a reason to rollback, we will do so as soon as possible.
SO MUCH TEXT: I AM LAZY
I am sorry you're lazy, we're a community, I put multiple hours per day into this community to make it fun for you all. I think reading for 5 minutes in return to let you enjoy 1.15 as soon as we can is the least I can ask. Oh, and to come online to help test.
Summery:
Mojang has to release Vanilla 1.15 for Java: DONE
SpigotMC has to release Spigot 1.15 for Java: Pre-X is out internally, we're waiting for a download to become available (I suspect it won't be stable, and is considered a dev build)
Spigot Plugin Authors have to upgrade their plugins to the new API so it works with Spigot 1.15 releases.
When the above conditions are done, and we're done testing: We will do a public test that you can join.
Again, if it all fails, and the CPU runs at 100% all the time, and nobody can play because the TPS is dropping to 15 or lower every hour etc .. We're canning the idea of upgrading and will stick to 1.13.2
As with every grace period between versions, as soon as ViaVersion supports 1.14.4 and 1.15.0 clients to connect to 1.13.2 servers, we will install it and help everybody play a little easier. We strongly suggestion to use 1.13.2 client to connect to 1.13.2 server.
