All versions
1.2.10
Release
Counter 1.2.105 days ago 146
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
Platforms
Bukkit
BungeeCord
Folia
Paper
Purpur
Spigot
Changes
New
- New tick-exact checks for scaffold, nuker, surround, silent swaps, and anchor and bed aura.
- Stepping up a full block in one tick is caught.
- Killaura and reach checks now also cover mobs: aim, attacking from inside a menu, attacking while blocking, and reach on mobs that stand still.
- Killaura is now checked while riding and during elytra boosts.
- High jump is caught on the takeoff tick.
- Optional fast punish for killaura: add
post_tickandmultitoproofand they punish in fewer flags. Off by default, leave it off if your proxy runs ViaVersion.
Improved
- Players on clients newer than your PacketEvents build now get the right physics.
- Timer can no longer hide behind right-click spam or teleports.
- Phase can no longer switch itself off by placing or breaking blocks.
- Wind charge, pearl and vehicle exemptions are shorter and much harder to abuse.
- Mob reach and hitbox checks keep working while the player lags, and on killing blows.
- Anti knockback is now checked properly at low ping.
- High ping players can no longer dodge a punish by going quiet or relogging. A single real lag spike is still let off.
- Less work per move and per packet, and spectators skip the physics engine.
- The database reconnects on its own and never counts a flag twice across a network.
Fixed
- Older clients on networks running ViaVersion on the proxy no longer flag killaura.
- Fake Bedrock IDs and a fake Geyser brand no longer skip checks.
- Plugin area damage (mcMMO, custom enchants) no longer counts as reach.
- Soul speed on honey and sneaking off ledges no longer flag.
- Memory leak when fighting lots of mobs.
- No flag data is lost on a crash or shutdown.
- A typo in config.yml on first start no longer makes alert only checks punish.
- Alert history now shows in each staff member's own language.
- Unfreezing an offline player now works.
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:wO6apIVf:g55VxfzP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wO6apIVf:g55VxfzP"
}

