Tags
Creators
Details
All versions
1.0.7
Release
Hitbox Reveal 1.0.75 months ago 368
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Unavailable version
Changes
v1.0.7
New Features
- Reveal All button — instantly reveals every player in the world permanently, bypassing range and count limits (same as F3+B but for players only)
- Reset Defaults button — resets every setting to its default value in one click
- Close color toggle — new option to disable the close-range color; targets will use the default color instead
- Crit color toggle — new option to disable the crit-ready color; targets will use the default color instead
- Pearl trail fade-out — trails now smoothly fade out after a pearl lands, lingering for a configurable duration before disappearing
Changes
- Line width slider minimum lowered from
2.0to0.5, allowing thinner outlines - Solo Auto max players input changed to a number field with a range of 1–100 (was a slider capped at 5)
- Entity fill now renders a proper top-to-bottom color gradient using the gradient top color setting
Performance
- Pearl trail renderer is now zero-allocation per frame — pre-computed sin/cos tables and reusable static arrays replace per-frame heap allocations
- Entity loop now uses a 64-block bounding box query instead of iterating all world entities, reducing CPU overhead at high entity counts
- Pearl trail search gated behind
pearlTrailEnabled— skipped entirely when the feature is off
Bug Fixes
- Pearl trails now use
LinkedListfor O(1) removal from the front instead of shifting anArrayList - Removed unused saturation/brightness color fields (
satDefault,satClose, etc.) that had no effect - Removed broken hit sound settings (
hitSound,hitSoundVolume) that referenced a non-existent sound API
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:oruOWMkO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8JVvckM3:oruOWMkO"
}

