Links
Tags
Creators
Details
All versions
1.2.3.2
Beta
SentinelCore - AntyCheat 1.2.3 [2]3 months ago 9
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
1.2.3 [2] - Flight Detection Overhaul
Added
- Ground Spoof detection - new dedicated check that verifies the client's
onGroundflag against the server's own physical collision test, catching players who fake ground contact (e.g. to suppress fall damage or slip past hover detection). - MotionY physics-curve check - Flight now simulates vanilla's actual vertical physics tick-by-tick and flags clients that deviate from it, catching subtler Fly hacks that fake a "legal-looking" trajectory instead of holding altitude outright.
- Vertical grace periods - knockback, explosions, Slime Block/Bed bounces, Wind Charge, and vehicle exits now grant a temporary, magnitude-scaled window where vertical checks relax, instead of a blanket "ignore everything" exemption.
- Position correction - once Flight/Ground Spoof evidence crosses the configured VL threshold, the player is reverted to their last confirmed safe ground location rather than just having the packet cancelled.
- New config sections:
checks.flight.*andchecks.ground-spoof.*, fully validated and hot-reloadable.
Changed
- Flight's hover detection now requires only 5 consecutive near-zero-delta ticks (down from 12) while airborne, tightening detection without needing a long airtime cap.
- Rewrote
FlightCheckinternals to reduce false positives around slime bounces, bed bouncing, and vehicle dismounts.
Fixed
- Slime Block, Bed, and vehicle-exit interactions no longer risk being misread as hover/motion anomalies.
Full technical detail available on request - this release focused on the Flight/Hover/GroundSpoof detection module specifically.
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:zhvEipaA:kTFEhMMb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zhvEipaA:kTFEhMMb"
}

