Links
Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 2 months ago
All versions
10.1.2
Release
[Fabric] 1.21-v10.1.22 years ago 2,781
Compatibility
Minecraft: Java Edition
1.21
Platforms
Fabric
Quilt
Supported environments
Client-side
Required content
Any compatible version
Changes
Latest changes (See all)
- fix armor bar not being moved correctly on fabric (c117f2c)
- reset sprite back to null if it is missing in config UI (5aecf80)
- run dev client window at 1280x720 (cc11f4d)
- replace ExpectPlatform with regular proxy style classes - ExpectPlatform is failing to randomly get applied on build (0d9fda3)
- fix config being overwritten on game start (b2f79ca)
- remove overflowing bars from curseforge and modrinth incompatible mods (806c2b5)
- allow OverlayHeart to have no absorption or health hearts (bf037df)
- add support for opaque flag from the API (3d109b0)
- add opaque flag to OverlayHeart (366e86e)
- go back to defaultBlendFunc after coloring a HeartDrawing (d8594b1)
- raise version constraints to 1.21+ (0901ec1)
- fix dependencies (93497b4)
- initial changes for 1.21 (e1f929d)
- add HeartSingleRenderEvent and add more details to HeartRenderEvent in the API (8e83cab)
- change into default method, so it does not have to be implemented on the entrypoint (d91855f)
- version bump (107cbac)
- make overlay hearts an actual overlay (b19523b)
- fully rename effect heart to overlay heart (56b07fb)
- fix old method names (144bfc4)
- move api to its own submodules (e979320)
- Rename StatusEffectHeart to OverlayHeart (1207f68)
- gradle update and port of few changes made in backports (99fcec1)
- update all dependencies for release (b2f7e73)
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| colorfulhearts-fabric-1.21-10.1.2-sources.jar | Unknown | 93.12 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:wQfMUdZT:IMAstosK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wQfMUdZT:IMAstosK"
}

