BlockRegen v2.3 - The Multiplier Update
This major update introduces the highly requested Regen Multiplier system, allowing players to invest in their mining progression, alongside a critical data persistence fix.

✨ New Features
New Regen Multiplier System
Players can now upgrade a personal multiplier that increases the amount of items dropped from regenerating blocks. This feature requires the Vault plugin and a compatible economy.

• Multiplier GUI: A new user-friendly GUI, accessible via /rm, allows players to view their current multiplier level and upgrade it.
  
  
• Admin Commands: Admins have full control with the new /rm set <player> <level> command to manage any player's multiplier.
  
  
• New Configuration: All aspects of the multiplier, including upgrade costs and max levels, are now managed in a new, dedicated multiplier.yml file.
  

Bug Fixes & Improvements

• Multiplier Data Persistence: Resolved a critical issue where a player's multiplier level would not save immediately after an upgrade. Player data is now saved instantly upon a successful upgrade, preventing any data loss or level rollbacks in the event of a server crash or restart.
  

BlockRegen v2.2 - The Compatibility & Optimization Update
This update focuses on improving compatibility with other plugins and introducing a new feature for server optimization based on user feedback.

Bug Fixes

• Placeholder API Compatibility: A major bug has been fixed where plugins using placeholder statistics (like Statistical) could not correctly track blocks broken by BlockRegen. This was especially noticeable with custom drops.
  • Technical Reason: The BlockBreakEvent was being completely cancelled, which prevented other plugins from processing the event.
    
    
  • Solution: The event handling logic in BlockBreakListener.java has been refactored. Instead of cancelling the event, BlockRegen now modifies its properties (e.g., clearing default drops and handling them manually). This makes the block break "visible" to other plugins, allowing them to correctly count scores and statistics while preserving all of BlockRegen's functionalities.

✨ New Features

• Auto EXP Pickup: A new option, auto-pickup-exp, has been added to blocks.yml.
  • Purpose: This feature is designed to improve server performance by reducing the number of spawned entities (experience orbs).
    
    
  • How it works:
    • When set to true, any experience points from breaking the block will be given directly to the player instead of being dropped as an orb.
      
      
    • When set to false (or if the line is omitted), the default behavior of dropping an experience orb will occur.
  • Example Usage in blocks.yml:
    
    COAL_ORE:
    replaced-block: STONE
    regen-delay: 5
    exp-drop-amount: '1-2'
    auto-pickup-exp: true # EXP is given directly to the player

⚙️ Technical Changes

• BlockBreakListener.java: Significantly refactored to no longer cancel BlockBreakEvent for regen blocks. It now uses event.setDropItems(false) and event.setExpToDrop(0) when custom drops or custom EXP handling is required.
  
  
• BlockData.java: Updated to include the new autoPickupExp boolean field, which is loaded from the blocks.yml configuration.

Thank you for your valuable feedback! These changes should provide a smoother and more optimized experience.

BlockRegen v2.1 - The Inventory Safety Update
This update introduces a new quality-of-life feature designed to protect players from accidentally losing valuable items.

✨ New Features

• Prevent Mining When Inventory is Full:
  • A new configurable option, prevent-break-on-full-inventory, has been added to config.yml.
    
    
  • When enabled (true), this feature prevents players from breaking a regenerating block if their inventory is full.
    
    
  • This is designed to stop players from losing valuable drops when they have no space to collect them.
    
    
  • The check is smart: it only prevents breaking if the block is configured to drop items (either natural-drop or custom-drops). Blocks that only run commands or give experience can still be broken normally.

⚙️ Configuration Changes

• A new option has been added to your config.yml:
  
  # config.yml
  # ... other settings
  
  # If true, prevents players from breaking a configured block if their inventory is full.
  # This check only applies if the block is set to drop items.
  prevent-break-on-full-inventory: true
  
  
• Your config.yml file will be automatically updated to include this new setting.

- Quick Fix MMOItems Tool Requirements

BlockRegen v2.0 - The Fortune Update
We are thrilled to announce a significant new feature that adds more depth and customization to your server's economy and progression: Fortune enchantment support for custom drops!

A special thank you to user MeoNguOfficial for suggesting this fantastic and detailed feature.

✨ New Feature: Fortune for Custom Drops
You can now enable and configure the Fortune enchantment to increase the yield of your custom-drops. This allows you to reward players for using enchanted tools, making custom mining feel more integrated with vanilla Minecraft mechanics.

How to Configure It: To enable this feature, simply add a new fortune: section to any custom drop in your blocks.yml file.

• Example:
  
  
  Code (Text):

  custom-drops:
    mystical_gem_drop:
     chance: 100.0
     amount: '1-2'      # The base amount without Fortune
     material: DIAMOND
     name: '&dMystical Gem'
     fortune:
       enabled: true    # Set to true to activate Fortune scaling
       multiplier:
         1: 1.5         # Fortune I multiplies the base amount by 1.5
         2: 2.0         # Fortune II multiplies the base amount by 2.0
         3: 2.5         # Fortune III multiplies the base amount by 2.5
• enabled: true: This switch activates the Fortune mechanic for this specific drop. If it's false or not present, Fortune will have no effect.
  
  
• multiplier:: Here, you define the exact multiplication factor for each level of the Fortune enchantment. The final drop amount will be calculated as (base amount * multiplier), then rounded.
  

⛏️ Clarification on Natural Drops (natural-drop: true)
As requested, here is a clarification on how Fortune works with natural drops.

Good news: Fortune for natural-drop works automatically, just as it always has!

If you have a block configured like this:

The plugin uses Minecraft's built-in drop system (block.getDrops()). This system natively supports Fortune without requiring any extra configuration from you. Players will get the expected increased yield from ores, just like in the vanilla game.

Summary of How Fortune Works
Drop Type

How Fortune Works

Is Configuration Needed?

Custom Drops

Scales the amount based on the multiplier you set.

Yes, you must add the fortune: section.

Natural Drops

Works automatically using vanilla mechanics.

No, it's built-in.

We hope you enjoy this new update that brings more dynamic and rewarding mining experiences to your server!

BlockRegen v1.9.1 - The Fortune Fix Update
This is a patch release that addresses a key issue with the Fortune enchantment to ensure it behaves exactly like vanilla Minecraft.

️ Fixes & Improvements

• Fortune Enchantment Fix:
  
  • The Bug: The natural-drop feature was not correctly interacting with the vanilla Fortune enchantment, preventing players from receiving the expected bonus drops.
    
    
  • The Fix: The plugin's drop calculation has been corrected. When natural-drop: true is set for a block, BlockRegen will now fully respect the drop amounts calculated by Minecraft's own Fortune logic.
    
    
  • Configuration Change: To allow Fortune to function properly, the natural-drop-amount setting is now automatically ignored when natural-drop is enabled. This ensures enchantments always behave as expected.
    

BlockRegen v1.9 - The Integration & Control Update
This update brings significant improvements to MMOCore integration, adds a powerful new WorldGuard feature, and enhances overall stability.

✨ New Features

• MMOCore Profession Experience: You can now grant MMOCore profession experience when a player breaks a configured block. Simply add a mmocore-exp section to any block in blocks.yml to define which professions receive experience and how much.
  
  • Example:
    
    DIAMOND_ORE:
    # ... other settings
    mmocore-exp:
    mining: 15 # Grants 15 EXP to the 'mining' profession
    woodcutting: 5
    
• WorldGuard Deny Region Override: A new option, break-regen-in-deny-regions, has been added to config.yml. When enabled (true), it allows players to break blocks configured in blocks.yml even inside a WorldGuard region where the block-break flag is set to deny. This is perfect for protecting an area while still allowing designated blocks to be farmed or mined.
  
  
• MMOCore Integration Toggle: A new enabled option has been added under the mmocore section in config.yml. This allows server owners to easily enable or disable the MMOCore integration without removing their configurations.
  

️ Fixes & Improvements

• Fixed MMOCore Integration: Completely overhauled the MMOCore experience handling. The plugin now uses the correct, up-to-date API methods (PlayerData -> PlayerProfessions -> giveExperience) to grant profession experience. This resolves previous errors, ensures stable integration, and guarantees experience is awarded correctly.
  
  
• Improved API Alignment: The internal code has been updated to better align with the latest MMOCore API structure, improving long-term stability and forward compatibility with future MMOCore updates.
  

BlockRegen v1.8 - The Custom Tool Update
This update introduces a major new feature that gives server administrators unprecedented control over block-breaking progression by allowing tools to be required by their specific name and lore.

✨ New Features
Advanced Tool Requirements (Name & Lore Matching)
You now have the power to require players to use custom tools with a specific display name and lore to break regenerating blocks. This is perfect for creating unique progression paths, integrating with custom item plugins, or designing special mining zones.

• How it Works: The tools-required list in blocks.yml now supports a new, more detailed format.
  
  
• Flexible Matching: You can require a tool by its material, its material + name, its material + lore, or all three combined.
  
  
• Backward Compatible: You can still list regular tools by their material name (e.g., NETHERITE_PICKAXE) in the same list, allowing for multiple ways to break a block.
  

⚙️ Configuration Example
Here is an example of how to configure a block that can be broken by either a special "Super Pickaxe" or a regular Netherite Pickaxe:

# blocks.yml

BlockRegen v1.7 - Commands on Custom Drop

This update introduces a highly requested feature that adds a new layer of customization to your server's economy and reward systems: Per-Drop Command Execution.

✨ New Features
Per-Drop Command Execution
You can now add a commands section directly inside a custom-drop configuration in your blocks.yml. These commands will only execute when that specific drop is successfully rolled (based on its chance) and given to the player.

This powerful feature allows you to:

• Grant players money, points, or temporary permissions for finding rare items.
  
  
• Broadcast a server-wide message when a legendary item is discovered.
  
  
• Trigger custom events, particle effects, or sounds specific to a drop.
  
  
• Create more engaging and rewarding mining experiences.
  

Example Configuration:

Improvements

• Refactored Drop Logic: The internal logic for handling block drops has been significantly refactored for better performance and reliability. This ensures that both items and their newly associated commands are processed correctly and efficiently.
  
  
• Modular Code Structure: Item creation and command execution logic have been made more modular, improving code clarity and making future updates easier to implement.
  

How to Update

1. Replace the JAR File: Simply replace your old BlockRegen.jar with the new v1.7 file in your plugins folder.
   
   
2. Configuration is Compatible: Your existing config.yml, regions.yml, and blocks.yml are fully compatible.
   
   
3. Use the New Feature: To use per-drop commands, simply add a commands: list to any of your existing custom-drops as shown in the example above.
   
   
4. Restart Your Server: It is highly recommended to perform a full server restart to ensure all changes are loaded correctly. Avoid using /reload.
   

BlockRegen v1.6 - The Admin & Experience Update!
This major update introduces powerful new tools for server administrators and significantly enhances the experience drop system to feel more intuitive and vanilla-like.

✨ New Features
Per-Player Debug Mode
Troubleshooting is now easier than ever!

• A new command, /blockregen debug (or /br debug), has been added for admins.
• This command toggles a personal debug mode. When enabled, all detailed debug information about block breaks is sent directly to you in the chat, keeping the server console clean for everyone else.
  

Admin Bypass Command
Admins no longer need to edit config files to build or clear areas.

• The new /blockregen bypass (or /br bypass) command allows admins to completely ignore the disable-other-break restriction.
• When bypass mode is active, you can break non-regenerating blocks normally without them being cancelled. Toggle it off to return to normal player behavior.
  

️ Improvements & Quality of Life
Intelligent Vanilla EXP Fallback
The experience drop system is now much smarter and more intuitive.

• If you do not specify an exp-drop-amount for a vanilla ore (like Diamond Ore, Coal Ore, etc.) in blocks.yml, the plugin will automatically drop the default vanilla amount of EXP.
• This means you get a natural, vanilla-like experience out of the box without needing to configure every single ore.
• You can still override this behavior by setting a custom exp-drop-amount for any block you wish.
  

Java 8 Compatibility

• Fixed a switch expression error by rewriting parts of the code to ensure full compatibility with Java 8, the version used by most Minecraft servers.

BlockRegen v1.5 - The Experience Update!
This version introduces a highly requested feature, allowing server administrators to have full control over experience drops from regenerating blocks.

✨ New Features
Configurable Experience Drops
Blocks managed by BlockRegen can now drop experience orbs when broken, just like vanilla ores!

• A new optional setting, exp-drop-amount, has been added to each block's configuration in blocks.yml.
  
  
• You can define a fixed amount (e.g., 5) or a random range (e.g., '3-7') of EXP to be dropped for each block individually.
  
  
• This feature is fully backward-compatible. If the exp-drop-amount line is omitted, the block will not drop any experience.

Example blocks.yml configuration:
️ Improvements

• The new experience drop feature works independently of the item drop system. This means players will still receive experience orbs correctly even when auto-inventory is enabled.

BlockRegen v1.4.1 - The Smart Compatibility Update!
This update focuses on intelligent plugin compatibility and improving the user experience by preventing conflicts with other popular server plugins.

✨ New Features
Smart HarvestFlow Compatibility
BlockRegen now automatically detects if the HarvestFlow plugin is installed on your server.

• If HarvestFlow is detected, BlockRegen will gracefully ignore all crop-breaking events (for wheat, carrots, potatoes, etc.), allowing HarvestFlow to manage them without any conflict.
  
  
• This ensures that you can use both plugins together seamlessly, even with disable-other-break set to true in BlockRegen's config.
  

️ Bug Fixes & Improvements

• Resolved Plugin Conflict: Fixed a critical issue where enabling disable-other-break: true would completely block HarvestFlow's functionality, preventing players from farming.
  
  
• Maintained Block Protection: If HarvestFlow is not detected on the server, the disable-other-break feature will continue to function as intended, protecting crops and other non-configured blocks from being destroyed.
  
  
• Code Cleanup: Removed all debug messages from the console output for a cleaner server log.
  

BlockRegen v1.4 - The MMOItems Integration Update!
This version introduces significant feature enhancements, focusing on deeper integration with other popular plugins like MMOItems and expanding the capabilities of existing features.

✨ New Features
MMOItems Tool Requirement Support
You can now require players to use specific tools from the MMOItems plugin to break regenerating blocks. This allows for creating powerful, custom mining progression tied directly to your MMOItems configuration.

• Configuration: Simply add the tool to the tools-required list using the format: 'mmoitems:TYPE:ID'.
  

Example:
Improvements & Fixes

• Universal ItemsAdder Drop Support: The system for handling custom drops from ItemsAdder has been completely overhauled. It now correctly processes items from any ItemsAdder namespace, not just itemsadder: or noblemetals:. This ensures full compatibility with all custom resource packs.
  
  
• Code Refactoring: The underlying code for handling tool requirements and custom drops has been refactored for better performance and easier implementation of future integrations.
  

BlockRegen v1.3.1 - The ItemsAdder Compatibility Patch!
This is a patch release focused on improving compatibility and fixing a critical bug related to custom drops from the ItemsAdder plugin.

Bug Fixes

• Fixed Custom Drops for All ItemsAdder Namespaces: A critical issue was resolved where custom drops from ItemsAdder would only work if the item's namespace was itemsadder: or noblemetals:. The system now correctly handles any namespaced ID (e.g., custompack:my_item), ensuring that custom drops work reliably with all ItemsAdder packs.
  

Improvements

• Enhanced ItemsAdder Integration: The logic for identifying and spawning custom items has been made more robust and flexible. This improves overall compatibility with plugins that add custom items, particularly ItemsAdder, allowing for more diverse and complex drop configurations without requiring code modifications.
  

BlockRegen v1.3 - The Auto-Updater Update!
✨ Added

• Automatic Config Updater: The plugin will now automatically update your config.yml file when a new version adds new configuration options. This process preserves all your existing settings and comments, ensuring a smooth upgrade experience for all future updates.
  

⚙️ Changed

• The config.yml file now includes a config-version number to track and manage updates seamlessly.
  

BlockRegen v1.2 - The Compatibility & Fixes Update!
️ Fixes & Improvements

• Fixed ItemsAdder Custom Drops: Resolved an issue where custom drops using ItemsAdder items were not functioning correctly. The plugin now properly recognizes and handles ItemsAdder custom item IDs, including those with custom prefixes like 'itemsadder:sapphire_ingot'.
  
  
• Improved Update Notification System: Implemented a configurable update notification message. Server administrators can now customize the update availability message via the config.yml file.
  
  
• Confirmed MMOItems Custom Drop Compatibility: Verified and ensured full compatibility with MMOItems for custom block drops. Players can now reliably receive MMOItems as custom drops from regenerated blocks, provided the correct mmoitems:TYPE:ID format is used in blocks.yml.
  

BlockRegen v1.1 - The ItemsAdder Integration Update!
✨ Features

• Full ItemsAdder Integration: BlockRegen is now fully compatible with ItemsAdder! You can make any custom block from ItemsAdder regeneratable.
  
  • Custom Block Support: To make a custom block regenerate, simply use its full namespaced ID (e.g., 'my_items:ruby_ore') as the main key in your blocks.yml file.
    
    
  • Custom Drop Support: The custom-drops section can now also use ItemsAdder items as drops. Just specify the item's namespaced ID under the material key.
    
    
  • All existing features, including regen-delay, replaced-block, tools-required, custom sounds, and particles, are fully compatible with ItemsAdder blocks.
    

Bug Fixes

• Fixed a critical bug where custom sounds and particles defined under regen-sound and regen-particle would fail to trigger when a block regenerated. The correct effects will now be applied.

Sorry Wrong Version before