Links
Tags
Creators
Details
0.1.5-a2
Compatibility
Changes
Summary
As per my previous post, I realized that tracking the hearth timer as a player attachment was a little silly when we have the ability to use a custom effect to do the same thing with less code required on my part. You'll note that this update is even smaller than the previous one, given the scope of the changes.
Hearth Changes
Hearth will no longer have a custom GUI. Instead, you'll gain a neutral effect that will end based on the configuration setting for the hearth cooldown. When you do not have that effect, you can use the Hearth ability.
I understand that this may be less obvious for first time players of the mod, but this will help reduce clutter and simplifies our code a lot.
Removed Features
- The Hearth GUI has been removed.
- The Hearth set of commands has been removed.
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:OoQc6URx:jcmxT9Gt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OoQc6URx:jcmxT9Gt"
}

