The maximum size of the world border is 59,999,968m, and that's also the initial size. However, the initial size used to be 60,000,000 before Minecraft 1.17. When upgrading from an old world, the world border becomes the correct size, but the stored value remains 60,000,000. This means that the /worldborder get
command returns the wrong value.
Steps to reproduce
Create a world in Minecraft 1.16.
Open the world in Minecraft 1.17 or a newer version and run
/worldborder get
It returns 60,000,000. Expected: 59,999,968.
Use a program like NBTExplorer to inspect the level.dat file
The
Data.BorderSize
value is 60,000,000d.
Teleport to the edge of the world (
/tp @s 29999999 ~ 29999999
)Notice that the world border is 59,999,968m wide, not 60 million.
Run the command
/worldborder set 60000000
It gives an error message: "Double must not be more than 5.9999968E7, found 6.0E7"
Run the command
/worldborder set 59999968
It is successful, but nothing changes about the world border.
Repeat step 6.
It gives an error message: "Nothing changed. The world border is already that size"
Repeat steps 2 and 3.
It correctly gives 59999968 this time.
Comments 6
I have found [MC-187668] though which appears to be a similar issue.
@@unknown Maybe you are right. However, you say its initial value is 60000000, I cannot reproduce it in 1.17.1. Has it already been fixed?
Thank you for your report!
After consideration, the issue is being closed as Won't Fix.
Please note that this is not the same as Working as Intended, as this bug report correctly describes behavior in the game that might not be the intended or desirable behavior, but it will not be fixed right now. Sometimes, this is because the issue reported is minor and/or impossible to change without large architectural changes to the code base.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
That issue was indeed fixed; it is stored as a double now. This is a different issue.