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.
- supports multiple languages [in 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:
nospread: - 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.
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
|anydropchance||max||random average||fixed (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
- .mob.fromfire: applies to bats and when above not set
- .painting.fromfire: paintings won't catch fire in listed worlds
- .drops.fromfire: dropped items
- .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 : node offering fixed fire durations. See its detailed description page.
nerf_fire.timeNetherackToo: if , even infinitely burning blocks like netherack will be subject to timedcauses.
nerf_fire.rainOverridesTimed: if , rain will put out blocks even if they are subject to timedcauses. [Added in 2.8]
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).
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".
nerf_fire: logstart: player: world lightning: world whitelist: false nospread: world nostartby: op: false logflushsecs: 600 woodropscharcoal: world charcoaldrop: random: true speciesmax: JUNGLE_LOG: 0 OAK_LOG: 2 BIRCH_LOG: 1 SPRUCE_LOG: 3 ACACIA_LOG: 4 DARKOAK_LOG: 5 anydropchance: 75 noplacelavaby: op: false nodamageto: peacefulmob: fromlava: world fromfire: world drops: fromfire: world logplace: lava: world rainOverridesTimed: false
Examples of timedcauses config is only found found here. It is not in the default config.
Permissions & Commands
Since 1.4 the plugin now sends statistics to mcstats.org. 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
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.
- Suppressing hissing sound when drops are not damaged by lava
- Allow different timedcause configuration per world
Change timeNetherackToo to a world-based config flag. [2.9] Add an option for rain to still put out timed fires [2.8] LanguageAPI support for translations Configurable in-game messaging
- Date created
- Apr 16, 2012
- Last update
- Aug 04, 2015
- Development stage
- GNU General Public License version 2 (GPLv2)
- Curse link
- Recent files