All versions
1.0.1
Release
Custom Hit Color 1.0.12 months ago 896
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
HitColor Changelog
[1.1.0] — 2025 (Minecraft 1.21.1)
Added
- Health-Based Color mode — the hit flash now dynamically shifts from green (full HP) → yellow (half HP) → red (near death), giving you instant visual feedback on an entity's health. Overrides the main hit color when enabled.
- Flash Intensity slider — control how opaque the hit flash is, from 0% (invisible) to 100% (full). Useful if the default flash feels too aggressive.
- Custom Player Color — assign a separate hit flash color specifically for your own character, so you can instantly tell apart your own damage from a mob's.
- Dedicated "Player" category in the config screen — player-specific settings are now grouped separately in the ModMenu GUI for clarity.
Changed
RedTintVertexConsumernow accepts a pre-resolved ARGB color and an alpha multiplier, instead of reading config values per-vertex. This is cleaner and makes future color modes easier to add.LivingEntityRendererMixinnow detects whether the entity being rendered is the local player (MinecraftClient.getInstance().player) and passes that context to color resolution.HitColorConfignow uses a clean innerDataclass for JSON serialisation instead of mixing static and instance fields. Existing config files are not compatible and will be regenerated on first launch.- Config GUI split into two categories: General and Player.
Fixed
- Alpha multiplier is now clamped to
[0.0, 1.0]on load, preventing invalid values from a hand-edited config file causing visual glitches.
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:x1ODWD2A:TfrcCfxo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:x1ODWD2A:TfrcCfxo"
}

