AntiFire
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]
- control fire duration by start type, providing fixed value or a range [in 2.7]
Configuration
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
Blocklist
The .blocklist entry is the same as you'll find in AntiCreeper's blocklists. It's a list of comma-separated block names, and allows sub-type listings in form of "#:#"[3.0] 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.
nerf_fire.logstart:
- .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 <some>_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 |
75% | 1 | 0.75 | 0.75 |
75% | 2 | 1.125 | 1.5 |
75% | 3 | 1.5 | 2.25 |
75% | 4 | 1.875 | 3 |
75% | 5 | 2.25 | 3.75 |
75% | 6 | 2.625 | 4.5 |
- [Deleted in 3.0]
.treetypemax list for setting max drops by type of woodset in this order: Oak, Spruce, Birch, Junglemust 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
- .drops.fromfire: dropped items
- .item.fromfire: anything not in previous categories
- all of above items with fromlava work as well
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 or random fire durations. See its detailed description page.
nerf_fire.timeNetherackToo: if set for a world, even infinitely burning blocks like netherack will be subject to timedcauses.
nerf_fire.rainOverridesTimed: if set for a world, 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).
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".
nerf_fire: logstart: player: world lightning: world whitelist: false nospread: world nostartby: op: false logflushsecs: 600 woodropscharcoal: world charcoaldrop: random: true anydropchance: 75
max: 4 noplacelavaby: op: false nodamageto: peacefulmob: fromlava: world fromfire: world drops: fromfire: world logplace: lava: world rainOverridesTimed: false
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
Statistics
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.
Possible features:
- 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
@DarkFool
Hmm... I just fixed fire spreading when spread was off in AntiFire v1.5. I may have made spreading easier when spread is on but not supposed to be spreading on burnproof blocks. Can you give me a scenario when it spreads? Only on burnproof blocks, or are there blocks of other types neighboring the fire?
What version of Bukkit/Minecraft are you using? That may make a difference.
@.@ Just a heads up. Something in the recent versions re-enabled fires spreading around burnproof blocks again (it's the revenge of ticket 5! xD). The burnproof property is correct, as the blocks don't get destroyed, but they do blaze quite merrily in the meantime. I'm using 1.5; but, I'm unsure of which exact version the spreading behavior was reintroduced.
@ronfkingswanson
Ron, you're right. I've determined that when a block is destroyed it turns into fire without a fireStart(SPREAD) event. I've been able to nerf that now.
Also, fixed a bug in that if you've turned off nerf_fire.logstart.player it was still logging at INFO level (to console). Sorry about that.
Thanks for the bug reports. New version 1.5 coming with both these fixes, but early release available here.
also a little confused, as I have fire spread disabled in the config - yet in some cases fire spreads quite a bit (even if it does eventually give up). I know its working, as sometimes only a single block of leaves will burn up, and stop there - but sometimes half a bigtree will burn up before the fire runs out.
I had expected the disabling of fire spread to mean *only the block on fire would burn*, and none of the neighboring blocks would catch. I've tried with wood, wool, leaves - leaves seem to be most likely to spread.
So while I'm happy that at least someone can't take down an entire forest, it's still spreading more than I'd like...
Love it, thank you very much. Only thing I would ask for his inability to disable the console notices every time someone starts a fire. With fire spread disabled I don't really care if they start a fire and I don't need my console filling up with messages telling me.
Been seeing strange log activity last two days on mcstats with extinguish command. Why would 45,000 commands be tried but only 1,000 blocks be extinguished??
All I can guess is that someone is trying to hack the command to do stranger things. Anyone notice some strange activity? Anyone want to do the following on their server log for me?
and mail it to me?
@BornToWemble
Not sure exactly what you've wanted. I've made what was set for the overworld also set for the End and the nether.
@filbert66
I tried everything I could think of and it still hasn't worked. Here's the attachment.
@BornToWemble
Easiest way to fix this is to use the commands to set it how you want, then save it.
To get my help you need to post the whole comfig.yml file as an attachment.
I'm having some trouble disabling fire and lava in the nether and the end. From my understanding this SHOULD be right?: nerf_fire: logstart: player: world, nether lightning: world, world_the_end nospread: world blocklist: 17:1, 10
Everything works fine in the overworld so I'm confused.
@xMinecraft
New release with console commands to set logstart and other missing config items.
@xMinecraft
Your question is not clear. Do you want to disable console messages, or want to know how you did it? The commands are documented above. Or you can configure in your config.yml as documented in nerf_fire.logstart above.
Do you want a command to change the logstart entries? I don't think I have one.
How i disabled the message on the console?
@Xxswordcross
I have been using JRE 6 so it may not work with 7, but it should work fine with 1.4.6 if you use JRE 6. What errors have you encountered with JRE 7?
Update it please, I don't think is works with jre 7, or maybe just not even 1.4.6
@garan2314
I can do that, but wouldn't it be easier to add capability to reference the firestart log like the tpf command can teleport to the last location, or last -3 location?
Can you add the extinguish command to extinguish all blocks in some coords like X:123 Y:123 to X:234 Y:234? Thanks :D
Good job
This is really good plugin, but I am too lazy to specify all worlds in config so
Can you make something like:
Thank you man and I hope you'll update this plugin for 1.4
PS: I have 12 worlds :D
@epb223
Ep, this is easy to do. You can view some examples on the Example Configs page here, but here is the short summary (replace "world" with your desired worlds where this should be effective)"
can somebody please help me make it so blocks don't get damaged form fire but players do. Honestly im not really understanding how the config works so if somebody could just make a config file that has it so fire damages players but not blocks and email it to [email protected] it would be much appreciated.