[1.4.3] - 2026-07-09

The last few versions focused on Discord. This one focuses on the question that comes right after a Discord alert fires: "okay, but what has this person actually been doing?" Right now the honest answer is "scroll through commands.log and squint." Not anymore.

Added

• Audit history you can actually query. Every event AdminWatchdog already tracks (commands, gamemode changes, creative-inventory grabs, item drops and pickups) now also lands in a small local SQLite database. Run /adminwatchdog history <player> and you get their last 10 actions with timestamps, right in chat. Add a number to see more, up to 50. No more digging through log files when someone asks "wait, what did Steve actually do?"
• A brake on custom-response spam. If a monitored player finds a pattern that triggers your custom alerts and decides to mash it, your Discord channel used to mash right along with them. Each player (and the console) is now capped at 5 triggers per 60 seconds by default. Both numbers are yours to change in config.yml.

Changed

• Old audit rows clean themselves up. Default retention is 30 days; set logging.database-retention-days: 0 if you'd rather keep everything forever.
• Config auto-migrates like it always has. Update the jar, restart, and the new keys show up in your existing config.yml without you touching anything.

Under the hood

• Rewrote the Discord embed builder around Gson instead of hand-assembled JSON strings. Same messages, less code duplicated across the three embed types.
• Dropped a Guava cache that was caching something cheaper to just recompute. One less moving part.

Upgrade notes

• New config keys: logging.database-logging, logging.database-retention-days, custom-responses.rate-limit.*. All optional, all have sane defaults, nothing breaks if you ignore them.
• New permission: adminwatchdog.history (defaults to op).
• The jar is noticeably bigger this release because it now bundles sqlite-jdbc, native database drivers included, so you don't have to install anything extra on the server.

[1.4.2] - 2026-04-13

This release adds native Folia support while preserving Paper compatibility.

Added

• Marked plugin metadata as Folia-supported so the plugin can load on Folia.

Changed

• Replaced Bukkit scheduler usage with Folia-compatible AsyncScheduler and GlobalRegionScheduler APIs.
• Updated update-notification delivery to use per-player entity schedulers.
• Made async command update responses scheduler-safe for both player and console senders.
• Updated docs/build instructions and Paper API baseline to current 1.21 Folia-compatible versions.

Notes

• The new scheduler usage works on both Paper and Folia.

[1.4.1] - 2026-04-08

This update is mostly about clarity. The plugin behavior stays familiar, but the text around it should feel easier to read and edit when you are moving fast.

Added

• Creative material triggers for creative inventory, drop, and pickup events.
• New placeholders for material-trigger messages: %matched_material% and %material_pattern%.
• Dedicated update download message template for command output.

Changed

• Player-facing message rendering now uses MiniMessage.
• config.yml comments and user-facing response strings were rewritten in a more natural tone.
• messages.yml comments and message strings were rewritten to be clearer and less robotic.
• Legacy section-sign formatting in update logs was removed.

Notes

• Key names and configuration structure were not changed.
• If your existing custom messages still use legacy color codes, convert them to MiniMessage tags.

This release is focused on real-world moderation load: fewer duplicate pings, better abuse detection, and less webhook spam when people start command-flooding.

Added

• Threshold matching in custom responses. You can now match numeric arguments with >=, <=, >, <, and ==.
• Repeat-time triggers for burst detection (for both player and console commands).
• Discord batching system to merge multiple logs into fewer webhook requests.

Changed

• Custom responses are now split cleanly into:
  • custom-responses.player
  • custom-responses.console
• Command blacklist is now split too:
  • monitoring.command-blacklist.player
  • monitoring.command-blacklist.console
• Added custom-responses.suppress-normal-logging so you can avoid duplicate log lines when a custom alert already fired.
• Pattern matching now accepts config keys with or without leading /.

Examples

Custom response for large gives only:

custom-responses:
 enabled: true
 player:
  "give * * >=5": "⚠️ Large give detected by %player%: %command%"

Burst detection for repeated /smg:

custom-responses:
 repeat-triggers:
  enabled: true
  player:
   - pattern: "smg"
    count: 3
    interval-seconds: 10
    response: "⚠️ %player% repeated /smg %count%x in %interval%s"

Separate console blacklist (useful for menu automation noise):

monitoring:
 command-blacklist:
  enabled: true
  player:
   - "msg"
  console:
   - "dm open"

Discord batching for spam-heavy servers:

discord:
 batching:
  enabled: true
  interval-ms: 1000
  max-messages: 10
  max-combined-length: 1800

Notes

• If you want only alert messages and no duplicate normal command logs, set:
  • custom-responses.suppress-normal-logging: true
• For key-give monitoring, pair threshold patterns with repeat triggers to catch both suspicious amount and suspicious frequency.

Fixed

• Fixed wildcard pattern matching in custom command responses - Wildcard patterns like ban * * now properly match commands with arguments
• Fixed Discord mention support - Added allowed_mentions to webhook payload to enable role/user pings (use <@&ROLE_ID> for roles, <@USER_ID> for users)
• Fixed pattern priority - More specific patterns (with more words) are now checked before simpler patterns, ensuring correct matching when both exist

Improvements

• Build system migrated from Gradle to Maven - Improved build performance and compatibility
• Update checker optimization - Now only checks for updates on server startup instead of every 60 minutes
• Added detailed debug logging for pattern matching (enable with debug: true in config.yml)

Technical Changes

• Improved wildcard regex generation by properly escaping pattern parts
• Enhanced pattern sorting algorithm to prioritize longer, more specific patterns
• Removed unnecessary forward slash escaping in JSON payloads

Changes implemented for v1.2:

1. bStats Integration (Plugin ID: 29010)

   • Added metrics tracking for:
     • Discord enabled/disabled
     • Creative inventory monitoring enabled/disabled
     • Custom responses enabled/disabled
     • Item drop tracking enabled/disabled

2. Creative Item Drop Tracking (Feature Request #1)

   • New PlayerDropItemEvent handler tracks items dropped by creative mode players
   • New EntityPickupItemEvent handler logs when another player picks up the dropped items
   • Uses ConcurrentHashMap with automatic cleanup for efficient tracking
   • Tracking duration configurable (default: 5 minutes)
   • Same monitoring rules as creative inventory (respects bypass permissions, ops/permission settings)

3. New Config Options in config.yml:

   creative-item-drops:
     enabled: true
     track-pickup: true
     tracking-duration: 300
   

4. New Messages in messages.yml:

   • logging.creative-item-drop
   • logging.creative-item-pickup
   • discord.creative-item-drop
   • discord.creative-item-pickup

5. Discord Integration:

   • Rich embeds for item drops (📦 icon)
   • Rich embeds for pickups (⚠️ icon, orange color for alert)
   • Fallback to simple messages if embeds fail

6. Build Changes:

   • Shadow plugin updated to com.gradleup.shadow:9.0.0-beta12 for Gradle 9 compatibility
   • bStats relocated to com.github.tejaslamba2006.adminwatchdog.bstats

Version 1.1 Changelog

Bug Fixes

• Fixed custom-responses triggering for all players regardless of monitoring permissions
• Fixed creative inventory logging everyone in creative mode instead of respecting monitoring settings

New Features

• Wildcard command pattern matching for custom-responses
  • Exact match: ban matches /ban
  • Prefix match: lp user matches /lp user Steve ...
  • Wildcard match: lp user * permission set * matches specific argument patterns
• Bypass permissions for trusted admins:
  • adminwatchdog.bypass.commands - bypass command logging
  • adminwatchdog.bypass.creative - bypass creative inventory logging
  • adminwatchdog.bypass.customresponses - bypass custom response triggers
  • adminwatchdog.bypass.gamemode - bypass gamemode change logging

Performance Improvements

• Async file logging via CompletableFuture
• Async Discord webhook dispatch
• Guava cache for item data (512 entries, 30-min TTL)
• Converted ItemData to Java record

Code Quality

• Switch expressions in Commands.java
• Pattern matching instanceof
• Removed unused oldVersion parameter in ConfigManager
• Cleaner import organization

Compatibility

• Updated to Paper API 1.21.4
• api-version bumped to 1.21

🚀 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

1. Download the plugin JAR
2. Place in your plugins folder
3. Configure Discord webhook in config.yml
4. Restart and enjoy!

🔧 Requirements

• Java 17+
• Minecraft 1.20+
• Paper/Spigot server

Download: Latest Release | Support: Discord | Sponsor: GitHub