Affects Version/s: Minecraft 14w29b, Minecraft 14w30c, Minecraft 14w31a, Minecraft 1.8-pre2, Minecraft 15w37a, Minecraft 1.9.4, Minecraft 16w20a, Minecraft 1.10, Minecraft 1.11, Minecraft 1.11.2, Minecraft 17w06a, Minecraft 1.12.2, Minecraft 17w43b, Minecraft 17w45b, Minecraft 17w46a, Minecraft 17w47a, Minecraft 1.13.1, Minecraft 1.14, Minecraft 1.14.1, Minecraft 1.14.2 Pre-Release 1, Minecraft 1.14.2 Pre-Release 2, Minecraft 1.14.2, Minecraft 1.14.3, Minecraft 1.14.4 Pre-Release 1, Minecraft 1.14.4 Pre-Release 3, Minecraft 1.14.4 Pre-Release 4, Minecraft 1.14.4 Pre-Release 5, Minecraft 1.14.4 Pre-Release 6, 1.14.4, 19w34a, 19w35a, 19w36a, 19w37a, 19w38b, 19w39a, 19w40a, 19w41a, 19w42a, 19w45b, 19w46b, 1.15 Pre-release 1, 1.15 Pre-Release 2, 1.15 Pre-release 3, 1.15 Pre-release 4, 1.15 Pre-release 5, 1.15 Pre-release 6, 1.15 Pre-release 7, 1.15, 1.15.1, 1.15.1 Pre-release 1, 1.15.2 Pre-Release 1, 1.15.2 Pre-release 2, 1.15.2
Fix Version/s: None
The worldborder of the End and the Nether uses the default values when you open a world.
- Go to the End
- Set the worldborder center to your current position while standing at least 10 blocks away from 0, 0
- Close and reopen the world
- Set the worldborder size to 10
- Try to place a block
→ It disappears after you placed it because the End uses 0, 0 as center
Based on 1.11 decompiled using MCP 9.35 rc1
When the worldborder settings are changed all IBorderListener are informed about the changes and when a WorldServerMulti (End and Nether) is created it adds its listener to the worldborder of the "main" server (WorldServer). When a server is created its init() method is called which reads the worldborder settings for the main server. The problem is that when the settings are read the other servers have not been created yet and because of this have not added any listeners. This causes them to use the default values.