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 103. 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.
Attachments
Comments 6
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.
Affects 1.19.2.
To test, create a new world with the following datapack:
. Then run the following commands:
Observe that the world border distance was also set to 10 in
clamlol:void.