Links
Tags
Creators
Details
Licensed ARR
Published 11 months ago
Updated 11 months ago
All versions
2.4-alpha
Alpha
Aegis AntiCheat 2.4-alpha11 months ago 11
Compatibility
Minecraft: Java Edition
1.21–1.21.10
Platforms
Bukkit
Paper
Changes
2.4-alpha — Release (alpha)
- Primary goal: dramatically reduce false positives so normal players will not be kicked or banned.
- Timer detection rewritten:
- Uses per-interval mean and standard deviation on move events.
- Flags only when mean deviates from expected tick (50 ms) AND variance is low (consistent timing).
- Requires multiple confirmation streaks to declare a violation.
- Skips Timer check in noisy environments (gliding, in vehicle, in liquid, moving fast, bypass perms).
- Global confirmation streak system added:
- Many checks now require sustained confirmations (configurable per-check 'streak.*') before committing a flag.
- This reduces single-spike false positives caused by lag, teleport, or normal gameplay.
- Raised conservative thresholds and required more flags/kicks before punitive actions (kicks/bans).
- Added more refined FastBreak / Nuker handling and tuned weights to be conservative.
- Added client-brand join alerts and retained async webhook support for flags, kicks and joins.
- Improved null-safety, thread-safety and persisted kick counts are retained.
- Recommended: run on staging, collect logs for a day, tune streak thresholds and weights before enabling on production.
Notes:
- This is an alpha focused on safety (avoid false positives). It is intended for server operators to test and tune.
- If you want, I will add a /aegis info <player> diagnostics command that prints current score, flags, check streaks and last-detected client to help tuning.
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:o4vjlC3x:6r6KScF5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:o4vjlC3x:6r6KScF5"
}

