ВЕРСИИ (35)

- \[Fabric only\] Fixed an issue where decimal numbers in the config file are truncated to integers when Jankson is installed (either directly or included in another mod)

- \[Fabric only\] Fixed an issue where decimal numbers in the config file are truncated to integers when Jankson is installed (either directly or included in another mod)

- \[Fabric only\] Fixed an issue where decimal numbers in the config file are truncated to integers when Jankson is installed (either directly or included in another mod)

- \[Fabric only\] Fixed an issue where decimal numbers in the config file are truncated to integers when Jankson is installed (either directly or included in another mod)

- \[Fabric only\] Fixed an issue where decimal numbers in the config file are truncated to integers when Jankson is installed (either directly or included in another mod) - Now requires Minecraft 26.1.2

Updated to Minecraft 26.2.

Updated to Minecraft 26.2.

First update for Minecraft 26.1 (snapshots and release). The mod loaders are still unstable, so use at your own risk. Please report any issues that you come across to our [issue tracker](https://github.com/ljfa-ag/TNTUtils/issues).

First update for Minecraft 26.1 (snapshots and release). The mod loaders are still unstable, so use at your own risk. Please report any issues that you come across to our [issue tracker](https://github.com/ljfa-ag/TNTUtils/issues).

- Added the entity type tags `#tntutils:deny_explosions` and `#tntutils:allow_explosions`, which can be used to disallow or allow entity types to create explosions, respectively. - *For example, tagging minecraft:ghast with deny_explosions (in a datapack) allows you to block explosions from Ghast fireballs.* - Individual entities (as opposed to entity types) can also be tagged with `tntutils.deny_explosions` and `tntutils.allow_explosions` to (dis)allow them to create explosions. - *The entity tags are not to be confused with entity type tags. They can be applied to an entity with the `/tag` command. Notice the dot instead of a colon, since the argument to `/tag add` cannot contain colons.* - *For example, to make a Creeper that explodes even when explosions are disabled in the config, you can use the command `/tag @n[type=creeper] add tntutils.allow_explosions`.* - *Note: While it is possible to tag a player with tntutils.deny_explosions, this will not completely prevent them from causing explosions, as, for example, they can still ignite TNT with a redstone signal.* - Added the config option `entityDamageMultiplier`, which can be used to change the amount of damage applied to entities. - *Note: Since the implementation of knockbackMultiplier would need to be much more complicated in 1.20.1 than in later versions, I decided not to backport it.* - The `/explode` command will now bypass the `disableExplosions` config option. - Added suggestion for the default explosion strength (4) to the '/explode' command.

- Added the entity type tags `#tntutils:deny_explosions` and `#tntutils:allow_explosions`, which can be used to disallow or allow entity types to create explosions, respectively. - *For example, tagging minecraft:ghast with deny_explosions (in a datapack) allows you to block explosions from Ghast fireballs.* - Individual entities (as opposed to entity types) can also be tagged with `tntutils.deny_explosions` and `tntutils.allow_explosions` to (dis)allow them to create explosions. - *The entity tags are not to be confused with entity type tags. They can be applied to an entity with the `/tag` command. Notice the dot instead of a colon, since the argument to `/tag add` cannot contain colons.* - *For example, to make a Creeper that explodes even when explosions are disabled in the config, you can use the command `/tag @n[type=creeper] add tntutils.allow_explosions`.* - *Note: While it is possible to tag a player with tntutils.deny_explosions, this will not completely prevent them from causing explosions, as, for example, they can still ignite TNT with a redstone signal.* - Added the config option `entityDamageMultiplier`, which can be used to change the amount of damage applied to entities. - *Note: Since the implementation of knockbackMultiplier would need to be much more complicated in 1.20.1 than in later versions, I decided not to backport it.* - The `/explode` command will now bypass the `disableExplosions` config option. - Added suggestion for the default explosion strength (4) to the '/explode' command.

- Added the entity type tags `#tntutils:deny_explosions` and `#tntutils:allow_explosions`, which can be used to disallow or allow entity types to create explosions, respectively. - *For example, tagging minecraft:ghast with deny_explosions (in a datapack) allows you to block explosions from Ghast fireballs.* - Individual entities (as opposed to entity types) can also be tagged with `tntutils.deny_explosions` and `tntutils.allow_explosions` to (dis)allow them to create explosions. - *The entity tags are not to be confused with entity type tags. They can be applied to an entity with the `/tag` command. Notice the dot instead of a colon, since the argument to `/tag add` cannot contain colons.* - *For example, to make a Creeper that explodes even when explosions are disabled in the config, you can use the command `/tag @n[type=creeper] add tntutils.allow_explosions`.* - *Note: While it is possible to tag a player with tntutils.deny_explosions, this will not completely prevent them from causing explosions, as, for example, they can still ignite TNT with a redstone signal.* - Added the config options `entityDamageMultiplier` and `knockbackMultiplier`, which can be used to change the amount of damage and knockback applied to entities, respectively. - The `/explode` command will now bypass the `disableExplosions` config option. - Added suggestion for the default explosion strength (4) to the '/explode' command.

- Added the entity type tags `#tntutils:deny_explosions` and `#tntutils:allow_explosions`, which can be used to disallow or allow entity types to create explosions, respectively. - *For example, tagging minecraft:ghast with deny_explosions (in a datapack) allows you to block explosions from Ghast fireballs.* - Individual entities (as opposed to entity types) can also be tagged with `tntutils.deny_explosions` and `tntutils.allow_explosions` to (dis)allow them to create explosions. - *The entity tags are not to be confused with entity type tags. They can be applied to an entity with the `/tag` command. Notice the dot instead of a colon, since the argument to `/tag add` cannot contain colons.* - *For example, to make a Creeper that explodes even when explosions are disabled in the config, you can use the command `/tag @n[type=creeper] add tntutils.allow_explosions`.* - *Note: While it is possible to tag a player with tntutils.deny_explosions, this will not completely prevent them from causing explosions, as, for example, they can still ignite TNT with a redstone signal.* - Added the config options `entityDamageMultiplier` and `knockbackMultiplier`, which can be used to change the amount of damage and knockback applied to entities, respectively. - The `/explode` command will now bypass the `disableExplosions` config option. - Added suggestion for the default explosion strength (4) to the '/explode' command.

- Added the entity type tags `#tntutils:deny_explosions` and `#tntutils:allow_explosions`, which can be used to disallow or allow entity types to create explosions, respectively. - *For example, tagging minecraft:ghast with deny_explosions (in a datapack) allows you to block explosions from Ghast fireballs.* - Individual entities (as opposed to entity types) can also be tagged with `tntutils.deny_explosions` and `tntutils.allow_explosions` to (dis)allow them to create explosions. - *The entity tags are not to be confused with entity type tags. They can be applied to an entity with the `/tag` command. Notice the dot instead of a colon, since the argument to `/tag add` cannot contain colons.* - *For example, to make a Creeper that explodes even when explosions are disabled in the config, you can use the command `/tag @n[type=creeper] add tntutils.allow_explosions`.* - *Note: While it is possible to tag a player with tntutils.deny_explosions, this will not completely prevent them from causing explosions, as, for example, they can still ignite TNT with a redstone signal.* - Added the config options `entityDamageMultiplier` and `knockbackMultiplier`, which can be used to change the amount of damage and knockback applied to entities, respectively. - The `/explode` command will now bypass the `disableExplosions` config option.

- Added the entity type tags `#tntutils:deny_explosions` and `#tntutils:allow_explosions`, which can be used to disallow or allow entity types to create explosions, respectively. - *For example, tagging minecraft:ghast with deny_explosions (in a datapack) allows you to block explosions from Ghast fireballs.* - Individual entities (as opposed to entity types) can also be tagged with `tntutils.deny_explosions` and `tntutils.allow_explosions` to (dis)allow them to create explosions. - *The entity tags are not to be confused with entity type tags. They can be applied to an entity with the `/tag` command. Notice the dot instead of a colon, since the argument to `/tag add` cannot contain colons.* - *For example, to make a Creeper that explodes even when explosions are disabled in the config, you can use the command `/tag @n[type=creeper] add tntutils.allow_explosions`.* - *Note: While it is possible to tag a player with tntutils.deny_explosions, this will not completely prevent them from causing explosions, as, for example, they can still ignite TNT with a redstone signal.* - Added the config options `entityDamageMultiplier` and `knockbackMultiplier`, which can be used to change the amount of damage and knockback applied to entities, respectively. - The `/explode` command will now bypass the `disableExplosions` config option.

Updated to Minecraft 1.21.11. And with that, Merry Christmas everyone!

Updated to Minecraft 1.21.11. And with that, Merry Christmas everyone!

Updated to Minecraft 1.21.9.

Updated to Minecraft 1.21.9.

Initial release for Minecraft 1.21.7. Since explosions received a significant refactor in Minecraft, things might not be stable yet or could function a bit differently from before. - Added suggestion for the default explosion strength (4) to the '/explode' command

Initial release for Minecraft 1.21.7. Since explosions received a significant refactor in Minecraft, things might not be stable yet or could function a bit differently from before. - Added suggestion for the default explosion strength (4) to the '/explode' command

Finally another release for Minecraft 1.12.2 after a very long time! This version fixes a longstanding oversight in the interaction with Applied Energistics 2, and brings the code and metadata more up-to-date. I'm currently not planning to add new features to the 1.12.2 version unless requested. - Added the config option 'alwaysAffectAE2Singularities', defaulting to true, which makes sure that Applied Energistics 2 Singularities are still affected by explosions when entity or item damage is disabled, so that it is possible to entangle them. - Updated the URL that is shown in the Mods screen - Fixed config values unnecessarily being loaded twice - Removed some code that is no longer needed

- Fixed item whitelist not being applied when 'disableEntityDamage' is set to true - In particular, AE2 Singularities can now be entangled when entity damage is disabled - \[Fabric only\] The config file can now be reloaded using the '/reload-tntutils-config' command ((Neo)Forge already reloads the config file when it is changed) - (Note: Primed TNT can't have custom block states in 1.20.1) - Changed the way the mod hooks into explosions. This has no impact on vanilla but might affect modded explosions.

- Fixed item whitelist not being applied when 'disableEntityDamage' is set to true - In particular, AE2 Singularities can now be entangled when entity damage is disabled - \[Fabric only\] The config file can now be reloaded using the '/reload-tntutils-config' command ((Neo)Forge already reloads the config file when it is changed) - (Note: Primed TNT can't have custom block states in 1.20.1) - Changed the way the mod hooks into explosions. This has no impact on vanilla but might affect modded explosions.

- Fixed item whitelist not being applied when 'disableEntityDamage' is set to true - In particular, AE2 Singularities can now be entangled when entity damage is disabled - \[Fabric only\] The config file can now be reloaded using the '/reload-tntutils-config' command ((Neo)Forge already reloads the config file when it is changed) - Primed TNT entities with a custom block state will now drop the corresponding block rather than TNT when 'disableTNT' is set to true - Changed the way the mod hooks into explosions. This has no impact on vanilla but might affect modded explosions.

- Fixed item whitelist not being applied when 'disableEntityDamage' is set to true - In particular, AE2 Singularities can now be entangled when entity damage is disabled - \[Fabric only\] The config file can now be reloaded using the '/reload-tntutils-config' command ((Neo)Forge already reloads the config file when it is changed) - Primed TNT entities with a custom block state will now drop the corresponding block rather than TNT when 'disableTNT' is set to true - Changed the way the mod hooks into explosions. This has no impact on vanilla but might affect modded explosions.

Fixed `java.lang.NoSuchMethodError` crash when trying to load a world. I accidentally uploaded the wrong JAR file for the Forge version. Initial release for Minecraft 1.20.1 with Fabric and Forge. Has the same features as 1.21.1-2.0.2 (excluding of course the options and tags relating to block triggering, which was only added in Minecraft 1.21).

Initial release for Minecraft 1.20.1 with Fabric and Forge. Has the same features as 1.21.1-2.0.2 (excluding of course the options and tags relating to block triggering, which was only added in Minecraft 1.21).

In commemoration of the 80th anniversary of the end of World War II in Europe. Let us keep defusing bombs! - Added the config option `disableCreeperBlockDamage`: Prevents Creepers from destroying blocks - Added the config option `modifyExplosionResistances`: Allows changing of explosion resistances for individual blocks - \[Fabric only\] The config file will now be backed up if it contains syntax errors (NeoForge already handles this) - TNT minecarts will now be damaged and destroyed by explosions when `preventChainExplosions` is turned on, rather than be immune to explosion damage - Fixed desync issues with TNT and TNT minecarts when client and server have differing config options

In commemoration of the 80th anniversary of the end of World War II in Europe. Let us keep defusing bombs! - Added the config option `disableCreeperBlockDamage`: Prevents Creepers from destroying blocks - Added the config option `modifyExplosionResistances`: Allows changing of explosion resistances for individual blocks - \[Fabric only\] The config file will now be backed up if it contains syntax errors (NeoForge already handles this) - TNT minecarts will now be damaged and destroyed by explosions when `preventChainExplosions` is turned on, rather than be immune to explosion damage - Fixed desync issues with TNT and TNT minecarts when client and server have differing config options

- Added the config option `preventChainExplosions`: Prevents explosions from igniting TNT and TNT minecarts, so that explosions cannot chain - Added the config option `disableTNT`: Prevents TNT and TNT minecarts from being ignited - Added various tags: - The block tag `#tntutils:explosion_blacklist`: These blocks will not be destroyed by explosions - The block tag `#tntutils:explosion_whitelist`: These blocks can be destroyed by explosions, even when the `disableBlockDamage` or `spareBlockEntities` options are turned on. The whitelist takes precedence over the blacklist. - The block tags `#tntutils:trigger_blacklist` and `#tntutils:trigger_whitelist`: Simliar to the above but for triggering blocks by Wind Charge explosions, etc. - The entity tags `#tntutils:explosion_blacklist` and `#tntutils:explosion_whitelist`: Similar to the above but for entity damage - The item tags `#tntutils:explosion_blacklist` and `#tntutils:explosion_whitelist`: Similar to the above but for items laying on the ground - Removed the config option `alwaysAffectAE2Singularities`. Instead, AE2 Singularities are tagged with `#tntutils:explosion_whitelist` by default

- Added the config option `preventChainExplosions`: Prevents explosions from igniting TNT and TNT minecarts, so that explosions cannot chain - Added the config option `disableTNT`: Prevents TNT and TNT minecarts from being ignited - Added various tags: - The block tag `#tntutils:explosion_blacklist`: These blocks will not be destroyed by explosions - The block tag `#tntutils:explosion_whitelist`: These blocks can be destroyed by explosions, even when the `disableBlockDamage` or `spareBlockEntities` options are turned on. The whitelist takes precedence over the blacklist. - The block tags `#tntutils:trigger_blacklist` and `#tntutils:trigger_whitelist`: Simliar to the above but for triggering blocks by Wind Charge explosions, etc. - The entity tags `#tntutils:explosion_blacklist` and `#tntutils:explosion_whitelist`: Similar to the above but for entity damage - The item tags `#tntutils:explosion_blacklist` and `#tntutils:explosion_whitelist`: Similar to the above but for items laying on the ground - Removed the config option `alwaysAffectAE2Singularities`. Instead, AE2 Singularities are tagged with `#tntutils:explosion_whitelist` by default

First prerelease for Minecraft 1.21.1. Due to the large difference from Minecraft 1.12 to 1.21, the mod has been rewritten from scratch, supporting both NeoForge and Fabric. **Please note that TNTUtils is still work in progress, not all features of the 1.12 version have been implemented yet.** See the config file for the features that are available. Please report any issues you encounter to our [issue tracker](https://github.com/ljfa-ag/TNTUtils/issues). Some notable differences from the 1.12 version: - The "/explosion" command has been renamed to "/explode" and now supports an additional argument specifying how the explosion interacts with blocks - The "dropChanceIncrease" option is now called "dropChanceMultiplier" and simply multiplies the drop chance by the given factor. Note that you can use the vanilla game rules "mobExplosionDropDecay", "tntExplosionDropDecay" and "blockExplosionDropDecay" to force the block drop chance to 100% depending on the explosion source. - Added an option "alwaysAffectAE2Singularities", which makes sure that Applied Energistics 2 Singularities will always be affected by explosions, so they can be entangled

First prerelease for Minecraft 1.21.1. Due to the large difference from Minecraft 1.12 to 1.21, the mod has been rewritten from scratch, supporting both NeoForge and Fabric. **Please note that TNTUtils is still work in progress, not all features of the 1.12 version have been implemented yet.** See the config file for the features that are available. Please report any issues you encounter to our [issue tracker](https://github.com/ljfa-ag/TNTUtils/issues). Some notable differences from the 1.12 version: - The "/explosion" command has been renamed to "/explode" and now supports an additional argument specifying how the explosion interacts with blocks - The "dropChanceIncrease" option is now called "dropChanceMultiplier" and simply multiplies the drop chance by the given factor. Note that you can use the vanilla game rules "mobExplosionDropDecay", "tntExplosionDropDecay" and "blockExplosionDropDecay" to force the block drop chance to 100% depending on the explosion source. - Added an option "alwaysAffectAE2Singularities", which makes sure that Applied Energistics 2 Singularities will always be affected by explosions, so they can be entangled