Tags
Creators
Details
All versions
2.1.0
Release
Fiw AntiCheat 2.1.0 (fabric 1.20.1)6 days ago 15
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
[2.1.0] - Tiered per-player exemptions
Added
- Added
/fiwmods exempt add <player> <tier> [hours] [preset],/fiwmods exempt remove <player>, and/fiwmods exempt listcommands for granting, revoking, and reviewing per-player exemption tiers. - Added six exemption tiers, replacing the old all-or-nothing bypass list:
bypass- skips scanning entirely and always allows the player to join (the original bypass behavior).silent- still scanned and profiled, but never kicked and never alerts staff; only a quiet console log line records what they're running.monitor- still scanned, profiled, and alerts staff, but never kicked.quiet_kick- normal detection and kick behavior, but the staff chat alert is suppressed.preset:<strict|balanced|lenient|custom>- evaluates that one player against a pinned preset instead of the server's global preset.force_block- always kicked on join, before any scan, for repeat offenders regardless of what mod list they report.
- Added optional expiry (
[hours]) on any granted exemption; expired grants are purged automatically the next time that player is evaluated. - Added
exemptions.escalation_rulesconfig: admin-defined rules that auto-apply a tier (e.g.force_blockfor 4 hours) once a player racks up a configured number of detections within a time window. An escalation never overrides a tier an admin already granted. - Added
exemptions.player_overridesconfig map backing the new tiers (exemptions.bypass_playersis unchanged and still works for permanent full bypasses).
Changed
- The legacy
exemptions.bypass_playerslist is still honored as a permanentbypassgrant; new grants from/fiwmods exempt addare written toexemptions.player_overridesinstead. - Floodgate/Geyser auto-exemption now resolves to the
bypasstier internally (same behavior as before, just expressed through the new tier system).
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:BUXFUwPg:gXwiMQAF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BUXFUwPg:gXwiMQAF"
}

