Tags
Creators
Details
1.0
Compatibility
Changes
⭐ Damage Profiling Suite
A Precision Combat Analytics Toolkit for Minecraft Forge 1.20.1
Tags: Combat • Analytics • Utility • Developer Tools • HUD • Profiling • DPS • BigInteger • Forge 1.20.1
🔍 Overview
Damage Profiling Suite is a lightweight, developer‑focused combat analytics mod built for creators who need accurate, readable insight into Minecraft’s damage engine. Whether you’re balancing bosses, tuning weapons, or analyzing player performance, this suite delivers precision without bloat.
📊 Core Features
Real‑Time Damage Tracking
- Profiles every hit as it happens
- Displays source, amount, timing, and type
- Zero clutter, zero guesswork
DPS Graph Overlay
- Clean, minimal HUD
- Hit‑by‑hit damage visualization
- Burst and sustained DPS tracking
- Ideal for boss testing and weapon tuning
Per‑Entity Combat Reports
- Total damage dealt
- Damage type breakdown
- Critical hit detection
- Hit frequency and peak DPS windows
BigInteger‑Safe Calculations
- Supports extreme modded damage values
- No caps, overflow, or precision loss
🎨 Design Philosophy
- Pure utility — adds no gameplay content
- Clean, unobtrusive UI
- Event‑driven and optimized
- Fully compatible with other combat or boss mods
- Built for modders, pack makers, and theorycrafters
⚙️ Configuration
Customize the suite to your workflow:
- Toggle overlays
- Adjust smoothing and timing windows
- Control logging verbosity
- Enable developer debug output
🧪 Perfect For
- Mod developers balancing weapons or bosses
- Pack creators tuning progression
- Players optimizing builds
- Content creators showcasing combat mechanics
- Anyone who wants deeper insight into damage behavior
🚀 Lightweight. Accurate. Essential.
Install, fight, analyze — Damage Profiling Suite is your drop‑in toolkit for understanding Minecraft combat at a professional level.
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:iLyk0sPx:GOQQnaHd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iLyk0sPx:GOQQnaHd"
}

