Tags
Creators
Details
2.0.0
Compatibility
Changes
TurtleLib 2.0.0 is a breaking release for mod developers: new package names, the MIT license, a reworked update checker, and no more translation helpers. Players only need to update TurtleLib together with the mods that require it.
Compatibility
- New packages: All classes moved from
com.github.hrobasti.turtlelibtonet.kroet.turtlelib; mods built for TurtleLib 1.x must be updated and do not run with 2.0.0. - Update together: Install TurtleLib 2.0.0 only together with mods that require it (e.g. PermaClicker 2.0.0).
- Removed helpers:
LangLoaderandMessageServiceare gone; mods translate with Minecraft's own lang files. - UpdateChecker API: One constructor with channel, Minecraft version and loader; the result lists the newest release with its link and an error reason per platform.
New features
- Core jar: Every release now includes
TurtleLib_x.y.z_core.jarfor compiling mods against TurtleLib; it is not meant for themods/folder.
Fixes
- Version comparison: A leading
v, build metadata such as+26.3and pre-release numbers such asbeta.2are now compared correctly. - Update check: No longer fails when a platform is unreachable, reads CurseForge results correctly and only counts releases for the given loader and Minecraft version.
- NeoForge warning: The "deprecated logoFile" warning no longer appears in the NeoForge log.
Other
- Mod Menu: Mod Menu may now check TurtleLib for updates as well.
- Mod details: Updated description, icon and links in Mod Menu and the NeoForge mod list.
- MIT license: TurtleLib is now licensed under MIT (previously Apache-2.0).
- Build from source: The repository now builds on its own, without the development workspace.
Full Changelog: https://github.com/hrobasti/turtle-lib-mod/compare/1.3.0...2.0.0
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| TurtleLib_2.0.0_MC-26-3_FABRIC_0-19-5-source.jar | Sources jar | 52.29 KiB |
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:hLEZN8uo:I80nS7AF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hLEZN8uo:I80nS7AF"
}

