HarvestFlow v1.11.1 - Fix World Guard Integration
This is a quality-of-life update focused on improving compatibility with other plugins, fixing persistent issues with region protection, and introducing a powerful new debugging tool for server administrators.

✨ New Features
Player-Specific Debug Mode
A new administrative command, /hf debug, has been introduced to make troubleshooting easier than ever.

• How it works: When a player with the harvestflow.admin permission runs /hf debug, it toggles a personal debug mode.
  
  
• In-Game Feedback: Instead of spamming the server console, all debug checks and steps are sent directly to the player's chat in real-time.
  
  
• Multi-Admin Friendly: Multiple administrators can enable their own debug modes simultaneously without interfering with each other or the server console. This allows for clean and efficient problem-solving, especially on live servers.

️ Fixes & Improvements
Major Compatibility Rework
The core event handling for harvesting has been completely rewritten to prevent conflicts with other plugins.

• No More Event Cancellation: HarvestFlow no longer cancels the BlockBreakEvent. It now allows the event to complete, ensuring that other plugins (like AuraSkills, Jobs, etc.) can correctly process the action and award players with XP, money, or other rewards.
  
  
• Seamless Integration: This change makes HarvestFlow significantly more compatible with the broader plugin ecosystem, allowing it to function as a seamless enhancement to your server's farming experience rather than a replacement.

Intelligent WorldGuard __global__ Handling
A persistent issue where HarvestFlow would not function in wilderness areas protected by WorldGuard's __global__ region has been resolved.

• Problem: Many servers set block-break: deny in the __global__ region to protect the wilderness. Previously, this would prevent HarvestFlow from working outside of claimed areas.
  
  
• Solution: The plugin is now smart enough to detect why an action is being denied. If the denial is only coming from the __global__ region (and not from a specific, player-made region), HarvestFlow will now safely override the denial and function as expected. This means you no longer need to set block-break: allow in your global region.

WorldGuard Integration Overhaul

• Fixed respect-named-regions: false Not Working: A major bug has been resolved where setting respect-named-regions to false in the config.yml did not correctly bypass WorldGuard's block-break flag. Previously, if a region had block-break set to deny, players were still unable to harvest crops even when the bypass was intended to be active.
  
  
  Code (Text):

  worldguard-integration:
    # If true, HarvestFlow will respect the 'block-break: deny' flag in named regions.
    # This is the safest option to prevent players from farming in protected areas.
    # If false, HarvestFlow will BYPASS the 'block-break: deny' flag for its crops in ALL regions.
    # Use 'false' only if you want HarvestFlow to work anywhere, regardless of protection.
    respect-named-regions: true
• How it was fixed: The plugin's event listener for block breaking has been re-prioritized to run after WorldGuard's listener. This ensures that HarvestFlow can now properly evaluate and override WorldGuard's decision to cancel a harvest event, making the respect-named-regions: false setting function as intended.
  
  
• What this means for you:
  
  • You can now confidently set respect-named-regions: false to allow HarvestFlow's mechanics to work globally, ignoring any and all block-break flags set by WorldGuard. If you want to respect protections, simply keep the setting as true.
    

Thank you for your feedback and bug reports! Please update to ensure the best compatibility with region protection plugins.
Configuration Robustness

• Fixed a logic bug related to how default configurations were handled, ensuring that user-made changes are always preserved correctly during updates.
  
  
• Cleaned up the default config.yml with better comments and examples to prevent common configuration errors.