Tags
Creators
Details
Licensed ARR
Published last year
Updated 5 months ago
All versions
1.1
Release
Dynamic Damage 1.1last year 248
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Added
- Initial release of Damage Indicator mod
- Animated damage indicators with smooth pop and fade animations
- Full Cloth Config API integration for in-game configuration
- ModMenu support for easy access to settings
- Configurable display settings:
- Toggle indicators on/off
- Adjustable max render distance (8-128 blocks)
- Customizable base scale (0.01-0.1)
- Text customization:
- Custom damage format strings
- Toggle between decimal and integer display
- Color customization:
- Separate colors for normal and critical damage
- Animation settings:
- Configurable lifetime (500-5000ms)
- Adjustable pop duration (50-1000ms)
- Custom fade start time (500-4000ms)
- Variable vertical speed (0.5-5.0)
- Adjustable horizontal spread (0.0-2.0)
- Critical hit settings:
- Custom scale multiplier for crits (1.0-2.0)
- Separate pop effects for critical and normal hits
- Proper critical hit detection based on player state
- Performance optimizations:
- Squared distance calculations
- Efficient CopyOnWriteArrayList for thread safety
- Configurable distance culling
- Networking system with custom payloads
- Full localization support (English and Russian)
- Comprehensive documentation
Optimizations
- Extracted magic numbers to constants for better performance
- Optimized distance checks using squared distance
- Improved critical hit detection algorithm
- Thread-safe indicator management
Optional dependencies
Any compatible version
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:5yjK29ni:OJJvprmq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5yjK29ni:OJJvprmq"
}

