
AdminWatchdog
AdminWatchdog lets you monitor what staff members do on your server. When an admin runs a command, changes gamemode, or takes items from creative mode, the plugin sends a message to your Discord channel. This helps server owners keep track of staff activit
Tags
Creators
Details
1.0
Compatibility
Changes
🚀 AdminWatchdog v1.0.0 - Initial Release
September 25, 2025
✨ New Features
🎯 Custom Command Responses
Configure custom Discord alerts for specific commands with role mentions:
custom-responses:
enabled: true
op: "🔐 **CRITICAL** - %player% used OP! <@&ROLE_ID> %time%"
"/stop": "🛑 **SHUTDOWN** - Console stopping server! %time%"
🔧 Smart Config Updates
- Automatic config migration preserves your settings
- New options added automatically without losing customizations
- Version tracking with
config-version: 1
💻 Console Command Monitoring
- Track console commands with custom responses
- Use
%sender%placeholder for console actions - Monitor critical server operations
🛡️ Production Ready
- Removed all development comments
- Enhanced error handling and performance
- Improved security and input validation
- Custom proprietary license for code protection
🎨 Core Features
- Discord Webhooks - Rich embeds with item images
- Creative Inventory Tracking - Monitor items taken from creative
- Command Monitoring - Track admin commands with permissions
- File Logging - Local logs with rotation
- Auto-Updates - Built-in update checker
📦 Installation
- Download the plugin JAR
- Place in your
pluginsfolder - Configure Discord webhook in
config.yml - Restart and enjoy!
🔧 Requirements
- Java 17+
- Minecraft 1.20+
- Paper/Spigot server
Download: Latest Release | Support: Discord | Sponsor: GitHub
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:eeVR5226:qyb5IoMa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eeVR5226:qyb5IoMa"
}
