Tags
Creators
Details
1.0.2
Compatibility
Changes
🇪🇸 Español
Se cambió el sistema de evolución para que las herramientas ya no progresen únicamente al romper bloques:
• Los picos, hachas y palas siguen progresando al romper bloques válidos.
• Las azadas progresan al labrar tierra válida y cosechar cultivos maduros.
• Las espadas progresan al conseguir bajas directas mientras se tienen en la mano.
• Los menús, el lore, los mensajes, /toolinfo y Discord ahora utilizan unidades dinámicas, como bloques, labores, bajas, entre otras.
🇺🇸 English
The evolution system has been changed so tools no longer progress only by breaking blocks:
• Pickaxes, axes, and shovels still progress by breaking valid blocks.
• Hoes progress by tilling valid soil and harvesting fully grown crops.
• Swords progress through direct kills while holding the sword.
• Menus, lore, messages, /toolinfo, and Discord now use dynamic units such as blocks, farming actions, kills, and more.
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:GSB9UeFn:UHRSJmGH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GSB9UeFn:UHRSJmGH"
}

