Is fire damaging your precious buildings or forests? Want to allow fire but restrict its mechanics? Or just log it? Or tp there and put it out? This plugin, inspired by @happypumkin and @x0pk1n, allows all that and more with detailed configurability. To be specific, it has the following features, all configurable by world:

  • disable fire spreading, by world
  • fire start controls:
    • log fire starting with detailed world location (players only, or also lightning and lava)
    • disable fire starting by lightning, fire spread, explosions, fireballs, explosions, ender crystals, and/or lava
    • disable starting fire to blocks by players (with enable by Permissions)
    • disable starting fire to mobs & players by players (with enable by Permissions)
    • make certain block types fireproof! Configurable list of block IDs.
  • fire duration controls:
    • by the mechanism that started the fire, regardless of the underlying material
  • disable fire damage to blocks, players, and/or non-player entries including mobs
  • disable lava damage to blocks, players, and/or non-player entries
  • disable lava placement by players, with permissions override support
  • commands to view last few locations of fire starting, by whom
  • commands to teleport to a log entry
  • command to put out fires nearby you, or in entire world
  • commands to view/set/save all config values, or reload from config.yml
  • command to flush fire start log to disk
  • option to make burnt logs drop charcoal.
  • now supports multiple languages [2.6]


Most of the controls of this plugin, like AntiCreeper, are solely by configuration flags. Almost all entries are lists of worlds in which that specific behavior will be active. You can either present them as a YML list of strings:

    - world 
    - world_the_end

But I found that to get hard to read when I have so many config items, so you can optionally present them on one line as a comma-separated list:

  nospread: world, world_the_end


The .blocklist entry is the same as you'll find in AntiCreeper's blocklists. It's a list of comma-separated block names/IDs, and allows sub-type listings in form of "#:#", which could be used, for example, to make jungle wood fireproof but allow burning other wood. If you wish to make almost everything fireproof except a few blocks, set .whitelist to true and then only list the ones that should burn. There are few rare cases where the block detection may not seem to work well, but this only happens if there is another burnable block adjacent to the fire location.

Configurable Fields

Description of configurable items. Most are lists of worlds per above.


  • .player: if set for a world, logs player, date/time, and location to server.log
  • .lava: if set for a world, logs event, date/time, and location to server.log
  • .lightning: if set for a world, logs event, date/time, and location to server.log
  • .fireball: if set for a world, logs event, date/time, and location to server.log
  • .explosion: if set for a world, logs event, date/time, and location to server.log
  • .crystal: if set for a world, logs event, date/time, and location to server.log

nerf_fire.whitelist: if false, blocks on blocklist are fireproof; if true, fire can only be started on blocks on blocklist

nerf_fire.blocklist: list of decimal block ids per above

nerf_fire.nospread: if set for a world, fire cannot spread from one block to another there.

nerf_fire.wooddropscharcoal: if set for a world, burnt logs drop 0-3 charcoal

nerf_fire.charcoaldrop: new node that modifies behavior when above is set for any world

  • .max integer that sets maximum number of charcoal dropped
  • .random [true|false] that sets if fixed to max or random from 1-max
  • speciesmax node to set max drops by species of wood
    • support for 1.7 types Acacia and Dark Oak
    • Each entry underneath should be <species>_LOG: #
    • See example in default below.
  • anydropchance 0-100 integer to set chance of any kind of drop, whether random or fixed at max
    • see table below for default chances, averages
anydropchancemaxrandom averagefixed (max) avg
  • Deprecated .treetypemax list for setting max drops by type of wood
    • set in this order: Oak, Spruce, Birch, Jungle
    • must set all four or else defaults to charcoaldrop.max.

nerf_fire.nostartby: node with below items

  • .op: if true, even Op cannot start a fire (without Permission set)
  • .lightning: if set for a world, lightning not supposed to start a fire
  • .fireball: if set for a world, fireballs from dispensers or other plugins not supposed to start a fire
  • .lava: if set for a world, lava cannot start fire on adjacent block
  • .player: if set for a world, NO players can start a fire in that world unless (a) they are Op or (b) have permission antifire.startfire set. Caution: Also means nerfed players can NOT enable a portal.
  • .explosion: if set for a world, all explosions in that world do not start a fire. Overrides other plugins, like AntiCreeper
  • .crystal: if set for a world, ender crystals do not start fires.

nerf_fire.nodamageto: node with below items

  • .block: burning blocks will not be destroyed in listed worlds
  • .player.fromlava: lava will not hurt players (2 hearts per tick) in listed worlds, but remember it also sets people on fire Refer to example config Walk on Lava
  • .player.fromfire: players will not catch fire or incur fire damage in listed worlds
  • nonplayer has now been replaced by the following:
    • .hostilemob.fromfire: hostile mobs won't catch on fire in listed worlds
    • .peacefulmob.fromfire:
    • .mob.fromfire: applies to bats and when above not set
    • .painting.fromfire: paintings won't catch fire in listed worlds
    • .item.fromfire: anything not in previous categories
    • all of above items with fromlava work as well

* .nonplayer.fromlava: mobs and creatures will incur no damage from lava

* .nonplayer.fromfire: mobs and creatures won't catch fire. Beware of setting this, since it means mobs will NOT burn in sunlight

nerf_fire.noburnmobby: node with below items

  • .player: players cannot light mobs with flaming weapons or arrows in supplied worlds,
    • unless they have permission antifire.burnmob
  • .mob: mobs cannot do the same, if they were to have such
  • .op: if true, OPs can NOT set mobs alight
    • unless they have permission antifire.burnmob

nerf_fire.noburnplayerby: similar to above, but against players

  • corresponding permission is antifire.burnplayer

nerf_fire.noplacelavaby: node controlling lava placement

  • .player: if set for a world, NO players can place lava in that world unless (a) they are Op or (b) have permission antifire.placelava set
  • .op: if true, even Op cannot place lava (without Permission set)

nerf_fire.timedcauses : NEW node offering fixed fire durations. See its detailed description page.

nerf_fire.logplace.lava: node that adds lava placement to the Antifire log for listed worlds.

nerf_fire.logflushsecs: age in seconds of fire start log entries to flush to disk. This only happens when a new entry is added (in order to avoid overhead of a periodic tic) and if the current list of entries is more than ten (all that can fit in chat display).

Default Configuration

Most of the mechanics of this plugin are disabled by default, except logging fire start locations to your server log file. and now fire spreading is Off by default. But only if your server has a world named "world".

    player: world
    lightning: world
  whitelist: false
  nospread: world
    op: false
  logflushsecs: 600
  woodropscharcoal: world
    random: true
      JUNGLE_LOG: 0
      OAK_LOG: 2
      BIRCH_LOG: 1
      SPRUCE_LOG: 3
      ACACIA_LOG: 4
      DARKOAK_LOG: 5
    anydropchance: 75
    op: false
    lava: world

Example Configurations (click here)

Examples of timedcauses config is only found found here. It is not in the default config.

Permissions & Commands

Has been moved to another page here. That page has some example commands


Since 1.4 the plugin now sends statistics to These are completely anonymous and help me as a plugin developer know how the plugin is being used. You can view the same data by clicking below. If you want to turn it off, simply edit plugins/PluginMetrics/config.yml and change opt-out: false to true

AntiFire mcstats

Languages and Translations

AntiFire now supports you configuring your own strings used to players, and setting alternate languages as well. This is done with LanguageAPI plugin. See the detailed language page for more.

Possible features:

  1. Allow different timedcause configuration per world

LanguageAPI support for translations

Configurable in-game messaging

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of ChillerKraft ChillerKraft Feb 02, 2015 at 11:55 UTC - 0 likes

    @filbert66: Go

    seems to work great! ty

  • Avatar of EN7 EN7 Feb 02, 2015 at 03:35 UTC - 0 likes

    @filbert66: Go

    The correct response was no, I came back to stop you!


  • Avatar of filbert66 filbert66 Jan 31, 2015 at 23:09 UTC - 0 likes

    @ChillerKraft: Go

    I haven't tried Spigot. Let me know.

    My plugins: Anticreeper, AntiFire, BedCheck, Thor, Unbreakable Items, Enchantment Limiter. Contributor: Tree-Assist


  • Avatar of ChillerKraft ChillerKraft Jan 31, 2015 at 20:38 UTC - 0 likes

    will this plugin work with 1.8.1 spigot??
    i will test soon once i backup my server

  • Avatar of EN7 EN7 Jan 28, 2015 at 22:13 UTC - 0 likes

    @filbert66: Go


  • Avatar of filbert66 filbert66 Jan 28, 2015 at 06:28 UTC - 0 likes

    @ChillerKraft: Go

    As I said in the ticket, netherrack is not affected by burn times since it burns forever; that's how I coded it. You could of course add netherrack to your blocklist, making it unburnable.

    I could easily add a boolean config that enforces burn times for things that otherwise burn infinitely. Is that what you'd like?

  • Avatar of ChillerKraft ChillerKraft Dec 23, 2014 at 05:24 UTC - 0 likes

    beautiful :D

    merry xmas bud :)

    would this also effect netherrack? id like that to still burn forever havin some hard times trying to think of how to keep my nether world lookin nice and firey, like... without block damage in nether, fires dont start, so ppl are just gonna eventually put out all the fires, i dont want people to be able to set fires orelse they will grief the nether, i turned on fireball block damage, and creeperheal heals the block damage, but puts out the fire. thats most of my issue, i need a way for there to always be some fires in the nether but not let ppl be able to start them manually at will, but my main question being, will netherrack be affected by burn times aswell, or can i whitelist netherrack or somethin? and do u have any other ideas off the top of ur head for havin a nice firey ungriefable nether?

    Last edited Dec 23, 2014 by ChillerKraft
  • Avatar of filbert66 filbert66 Dec 23, 2014 at 05:11 UTC - 0 likes

    @ChillerKraft: Go

    Yes. While normally the decision of when fires goes out has no Bukkit API, you can use the timedcauses config item to set max Fire time for configured causes. See detail page.

    Last edited Dec 23, 2014 by filbert66: By causes, not materials
  • Avatar of ChillerKraft ChillerKraft Dec 23, 2014 at 05:04 UTC - 0 likes

    can i use this plugin to help stop fires from burning way to long when i have firespread off? sometimes when leaves are burning and firespread is off, the fires never extinguish, and i believe this could turn into a problem eventually.

  • Avatar of ChillerKraft ChillerKraft Dec 19, 2014 at 00:24 UTC - 0 likes

    @filbert66: Go

    sry i was afraid i upset u when i said i wouldnt send my full logs or somethin cause you were replying quickly up until that point :p np im glad to hear ur still there for me


Date created
Apr 16, 2012
Last update
Jan 28, 2015
Development stage
  • enUS
GNU General Public License version 2 (GPLv2)
Curse link
Recent files