Tags
Creators
Details
0.4.0+1.21.1-fabric
Compatibility
Changes
Changelog
All notable changes to this project will be documented in this file. See conventional commits for commit guidelines.
0.4.0 - 2026-09-08
Chores
Features
-
(stonecutter) add 1.21.1 version support for both fabric and neoforge - (2300556) - lívia
-
(drops) add creative player drop chance and improve spawn logic - (2981704) - lívia
-
(assets) add heart shard item model and textures - (9f81fe4) - lívia
-
(registry) add item registry with platform-specific implementations - (6feb570) - lívia
-
(sounds) add pickup sound - (f1a2fa0) - lívia
-
(registry) add sound registry with platform-specific implementations - (0c4ae83) - lívia
-
(sounds) improve sound effects with better pitch and volume - (51a7994) - lívia
-
add logger and improve
Identifiercompatibility across versions - (125af26) - lívia
Fixes
-
(neoforge) add version-specific dist check for 1.21.1 compatibility - (f42f68d) - lívia
-
(registry) add version-specific entity type building for 1.21.1 - (f16b8d2) - lívia
-
(renderer) add version-specific render state for 1.21.1 compatibility - (c9912ec) - lívia
-
(entity) improve ground collision - (fcbcef4) - lívia
-
(fabric) register items and sounds in fabric entrypoint - (8bec362) - lívia
Other
Performance
- (build) enable gradle caching and increase memory allocation - (1563803) - lívia
Refactoring
-
(config) extract default values to constants for better maintainability - (dfb40fc) - lívia
-
(physics) improve smooth attraction behaviour - (403d77a) - lívia
-
(build) use configured minecraft version ranges instead of hardcoded values - (0876117) - lívia
-
(renderer) use fabric API entity renderer registry for compatibility - (4638c04) - lívia
-
(renderer) use item stack rendering instead of custom plane geometry - (08d523e) - lívia
Optional dependencies
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:hwNYMvXr:U6N5WZP9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hwNYMvXr:U6N5WZP9"
}


