Links
Tags
Creators
Details
Licensed ARR
Published 11 months ago
Updated 11 months ago
All versions
2.5-beta
Beta
Aegis AntiCheat 2.5-beta11 months ago 12
Compatibility
Minecraft: Java Edition
1.21–1.21.10
Platforms
Bukkit
Paper
Changes
2.5-beta — Release (beta)
- Focus: Safety-first anti-cheat improvements to minimize false positives for normal players.
- New detections:
- AimAssist: heuristic detection using low-variance aim changes during hits; requires multi-confirmation before action.
- VelocitySpoof: detects inconsistent or missing knockback responses with confirmation streaks.
- VClip: detects suspicious vertical teleport-like movement not explainable by normal gameplay.
- Timer detection upgraded:
- Uses per-interval mean + standard deviation.
- Requires sustained deviation + low variance and environment filters (no gliding, no vehicle, low horizontal speed).
- Confirmation streaks required before applying full violation.
- Global confirmation-streak system introduced:
- Many checks now require multiple confirmations (configurable) before committing a violation and adding weight.
- Decay reduces streaks over time to avoid stale confirmations.
- Conservative enforcement:
- Raised score thresholds and number of flags required to kick/ban.
- Default behavior ensures normal players are not kicked/banned; intended for staging validation and tuning.
- Added diagnostics command: /aegis info <player> (shows score, flags, streaks, client).
- Client-brand join alerts retained; webhook integration async and optional.
- Persistence: kick counts saved in config; bans take effect only after multiple kicks as configured.
- Continued hardening: null-safety, thread-safe collections, safe main-thread kicks/bans and async webhook calls.
- Recommended: deploy to staging, gather logs for 24–72 hours, use /aegis info to assist tuning, then adjust streaks/weights.
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:zixCHFMV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:o4vjlC3x:zixCHFMV"
}

