Every dimension's world border is operating independently, and doesn't appear where it actually is
The bug
Every dimension's world border is operating independently. Changing the world border in one dimension doesn't effect the other dimensions, and in the case of the Nether and End, won't visually change location even though it has.
How to reproduce
- Go into creative mode and do this command in the overworld:
/worldborder set 1000
- Go to the Nether and /tp to the world border there:
/tp @s 0 50 500
- Do this command while in the Nether:
/worldborder set 10
It looks as though the world border hasn't moved at all.
/worldborder get
and see that it says the border is 10 blocks, even though you can see otherwise. It looks like the original 1000-block length border.
- Stay within the bounds of the world border you see and put yourself in survival. You will die. The world border you saw wasn't the world border, it really did move to 10 blocks wide.
- Go back into creative mode and re-enter the nether, this time teleport to the world border's centre.
/tp @s 0 50 0
- Go into survival and walk around. The actual world border is invisible, but it's still at 10 blocks wide. You'll experience an invisible force hindering your walk.
- Return to the overworld and do the /worldborder get command again. Now it tells you it's 1000 blocks, which it is... for that dimension.
- Repeat for the End, but use a number other than 10 to ensure that the Nether world border and the End world border are operating separately from each other as well as the overworld's.
If you do the /worldborder get command in all three dimensions, you will get three different answers... and the Nether and End's world borders will not be where they look like they are. They will look like they have the same border as the overworld. - Repeat the process, changing world border centres instead of size. Changing the worldborder's centre in the Nether won't be the coordinates you put in, they'll be divided by 8. All three dimensions can have different world border centres as they are all operating independently.
Linked Issues
is duplicated by12
- Fixed
Paint
[Mojang] Ulraf- 47
- 25
- Confirmed
Normal
- Commands
- end nether overworld the_end the_nether world-border
1.12.2 - 21w44a
1.12.2 17w45b 17w46a 17w47a 17w47b 17w48a 17w49a 17w49b 17w50a 18w01a 18w02a 18w03b 18w05a 18w06a 18w07c 18w08a 18w10c 18w11a 18w14a 18w14b 18w20c 18w21b 18w22c 1.13-pre1 1.13-pre2 1.13-pre3 1.13-pre6 1.13-pre9 1.13 18w30a 18w30b 18w31a 18w32a 18w33a 1.13.1-pre1 1.13.1-pre2 1.13.1 1.13.2 18w43b 18w43c 18w44a 18w45a 18w46a 1.14 1.14.1 1.14.2-pre1 1.14.2-pre2 1.14.2 1.14.3 1.14.4-pre1 1.14.4-pre3 1.14.4-pre4 1.14.4-pre5 1.14.4-pre6 1.14.4 19w34a 19w35a 19w36a 19w37a 19w38b 19w39a 19w40a 19w41a 19w42a 19w44a 19w45a 19w45b 19w46b 1.15-pre1 1.15-pre2 1.15-pre3 1.15-pre4 1.15-pre5 1.15-pre6 1.15-pre7 1.15 1.15.1 1.15.1-pre1 1.15.2-pre1 1.15.2-pre2 1.15.2 20w06a 20w07a 20w08a 20w09a 20w10a 20w11a 20w12a 20w13a 20w13b 20w14a 20w15a 20w16a 20w17a 20w18a 20w19a 20w20a 20w20b 20w21a 1.16-pre2 1.16-pre3 1.16-pre8 1.16-rc1 1.16 1.16.1 20w28a 20w30a 1.16.2-pre1 1.16.2-rc1 1.16.2-rc2 1.16.2 1.16.3-rc1 1.16.3 1.16.4-pre1 1.16.4-pre2 1.16.4-rc1 1.16.4 20w46a 20w48a 20w51a 21w03a 1.16.5 21w05a 21w05b 21w06a 21w07a 21w10a 21w11a 1.17-pre2 1.17 1.17.1 21w44a- 1.18-pre1
Created Issue:
Every dimension's World Border is operating independantly, and doesn't appear where it actually is.
The Bug
Every dimension's World Border is operating independently. Changing the world border in one dimension doesn't effect the other dimensions, and in the case of the Nether and End, won't visually change location even though it has.
How to Reproduce
1. Go into Creative and do this command in the overworld
My title/worldborder set 1000
2. Go to the Nether and tp to the world border there.
My title/tp @s 0 50 500
3. Do this command while in the Nether
My title/worldborder set 10
It looks as though the world border hasn't moved at all.
My title/worldborder get
and see that it says the border is 10 blocks, even though you can see otherwise. It looks like the original 1000-block length border.
4. Stay within the bounds of the world border you see and put yourself in survival. You will die. The world border you saw wasn't the world border, it really did move to 10 blocks wide.
5. Go back into Creative Mode and re-enter the nether, this time teleport to the world border's centre.
My title/tp @s 0 50 0
6. Go into survival and walk around. The actual world border is invisible, but it's still at 10 blocks wide. You'll experience an invisible force hindering your walk.
7. Return to the overworld and do the worldborder get command again. Now it tells you it's 1000 blocks, which it is... for that dimension.
5. Repeat for the End, but use a number other than 10 to ensure that the Nether world border and the End world border are operating separately from each other as well as the overworld's.
If you do the worldborder get command in all three dimensions, you will get three different answers... and the Nether and End's world borders will not be where they look like they are. They will look like they have the same border as the overworld.
6. Repeat the process, changing world border centres instead of size. Changing the worldborder's centre in the Nether won't be the co-ordinates you put in, they'll be divided by 8. All three dimensions can have different world border centres as they are all operating independently.
The Bug
Every dimension's World Border is operating independently. Changing the world border in one dimension doesn't effect the other dimensions, and in the case of the Nether and End, won't visually change location even though it has.
How to Reproduce
1. Go into Creative and do this command in the overworld
My title/worldborder set 1000
2. Go to the Nether and tp to the world border there.
My title/tp @s 0 50 500
3. Do this command while in the Nether
My title/worldborder set 10
It looks as though the world border hasn't moved at all.
My title/worldborder get
and see that it says the border is 10 blocks, even though you can see otherwise. It looks like the original 1000-block length border.
4. Stay within the bounds of the world border you see and put yourself in survival. You will die. The world border you saw wasn't the world border, it really did move to 10 blocks wide.
5. Go back into Creative Mode and re-enter the nether, this time teleport to the world border's centre.
My title/tp @s 0 50 0
6. Go into survival and walk around. The actual world border is invisible, but it's still at 10 blocks wide. You'll experience an invisible force hindering your walk.
7. Return to the overworld and do the worldborder get command again. Now it tells you it's 1000 blocks, which it is... for that dimension.
5. Repeat for the End, but use a number other than 10 to ensure that the Nether world border and the End world border are operating separately from each other as well as the overworld's.
If you do the worldborder get command in all three dimensions, you will get three different answers... and the Nether and End's world borders will not be where they look like they are. They will look like they have the same border as the overworld.
6. Repeat the process, changing world border centres instead of size. Changing the worldborder's centre in the Nether won't be the co-ordinates you put in, they'll be divided by 8. All three dimensions can have different world border centres as they are all operating independently.
The Bug
Every dimension's World Border is operating independently. Changing the world border in one dimension doesn't effect the other dimensions, and in the case of the Nether and End, won't visually change location even though it has.
How to Reproduce
1. Go into Creative and do this command in the overworld
/worldborder set 1000
2. Go to the Nether and tp to the world border there.
/tp @s 0 50 500
3. Do this command while in the Nether
/worldborder set 10
It looks as though the world border hasn't moved at all.
/worldborder get
and see that it says the border is 10 blocks, even though you can see otherwise. It looks like the original 1000-block length border.
4. Stay within the bounds of the world border you see and put yourself in survival. You will die. The world border you saw wasn't the world border, it really did move to 10 blocks wide.
5. Go back into Creative Mode and re-enter the nether, this time teleport to the world border's centre.
/tp @s 0 50 0
6. Go into survival and walk around. The actual world border is invisible, but it's still at 10 blocks wide. You'll experience an invisible force hindering your walk.
7. Return to the overworld and do the worldborder get command again. Now it tells you it's 1000 blocks, which it is... for that dimension.
5. Repeat for the End, but use a number other than 10 to ensure that the Nether world border and the End world border are operating separately from each other as well as the overworld's.If you do the worldborder get command in all three dimensions, you will get three different answers... and the Nether and End's world borders will not be where they look like they are. They will look like they have the same border as the overworld.
6. Repeat the process, changing world border centres instead of size. Changing the worldborder's centre in the Nether won't be the co-ordinates you put in, they'll be divided by 8. All three dimensions can have different world border centres as they are all operating independently.The Bug
Every dimension's World Border is operating independently. Changing the world border in one dimension doesn't effect the other dimensions, and in the case of the Nether and End, won't visually change location even though it has.
How to Reproduce
1. Go into Creative and do this command in the overworld
/worldborder set 1000
2. Go to the Nether and tp to the world border there.
/tp @s 0 50 500
3. Do this command while in the Nether
/worldborder set 10
It looks as though the world border hasn't moved at all.
/worldborder get
and see that it says the border is 10 blocks, even though you can see otherwise. It looks like the original 1000-block length border.
4. Stay within the bounds of the world border you see and put yourself in survival. You will die. The world border you saw wasn't the world border, it really did move to 10 blocks wide.
5. Go back into Creative Mode and re-enter the nether, this time teleport to the world border's centre.
/tp @s 0 50 0
6. Go into survival and walk around. The actual world border is invisible, but it's still at 10 blocks wide. You'll experience an invisible force hindering your walk.
7. Return to the overworld and do the worldborder get command again. Now it tells you it's 1000 blocks, which it is... for that dimension.
8. Repeat for the End, but use a number other than 10 to ensure that the Nether world border and the End world border are operating separately from each other as well as the overworld's.
If you do the worldborder get command in all three dimensions, you will get three different answers... and the Nether and End's world borders will not be where they look like they are. They will look like they have the same border as the overworld.
9. Repeat the process, changing world border centres instead of size. Changing the worldborder's centre in the Nether won't be the co-ordinates you put in, they'll be divided by 8. All three dimensions can have different world border centres as they are all operating independently.
Every dimension's World Border is operating independantly, and doesn't appear where it actually is.Every dimension's World Border is operating independently, and doesn't appear where it actually is.
Every dimension'sWorldBorder is operating independently, and doesn't appear where it actually is.Every dimension's world border is operating independently, and doesn't appear where it actually is
relates to
The
BugEvery dimension's World Border is operating independently. Changing the world border in one dimension doesn't effect the other dimensions, and in the case of the Nether and End, won't visually change location even though it has.
How to
Reproduce1. Go into Creative and do this command in the overworld
/worldborder set 10002. Go to the Nether and tp to the world border there.
/tp @s 0 50 5003. Do this command while in the Nether
/worldborder set 10It looks as though the world border hasn't moved at all.
/worldborder getand see that it says the border is 10 blocks, even though you can see otherwise. It looks like the original 1000-block length border.
4. Stay within the bounds of the world border you see and put yourself in survival. You will die. The world border you saw wasn't the world border, it really did move to 10 blocks wide.
5. Go back into Creative Mode and re-enter the nether, this time teleport to the world border's centre.
/tp @s 0 50 06. Go into survival and walk around. The actual world border is invisible, but it's still at 10 blocks wide. You'll experience an invisible force hindering your walk.
7. Return to the overworld and do the worldborder get command again. Now it tells you it's 1000 blocks, which it is... for that dimension.
8. Repeat for the End, but use a number other than 10 to ensure that the Nether world border and the End world border are operating separately from each other as well as the overworld's.
If you do the worldborder get command in all three dimensions, you will get three different answers... and the Nether and End's world borders will not be where they look like they are. They will look like they have the same border as the overworld.
9. Repeat the process, changing world border centres instead of size. Changing the worldborder's centre in the Nether won't be the co-ordinates you put in, they'll be divided by 8. All three dimensions can have different world border centres as they are all operating independently.
The bug
Every dimension's World Border is operating independently. Changing the world border in one dimension doesn't effect the other dimensions, and in the case of the Nether and End, won't visually change location even though it has.
How to reproduce
1. Go into Creative and do this command in the overworld
/worldborder set 10002. Go to the Nether and /tp to the world border there.
/tp @s 0 50 5003. Do this command while in the Nether
/worldborder set 10It looks as though the world border hasn't moved at all.
/worldborder getand see that it says the border is 10 blocks, even though you can see otherwise. It looks like the original 1000-block length border.
4. Stay within the bounds of the world border you see and put yourself in survival. You will die. The world border you saw wasn't the world border, it really did move to 10 blocks wide.
5. Go back into Creative Mode and re-enter the nether, this time teleport to the world border's centre.
/tp @s 0 50 06. Go into survival and walk around. The actual world border is invisible, but it's still at 10 blocks wide. You'll experience an invisible force hindering your walk.
7. Return to the overworld and do the worldborder get command again. Now it tells you it's 1000 blocks, which it is... for that dimension.
8. Repeat for the End, but use a number other than 10 to ensure that the Nether world border and the End world border are operating separately from each other as well as the overworld's.
If you do the worldborder get command in all three dimensions, you will get three different answers... and the Nether and End's world borders will not be where they look like they are. They will look like they have the same border as the overworld.
9. Repeat the process, changing world border centres instead of size. Changing the worldborder's centre in the Nether won't be the co-ordinates you put in, they'll be divided by 8. All three dimensions can have different world border centres as they are all operating independently.
The bug
Every dimension's
WorldBorder is operating independently. Changing the world border in one dimension doesn't effect the other dimensions, and in the case of the Nether and End, won't visually change location even though it has.How to reproduce
1. Go into
Creative and do this command in the overworld/worldborder set 10002. Go to the Nether and /tp to the world border there
./tp @s 0 50 5003. Do this command while in the Nether
/worldborder set 10It looks as though the world border hasn't moved at all.
/worldborder getand see that it says the border is 10 blocks, even though you can see otherwise. It looks like the original 1000-block length border.
4. Stay within the bounds of the world border you see and put yourself in survival. You will die. The world border you saw wasn't the world border, it really did move to 10 blocks wide.
5. Go back into
CreativeMode and re-enter the nether, this time teleport to the world border's centre./tp @s 0 50 06. Go into survival and walk around. The actual world border is invisible, but it's still at 10 blocks wide. You'll experience an invisible force hindering your walk.
7. Return to the overworld and do the worldborder get command again. Now it tells you it's 1000 blocks, which it is... for that dimension.
8. Repeat for the End, but use a number other than 10 to ensure that the Nether world border and the End world border are operating separately from each other as well as the overworld's.
If you do the worldborder get command in all three dimensions, you will get three different answers... and the Nether and End's world borders will not be where they look like they are. They will look like they have the same border as the overworld.
9. Repeat the process, changing world border centres instead of size. Changing the worldborder's centre in the Nether won't be the co-ordinates you put in, they'll be divided by 8. All three dimensions can have different world border centres as they are all operating independently.
The bug
Every dimension's world border is operating independently. Changing the world border in one dimension doesn't effect the other dimensions, and in the case of the Nether and End, won't visually change location even though it has.
How to reproduce
1. Go into creative mode and do this command in the overworld:
/worldborder set 10002. Go to the Nether and /tp to the world border there:
/tp @s 0 50 5003. Do this command while in the Nether:
/worldborder set 10It looks as though the world border hasn't moved at all.
/worldborder getand see that it says the border is 10 blocks, even though you can see otherwise. It looks like the original 1000-block length border.
4. Stay within the bounds of the world border you see and put yourself in survival. You will die. The world border you saw wasn't the world border, it really did move to 10 blocks wide.
5. Go back into creative mode and re-enter the nether, this time teleport to the world border's centre.
/tp @s 0 50 06. Go into survival and walk around. The actual world border is invisible, but it's still at 10 blocks wide. You'll experience an invisible force hindering your walk.
7. Return to the overworld and do the /worldborder get command again. Now it tells you it's 1000 blocks, which it is... for that dimension.
8. Repeat for the End, but use a number other than 10 to ensure that the Nether world border and the End world border are operating separately from each other as well as the overworld's.
If you do the /worldborder get command in all three dimensions, you will get three different answers... and the Nether and End's world borders will not be where they look like they are. They will look like they have the same border as the overworld.
9. Repeat the process, changing world border centres instead of size. Changing the worldborder's centre in the Nether won't be the co-ordinates you put in, they'll be divided by 8. All three dimensions can have different world border centres as they are all operating independently.
The bug
Every dimension's world border is operating independently. Changing the world border in one dimension doesn't effect the other dimensions, and in the case of the Nether and End, won't visually change location even though it has.
How to reproduce
1. Go into creative mode and do this command in the overworld:
/worldborder set 10002. Go to the Nether and /tp to the world border there:
/tp @s 0 50 5003. Do this command while in the Nether:
/worldborder set 10It looks as though the world border hasn't moved at all.
/worldborder getand see that it says the border is 10 blocks, even though you can see otherwise. It looks like the original 1000-block length border.
4. Stay within the bounds of the world border you see and put yourself in survival. You will die. The world border you saw wasn't the world border, it really did move to 10 blocks wide.
5. Go back into creative mode and re-enter the nether, this time teleport to the world border's centre.
/tp @s 0 50 06. Go into survival and walk around. The actual world border is invisible, but it's still at 10 blocks wide. You'll experience an invisible force hindering your walk.
7. Return to the overworld and do the /worldborder get command again. Now it tells you it's 1000 blocks, which it is... for that dimension.
8. Repeat for the End, but use a number other than 10 to ensure that the Nether world border and the End world border are operating separately from each other as well as the overworld's.
If you do the /worldborder get command in all three dimensions, you will get three different answers... and the Nether and End's world borders will not be where they look like they are. They will look like they have the same border as the overworld.
9. Repeat the process, changing world border centres instead of size. Changing the worldborder's centre in the Nether won't be the co
-ordinates you put in, they'll be divided by 8. All three dimensions can have different world border centres as they are all operating independently.
is duplicated by
relates to
is duplicated by
is duplicated by
The bug
Every dimension's world border is operating independently. Changing the world border in one dimension doesn't effect the other dimensions, and in the case of the Nether and End, won't visually change location even though it has.
How to reproduce
1. Go into creative mode and do this command in the overworld:
/worldborder set 10002. Go to the Nether and /tp to the world border there:
/tp @s 0 50 5003. Do this command while in the Nether:
/worldborder set 10It looks as though the world border hasn't moved at all.
/worldborder getand see that it says the border is 10 blocks, even though you can see otherwise. It looks like the original 1000-block length border.
4. Stay within the bounds of the world border you see and put yourself in survival. You will die. The world border you saw wasn't the world border, it really did move to 10 blocks wide.
5. Go back into creative mode and re-enter the nether, this time teleport to the world border's centre.
/tp @s 0 50 06. Go into survival and walk around. The actual world border is invisible, but it's still at 10 blocks wide. You'll experience an invisible force hindering your walk.
7. Return to the overworld and do the /worldborder get command again. Now it tells you it's 1000 blocks, which it is... for that dimension.
8. Repeat for the End, but use a number other than 10 to ensure that the Nether world border and the End world border are operating separately from each other as well as the overworld's.
If you do the /worldborder get command in all three dimensions, you will get three different answers... and the Nether and End's world borders will not be where they look like they are. They will look like they have the same border as the overworld.
9. Repeat the process, changing world border centres instead of size. Changing the worldborder's centre in the Nether won't be the coordinates you put in, they'll be divided by 8. All three dimensions can have different world border centres as they are all operating independently.
The bug
Every dimension's world border is operating independently. Changing the world border in one dimension doesn't effect the other dimensions, and in the case of the Nether and End, won't visually change location even though it has.
How to reproduce
- Go into creative mode and do this command in the overworld:
/worldborder set 1000- Go to the Nether and /tp to the world border there:
/tp @s 0 50 500- Do this command while in the Nether:
/worldborder set 10It looks as though the world border hasn't moved at all.
/worldborder getand see that it says the border is 10 blocks, even though you can see otherwise. It looks like the original 1000-block length border.
- Stay within the bounds of the world border you see and put yourself in survival. You will die. The world border you saw wasn't the world border, it really did move to 10 blocks wide.
- Go back into creative mode and re-enter the nether, this time teleport to the world border's centre.
/tp @s 0 50 0- Go into survival and walk around. The actual world border is invisible, but it's still at 10 blocks wide. You'll experience an invisible force hindering your walk.
- Return to the overworld and do the /worldborder get command again. Now it tells you it's 1000 blocks, which it is... for that dimension.
- Repeat for the End, but use a number other than 10 to ensure that the Nether world border and the End world border are operating separately from each other as well as the overworld's.
If you do the /worldborder get command in all three dimensions, you will get three different answers... and the Nether and End's world borders will not be where they look like they are. They will look like they have the same border as the overworld.- Repeat the process, changing world border centres instead of size. Changing the worldborder's centre in the Nether won't be the coordinates you put in, they'll be divided by 8. All three dimensions can have different world border centres as they are all operating independently.
is duplicated by
is duplicated by
The problem here is that world borders break when edited outside the overworld. To work around this glitch, add "execute in minecraft:overworld run" before editing the world border.
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
relates to
The Bug
When travelling from the Nether to the overworld, it is usually the case that portals outside of the world border are considered invalid, and therefore a new portal inside the world border is created so players are safe.
But this is not the case for outside portals that are outside of the world border by ~128m or less. These portals will let the player use them, and then the player will instantly die.
How to Reproduce:
- Create a world and input these 3 commands:
/worldborder center 0 0 /worldborder set 2000 /tp @s 1000 70 0
- Build a portal and go to the nether.
- Input:
/execute in overworld run worldborder set 1780
Your overworld portal is now ~110m from the border, on the wrong side. We had to use an execute command because without it we'd only be affecting the nether's world border and not the overworld's. See
MC-121997. - /gamemode survival and return to the overworld.
-> "Player suffocated in a wall."
If you repeat these steps and use 1750 instead of 1780, you'll find that a new portal is created, as intended.
No, but MC-121997 does
Thank you for your report!
We're actually already tracking this issue in MC-121997, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Thank you for your report!
We're actually already tracking this issue in MC-121997, so I resolved and linked this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
Does MC-121997 describe your issue?
Thank you for your report!
We're tracking this issue in MC-121997, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-121997, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature in the future to see if the issue has already been reported.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 Game Wiki
This appears to be a duplicate of MC-121997, which hasn't yet been resolved. If you have any additional information to provide regarding this issue, feel free to comment on the parent ticket. If you feel that this issue is affecting you, feel free to vote for the duplicated ticket, to give Mojang a basic idea of how many people are impacted by the problem. Just to further inform you, this will not determine how quickly the bug gets handled or fixed.
Thank you for your report!
We're tracking this issue in MC-121997, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-121997, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-121997, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Duplicate of MC-121997.
Thank you for your report!
We're tracking this issue in MC-121997, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MC-121997, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
The Bug :
The world border cannot be different in a custom dimension and in the overworld. If it is modified in one, it is also modified in the other. This bug is due to the fix MC-121997, which solved a bug on the worldborder which could, at that time, work independently but not correctly. The MC-121997 fix seems to have simply removed this feature, instead of fixing it.
This bug appeared in 1.18-pre1, at the time of the fix. (verified)
This bug is now very annoying for map creators, but especially for datapack creators, since creating a custom dimension to use the worldborder is the only way for us to measure real time without lag.
How to reproduce :
1. Create a new world and a custom dimension using a datapack. The worldborder is 59999968.
2. Modify the worldborder of the custom dimension while being in the overworld with this command :
execute in custom:world run worldborder set 10
3. You can see that the world border has changed in the overworld and in the custom dimension, while before the MC-121997 fix, it would have just changed in the custom dimension.
Observed behavior :
The world border has been set to 10 in the overworld and in the custom dimension.
Expected behavior :
The world border should be set to 10 in the custom dimension and stay at 59999968 in the overworld.
WAI per fixing of MC-121997, for feature/change suggestions go to feedback.minecraft.net.
My hope is that only the second part of MC-121997 was a bug and that the /worldborder command will be changed so that it can only affect particular dimensions (either via an additional argument or via /execute, preferably the former).
I should say, the main concern with this issue is that a mod or data pack could add a custom dimension which is intended to be explored only for short periods of resource gathering, with the player dropped into a random location each time. If a group of players wanted to constrain their overworld play area with the world border so that their bases are close together, some implementations of the custom dimension would be broken due to the game trying to drop the player outside the universal world border. (I'm already aware of one instance of this happening with the Vault Hunters modpack). So it's a rather niche problem, but it would still be nice if it were solved, preferably along with giving custom dimensions their own day/night cycles.
Still affects 1.14 full release
Still in 1.14.1 Release
Still in 1.14.2 Pre-Release 1 and 1.14.2 Pre-Release 2
If you change the worlborder from the nether with the command
/execute in minecraft:overworld run worldborder set 10
It works fine
I can confirm it's still the case in 20w12a as well.
BisUmTo your command does put the border visuals in the nether to that area, but that also moves the worldborder in the overworld, which is not always what people want. Considering the coordinate system in the nether, one might want to limit the worldborder size in the nether to 1/8th the size of the overworld. I had one of my friends die on my private server due to also being able to walk over the worldborder due to there being no visual clue, which is how this bug was brought to my attention in the first place.
Basically the problem afaik is that no matter what dimension you're in, the visuals of the worldborder seem to match those of the overworld, but the actual worldborder can be set per dimension individually, which means there can be a mismatch between the visuals and the actual deadly area. If the overworld has the smallest worldborder, it'll only be a minor issue. If you have it the other way round however (like I did until I learnt about this bug and will again if this bug gets fixed), players have no idea that they're past the worldborder and will start taking damage, seemingly for no reason.
The problem here is that world borders break when edited outside the overworld. To work around this glitch, add "execute in minecraft:overworld run" before editing the world border. All worldborder commands will work properly when executed in the overworld, regardless of which dimension you're in.
@gaspoweredpick that fixes the visual glitch yes but also move the border in the overworld. We can change the worldborder per dimension but having the visualglitch (border not present), or have the visual ok but have a common worlderborder in every dimensions.
confirmed for 1.16-pre release 1,2 & 3
For custom dimensions I view this as a feature, not a bug. It gives me a way to limit the size of custom dimensions easily. Barrier blocks are useful, but are not able to be water logged, so this looks better. The nether being a tiny dimension but the same size has always been a problem. This "bug" can fix that.
Please don't fix this bug.
Side note, am I the only one that doesn't see the world border visually in custom dimensions? I like that as well, as seeing it would be distracting for small pocket dimensions for mini games and adventures. To me, this is also a feature, not a bug. We can use the warning part of the worldboarder command to warn a player. Perhaps adding a distance to how close you have to be to see it would be a better option.
I agree that this is useful, especially for custom dimensions. But they really need to fix it so it actually works as one would hope. I noticed that the border size resets in dimensions other than the Overworld when you relog, and it's somehow split into two distinct pieces:
The visible part, which mirrors the border in the Overworld and stops player movement as well as block placement.
And the invisible part, which can be altered by the /worldborder command, causes damage when you cross it, and also stops block placement.
The most dangerous part about this in my opinion is that a player could pass the invisible border without realizing, until they start taking damage and can't interact with blocks that is.
It seems that the issue is that while the server respects world borders in multiple dimensions, the client only recognizes the world border in the overworld even when in another dimension. This means that visually, the world border is always in the position that it is in in the overworld.
If the overworld has a larger world border than the dimension that you are in, you will start taking damage at random and blocks will reappear as you break them, as the server recognizes that you have moved outside the world border but the client allows you to move.
If the overworld has a smaller world border than the dimension that you are in, it just seems like the dimensions have the same world border since the client prevents you from going outside even though it should be entirely possible. If you teleport outside of the world border, you will not take damage in this situation.
Also, it seems that the world border is reset server-side in other dimensions after reopening the world
Affects 21w10a
Potential code analysis in the duplicate
MC-213713.So, i'm not sure if this is related. My world border in the overworld, nether and end work, they are correct to the size i want it to be and the world border appears. However, the world border in my custom dimension, it works but does not have a visual appearance. Its completely invisible and the only way we notice we are going past the world border is the damage taken.
If you have a server with similar issues Spigot will solve them I tested it
Can confirm in 21w44a.