ExplodeAny

Changelog

• Added specific TNT properties [see the wiki]: some new properties have been added specifically for TNT. They can be used in the same entity "Properties" section that all explosive entities have. Some of these entities are:
  • MinimumTravelDistanceToDamageBlocksUnderwater: it allows to set a minimum distance that a primed TNT must travel after it is primed in order to enable underwater damage. This is a workaround for vanilla TNT cannons blowing up after enabling ExplosionDamageUnderwaterBlocks. You can set a minimum distance (like 10) so that propellant TNT does not damage the cannon, but still propel the projectile TNT.
  • SnapToBlockGridOnPriming: stops primed TNT from moving from its position, allowing to keep primed TNT aligned with the block grid.
  • DisableExplosionChaining: allows to disable explosion chaining, i.e., TNT won't be primed by other exploding TNTs.
• Added OnHit and OnBreak particles [see the wiki]: until now, the entity material Particles section allowed to configure particles that spawn when a block is broken. This stays as the default behavior, but you can now configure particles when a block is hit by the exploding entity too.
• Fix boss bar duration not being properly computed: while a duration could be used for configuring the checktool's boss bar, the real duration did not match the specified one. It is fixed now.
• Compatibility rework: to ensure the plugin will continue running in different server implementations (such as Paper, after their hard-fork on Spigot), we have reworked our compatibility layers. Now, paper-based servers will load an specific compatibility layer, allowing to leverage Paper-only features.
• Minor improvements

Server support

• Folia-based server 1.8 - 1.21.8

Changelog

• Added specific TNT properties [see the wiki]: some new properties have been added specifically for TNT. They can be used in the same entity "Properties" section that all explosive entities have. Some of these entities are:
  • MinimumTravelDistanceToDamageBlocksUnderwater: it allows to set a minimum distance that a primed TNT must travel after it is primed in order to enable underwater damage. This is a workaround for vanilla TNT cannons blowing up after enabling ExplosionDamageUnderwaterBlocks. You can set a minimum distance (like 10) so that propellant TNT does not damage the cannon, but still propel the projectile TNT.
  • SnapToBlockGridOnPriming: stops primed TNT from moving from its position, allowing to keep primed TNT aligned with the block grid.
  • DisableExplosionChaining: allows to disable explosion chaining, i.e., TNT won't be primed by other exploding TNTs.
• Added OnHit and OnBreak particles [see the wiki]: until now, the entity material Particles section allowed to configure particles that spawn when a block is broken. This stays as the default behavior, but you can now configure particles when a block is hit by the exploding entity too.
• Fix boss bar duration not being properly computed: while a duration could be used for configuring the checktool's boss bar, the real duration did not match the specified one. It is fixed now.
• Compatibility rework: to ensure the plugin will continue running in different server implementations (such as Paper, after their hard-fork on Spigot), we have reworked our compatibility layers. Now, paper-based servers will load an specific compatibility layer, allowing to leverage Paper-only features.
• Minor improvements

Server support

• Bukkit-based server 1.8 - 1.21.8 (Bukkit, Spigot, Paper...)

Changelog

• Fix in groups configuration: Fixed an issue where single entities would replace groups configuration. See the issue for more information

Server support

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

Changelog

• Fix in groups configuration: Fixed an issue where single entities would replace groups configuration. See the issue for more information

Server support

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

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]