[MC-121997] 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

relates to 1

MC-62550 Worldborder not correctly initialized for the End and Nether Resolved

Comments 16

Arcensoth 2019-04-30T14:41:32Z

Still affects 1.14 full release

ZeNico13 2019-05-13T17:23:45Z

Still in 1.14.1 Release

ZeNico13 2019-05-17T19:19:33Z

Still in 1.14.2 Pre-Release 1 and 1.14.2 Pre-Release 2

BisUmTo 2020-03-15T19:47:26Z

If you change the worlborder from the nether with the command
/execute in minecraft:overworld run worldborder set 10
It works fine

Den_drummer 2020-03-20T21:13:41Z

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.

6 more comments

gaspoweredpick 2020-05-05T23:51:27Z

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.

Julien T 2020-05-07T01:19:17Z

@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.

god_of_sound 2020-06-11T13:39:01Z

confirmed for 1.16-pre release 1,2 & 3

Michael McDaniel 2020-07-25T20:24:44Z

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.

Michael Wood 2020-08-06T01:46:50Z

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.

chokoboy3 2020-08-16T14:56:34Z

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

Marty McFly 2021-03-12T13:41:41Z

Affects 21w10a

ampolive 2021-06-09T01:00:08Z

Potential code analysis in the duplicate MC-213713.

RainbowTea 2021-06-09T04:56:47Z

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.

Gijs Klein 2021-10-16T00:55:11Z

If you have a server with similar issues Spigot will solve them I tested it

ampolive 2021-11-09T13:28:53Z

Can confirm in 21w44a.