
AntiAutoFishing
AntiAutoFish is a comprehensive anti-autofish plugin for Paper/Spigot servers. Unlike other plugins that use simple detection methods, it offers an intelligent CAPTCHA system with rewards, a FishBan system for temporarily banning suspicious players, and a
v1.5
Compatibility
Changes
AntiAutoFishing v1.5 - Changelog
š New Features
- Leaderboard System - New commands
/aaf top [page]and/aaf top fails [page]to view top players - Asynchronous Discord Webhook - Discord notifications now run asynchronously with 5s timeout (no more server freezes!)
- Automatic Language Updates - Language files are automatically updated with missing messages from the JAR
- Config Auto-Update - Missing sections in config.yml are automatically added (e.g., Discord module)
š Leaderboard Commands
| Command | Description |
|---|---|
/aaf top |
View top 10 players (most successful CAPTCHAs) |
/aaf top 2 |
View page 2 of leaderboard |
/aaf top fails |
View top 10 players (most failed CAPTCHAs) |
/aaf top fails 2 |
View page 2 of fail leaderboard |
š§ Improvements
- Discord webhook now runs asynchronously with 5-second connection/read timeout
- Language files now auto-update with missing messages from JAR (preserves custom translations)
- Config.yml now auto-adds missing sections (
Modules.Discord,Log.Life, etc.) - Better config loading order (fixes locale detection issues)
- Removed
loadDefaults()that was overwriting user configs
š Bug Fixes
- Fixed Discord webhook causing server freeze/crash (now fully async)
- Fixed locale not loading from config.yml (now correctly reads
Localesetting) - Fixed config.yml being overwritten on startup
- Fixed language files not updating with new messages
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:IfFeBkey:w1PMpRTE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:IfFeBkey:w1PMpRTE"
}
