All versions
0.1.2
Release
Enemy Lock-On 0.1.22 months ago 145
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
- Added a red X inside the white lock-on square whenever the currently locked entity cannot actually be hit because solid block collision geometry is obstructing its hitbox.
- The lock itself stays active when Break Lock When Obstructed is OFF, which remains the default.
- The red X automatically disappears the moment any sampled part of the entity's hitbox becomes directly reachable again.
- Visibility checks use the block's actual collision shape, rather than simply treating the entire block position as solid.
- Full oak-plank wall → red X stays visible.
- Fence → the system checks through its actual gaps.
- If part of the target hitbox becomes reachable through a fence opening → red X disappears.
- Move so the fence geometry blocks the hitbox again → red X returns.
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:LHLHcfms:qNtzlJHS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LHLHcfms:qNtzlJHS"
}

