HarvestFlow Version 1.17.2 - Patch Notes
This is a maintenance update focused on correcting the Area of Effect (AoE) harvesting permission logic to ensure it functions as intended and is easier for server administrators to configure.

Bug Fixes & Logic Corrections

• Fixed AoE Harvest Permission Logic: The core logic for determining a player's harvest radius has been completely overhauled to be more strict and intuitive when use-permissions is enabled in config.yml.
  
  • When use-permissions: true, the plugin now exclusively relies on harvestflow.area.radius.<number> permissions to grant AoE capabilities. The radius value in config.yml is ignored in this mode.
    
    
  • A player's effective radius is determined by the highest harvestflow.area.radius.<number> permission they possess. For example, a player with both .radius.1 and .radius.2 will correctly receive the 5x5 area from the .radius.2 permission.
    
    
  • Players who have the base harvestflow.area.use permission but lack a specific harvestflow.area.radius.<number> permission will now correctly have an effective radius of 0 (single-block harvesting only). This prevents unintended AoE harvesting from the config's fallback value.
    
    
  • If a player attempts an area harvest action without the required radius permissions, the action is now fully cancelled instead of defaulting to a single-block harvest.
    

Improvements

• Enhanced Debug Logging: The permission check for harvest radius is now much more detailed. When an administrator enables debug mode (/hf debug), they will see a step-by-step breakdown in chat that explains exactly how the plugin determined the player's effective radius. This makes it significantly easier to diagnose permission issues, especially those caused by wildcard permissions (e.g., harvestflow.*).
  

For Server Administrators
If you are using a permissions plugin like LuckPerms and grant players wildcard permissions (e.g., harvestflow.*), please be aware that this will grant them the highest possible radius permission (harvestflow.area.radius.10). To correctly limit their radius, you must use "negative permissions".

Example: To give a group a maximum 3x3 (radius 1) area, you must negate the permissions for all higher radii:

• lp group <name> permission set harvestflow.area.radius.1 true
  
  
• lp group <name> permission set harvestflow.area.radius.2 false
  
  
• lp group <name> permission set harvestflow.area.radius.3 false
  
  
• ...and so on.