-
Bug
-
Resolution: Unresolved
-
None
-
1.16.3, 1.16.5, 21w08b, 1.17.1, 1.18 Pre-release 1, 23w03a
-
None
-
Confirmed
-
(Unassigned)
Issue:
When an op calls "worldborder add <size> <time>" while the worldborder is currently shrinking or growing, the worldborder size will change appropriately according to the command, but it will not do it in the time given. The message printed to the user will contain the correct size, but the incorrect growth time (the time given is the time left on the current shrinking/growing of the wall added to the given time).
Example:
The worldborder is currently 100 blocks in size, shrinking at 0.5 blocks per second, down to 10 blocks wide. This could be achieved with the following commands:
/worldborder set 100
> Set the world border to 100.0 blocks wide
/worldborder set 10 180
> Shrinking the world border to 10.0 blocks wide over 180 seconds
Then, after 10 seconds, the op enters the following command:
/worldborder add 10 5
> Growing the world border to 105.0 blocks wide over 175 seconds
*Note: 175 seconds is the time remaining from the previous "set" command (170 seconds) added to the time given by this "add" command (5 seconds)
The world border then proceeds to grow to the stated width (105 blocks) in the stated time (175 seconds).
Expected Behavior:
When the "/worldborder add 10 5" command is executed, the world border should proceed to grow by 10 blocks in 5 seconds irrespective of whether or not the world border was previously shrinking/growing or not. This should be true regardless of the size and time values given.
- relates to
-
MC-59769 Changing worldborder size is inconsistent / behaves erratically when the border is already moving
- Resolved