3.0.0 marked as stable.

THIS IS A BETA RELEASE
This update includes significant changes required for 26.x compatibility, along with additional fixes and improvements. While extensive testing has been performed, some bugs may still be present.

26.x compatibility
Lots of things under the hood have been changed to support Minecraft version 26.x.

Unintended Behavior Fix
Fixed the following unintended behaviour to match vanilla leashing mechanics: when right-clicking a mob leashed to a fence with a lead in hand, the mob would simply unleash from the fence instead of also being leashed by the player.

WorldGuard Integration Rework
Tether’s custom LEASH flag now respects the default INTERACT flag, which in turn respects the BUILD flag.

• However in the __global__ region, only BUILD is checked.

Updates to Lands Integration
Added support for bypass permission via the lands.bypass.interact_general permission.

Player Leashing Bug Fix
A longstanding known bug has been fixed. Whenever a player is leashed, and the lead is broken (by the leasher flying away with an elytra), the leashed player is left sitting, stuck on an invisible entity until they manually crouch to escape.

This bug was around for so long because it was an issue with Paper, so it was out of my control. TLDR, Paper wasn’t sending the proper events for unleashing.

Fixed a bug where the “Leash target is in protected land" message would mistakenly appear when right-clicking a fence in protected land that the player doesn’t have access to, when the right-click had nothing to do with fence leashing.

Adds official support for Minecraft version 26.1.1.

This update adds the highly-requested feature that is WorldGuard support!

Changelog:

• WorldGuard Integration via “leash” flag.
• Flag is set to ALLOW by default.
• WorldGuard’s admin region bypass (/rg bypass) is respected.
• WorldGuard integration is automatic and always active as long as you have WorldGuard installed. (i.e. You do not have to enable it in the config).
• config.yml updates (updates automatically):
  • messages.in-claim-deny-mob → messages.target-mob-in-protected-land
  • messages.in-claim-deny-player → messages.target-player-in-protected-land

Thank you to @beacon and @drey in my discord for the suggestion.

2.12.2 brings some small fixes and behind-the-scenes improvements.

Changelog:

• Fixed a bug where Tether would sometimes throw a NullPointerException error for the GriefPrevention integration upon startup. (Thanks to Drey in my Discord for the report)!
• Residence dependency updated.
• GriefDefender dependency setup updated.

Fixes a bug where leashing non-living entities that should be leashable by default, like boats, did not work in Tether.

Thanks Drey in my discord for the bug report!

This update adds support for the Residence land management plugin.

Uses the " leash" flag.

This has been suggested by a few people, notably @bigBeacon. Thank you for the suggestion!

Added support for leashing all mobs together (1.21.6 feature).

This is the last feature from the 1.21.6 leash rework that Tether needed to support. With this update, Tether is fully compatible with Minecraft’s new leashing mechanics.

This update adds Citizens integration.

Details:

• Tether will now respect your ‘leashable’ setting on your Citizens NPCs.
• NPCs of type “Player” will not be able to be leashed at all.

Functionality note:
Your ‘leashable’ setting on your NPCs works alongside your mob blacklist/whitelist. If your NPC is leashable but doesn’t pass the blacklist/whitelist check, it won’t leash, and vice versa.

Thank you to Ken on my Discord for the suggestion!

The following are all bug fixes for Griefprevention integration.

1. Fixed a bug where anytime admins right-click on a mob in someone else’s claim, even without a lead in their hand, it would print out the ‘in-claim-deny-mob’ message.

2. Fixed a bug where whenever an admin is ignoring claims and tries to leash a mob not leashable by the vanilla game in someone else’s claim, it doesn’t leash.

3. Fixed a bug where when an admin is ignoring claims and leashes a mob that is leashable in the vanilla game, in someone else’s claim, it prints out the ‘in-claim-deny-mob message’ message, even though they can leash it.

These bugs were reported by @ken on my Discord, thank you!

This updates add a new feature: a mob whitelist!

How does it work?

• Any mobs that you write in the whitelist will be the only mobs leashable.
• In order to enable the whitelist, you need to set use-whitelist-over-blacklist in the config to true. This will ignore the blacklist and use the whitelist instead.

Generating a new config is NOT required.
The new config options will generate automatically.
The comments along with them won't however. So if you want them, either generate a new config or copy them from the config displayed on this plugin's homepage.

Suggestion Credits
Thank you to lecraeman for the great suggestion!

Other Fixes

• Mob blacklist works properly now.

Added official support for 1.21.5.

• Fixed entities not being cleared properly when multiple players use a lead. (By: ApliNi)

• Added prevent-nesting functionality. (By: ApliNi)
  • If you are already riding an entity, you cannot leash other players.
  • Toggled off by default.

• Official support for Minecraft version 1.20 + (By: Naspo)

Thank you ApliNi for your contributions!

- Officially added 1.19.4 support.

- Officially added 1.19.3 support.

- 1.19 compatibility.

- Added GriefDefender support.
(New config generation is not required).

Fixed a bug where player leashing would be denied due to a faulty protected land check.

Changelog:

• Added support for GriefPrevention, Towny, and Lands. (For both mobs and players).
• Config version updated to config-version 3.
  • Added toggleable hooks for land management plugins.
  • Added more message customization.

*Generating a new configuration file is required for this update.

Thanks for the suggestion!

- Fixed a bug where if a lead is broken (not right-click unleashed, but broken), and escapable is set to false, the player remains in the seated position and is unable to escape.

Thanks for the report!

- Added support for leashing players. (Thanks for the suggestions)!
- Config has been updated to config-version 2.
- Added options in the config for player leashing settings.

Note: If you are updating to this version and actually want to be able to use the new things it brings (i.e. player leashing), you need to delete your config.yml file and let it auto-regenerate with the new options.

- Completely changed the way the plugin handles leashing. This should prevent any dupe and reverse dupe exploits indefinitely.

- Fixed a dupe exploit involving slimes.

- Fixed a typo in the config.
- Implemented version number in jar name.

- Fixed LivingEntity bug.
- Fixed a bug where 2 leads would be removed from a player's inventory when leashing certain mobs.