Tags
Creators
Details
4.0.0-beta.3
Compatibility
Changes
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.
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:TMhrpWMa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hs6CnYEL:TMhrpWMa"
}

