It's been a while since the last update (almost a year!), but we keep going. There are some suggested features that couldn't be implemented yet due to lack of time, but every feature request is tracked, I promise!

Changelog

• Added block durability regeneration: Blocks can now recover durability! See the wiki for more information
• Added support for name wildcards: It is now possible to specify wildcards () in entity/material names, allowing to group entity/materials that have a similar name! (For example, "_WOOL" will group all types of wool!). See the wiki for more information
• Added custom drops: It is also possible to specify a custom material/item as a drop when a certain type of block breaks due to a explosion. See the wiki for more information
• Added world hole protection: It is now possible to specify certain heights in worlds where blocks won't be removed in order to avoid world holes. See the wiki for more information
• We have a wiki! Every important piece of information about the plugin will be posted on the wiki, instead of scattering files in the plugin's folder. This way, we can have a centralized, up-to-date source of information for the plugin. Therefore, exampleConfig.yml and TUTORIAL.md files have been removed, honoring the wiki, which will expand over time.
• Better warning/error messages: ExplodeAny will now warn the user whenever it finds invalid entities/materials, instead of remaining silent until nothing in the list is valid. I hope it helps to understand which entities/materials are actually understood by the plugin.
• Improved /eany config show: (Almost) all sections of the plugin's configuration file can now be consulted through the command to give a better understanding of how the configuration was resolved.
• Bukkit 1.7 was not properly supported and has been dropped: After some testing, it seems that only some revisions of Bukkit 1.7 were not really compatible with ExplodeAny, so server support has been adjusted. Just to make it clear: we didn't make any change to reduce compatibility, and we won't, ever. Someone reached out concerned about the Paper hard-fork. Similar as we do for Folia, we will provide a custom build in case they diverge from Spigot's API (not yet, since ExplodeAny only uses common standard Bukkit API, which is unlikely to be removed or changed in the future).

Server support

• Bukkit-based server 1.8 - 1.21.5 (Bukkit, Spigot, Paper...) [Download]
• Folia-based server 1.8 - 1.21.5 [Download]