Bukkit

1.1.1 release:

• Fixed: allow for spaces in blocklist in config.yml Ticket 2]

1.1 release:

• Added nostartby.fireball, logstart.fireball
• Added reload command
• Added: burnable/fireproof commands now accept Bukkit Material name strings as well as ID numbers

1.0.1 release:

• Changed: extinguish command now tied to new permission antifire.fireman
• Tested : built against 1.4.5-R0.2

1.0 release:

• Added: new extinguish command to put out fires in world(s) or w/in a radius as requested by @garan2314

0.9.2 release:

• Avoid conflicts with AntiCreeper 4.0; built with same libraries

0.9.1 release:

• Recompiled and tested against CB 1.4.2-R0.2. No changes.

0.9: release

• Added: new af admin command to print/modify (some)/save config settings
• Added: now automatically flushes antifire.log to disk after configurable logflushsecs

0.8: release

• Added: new nerf_fire.nostartby.explosion feature
• Added: more discrete logstart ability, by lava, player, lightning

0.7: release

• Changed: added "world" to default antifire.nospread.
• Added: Zip file with example config file

0.6: release

• Fixed: default true for antifire.startfire was always overriding config nostartby.player.

0.5: release

• Added:
  • maintain separate log file of fire starts in AntiFire/antifire.log.
    • .logstart now only controls level of detail to server console
  • default permissions, so using a Permissions plugin is optional
  • colored messages to chat window for easier eye parsing
• Changed:
  • teleport command now named tpf to retain vanilla tp command
  • startfire permission to antifire.startfire (removed "nerf_fire").
• Fixed: log and tp commands crash when searching on a username of two or more digits. Not fatal.
• Tested with PermissionsBukkit but should work with any plugin compatible with Bukkit perm API.

0.2: beta

• Added: commands "tp" and "log". See known issues below. Should I change their names?

0.1: First release

1. One can sometimes start a fire when pointing at a block on your blacklist. This is because there is a burnable block adjacent to the block where the fire is. Could spend more time determining exactly where player is pointing, but they could just point at that other block, so "Won't Fix". Also happens if you start fire on ground next to a fireproof tree, then you can start fire above the tree since "fire" block underneath is burnable.

Fixed in MC 1.4.4: Lightning still lights paintings and other blocks on fire when nerfed, but this is an error on client side (see this discussion). Log out and the fire will go away.