When performing a worldborder set command while the border is moving, the resulting motion will assume that the world border had already reached its stopping point.
For example, type
/worldborder set 100then
/worldborder set 10 60then
/worldborder set 100 60Instead of reversing its movement back out to 100, it will jump in to 10 and start moving outward.
Linked issues
duplicates 1
Comments 5
I did. When the set command is used, it calculates current position and motion based on where the world border was going to end up. Do I really need to provide example worldborder commands?
Is this still an issue in the latest snapshot 16w44a? If so please update the affected versions.
This is an automated comment on any open or reopened issue with out-of-date affected versions.
Looks like this is sadly a duplicate of MC-59769
Please provide steps to reproduce and explain the issue in detail.