Bukkit

FatTnt 0.2.0-DEV-3 - beta [1.2.5]

Almost usable beta/dev. Might work with a range of earlier CB/RB builds as well.

Important changes:

• Configuration path: resistence is changed to resistance.
• Configuration: entities is outdated, you now have sub sections in exploding-entities, which will allow for individual explosion settings.

Additions:

• Scheduling for explosions and other, allowing to control roughly how much time your server spends for explosions per tick.
  (Somewhat fair scheduling, per chunk and total maxima, timeouts.)
• Top level (defaults) as well as settings for each world can contain sub sections for exploding-entities, to override entries individually. No need to fill in all settings, just add the differing ones. To control certain aspects you can add a priority to explosion settings to ensure the set values are used or not used. The settings will be applied in order defaults (real defaults, entity specific) then world settings (defaults, then entity specific), equal priority overrides. If useing resistance or passthrough you have to specify BOTH default and individual sets, defaults or sets can not be inherited (subject to another update, in some way).
• direct-explode threshold is used now, i.e. explosions get scheduled for the next tick if hit with enough force.
• By default FatTnt will now handle ALL explosions and prevent other explosions that have not been done via FatTnt (if can grip it). Fully configurable for which entities/worlds entities in worlds etc. explosions are handled or prevented.
• Enabling, disabling, panic, unpanic: remove all primed tnt, cancel all explosions till unpanic.

Expect configuration changes in the future, if in doubt, get the default configuration and check the changes.

Not yet in:

• Individual fuse ticks for different ways of ignition !
• Fire
• More convenient way to use the same sets of resistance or passthrough (or propagate damage) block ids for different settings.
• Other things...

Issues:
* The preset configuration values are //still// mild guesses (or wild), and need adaption.
* The schedulers are global and not per world, this means if two worlds have lots of explosions at the same chunk coordinates, they will compete for removal due to limits.
* Some global scheduler settings are hidden and not generated with the default configuration. They are included in the Configuration page.