Links
Tags
Creators
Details
Licensed ARR
Published 11 months ago
Updated 11 months ago
All versions
2.8-beta
Beta
Aegis AntiCheat 2.8-beta11 months ago 266
Compatibility
Minecraft: Java Edition
1.21–1.21.10
Platforms
Bukkit
Paper
Changes
2.8-beta — Release (beta)
Release date: 2025-10-28
Highlights:
- Packet-level optional integration:
- Aegis attempts to detect ProtocolLib at runtime (no compile-time dependency).
- If ProtocolLib is present, additional packet-level heuristics can be plugged in for better AimAssist/AutoBlock detection (implementation placeholder — operators with ProtocolLib may extend with packet listeners).
- Ping-aware thresholds:
- Configurable ping-scaling that relaxes thresholds for high-ping players to drastically reduce false positives.
- Base and max ping and a scale-factor allow operators to tune behavior per network conditions.
- Safety-first defaults:
- enforcement-mode: monitor|warn|enforce (default: monitor). In monitor mode Aegis only logs and sends soft confirmations; never kicks/bans.
- Kick and ban are disabled by default; operators must explicitly enable enforcement and tune weighting thresholds.
- False-positive reduction improvements:
- Larger Timer sample windows, stricter mean/stddev checks.
- Confirmation streak increases for sensitive detections (AimAssist, Timer, VClip, etc.).
- Environment filters: skip checks while gliding, in vehicles, in liquids, or when bypass perms are present.
- Multi-factor confirmation: many detections require multiple complementary signals to escalate.
- New & improved detections:
- Robust Timer, AimAssist, VelocitySpoof (AntiKB), VClip, AutoBlock (heuristic), AutoTool, AutoArmor, AutoClicker, FastBreak, Nuker, Reach, KillAura, Fly, Speed, Spider, Jesus, Phase, Elytra, FastPlace, FastBow, FastConsume.
- Diagnostics:
- /aegis info <player>, /aegis dumpflags, violations.log
- Soft violations are recorded in monitor mode with small weights so admins can tune safely.
- Operational guidance:
- Run in monitor mode on staging for 48–72 hours, gather logs and /aegis info outputs, then tune streaks and weights.
- For highest precision, integrate packet-level listeners (ProtocolLib or custom NMS hooks).
- Robustness:
- Null safety, thread-safe collections, all enforcement (kicks/bans) executed on main thread; webhooks async.
Notes for operators:
- ProtocolLib is optional: install it on your server if you want packet-level precision; Aegis will detect it automatically.
- Configure ping-scaling based on your player base network conditions.
- Keep enforcement-mode in monitor until you validate the logs.
If you want, I can:
- Add sample ProtocolLib-based packet listeners (as an optional separate module) to detect packet-level swings/blocks/packets for AimAssist and AutoBlock — this requires adding ProtocolLib plugin on your server.
- Provide a tuning guide with recommended starting adjustments for specific false positives you find in logs.
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:uRVIgtWf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:o4vjlC3x:uRVIgtWf"
}

