as you have seen in one of my previous posts, there were worries about the next version “breaking everything”. The issue was that a change to the way blocks are named (which has been implemented already a long time ago) would be enforced and the old naming scheme removed from the code. The worry was that a lot of plugins might break then because they were not updated at the time.
It turns out now that the spigot team (who make the adaption of the vanilla minecraft server that we use) have implemented already a mitigation to the changes that were done in minecraft to keep old plugins working. While I did not test anything yet, I think we can stay reasonably calm and looking forward for the new version to not have too many issues.
Further, as you might have read on Mojang’s news, they delayed the next update to roll it together with the one coming after that. The new update will then include new water mobs and more. So there is something to look forward to! Unfortunately, as usual, there is no confirmed release date for the next version, I am assuming something like April/May or similar. Let’s see.
However, there is the question when we will change the empty lots in the empire (and possibly also in the Kingdom). To remind you what this is about: Normally, we only re-generate the Empire lots when there are REALLY significant biome/block changes. The kingdom was on top of that never meant to be re-generated since it’s purely for building, mining and landscape there is secondary. However in the last updates that introduced Andesite, Diorite etc, the underground environment changed, but the landscape did not change too much – if at all. There is therefore now the opportunity to re-generate the empty lots in those worlds so that the underground generated according to the current minecraft version, without creating nasty breaks in the surface, landscape and biomes above ground. We could also give the opportunity to lot owners to reset their lots as a one-off feature.
The choice there is to do that now, once, or to wait for the next version to be released. We can then check if the new version generates a completely different landscape, in which case we have different decisions to make.
So what is your opinion? In general, we can always wait for the next version – and then therefore never change anything. On the other hand, we want to avoid excessive changes and workload if it’s not needed or wanted.