- Joined
- Jan 1, 2001
- Messages
- 60,192
Dear excited players,
Wow, what bomb did Mojang drop on us in 2020 by letting us know there's a Cave & Cliffs update coming! And with the recent tweet by slicedlime that a pre-release should be out later today. I think it's fair to assume we should be getting ready.
Not only that, there's also a leaked tweet (now deleted) saying the migration from Mojang to Microsoft Accounts is basically set for this summer season. Before we get into the 1.17 information, let's jump on that MSA migration and tell you what you can do to prepare for that: Make sure you have an active and valid email on your Mojang account. And that you know your Mojang password. You will need both in order to start the migration process when the official Mojang launcher invites you to migrate. And be careful! There might be fake links, emails and websites out there trying to trick you into sharing your login details. Don't fall for those.
Okay, 1.17, and 1MoreBlock, what does that mean? Let's deep-dive into where we are now, what we expect and what that could mean for you the player. I know, it's a bit of a read, but I rather have it all in one spot than having to answer the same questions over and over.
Minecraft version 1.17.x is the Cave & Cliffs 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. of the available snapshot of 1.17. And boy, it's a big update. And not only that, but it's so big that Mojang has decided to keep the biomes / world changes as a separate release for later this year (I heard Christmas, let's hope they make it).
Testing and testing
Internally we've been testing the snapshot and will soon test the 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.16.5, but it's worth noting if you have a somewhat dated system, or only integrated graphics. You might notice a bit of suffering in the performance. There's a lot more, more code, more chunks, more things, items, entities, blocks, etc. And they all contribute to your system having to deal with it.
We invite you to go play singleplayer sessions yourself and see how your system performs. If you don't have something like Sodium or Optifine, we recommend to look into those client-side mods to help you squeeze the most out of the Minecraft client.
Heads-up!
This forum thread is to give everybody a heads-up that Mojang is working on 1.17, that we're looking into our options to upgrade 1MoreBlock.com from 1.16.5 to 1.17 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.
Once we're on a stable version of 1.17 we will re-introduce these temporary resource worlds so we can guarantee you basically all the resources from the new server engine. The temporary worlds share the inventory with the main wilderness world (currently /general).
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, /skyblock, /oneblock, 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.17.x.
With the news however, that biomes and world height changes are part of a future release, we are still putting a hold on the /wild world. However, we are aiming to properly introduce /souls as a perm Nether world. Hey, if you think we should have a perm End world as well, let us know!
Upgrading software.
We are using the switch to 1.17 as an opportunity to upgrade our internal tools from 1MB 2.8.x to 1MB 2.9.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.17.x as a stable and working version that we can upgrade from, and then depend on (Craft)Bukkit / Spigot / Paper / Tuinity / Airplane 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.17 and java16 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.
Java 16
Yep, with a snapshot from the other week Mojang let us know that it's minimum requirement for Java will be 16. So be sure to check that your system supports Java 16, it's unclear if they will include a legacy option (but I kinda doubt it).
We've been preparing internally already. Our 1.16 set-up currently is Paper which supports Java16, we've been starting our server with Java16 JVM and have been updating a bunch of our plugins to Java16 JDK. And have tested all the plugins on our 25+ server network (that's over 175 plugins in total) and things are looking promising.
What we have done so far
We have been keeping an eye on the specifics of the snapshots and will do so with todays' pre-release, etc. We have been trying to speak to developers, server owners, and even 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 more room to allocate more of our 64gb RAM available (yay ram-disk) and an array of nvme/sata3 SSD disks for storage and backups, testing and archiving of user data. 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, developers, and we've tried to learn from our mistakes during upgrades in the past.
Huge but here!
<insert huge but here> BUT, we do what we can do. And we care about you as a player. WE WILL NOT RESET any perm-worlds, as 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.17 upgrades, converts, patches, and all sorts of stuff to try and make that happen.
And if 1.17 has corruption issues, chunks disappearing, items disappearing from armor stands and item frames, and weird stuff like that: We will just wait for 1.17.1, or 1.17.2, or even skip the 1.17 update and wait for 1.18.x and try 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.
Additionally, it's worth noting that even if we are back online that not all the worlds will be there, or that world borders are really small. This does not mean that we have removed worlds, it means that maybe certain worlds are still being converted, or we found a serious bug and are holding off running that particular section of our server setup live until we hear back from developers. This is a measure to try and cut down on potential downtime. For example. If /skyblock requires BentoBox to update, and it's not ready yet, or their developer-release isn't stable enough. We might just go live with the /general worlds and wait a few more days for bentobox to update. Things like that.
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. If this is June (hope so, might just be?!) or July or beyond, we do not know until testing and software, plugins, etc are actually available to us and testing has completed.
When we have a stable core engine, with stable core plugins, and we have converted from 1.16.5 to 1.17 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.16.5 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.17 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:
We have to wait for Mojang to release their server jar, before Bukkit/Spigot can update and before Paper/Airplane etc can update. Once they're all stable, we can look into the plugin releases by developers and complete our server testing. 1.17 is coming pretty quick now (my assumption), and that means it's an exciting time and this is a heads-up for you to take your stuff out of the temporary worlds. Temp worlds will be reset, perm worlds will stay.
When the above conditions are done, and we're done testing: We will do a public test that you can join.
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!
Wow, what bomb did Mojang drop on us in 2020 by letting us know there's a Cave & Cliffs update coming! And with the recent tweet by slicedlime that a pre-release should be out later today. I think it's fair to assume we should be getting ready.
Not only that, there's also a leaked tweet (now deleted) saying the migration from Mojang to Microsoft Accounts is basically set for this summer season. Before we get into the 1.17 information, let's jump on that MSA migration and tell you what you can do to prepare for that: Make sure you have an active and valid email on your Mojang account. And that you know your Mojang password. You will need both in order to start the migration process when the official Mojang launcher invites you to migrate. And be careful! There might be fake links, emails and websites out there trying to trick you into sharing your login details. Don't fall for those.
Okay, 1.17, and 1MoreBlock, what does that mean? Let's deep-dive into where we are now, what we expect and what that could mean for you the player. I know, it's a bit of a read, but I rather have it all in one spot than having to answer the same questions over and over.
Minecraft version 1.17.x is the Cave & Cliffs 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. of the available snapshot of 1.17. And boy, it's a big update. And not only that, but it's so big that Mojang has decided to keep the biomes / world changes as a separate release for later this year (I heard Christmas, let's hope they make it).
Testing and testing
Internally we've been testing the snapshot and will soon test the 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.16.5, but it's worth noting if you have a somewhat dated system, or only integrated graphics. You might notice a bit of suffering in the performance. There's a lot more, more code, more chunks, more things, items, entities, blocks, etc. And they all contribute to your system having to deal with it.
We invite you to go play singleplayer sessions yourself and see how your system performs. If you don't have something like Sodium or Optifine, we recommend to look into those client-side mods to help you squeeze the most out of the Minecraft client.
Heads-up!
This forum thread is to give everybody a heads-up that Mojang is working on 1.17, that we're looking into our options to upgrade 1MoreBlock.com from 1.16.5 to 1.17 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.
Once we're on a stable version of 1.17 we will re-introduce these temporary resource worlds so we can guarantee you basically all the resources from the new server engine. The temporary worlds share the inventory with the main wilderness world (currently /general).
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, /skyblock, /oneblock, 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.17.x.
With the news however, that biomes and world height changes are part of a future release, we are still putting a hold on the /wild world. However, we are aiming to properly introduce /souls as a perm Nether world. Hey, if you think we should have a perm End world as well, let us know!
Upgrading software.
We are using the switch to 1.17 as an opportunity to upgrade our internal tools from 1MB 2.8.x to 1MB 2.9.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.17.x as a stable and working version that we can upgrade from, and then depend on (Craft)Bukkit / Spigot / Paper / Tuinity / Airplane 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.17 and java16 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.
Java 16
Yep, with a snapshot from the other week Mojang let us know that it's minimum requirement for Java will be 16. So be sure to check that your system supports Java 16, it's unclear if they will include a legacy option (but I kinda doubt it).
We've been preparing internally already. Our 1.16 set-up currently is Paper which supports Java16, we've been starting our server with Java16 JVM and have been updating a bunch of our plugins to Java16 JDK. And have tested all the plugins on our 25+ server network (that's over 175 plugins in total) and things are looking promising.
What we have done so far
We have been keeping an eye on the specifics of the snapshots and will do so with todays' pre-release, etc. We have been trying to speak to developers, server owners, and even 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 more room to allocate more of our 64gb RAM available (yay ram-disk) and an array of nvme/sata3 SSD disks for storage and backups, testing and archiving of user data. 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, developers, and we've tried to learn from our mistakes during upgrades in the past.
Huge but here!
<insert huge but here> BUT, we do what we can do. And we care about you as a player. WE WILL NOT RESET any perm-worlds, as 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.17 upgrades, converts, patches, and all sorts of stuff to try and make that happen.
And if 1.17 has corruption issues, chunks disappearing, items disappearing from armor stands and item frames, and weird stuff like that: We will just wait for 1.17.1, or 1.17.2, or even skip the 1.17 update and wait for 1.18.x and try 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.
Additionally, it's worth noting that even if we are back online that not all the worlds will be there, or that world borders are really small. This does not mean that we have removed worlds, it means that maybe certain worlds are still being converted, or we found a serious bug and are holding off running that particular section of our server setup live until we hear back from developers. This is a measure to try and cut down on potential downtime. For example. If /skyblock requires BentoBox to update, and it's not ready yet, or their developer-release isn't stable enough. We might just go live with the /general worlds and wait a few more days for bentobox to update. Things like that.
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. If this is June (hope so, might just be?!) or July or beyond, we do not know until testing and software, plugins, etc are actually available to us and testing has completed.
When we have a stable core engine, with stable core plugins, and we have converted from 1.16.5 to 1.17 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.16.5 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.17 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:
We have to wait for Mojang to release their server jar, before Bukkit/Spigot can update and before Paper/Airplane etc can update. Once they're all stable, we can look into the plugin releases by developers and complete our server testing. 1.17 is coming pretty quick now (my assumption), and that means it's an exciting time and this is a heads-up for you to take your stuff out of the temporary worlds. Temp worlds will be reset, perm worlds will stay.
When the above conditions are done, and we're done testing: We will do a public test that you can join.
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!
