All versions
1.0
Release
AdminAbuseDetector 1.0last year 175
Compatibility
Minecraft: Java Edition
1.21–1.21.5
Platforms
Bukkit
Paper
Spigot
Changes
AdminAbuseDetector - Changelog
Version 1.0-SNAPSHOT
🚀 Features
- Command Detection System: Monitors suspicious admin commands including
give,effect,summon,xp,gamemode,tp,teleport,kill,clear,enchant,setblock,fill,weather,time, anddifficulty - Multi-Source Monitoring: Detects commands from both players and console
- Discord Integration: Sends formatted webhook notifications to Discord with detailed embed messages
- Real-time Alerts: Instantly notifies online administrators when suspicious commands are detected
- Comprehensive Logging: Logs all detected command usage with timestamps and sender information
- Permission-based Notifications: Only sends alerts to players with
adminabuse.notifypermission or OP status
🔧 Technical Features
- Asynchronous Discord Webhooks: Non-blocking webhook requests to prevent server lag
- Configurable Settings: Discord webhook URL configurable through plugin config file
- Event Priority Handling: Uses appropriate event priorities for reliable command interception
- Rich Discord Embeds: Professional-looking Discord notifications with emojis, colors, and structured fields
- Error Handling: Robust error handling for network requests and plugin operations
📋 Configuration
discord.webhook-url: Set your Discord webhook URL in the config.yml file- Plugin automatically creates default configuration on first startup
- Clear console warnings if webhook URL is not configured
🛡️ Security
- Clean, auditable codebase
- Reliable detection system that cannot be easily bypassed
📊 Monitoring Capabilities
- Player Commands: Detects when players execute monitored commands
- Console Commands: Monitors console command execution
- Timestamp Logging: All events logged with precise timestamps
- Multi-channel Alerts: Notifications sent to Discord, in-game admins, and server console
This plugin is designed to help server administrators monitor and detect potential admin command abuse in real-time.
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:e33rNBG3:DTVMUOJY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:e33rNBG3:DTVMUOJY"
}

