- Joined
- Jan 1, 2001
- Messages
- 60,191
Dear excited players,
Not long after the release of 1.15 and us upgrading to it, we've by now enjoyed it for about six plus months. Not long after the release, Mojang let us know there's a Nether Update coming, (and a combat update is being worked on, and a Mountain update was voted on by the community, etc., and we're still all begging for a cave update right?)
Minecraft version 1.16.x is the Nether Update.
We here at 1MoreBlock.com have been doing private and public live-streams of playing creative, survival, hardcore, events, and exploring-features, bug-hunting, etc.
Testing and testing
Internally we've been testing the snapshot and pre-releases through Mojang's provided server.jar file. And so far as performance wise what we can expect should be on-par with 1.15.2.
Heads-up!
This forum thread is to give everybody a heads-up that Mojang is working on 1.16, that we're looking into our options to upgrade 1MoreBlock.com (and network) from 1.15.2 to 1.16.x at some point this year. And that if you have resources in any temporary worlds that you should remove them in time.
Temporary Worlds
1MB has a couple of temporary worlds, these are our resource worlds. For example: /nether, /end, and /mine.
If you have a temporary base here, or grinders with chests, etc. please collect your items to avoid loss.
Not too long ago we've announced this on Discord, today on the forums, and soon we will have do so in-game as well. Making sure nobody can miss this heads-up. Because lost items will not get restored.
Permanent Worlds
1MB has a few permanent worlds, these are our build and survival worlds. For example: /spawn, /general, /legacy, /wild, etc.
If you have a base here, grinders, or various homes. Do not worry, we will keep these worlds (we never reset perm-worlds).
We will convert and upgrade existing worlds to 1.16.x.
Upgrading software.
We are using the switch to 1.16 as an opportunity to upgrade our internal tools from 1MB 2.7.3 to 1MB 2.8.x, this will take a bit of time. We might also consider converting our Minecraft engine, this will also take a bit of time.
To clarify, we are depending on Mojang to release 1.16 as a stable and working version that we can upgrade from, and then depend on (Craft)Bukkit/Spigot to release a (stable) and working version that we can test our worlds on, and our plugins. We then depend on the authors of these plugins to update their resources to support 1.16 properly. This requires time to wait for, to test with, to wait for bug fixes, etc.
How long it takes to update our software depends on a handful of things, and can take from days to months. Please have as much patience as we're trying to have.
What we have done so far
We have been keeping an eye on the specifics of the snapshots and pre-releases, we have been trying to speak to developers, server owners, and Mojang staff to learn (and raise concerns). We have also been internally testing individual step-upgrades (one world, multiple worlds, one feature, multiple features, one world with one feature, multiple.. etc)
We've increased our system memory and storage features to prepare for the increase in traffic, storage, and performance required (sigh, this wasn't cheap, thank you for your donations btw, if you want to help). We now have 64gb RAM available (yay ram-disk) and an array of nvme/sata3 SSD disks for storage and backups. We have been preparing developer setups, testing environments, and discussing specifics of our rules and policies for the rest of the year. Any bugs we've found we've reported to Mojira.
Huge but here!
<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.16 upgrades, converts, patches, and all sorts of stuff to try and make that happen.
And if 1.16 has corruption issues, chunks disappearing, items disappearing from armor stands and item frames, and weird stuff like that: We will just wait for 1.16.1, or 1.16.2, or 1.17.x.. before trying again.
It's also possible that due to disappearing developers some features we currently enjoy do not get an upgrade (just yet) and we go live without it.
Rules
We will also take this opportunity to adjust our Forum/Discord/Minecraft rules again. We will review them individually and try to make things a bit more clear. We want to make a safe and friendly space for people to enjoy their time with others, building things while surviving, etc.
So what's next?
Test internally, prepare for an upgrade, and hope for the best.
When we have a stable core engine, with stable core plugins, and we have converted from 1.15.2 to 1.16.1 (or .2) 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 or grace' 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. If players come online and test everything and find issues, we roll back to 1.15.2 and try fixing the issues reported and create a new buffer-period upgrade.
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.16 as soon as we can is the least I can ask. Oh, and to come online to help test. And this way you get answers to all the questions I get. Thank you for understanding and your time as well. wubya
Summery:
Mojang has to release Vanilla 1.16 for Java: DONE!? (They already released an update as well 1.16.1)
SpigotMC has to release Spigot 1.16.1 for Java: md_5 has it internally, we're waiting for a download to become available.
Spigot Plugin Authors have to upgrade their plugins to the new API so it works with Spigot 1.16 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.15.2
As with every grace period between versions, as soon as ViaVersion supports 1.15.2 and 1.16 clients to connect to 1.16 servers, we will install it and help everybody play a little easier. We strongly suggestion to use 1.16 client to connect to 1.16 server. And 1.15.2 client to connect to 1.15.2 server.
Final words
If you have any questions, any concerns, this is the time to ask them. Post them to this thread please and I will do my best to answer/explain.
Thank you for playing on 1MoreBlock.com, some of your already for nearly a decade!
Not long after the release of 1.15 and us upgrading to it, we've by now enjoyed it for about six plus months. Not long after the release, Mojang let us know there's a Nether Update coming, (and a combat update is being worked on, and a Mountain update was voted on by the community, etc., and we're still all begging for a cave update right?)
Minecraft version 1.16.x is the Nether Update.
We here at 1MoreBlock.com have been doing private and public live-streams of playing creative, survival, hardcore, events, and exploring-features, bug-hunting, etc.
Testing and testing
Internally we've been testing the snapshot and pre-releases through Mojang's provided server.jar file. And so far as performance wise what we can expect should be on-par with 1.15.2.
Heads-up!
This forum thread is to give everybody a heads-up that Mojang is working on 1.16, that we're looking into our options to upgrade 1MoreBlock.com (and network) from 1.15.2 to 1.16.x at some point this year. And that if you have resources in any temporary worlds that you should remove them in time.
Temporary Worlds
1MB has a couple of temporary worlds, these are our resource worlds. For example: /nether, /end, and /mine.
If you have a temporary base here, or grinders with chests, etc. please collect your items to avoid loss.
Not too long ago we've announced this on Discord, today on the forums, and soon we will have do so in-game as well. Making sure nobody can miss this heads-up. Because lost items will not get restored.
Permanent Worlds
1MB has a few permanent worlds, these are our build and survival worlds. For example: /spawn, /general, /legacy, /wild, etc.
If you have a base here, grinders, or various homes. Do not worry, we will keep these worlds (we never reset perm-worlds).
We will convert and upgrade existing worlds to 1.16.x.
Upgrading software.
We are using the switch to 1.16 as an opportunity to upgrade our internal tools from 1MB 2.7.3 to 1MB 2.8.x, this will take a bit of time. We might also consider converting our Minecraft engine, this will also take a bit of time.
To clarify, we are depending on Mojang to release 1.16 as a stable and working version that we can upgrade from, and then depend on (Craft)Bukkit/Spigot to release a (stable) and working version that we can test our worlds on, and our plugins. We then depend on the authors of these plugins to update their resources to support 1.16 properly. This requires time to wait for, to test with, to wait for bug fixes, etc.
How long it takes to update our software depends on a handful of things, and can take from days to months. Please have as much patience as we're trying to have.
What we have done so far
We have been keeping an eye on the specifics of the snapshots and pre-releases, we have been trying to speak to developers, server owners, and Mojang staff to learn (and raise concerns). We have also been internally testing individual step-upgrades (one world, multiple worlds, one feature, multiple features, one world with one feature, multiple.. etc)
We've increased our system memory and storage features to prepare for the increase in traffic, storage, and performance required (sigh, this wasn't cheap, thank you for your donations btw, if you want to help). We now have 64gb RAM available (yay ram-disk) and an array of nvme/sata3 SSD disks for storage and backups. We have been preparing developer setups, testing environments, and discussing specifics of our rules and policies for the rest of the year. Any bugs we've found we've reported to Mojira.
Huge but here!
<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.16 upgrades, converts, patches, and all sorts of stuff to try and make that happen.
And if 1.16 has corruption issues, chunks disappearing, items disappearing from armor stands and item frames, and weird stuff like that: We will just wait for 1.16.1, or 1.16.2, or 1.17.x.. before trying again.
It's also possible that due to disappearing developers some features we currently enjoy do not get an upgrade (just yet) and we go live without it.
Rules
We will also take this opportunity to adjust our Forum/Discord/Minecraft rules again. We will review them individually and try to make things a bit more clear. We want to make a safe and friendly space for people to enjoy their time with others, building things while surviving, etc.
So what's next?
Test internally, prepare for an upgrade, and hope for the best.
When we have a stable core engine, with stable core plugins, and we have converted from 1.15.2 to 1.16.1 (or .2) 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 or grace' 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. If players come online and test everything and find issues, we roll back to 1.15.2 and try fixing the issues reported and create a new buffer-period upgrade.
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.16 as soon as we can is the least I can ask. Oh, and to come online to help test. And this way you get answers to all the questions I get. Thank you for understanding and your time as well. wubya
Summery:
Mojang has to release Vanilla 1.16 for Java: DONE!? (They already released an update as well 1.16.1)
SpigotMC has to release Spigot 1.16.1 for Java: md_5 has it internally, we're waiting for a download to become available.
Spigot Plugin Authors have to upgrade their plugins to the new API so it works with Spigot 1.16 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.15.2
As with every grace period between versions, as soon as ViaVersion supports 1.15.2 and 1.16 clients to connect to 1.16 servers, we will install it and help everybody play a little easier. We strongly suggestion to use 1.16 client to connect to 1.16 server. And 1.15.2 client to connect to 1.15.2 server.
Final words
If you have any questions, any concerns, this is the time to ask them. Post them to this thread please and I will do my best to answer/explain.
Thank you for playing on 1MoreBlock.com, some of your already for nearly a decade!
Last edited: