MC-56162Worldborder damage 0
Setting the worldborder damage to 0: /worldborder damage amount 0
doesn't work it just uses the last set value even it says: "Set worldborder damage amount per block to 0.0"
Relates to: MC-62550
Linked Issues
Created Issue:
Worldborder damage 0
Setting the worldborder damage ("/worldborder damage amount 0") doesn't work it just uses the last set value even it says: "Set worldborder damage amount per block to 0.0"
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
Setting the worldborder damage ("/worldborder damage amount 0") doesn't work it just uses the last set value even it says: "Set worldborder damage amount per block to 0.0"
Relates to:
MC-62550
Setting the worldborder damage ("/worldborder damage amount 0") doesn't work it just uses the last set value even it says: "Set worldborder damage amount per block to 0.0"
Relates to:
MC-62550Setting the worldborder damage to 0: /worldborder damage amount 0
doesn't work it just uses the last set value even it says: "Set worldborder damage amount per block to 0.0"Relates to:
MC-62550
![[Mod] redstonehelper](../../../data/avatars/users/10122.svg){kind=small}
![[Mod] Torabi](../../../data/assets/gravatar/torabi.png){kind=small}
![[Mojang] Searge (Michael Stoyke)](../../../data/assets/gravatar/searge.png){kind=small}
[Mojang] Searge (Michael Stoyke)
relates to
Confirmed
Yep. This needs to be fixed because right now having temporary world borders for events on servers will kill all mobs on the outside.
An alternative (that would be a great addition in any case) would be to have an option like: "onlyPlayers" with true/false that would make the world border to only affect players and nothing else.
In our case we wanted to keep our existing world but have a world border in the beginning of new patch releases (like 1.8) and then open up the world again in like 3 months. But since it kills everything (and maybe changes other stuff aswell), we cant really do that. =(
Confirmed for 15w49b, 15w50a, & 15w51b.
Confirmed for 16w02a.
Confirmed for 16w05a.
Confirmed for Minecraft 1.9
Looking at the NBT data of level.dat, it does appear 'BorderDamagePerBlock' is being updated after typing "/worldborder damage amount 0". So the command itself appears to be working at that level, but the game itself is ignoring the "0" value, and continues to damage players.
Entities like mobs don't appear to be taking damage.
It will be fixed in 1.9.1, but there's already a workaround for 1.9 by using the worldborder buffer zone, setting that to a very high value means that within the distance of x blocks outside of the border, no damage will be applied.