All versions
NeoForge-1.2.0-1.20.2-1.20.3
Release
Accurate Hitboxes 1.2.0-1.20.2-1.20.37 months ago 20
Compatibility
Minecraft: Java Edition
1.20.2–1.20.3
Platform
NeoForge
Supported environments
Client and server
Changes
v1.2.0
New
- Whitelist/Blacklist Mode Toggle: The
config/accuratehitboxes.jsonnow supports a"mode"field that can be set to"blacklist"or"whitelist". - In blacklist mode, entities in the list are excluded from accurate hitboxes — this is the default behavior.
- In whitelist mode, only entities in the list receive accurate hitboxes — everything else uses vanilla. Perfect for large modpacks!
Other Improvements
- Old v1.1.x configs using
blacklisted_entitiesare automatically migrated to the new format on first launch — no manual editing required.
Credits & Notes
- 💖 Special thanks to Crimson_Steve for suggesting the brilliant Whitelist mode idea!
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:tNiXqJK9:6LjeDYTq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:tNiXqJK9:6LjeDYTq"
}

