Shared private waypoints will appear in the other player's private waypoint list
Remove player access in the waypoint options menu
Added more checks and default fallbacks for any missing plugin data or config items
A beacon no longer needs a public waypoint associated with it to open the waypoint menu, though it still requires at least one public or private waypoint. This may change to have no restrictions in a future update so that any beacon can be used to teleport, even if it doesn't have any waypoint set
Fixes:
Messages are now properly sent to waypoint owner(s) when a beacon with waypoints is broken
Players are no able to take items from inventory menus if there is an error on a click event
NOTE: *This update also adds support for 1.21, but player heads will show as default skins. This will affect back and forward menu buttons as well as player heads in the waypoint sharing menu. I will try to find an alternative way to load player skulls for 1.21+.
I recommend backing your plugin data in case upgrading to this version breaks something. I thoroughly tested upgrading versions and making sure it filled in missing language and config values wherever it could, but you should probably back up just in case.
Note: There have been changes to both config.yml and language.yml. The plugin will use defaults for anything that is not in these files, but it is recommended to take a look at the example/default files to see what changed.
Changes:
Added support for 1.19.3
Added Discovery Mode: Players can discover public waypoints by interacting with the beacon and can only teleport between discovered waypoints
Added config options for payment to teleport
XP payment
EssentialsX money payment
Cost multiplier based on distance
Cost for teleporting between dimensions
Required items
Custom names
Optional consuming of items
Checks for items in shulker boxes
Added config option for banned items for players to have in order to teleport
Added ability to pin public waypoints to the top of the list for players with the BeaconWaypoints.manageAllWaypoints permission
Waypoint names no longer need to be alphanumeric, but this can be force in the config file
Fixes:
- Added compatibility with NoCheatPlus by adding temporary exemptions when a player is teleporting.
- Added launch-player-height config option to change how high players are launched before teleporting. Anti-cheat plugins might not allow players above a certain height, so this is a way to work around that.
Changes:
- The default waypoint type is now public, so typing out "public" is no longer required when creating a new waypoint
- Changed permissions
- Removed waypoint permission
- Added createWaypoints permission
- Added useWaypoints permission
- Added usePrivateWaypoints permission
- Added breakWaypointBeacons permission
- Added manageAllWaypoints permission
- Changed config.yml
- Added launch-player option
- Added allow-beacon-break-by-owner option
- Added allow-all-worlds option
Bug Fixes:
- The back arrow player texture for the player skull in the waypoint options menu would not load
- A waypoint would be removed if a beacon became obstructed and then unobstructed
Changes:
- Added support for versions 1.14-1.17.1 and 1.18.2
- Added bStats metric for the total number of waypoints
Bug Fixes:
- config.yml would not be created automatically (bruh moment)
- Players could activate beacon teleportation if they opened the menu, got moved away, and selected a destination
Added a config option "disable-group-teleporting" that prevents all players standing on a beacon from teleporting at the same time when it was activated, and instead only teleports the player choosing the destination, when enabled.
Added config reload command (/waypoints reload). This adds the permission BeaconWaypoints.reload which is enabled for operators by default.Changed the icon for the "Options for this waypoint" button from a comparator to the icon of the waypoint being interacted with.
Added an update checker that notifies the console and operators of an update to the plugin.
Bug fixes:
A waypoint was not deleted if the beacon was removed with the setblock or fill commands. Changing or deleting blocks using WorldEdit still does not remove the waypoint.
BeaconWaypoints could conflict with other plugins and make players take fall damage when landing on the destination beacon.