New command /wb bypass [player] [on/off], which allows the player to go beyond the border without being knocked back. Requires "worldborder.bypass" permission (Ops only by default). Nobody has bypass mode enabled by default (has to be toggled on), and the list of people with bypass enabled is wiped on server restarts. Player name ("[player]") is optional if run in-game and defaults to the player running the command, but must be specified if run from console. If on or off ("[on/off]") is not specified, it will simply be toggled.
Thanks to mikeprimm for adding a couple of requested features to DynMap which made this feature possible.
New commands:
/wb dynmap <on/off> - turn DynMap border display on or off.
/wb dynmapmsg <text> - DynMap border labels will show this.
New permissions:
worldborder.dynmap (Op): Can enable/disable DynMap border display integration
worldborder.dynmapmsg (Op): Can set the label text for borders shown in DynMap
Also, a slight improvement to how boolean values are determined from command input; it accepts "y", "yes", "true" instead of just "on".
Removed plugin "loading" and "shutting down" log messages at startup and shutdown since Bukkit now handles such messages itself.
Updated CoordXZ to have slightly more unique hashCode values for fewer hashCode intersections.
Support for newly available built-in Bukkit "superperms" permission system; uses the same nodes as for the Permissions plugin
Support for colors in console messages
Knockback distance is now required to be at least 1.0
A couple of other tweaks
moved border checking routine out into a timed task, for even lower server impact
added new configurable "delay" value, for the number of ticks it will wait between border checks, the default is 4 (~200ms); each server tick is ~50ms or so
added new configurable "knockback" value, for how far back inside the border to move a stray player, the default is 3.0
changed world-name encoding method for worlds with dots in the name to use an uncommon high-range ASCII character ("¨"), since forward-slash ("/") can occur in world names; don't worry, old configurations which have the "."->"/" encoding will be automatically and safely converted
split command listing to 2 pages for players, since there are too many commands to fit on the screen now
