[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