Tags
Creators
Details
4.0.0-beta.1
Compatibility
Changes
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.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:hs6CnYEL:HHpeCw9K"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hs6CnYEL:HHpeCw9K"
}

