All versions
1.1.0
Release
BS-AntiCheat 1.1.03 weeks ago 104
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
Platforms
Folia
Paper
Purpur
Changes
[1.1.0] - 2026-10-07
Added
- Minecraft 26.1â26.3 support: new attack and punch packets (PacketEvents 2.14), spear reach, Lunge, wind charges, bouncy blocks and geysers, new mounts and physics attributes.
- New checks: NoFall, Sprint (hunger/blindness/omni-sprint), Mace smash, CrystalAura/AnchorAura, PingSpoof and extended BadPackets.
Fixed
- Closed detection bypasses: ender pearl/chorus teleport grace, Timer pauses, packet bundling, oscillating or slowly sinking Fly/BoatFly, speed pulsing, dig-packet AutoClicker suppression, spoofed ground flag for InventoryMove, uncapped ping allowance.
- Fewer false positives: Jesus at shores and piers, flight/gamemode changes, fast-moving reach targets, vein-miner bursts (Nuker/FastPlace), team-fight KillAura, X-Ray in overgrown caves and dense veins, knockback in cobwebs/powder snow, riptide while gliding.
- Violation levels now survive a relog; punishment commands run in order on the correct Folia thread.
- PerformanceAnalyzer migration no longer imports Discord or silent-player settings into fresh installs; foreign keys from earlier imports are removed.
- Discord alerts share one rate limit per webhook and retry on HTTP 429; fallback log is flushed periodically.
Changed
- Timer check uses the client tick-end packet; lag detection uses a short window (per region on Folia).
- Update notice shows clickable Modrinth and CurseForge links to operators on join.
- Validation for all numeric config values;
clear --dbdeletes by player UUID. - Console messages are English throughout;
/acsilentcategory names come from the language files. - Various smaller thread-safety, memory and performance fixes.
API
ViolationEventnow fires on the thread owning the player (region thread on Folia), one tick later than before.
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:4qr15r67:JN0q6VeF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4qr15r67:JN0q6VeF"
}

