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
@filbert66
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
@ChillerKraft
Dude, calm down. I just got back from flying for 21 hours, and I'm not even home yet!
Remember that this is entirely a volunteer thing. I'm not getting paid and I do it in my free time, which hasn't been much recently. I am working on your request, even while I was on the plane.
why did you stop replying at all after i said i wouldnt send my logs?
i made a ticket, and sent the error portion. can you reply to the rest of our conversation aswell please??????
@ChillerKraft
Sure, send me a log file (pref a link to a pastebin or Bukkit attachment or something).
@ChillerKraft
You're asking about breaking out different protection of drops?
Can you give me the server logs for when it reports an error?
i hope you can update this to at least beta :) would be realllly great, i cant find any other plugins as detailed as this one and i realllllly want it :) i tested on 1.7.9, i only added a world on my server to the config option nodamageto nonplayer from fire and tested it there, but the fire still broke the drop.i believe that's all i really need to change in order to see if that works, right? also when i stop server i get an error for the plugin which i suppose means the plugin wont work on beta.
i figured it would be that if anything, but i tried it out and it didnt work. might be because of the bukkit version i was using though which was 1.7.10,
im using 1.7.9 now, does this work with it?? i could test it again
id really like my servers item entities to be safe n sound while on the ground
@ChillerKraft
I think drops (Item entities) are impacted by nerf_fire.nodamageto.nonplayer.fromfire along with all non-player entities. Could break that out in a new feature...
o this doesnt block drop damage from fire does it...
work with 1.7.9?? i noticed i need a way to protect drops from fire so im interested in this plugin, looks all around very useful too
@EN7
Examples of timedcauses config is only found found here. It is not in the default config.
@filbert66
I can't find the timedcauses node in my configuration
I am using latest version@shortsonfire79
Hey, Shorts. Thanks for trying it. Most obvious thing to check is the name of your world(s). The config file uses them extensively. My examples assume "world" and "nether". You might need to change those if you've named your worlds differently.
Or you can use the commands, and even modify your config without having to edit the YML file. I recommend trying the following:
This will turn off fire starting by lightning, and all fire spreading, in the world in which you are logged in. If you want that in more than one, you'll have to log into each world; alternatively nostartby does support this option. If you read the Commands page you'll find you can do just about everything with the in-game commands, so have fun!
I'm having a wee bit of trouble understanding the config file. I want to turn off only lightning fire, but I'm just testing the "Nerf fire a lot" example with this config. http://pastebin.com/eDiNigQ6 And this 2x5 wood bit burned away. :( http://i.imgur.com/PAOmNE7.png
@Wbfw
Fixed! I'll DM you a download link as it will take Bukkit staff a few days to approve.
@filbert66
I have used craftbukkit 3023 build and AntiFire 2.4 version. http://pastebin.com/VvkAi1QN << It's my config .yml
@Wbfw
Please DM me you config.yml and I can attempt to duplicate. Also what version of Bukkit and AntiFire are being used?
If TNT is burned by near fire, TNT vanished! This doesn't explode! How can I solve situation?
@rohan0444mc
Are you trying to set both FLINT_AND_STEEL and FIRECHARGE? Then you should have entered the below:
Please see the example config for timedcauses here. I've tried to clarify it a bit.
Or you could just use the new commands to change the config in-game and then save it.
The config is example is kinda confusing... or maybe im just dumb anyway I put in this
nerf_fire: timedcauses: FLINT_AND_STEEL: charge: 5000 logstart: player: world lightning: world crystal: world
and I added the
timedcauses: FLINT_AND_STEEL: charge: 5000
part because I thought thats what it said to do and I added nerf_fire.timedcauses to my perms but still doesnt work