Bukkit

2.4: Support charcoal for new 1.7 log types

• Added:
  • charcoaldrop.anydropchance config item added, 0-100
    • sets chance for any drop, random or fixed to max
    • adjusted default from 50% to 75%
  • support for new 1.7 log types Acacia and DarkOak within speciesmax
    • was already in place, but code was not working due to bug in Bukkit TreeSpecies for these new types
    • default for Acacia is 4 max; DarkOak is 5
• Dependency: since this shares code with my other plugins, if you use AntiCreeper or Thor use their latest versions (4.13.1 and 4.3.1 respectively).

2.3: Permit alternative Material strings that infer data values in blocklist

• Added: blocklist strings that infer Material data
  • allows specifying types/colors of materials in string rather than looking up magic numbers
  • see list of alternative names here.
• Dependency: since this shares code with my other plugins, if you use AntiCreeper or Thor use their latest versions (4.13 and 4.3 respectively).

2.2: Prep for 1.7

• Added: speciesmax will replace treetypemax, but either works for now
  • explicit listing of Log types as strings within configuration
  • advance support for 1.7 new log types Acacia and DarkOak (only configure if you are running 1.7.x)

2.1.2: Bug Fix

• Fixed: NPE when fire is lit and there are no timedcauses config items

2.1.1:

• Added: colors printed to in-game console for some errors
• Improved: Removed timedcauses dependency on doDaylightCycle rule.
• Tested against 1.6.4-R1.0 - yay, it's a Recommended Build now!

2.1: Commands for timed fire controls

• Added: timed subcommand of af to set timedcauses config
  • Tested and confirmed that RAM usage does not significantly increase the more blocks you have being timed.

2.0: Timed Fire controls

• Added: config to permit fixed fire durations for configured causes via timedcauses node
  • any block lit because of the configured cause will always burn for the configured time.
  • the block will not naturally expire nor will flammable materials be burnt up.
• Compatibilty:
  • This version requires Bukkit 1.6.4 build 2894 or later
    • that is, anything that includes Commit 7d680d39 fixing Bukkit-4835
  • It will work with earlier (ex. 1.6.2-R1.0) builds, but timed fire controls will not work well for non-flammable blocks, as the fire may fade before the timer expires.

1.9: private testing release

1.8: Lava placement controls

• Added: config & commands to control lava placement
  • defaults to allow so as to not upset existing users
• Note: metrics.org is "rebooting" and not recording. Shouldn't cause lag, but if you don't want it,
  • Simply edit plugins/PluginMetrics/config.yml and change opt-out: false to true

1.7.1: Metrics Fix

• Fixed: Crash on startup when server has another plugin using R7 of Metrics. Description here.
  • Caveat: couldn't test as mcstats.org is not updating with new metrics, but I did confirm it no longer crashes.

1.7:

• Added:
  • New config node charcoaldrop for altering charcoal drop behavior
    • .max [int] sets maximum drops
    • .random [true|false] sets if fixed to max or not
    • .treetypemax list for setting max drops by type of wood
  • New max [int] and random|fixed command options to charcoal command
• Fixed: was burning block (or making charcoal) even when nerf_fire.nodamageto.block set

1.6.3: Added commands for new items from last version

• Added:
  • commands noburnmob[by] and noburnplayer[by]

1.6.2: Added commands and split config items

• Added:
  • command charcoal sets wooddropscharcoal
  • commands nostartby and logstart now work for crystal and explosion
• Improved:
  • Permission burnentity split into burnmob and burnplayer
  • Config item similarly split into noburnmobby and noburnplayerby
• wooddropscharcoal default is now true for world name "world"
• Fixed:
  • When player is not permitted to light mobs with fire aspect weapons, cows and pigs no longer flame on for a sec, nor do they drop "cooked" meat if death results from attack.

1.6.1: Fixed plugin.yml with new permission

1.6:

• Added:
  • wooddropscharcoal if set for a world, burning logs drop 0-3 charcoal
  • noburnentityby.player if set for a world, players can NOT light mobs or other players on fire
    • will be refined to noburnmobby.player, noburnplayerby.player, and *by.mob
  • nostartby.crystal and nostartby.explosion nerf starts by those
  • logstart.crystal and logstart.explosion derp
• Improved:
  • nodamageto.player.fromfire now works when entities light players on fire (e.g. flaming swords)

1.5:

• Improved: nospread now nerfs implicit spread when blocks are damaged by fire; used to be replaced by fire
• Fixed: if nostartby.player is turned off, stops logging to server console when fire is started

1.4.1 patch:

• Fixed: opstart command causing exception when used with no params

1.4 release:

• Added: commands under af to set nostartby, nodamageto, logstart.
• Added: report anonymous statistics to mcstat.org
  • this helps me as plugin developer to know how it is being used
  • if desired to turn off, Simply edit plugins/PluginMetrics/config.yml and change opt-out: false to true

1.3.1 release:

• Fixed again: turn off fires adjacent to fireproof blocks. [Ticket 5] 1.3 release:
• Fixed: fireproof blocks adjacent to burning, burnable blocks are destroyed by fire (Ticket 5)
• Improved: improved burning block detection (by line of sight) when using flint

1.2.1 release: compiled against Bukkit release 1.4.5-R1.0

1.2 release:

• Added: "last" or <playername> option for extinguish command. Originated by @garan2314
• Changed: releasing as .jar only; removed sample config.yml. If you don't have one, the defaults are saved to pluginsAntiFire/config.yml

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

Charcoal is not produced if fire extinguishes naturally without destroying a LOG block.

If your overworld is called "world" and you do NOT want to log player fire starts, simply commenting out logstart.player or deleting its values in your config file doesn't work since the default is "world". So set it to some nonsense world, like "fooblitzky".

Fixed in 1.6.2: - noburnentityby.player if set still burns the entity for a half a sec. Struck cows will drop cooked steak. Think it's an NMS thing.

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.

Fixed in 1.3: 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.

Player can still point at adjacent burnable block, but the fireproof block won't burn up when the burnable block's fire goes out.