Tags
Creators
Details
All versions
1.0.5
Release
Hitbox Reveal 1.0.56 months ago 78
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Unavailable version
Changes
1.0.5 — Entity Hitboxes, Solo Auto-Reveal, Pearl Trajectories & More
New: Entity Hitboxes
- TNT Minecart hitbox with configurable color, size multiplier, and outline-only mode
- Fireball hitbox (ghast, blaze, etc.) with same options
- Boat & Chest Boat hitboxes with same options
- All entity hitboxes respect the existing "Only enemy projectiles" toggle
New: Gradient Flip
- Option to reverse the gradient direction (bottom-to-top instead of top-to-bottom)
New: Player Box Size Presets
- Three presets: Default, Minimum, Maximum
- Minimum and Maximum scales are fully configurable
- Useful on servers with custom entity scaling
New: Solo Auto-Reveal Max Players
- Slider to set how many nearby players can be auto-revealed at once (1–5)
- Replaces the old hardcoded solo-only (==1) behaviour
New: Pearl Trajectories
- Enemy ender pearls leave a visible cylindrical trail as they fly
- Trail uses a smooth color gradient (start → end), configurable opacity, width, length, and linger time
- Optional: show trails on your own pearls too
- Landing beam marks where a pearl lands — vertical beam with animated lightning effect
- Portal particles spawn on impact
- All settings under the new Trajectories tab in the config screen
New: Trajectories Config Tab
- New tab in the config screen (
B) with Pearl Trail and Landing Beam groups
Credits
- Pearl trajectory rendering adapted from Pearl-Trajectories-Fabric by szokk (MIT License)
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:2p8w3kdG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8JVvckM3:2p8w3kdG"
}

