Tags
Creators
Details
All versions
1.0.3
Release
Hitbox Reveal 1.0.36 months ago 28
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Unavailable version
Changes
1.0.3
New Features
- ModMenu support — config screen now accessible via the ModMenu mod list
- YACL config screen — completely rebuilt config UI using YetAnotherConfigLib with tabbed layout, proper sliders, colour pickers, and descriptions for every option
- Gradient system — toggle gradient fill on/off; choose a single top colour or enable per-state gradients with separate top colours for default, close range, and crit states
- Fade out — hitbox opacity smoothly fades as the reveal timer expires
- Pulse animation — hitbox opacity animates with a configurable pulsing effect and speed
- Corner-only outline — render clean bracket-style corners instead of a full outline, with adjustable corner length
- Range indicator — circle on the ground showing your close-range threshold radius, with configurable colour
- Self-reveal — show your own hitbox in third-person, either permanently or only after hitting someone
- Dedicated keybind category — toggle and config keys now appear under their own HitboxReveal category in controls
Changes
- Config screen tabs ordered as: Options → Colors → Gradient → Effects
- Outline toggle no longer hides the translucent fill — they are now independent
- Line width scales with distance so outlines stay visually consistent at range
- Hitbox rendering now uses smooth sub-tick position interpolation for fluid movement
Fixes
- Config screen crash on open fixed
- Gradient colours now correctly applied per state when per-state mode is enabled
Optional dependencies
Unavailable 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:8JVvckM3:vPd5cRAw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8JVvckM3:vPd5cRAw"
}

