[SPIGOT-1663] WorldBorder moving borders don't appear to be sent to client. Created: 02/Mar/16 Updated: 06/Mar/16 Resolved: 06/Mar/16 |
|
Status: | Resolved |
Project: | Spigot |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Bug | Priority: | Minor |
Reporter: | Melair | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | 1.9, worldborder | ||
Environment: |
Java(TM) SE Runtime Environment (build 1.8.0_74-b02) |
Description |
It appears that clients are not sent an update for the world border when the size is set to change over time. The server is still tracking the border as players are damaged when outside where the border would be. The client renders the border as stationary as it was at the starting position. This occurs if it's requested via command or by API. Tested in 1.9 vanilla as working. To reproduce in Spigot: /gamemode creative |
Comments |
Comment by Melair [ 03/Mar/16 ] |
It did include that commit, however to clarify, I retested this morning on a clean build: [08:16:21 INFO]: This server is running CraftBukkit version git-Spigot-43ef916-e2c5473 (MC: 1.9) (Implementing API version 1.9-R0.1-SNAPSHOT) The issue still occurs. If you set a worldborder on a world other then the first loaded world then players on that world are not sent the world border. |
Comment by Black Hole [ 03/Mar/16 ] |
Please update your Spigot version. Since you're running a customized version, it's unclear if it contains this commit: https://hub.spigotmc.org/stash/projects/SPIGOT/repos/craftbukkit/commits/f5d92d6b12dcc43cb9a05f2e16357ebe0d9fdc20 |
Comment by Melair [ 02/Mar/16 ] |
Nope I rescind that, I've got it. If the WorldBorder is set on a world which is not the first world (as defined by level-name in server.properties), then the world border updates are not sent to the clients on that world. Can be confirmed by going to the nether: /tp @p 0 200 0 Notice no set border, or then no moving border . |
Comment by Melair [ 02/Mar/16 ] |
Okey this is mildly embarrassing, I can't reproduce this all of a sudden and the report was against one I had a patch against. It's possible I damaged the build. Feel free to close, and I'll relog if I can reproduce in a sane way. |
Comment by Melair [ 02/Mar/16 ] |
Forgot to mention, tested on Spigot with no plugins loaded. |