A new update (0.2.0-DEV-3) is coming relatively soon:

• Configuration change: resistence will now be resistance
• Added behavior: Will handle ALL explosions by default, can prevent explosions, will prevent explosions that are not from FatTnt (all configurable)
• panic command to stop and remove all primed tnt.
• fine grained configuration, explosion settings contain a section for the exploding entity, same for world dependent settings - no need to set all entries, only set the entries to override (for instance creepers in nether).
• Threshold for "direct" explosion: If hit by an explosion with sufficient strength, tnt can be scheduled to explode right for the next tick.
• Scheduling ! Explosions, Item and entitiy (tnt) spawns can be managed by a scheduling system, that also reduces the numbers based on global and chunkwise thresholds as well as timeouts. Configurable thresholds and time to spend per tick allow for setting up tnt according to oyur needs and the power of your server !

Left to do for this version:

• Fire: a) at-all, for instance for fireballs b) override fire to have it always, if desired
• Testing out the configuration and overriding behavior (including priority setting).
• Adding a more detailed default configuration.

Version after the next version:

• The schedulers are global and schedule all worlds at once (unlikely to be a frequent problem: in one world much tnt is going off in one chunk, and some one wants to use tnt in another world at the same position, which might then get scheduled away for the thresholds).
• The explosion scheduler has the biggest part (block changing + Explosion events, depending on protection plguins) while enitties and items are relatively light. I will evaluate other concepts (load dependent, randomized, configurable, total scheduling time for all).

@ClockworkHatter

In addition it is possible to define passthrough-resistence values for materials - this would allow to let the explosion pass through blocks like crops, fences or wooden doors, while not destroying anything (provided the resistance values for those are high enough).

Then the passthrough value just defines by how much the explosion strength gets less when passing through such material.

Another thing that one might do is to define the blocks that pass on entity damage, i.e. allow entities/ players outside of the explosion core radius to be damaged if the explosion would propagate to the entity along a ray from the center only touching these kind of blocks.

At some point i might try to give more "complete" configuration examples for the explosion strength thingy, but currently i don't have much time...

@ClockworkHatter

Yes, you can set the default resistance value to very high, while you use one set with a reasonably low resistance value for stone brick.

resistence:
  # very high default value to make things undestroyable, 
  # which are not in one of the sets below.
  default: 10000.0 
  # Default resistence for air, to let the explosion pass on:
  low:
    value: 1.0
    ids:
    - 0
  destroyable:
    # some value for stone brick, you migth adjust it to something reasonable.
    value: 3.0
    ids:
    # correct me if 98 is not stone brick.
    - 98

FatTnt does not yet have "greedy settings" to replace all possible explosions, but if your intention is creepers and tnt then it should work if you have them in the entities list.

@IceSpike

"after 5 blocks have passed" - What is your intention with it, do you want it to detonate after some time or when the player is away more than 5 blocks?

At least you will need to register for some PlayerInteract event and check what block is clicked and what item the player has in hand, then you will need a way to get the tnt detonate.

For detonation there are two basic ways - you can make a direct explosion with World.createExplosion (kind of fake, no warning to the player), or you need to use CraftBukkit to use TNTPrimed.class as argument to World.spawn (and remove the tnt block) you can then set the fuse ticks of the tnt to control when it will explode.

Further you could also control the TNTPrimed by storing the entity-id of it, and cancel its ExplosionPrimeEvent, if you want to prevent explosion while near to the player that ignited it, then maybe remove it and create a new TNTPrimed, till the player is far enough, or even turn it back into a block or spawn a tnt item instead, but there i am not sure what you are aiming at!

@Migrosbudget The number of explosions does not (yet) matter because the blocks have a fixed resistance value. In the default configuration you can remove obsidian from the strongest group (resistance 20, TNT can not destroy it by default) to some other in the resistance section. The Strength of TNT is by default somewhere around 8 so you can experiment with the settings how near the tnt must be to destroy it. The id is 49, the default resistance group is "strongest".

Currently only the explosion strength that arrives at a position determines if the block can be destroyed, no cumulative damage, just the resistance value from the configuration. Though that would be an interesting feature...

Here the group in which obsidian(49) is in the default configuration:

resistance:
  strongest:
    value: 20.0
    ids:
    - 49
    - 116

You can remove it form the list and put it to some other group, or create a new one.

@Buttercake_

Most blocks like obsidian do not really take damage over time in minecraft (see above), you can change the resistance value for obsidian as described above.

I am sorry about the undocumented appearance of this plugin ... yet it is comparably early stage in development and i am considering changing the configuration around a bit.

Currently you have to ask and experiment a bit with the settings. I will try to keep the block resistence and passthrough settings, such that those wont change when the configuration changes.

I will add documentation with time...

EDIT: Sorry, it must be resistence for this version ,if i am not mistaken.

@ultimateowner56

Not affected - what exactly do you need, concerning water/lava?

You can configure to have water and lava pass on entity and block damage, to never get destroyed (though passing on damage and destruction), to always get destroyed.... such is already possible.

I will make major changes to the configuration more or less soon, so if you really start using it there may be some work to adjusting the settings, then.

By default i think that lava and water are configured to pass on all kinds of damage, but not get destroyed.

@ChainSawXL

It will not be a quick addition, because i have to clean up the configuration a lot, to make it easier readable and understandable and flexible enough to bring in specific settings to different contexts (defaults, worlds, entities, confinement, ).

To make that transition more easy you could state what features you (most) need !

Are you mainly interested in restricting the detonation and/or block effects and/or entity damage to a certain part of the world ( minY <= y <= maxY)?

I am not sure if i will too soon add player specific permissions for placing tnt, linking it with redstone, or igniting it directly, because those are slightly off center of my intentions with this plugin (replace, adjust, control explosion effects on blocks, entities), though not impossible to add.

@daeger

Will be added at some point ...

@asofold

Ok i misspelled my search keyword "creaper"...

I am not sure what exactly CreeperHeal does to do damage but not have blocks destroyed for instance, but if it just alteres the blocks of an EntityExplodeEvent for that case, then it will likely be compatible for FatTnt also throws those events as if normal tnt exploded, except that the calculations for blocks and damage have been done by FatTnt, then.

What do you need FatTnt for?

Yet it is in quite early stage, though i find it interesting myself and probably will make it "fully work".

@S3thc0n

What does CreeperHeal do ?

By default FatTnt will only replace tnt explosions, do you intend to use it for creepers too ?

It might be possible, but currently i am focusing on TNT, mainly.

There still are some basic issues that i want to fix, then i will have to extend the configuration. All the settings are more like examples yet, very roughly guessed.

You can already now let it only destroy certain blocks, let explosions go through water and lava (and off water), configure blast resistance of any material, and manipulate quite some aspects of it.

Next thing i want to fix is, that the explosion is slightly offset for tnt, which lets it go off inside an obsidian wall (and thus do nothing), though the tnt is outside - that might be a simple fix. Then i will add that other tnt blocks will trigger if in range, so they explode too.