ВЕРСИИ (16)

Fixed a bug where a faulty "entity in protected land" message would be shown when crouch + right-clicking any entity in protected land without a lead in hand, or without having other entities leashed. _Thanks Ken in my Discord for reporting this!_

Fixed a bug where when a non-leashable entity is interacted with, a faulty error is thrown in the console.

Added a `player-leash.suppress-leashed-player` option in the config that, if enabled, will prevent leashed players from interacting with anything in any way. For example: They cannot place blocks, hit players, interact with stuff, etc… _Thank you Jupi in my Discord for the suggestion!_

Tether version 4.0.0 is now marked as stable. For the full changelog, please see the changelogs for the previous 4.0.0 beta releases.

**v4.0.0-beta.3 - Continuation of Isolate Default Leashable Mobs Update** ℹ️ **This is a BETA Release**\ This update includes significant changes. While extensive testing has been performed, some bugs may still be present. # Config Backwards Compatibility Improved with Safe Migration For every key in `config.yml`, Tether will now check: If it's a legacy key and its modern equivalent is not present, copy the value(s) from the legacy key to the modern one, then delete the legacy one. ## Example In this 4.0.0 update, `blacklisted-mobs` changed to `entity-blacklist`. Now, on startup, Tether will check if the user's config has the old `blacklisted-mobs` key. If it does, create the `entity-blacklist` key and copy over the values. Then delete `blacklisted-mobs`.

# v4.0.0-beta.2 - Continuation of Isolate Default Leashable Mobs Update # ℹ️ This is a BETA Release This update includes significant changes. While extensive testing has been performed, some bugs may still be present. # ❗ BREAKING CHANGE - Tether only supports Paper now (and direct forks) As of this release, 4.0.0-beta.2, Tether has moved off of the Spigot API and over to the Paper API. _Development of this update uncovered the need to make this change._ ## What This Means For You ❗ **Tether will no longer work on plain Spigot servers, and will only work on Paper (or Paper-based) servers (like Purpur).** **Estimated affected audience:**\ Basically no one. For years Paper has been the gold standard Minecraft server. No one really runs a plain Spigot server anymore anyways. _(See more below)._ ## Why? Paper has always been a direct superset of Spigot, meaning all Spigot plugins will work on Paper. However, in 2024 Paper officially stopped this commitment and moved away from relying on Spigot so that they may become independent and move more quickly. Things still continued be compatible for a while though, until eventually certain plugins would run into a point where the differences mattered. This was the case for Tether recently, as Paper changed things to do with leashing under the hood that no longer matched Spigot. These situations leave developers like me with a few options: - A. Stop supporting Paper and stick with Spigot. (Yeah, no way). - B. Develop two streams of the plugin, one for plain Spigot and one for Paper. - C. Abandon plain Spigot entirely and go all in on Paper and paper-based servers. I of course chose option C. Option B, while valid, is too much work (for me at least). Especially considering the fact that the vast majority of Minecraft servers nowadays run Paper or some paper-based server (like Pupur). Almost no one is running a plain Spigot server. So that would be wasted effort. Option C is the clear winner here. # Bug Fix: Non-mob Entities Are Ignored by Tether Fixed a bug introduced in the 4.0.0 update where non-mob entities, like boats, would be ignored by tether. # Config Changes Updated verbiage from “default leashable mobs” to “default leashable entities”. **Config changes:** - `DEFAULT_LEASHABLE_MOBS` value has been changed to `DEFAULT_LEASHABLE_ENTITIES` - Backwards compatibility has been added for this. - `blacklisted-mobs` and `whitelisted-mobs` have changed to `entity-blacklist` and `entity-whitelist`. - Backwards compatibility has been added for this. Thanks @ Ken in my Discord for pointing this out!

# v4.0.0-beta.1 - Isolate Default Leashable Mobs ## ℹ️ This is a BETA Release This update includes significant changes. While extensive testing has been performed, some bugs may still be present. ## Overview This update changes how Tether operates at its core when it comes to mob leashing. Instead of treating every mob the same and completely overriding vanilla behaviours, Tether now deliberately distinguishes between mobs which are leashable by default in the game, and mobs which are not. This allows Tether to better handle leashing mechanics, and to not get in the way of vanilla behaviours since Tether can decide to let the game handle vanilla leashing. ## ❗ Minimum Version of 26.2 This update only supports Minecraft version 26.2 and onwards! ## 🎉 New Feature: Target Default Leashable Mobs in the Blacklist/Whitelist You can now write `DEFAULT_LEASHABLE_MOBS` in your blacklist/whitelist to target all mobs which are leashable by default. This is helpful, for example, for server administrators who like to allow only default leashable mobs plus one or two others. Thank you Ken and _das in my discord for the suggestions! ## ⚙️ Bug Fix: When the Squad Hops into Town Achievement "When the Squad Hops into Town" is an achievement which involves leashing all 3 types of frogs. This didn’t work because the game didn’t recognize that the player had done this, since Tether previously overrode the game’s vanilla leashing. Because of this overhaul, this bug, and potentially others like it that are unknown, are fixed. Thank you _das in my discord for reporting it! ## Tether ❤️ Kotlin This version of Tether also introduces the use of the Kotlin programming language! From this point on, Tether will prefer new contributions to be made in Kotlin where possible. Java is still completely welcome, and is necessary for maintenance of existing code.

# Fixed Named Lead Duplication Bug Fixed a bug where, when the player was holding a named lead in their hand and leashed a mob, the named lead wouldn't be removed from their inventory. When unleashing the mob, a lead would drop, duplicating the lead. Thank you TZ122 on github for reporting this bug!

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. ## Changelog ### 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.

- Fixed a bug where certain integrations wouldn’t enable properly. - Fixed a bug where fence leashing and mob-to-mob leashing wouldn’t respect land protection integrations. - In the config: **~~messages.target-mob-in-protected-land~~** and **~~messages.target-player-in-protected-land~~** have been replaced with **messages.leash-target-in-protected-land** - This change generalizes the land protection message to include mobs, players, and fence posts. - Made plugin prefix no longer bold. _Thanks to SirBedrock on GitHub and Ken in my Discord for the reports!_

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._

- For player leashing, when the invisible entity is killed upon unleash, it is now ensured that it won’t drop any XP. - Added official support for Minecraft version 1.21.11. - Updated to Java 21 (so from here on out new versions Tether only support Minecraft versions 1.20.5+).

Tether's first release on Modrinth! See all it's features up to version 2.12.2 in the plugin description.