These are the main configuration keys used in config.yml to control the plugin's global behavior.
Below is a list of each property, its purpose, and example values.

Defaults:

UseBlockDatabase: false
CheckBlockDatabaseAtStartup: false
BlockDurability: 100.0
EnableMetrics: true

These properties are used to control the localization of the plugin.

The Locale property contains all the localized messages used by the plugin. Each message is defined with a key and a value. The key is used to reference the message in the code, while the value is the actual message that will be displayed to the player. Color and formatting codes are supported in all messages.

The LocalePrefix property is a string that is prepended to all messages sent to the player. This can be used to customize the prefix for all messages, such as adding a color code or changing the text.

Some messages have placeholders that can be replaced with dynamic values. The placeholders are enclosed in % symbols and will be replaced with the corresponding value when the message is sent to the player. Below is a list of all the messages used by the plugin, along with their descriptions and placeholders.

Defaults:

Locale:
  NotAllowed: "You are not allowed to perform this action!"
  Usage: "Usage: %DESCRIPTION%"
  OnlyPlayerAllowed: "Only players can perform this action!"
  PlayerDoesntExist: "Player %NAME% doesn't exist in the server!"
  PlayerIsOffline: "Player %NAME% must be online to perform that"
  EnterChecktoolMode: "You can now right-click a block with %PRETTY_ITEM% to display block durability"
  LeaveChecktoolMode: "You can no longer check for a block durability"
  ChecktoolToggledOn: Checktool mode toggled on for player %NAME%
  ChecktoolToggledOff: Checktool mode toggled off for player %NAME%
  ChecktoolUse: "Block health: %DURABILITY_PERCENTAGE%% (%PRETTY_MATERIAL%)"
  ChecktoolUseBossBar: "%PRETTY_MATERIAL%: %DURABILITY_PERCENTAGE%%"
  ChecktoolSet: "Checktool successfully set to %PRETTY_ITEM%!"
  ChecktoolNotPersisted: "Checktool item was set to %PRETTY_ITEM%, but it couldn't be persisted"
  ChecktoolGiven: "A checktool (%PRETTY_ITEM%) was given to player %NAME%"
  ChecktoolReset: "Checktool successfully reset to bare hand (Air)"
  ChecktoolNotHandled: "%PRETTY_MATERIAL% is not handled by the current configuration"
  ChecktoolInfo: "Current checktool item: %PRETTY_ITEM%"
  ChecktoolAlwaysEnabled: "Checktool can't be toggled off because it's always enabled"
  DisabledInThisWorld: "This functionality is disabled in this world"
  Reloaded: "Reloaded successfully!"
  DebugEnabled: "Debug mode has been enabled"
  DebugDisabled: "Debug mode has been disabled"

LocalePrefix: "[ExplodeAny] "

These properties are used to control the checktool item. The checktool item is an item that players can use to check the durability of blocks. By default, the checktool item is set to bare hand (Air), but it can be changed to any item in the game. Note that all properties of the item are persisted, including the name, lore, and enchantments, so only a clone of the item will be recognized as a checktool item.

Defaults:

Checktool:
  AlwaysEnabled: false
  EnabledByDefault: false
  PreventActionWhenCheckingHandledBlocks: true
  PreventActionWhenCheckingNonHandledBlocks: true
  SilentWhenCheckingOnDisabledWorlds: false
  SilentWhenCheckingWithoutPermissions: false
  SilentWhenCheckingNonHandledBlocks: false
  SilentWhenCheckingHandledBlocks: false
  ShowBossBar: false
  BossBarColor: PURPLE
  BossBarStyle: SOLID
  BossBarDuration: 1500ms

This list contains all the worlds where the plugin is disabled. While the plugin will still be loaded, it will not perform any action in these worlds. This is useful for worlds where you don't want the plugin to interfere with the gameplay, such as creative worlds or minigames. Some commands, like reloading or configuration related commands, might still be accessible.

Defaults:

DisabledWorlds: []

Example:

DisabledWorlds:
  - MyWorld
  - MyWorld2

Since the plugin allows breaking all blocks, it is possible to create world holes by breaking blocks in the world. This can be problematic, especially in survival worlds. To prevent this, the plugin has a world hole protection feature that prevents players from breaking blocks at certain heights/layers.

Each key in the list represents a world where the world hole protection is enabled. The allowed values are described below:

Defaults:

WorldHoleProtection: {}

Example:

WorldHoleProtection:
  default:
    Heights:
      - -64 # Bedrock layer post-1.18
    #   - 0   # Bedrock layer pre-1.18 (only one of these two is usually needed)
  world_nether:
    Heights:
      - 127
      - 0

The behavior of ExplodeAny can be customized by specifying the properties of each couple of entities that can explode + blocks that can be destroyed. Different sections in the configuration file group different types of explosive entities, thus allowing to customize different types of explosions. Most common entities, like TNT or CREEPER, fall into the VanillaEntity section, which contains Minecraft's vanilla entities. Other sections allow to configure explosions from other plugins or even mods.

An overview of a simple configuration can be seen below:

VanillaEntity:
  TNT:
    Properties:
      ExplosionDamageBlocksUnderwater: true
    Materials:
      OBSIDIAN:
        Damage: 50.0

CustomEntity:
  CGM_MISSILE: # This entity comes from a mod
    Properties:
      ExplosionRadius: 4.0
    Materials:
      OBSIDIAN:
        Damage: 50.0

As you can see, the configuration is divided into sections. Each section contains a list of entities, their properties and the materials that will be affected by their explosions. The properties are used to customize the behavior of the explosion itself, such as the explosion radius, damage underwater and other effects. The materials section contains a list of blocks that will be affected by the explosion, along with their properties, such as damage, drop chance for blocks, etc.

While different sections can have different entities allowed, the overall structure (including available materials and properties) remains the same.

The list of supported sections includes:

The list of entities available in each section is listed below:

Given a section (represented by the placeholder <SECTION>) and an entity (represented by the placeholder <ENTITY> in the following example), the structure of the configuration is as follows:

<SECTION>:
  <ENTITY/GROUP>:
    Properties:
      <ENTITY-PROPERTY-1>: <VALUE>
      <ENTITY-PROPERTY-2>: <VALUE>
    Materials:
      <MATERIAL/GROUP>:
        <MATERIAL-PROPERTY-1>: <VALUE>
        <MATERIAL-PROPERTY-2>: <VALUE>

Where Properties is a section that contains the properties of the entity (aka Entity properties), and Materials is a section that contains the materials (or group names) that will be affected by the explosion. Each material can have its own properties when affected by a given entity (aka Entity-material properties). We will cover these properties in the next sections.

For example, given the section VanillaEntity and the entity TNT, the configuration would look like this:

VanillaEntity:
  TNT:
    Properties:
      <ENTITY-PROPERTY-1>: <VALUE>
      <ENTITY-PROPERTY-2>: <VALUE>
    Materials:
      <MATERIAL/GROUP>:
        <MATERIAL-PROPERTY-1>: <VALUE>
        <MATERIAL-PROPERTY-2>: <VALUE>

Groups can also be used in every place where entity and materials appear. They are a way to group multiple entities or materials together, avoiding repetition. To know more about groups, see Groups.

Entities and materials also accept wildcards. For example, TNT* will match all entities that start with TNT, such as TNT, TNT_MINECART, etc. Similarly, * will match all entities or materials. As with groups, they allow to avoid repetition. See Name wildcards for more information.

When entity properties are not set, there's an alternative structure that shortens the configuration, allowing to list materials directly under the entity name, as shown below:

VanillaEntity:
  TNT:
    <MATERIAL/GROUP>:
      <MATERIAL-PROPERTY-1>: <VALUE>
      <MATERIAL-PROPERTY-2>: <VALUE>

Which, in turn, is equivalent to the following too:

VanillaEntity:
  TNT:
    Materials:
      <MATERIAL/GROUP>:
      <MATERIAL-PROPERTY-1>: <VALUE>
      <MATERIAL-PROPERTY-2>: <VALUE>

Note how any of Properties and Materials can be completely skipped, as they are optional. The following example is also valid:

VanillaEntity:
  TNT:
    Properties:
      <ENTITY-PROPERTY-1>: <VALUE>
      <ENTITY-PROPERTY-2>: <VALUE>

The properties of the entity are used to customize the behavior of the explosion itself. All entities have the same set of properties available:

Example of configuration (omitting particles and sound properties, which will be covered later):

<SECTION>:
  <ENTITY/GROUP>:
    Properties:
      ExplosionRadius: 10.0
      ExplosionFactor: 2.0
      ReplaceOriginalExplosion: true
      UnderwaterExplosionFactor: 1.5
      ExplosionDamageBlocksUnderwater: true
      ExplosionRemoveWaterloggedStateFromNearbyBlocks: true
      ExplosionRemoveNearbyWaterloggedBlocks: true
      ExplosionRemoveNearbyLiquids: true
      PackDroppedItems: false

The particle properties are used to customize the behavior of the particles that will spawn when the entity explodes. The properties are as follows:

Example of properties:

<SECTION>:
  <ENTITY/GROUP>:
    Properties:
      Particles:
        Name: BLOCK_CRACK
        DeltaX: 1.0
        DeltaY: 1.0
        DeltaZ: 1.0
        Amount: 100
        Speed: 0.5
        Force: true
        Material: STONE

<SECTION>:
  <ENTITY/GROUP>:
    Properties:
      Particles:
        Name: REDSTONE
        DeltaX: 1.0
        DeltaY: 1.0
        DeltaZ: 1.0
        Amount: 100
        Speed: 0.5
        Force: true
        Red: 0
        Green: 127
        Blue: 255

The sound properties are used to customize the behavior of the sound that will be played when the entity explodes. The properties are as follows:

Example of properties:

<SECTION>:
  <ENTITY>:
    Properties:
      Sound:
        Name: ENTITY_GENERIC_EXPLODE
        Volume: 1.0
        Pitch: 1.0

The entity-material properties are used to customize how a specific material is affected by a given explosion. The properties are as follows:

Outside of explosions, blocks (materials) also have properties that can be configured. The general structure is as follows:

...(other global properties)

Materials:
    <MATERIAL/GROUP>:
        Properties:
            <PROPERTY>: <VALUE>

The properties that can be configured are as follows:

Example of configuration:

...(other global properties)

Materials:
    OBSIDIAN:
        TimeToFullRegeneration: 1m # (if it had 0 durability, it would take 1 minute to completely regenerate)
        DelayBeforeStartRegenerating: 10s # (wait 10 seconds before starting to regenerate)

Groups are used to group multiple entities, materials or both together. They can be used in the same place of the configuration where entities and materials are accepted. If the group contains both materials and entities, then the plugin will choose the right one depending on the section where the group is used. When no item in the group is valid for the section, then the group will be considered invalid.

Groups can have any name, as long as it doesn't coincide with a valid material or entity name. If the name of the group coincides with a valid material or entity name, then the valid material or entity will be selected as the target, not the group.

It can happen that a group contains entities or materials that are also present individually in the same section. In this case, the plugin will merge all configurations depending on where the group is being used. The merging rules are as follows:

• If the group is used in the Entities section, then materials will be merged as follows:

1. If an entity appears in two or more groups, then materials will try to merge without overwriting each other. If the same material appears listed in both groups, then the first occurrence of the material will be kept.
2. If an entity appears in two or more groups but also as an individual item, then rule 1 applies, and after that, the materials in the individual configuration will be merged, overwriting existing materials if necessary (individual configuration has greater priority than groups).

• If the group is used in the Materials section, then entity-material configurations will be merged as follows:

1. If a material appears in two or more groups, then the first occurrence of the entity-material configuration will be kept.
2. If a material appears in two or more groups but also as an individual item, then the individual material will be kept.

Examples of groups and their usage:

Groups:
  myUnbreakableBlockGroup:
    - OBSIDIAN
    - CRYING_OBSIDIAN
  myExplosiveEntityList:
    - PRIMED_TNT
    - CREEPER

VanillaEntity:
  myExplosiveEntityList:
    Properties:
      ExplosionDamageBlocksUnderwater: true
    Materials:
      myUnbreakableBlockGroup:
        Properties:
          Damage: 50.0
          DropChance: 50.0

The above example is equivalent to the following configuration:

VanillaEntity:
  PRIMED_TNT:
    Properties:
      ExplosionDamageBlocksUnderwater: true
    Materials:
      OBSIDIAN:
        Properties:
          Damage: 50.0
          DropChance: 50.0
      CRYING_OBSIDIAN:
        Properties:
          Damage: 50.0
          DropChance: 50.0
  CREEPER:
    Properties:
      ExplosionDamageBlocksUnderwater: true
    Materials:
      OBSIDIAN:
        Properties:
          Damage: 50.0
          DropChance: 50.0
      CRYING_OBSIDIAN:
        Properties:
          Damage: 50.0
          DropChance: 50.0

Name wildcards are used to match multiple entities or materials with a single name. Currently, the only wildcard available is * (asterisk), which can be used to match any number of characters in a given position of the name.

To be able to use the wildcard, it is necessary to enclose the name in double quotes:

VanillaEntity:
  TNT:
    Properties:
      ExplosionDamageBlocksUnderwater: true
    Materials:
      "*_WOOL":
        Properties:
          Damage: 50.0
          DropChance: 50.0

For example, consider the following examples:

*_OBSIDIAN will match all materials that end with the word _OBSIDIAN in their name, such as OBSIDIAN and CRYING_OBSIDIAN

*_WOOL will match all materials that end with the word WOOL in their name, such as WHITE_WOOL, ORANGE_WOOL, MAGENTA_WOOL, etc.

*CREEPER will match all entities that end with the word CREEPER in their name, such as CREEPER, CHARGED_CREEPER, etc.

TNT_* will match all entities that start with the word TNT in their name, such as TNT, TNT_MINECART, etc.

* will match any material or entity name, so you can use it to list all materials or entities in the game.

Durations can be specified in the following format:

Remember that 1 second is 20 ticks, so 1s = 20 ticks.

Units can be combined by spaces, and do not need to be in any particular order. For example, the following formats are all valid:

• 1h 30m = 1 hour and 30 minutes
• 1d 2h 3m 4s = 1 day, 2 hours, 3 minutes and 4 seconds
• 1w 2d 3h 4m 5s = 1 week, 2 days, 3 hours, 4 minutes and 5 seconds
• 1s 10 = 1 second and 10 ticks

Materials are keys used to represent the different types of blocks and items that exist in the game. You can find a list of all the materials in the official Spigot API.

Particles are keys used to represent the different types of particles that exist in the game. You can find a list of all the particles in the official Spigot API.

Sounds are keys used to represent the different types of sounds that exist in the game. You can find a list of all the sounds in the official Spigot API.