Flame Arrows
This plugin will allow a player to set blocks on fire with flaming arrows
Permissions:
- flamearrows.ignite : allows a player to set blocks alight with flaming arrows (defaults op)
Usage:
- Have a bow and arrow(s)
- Shoot through lava OR Have a bow with the Flame enchantment applied
- Shoot!
- The block that it hits will be ignited. It will ignite only flammable blocks.
Configuration:
The configuration file is located inside the plugins folder. There is only a single file (config.yml).
You can add or remove block-id's that will catch fire under the block-ids heading. By default, all standard minecraft flammable blocks are on the list (including TNT).
Ensure there are no tabs in the file, or the plugin will fail to start.
All words after a hash are comments: they are not required, but provided to help administrators
You can specify a percentage chance that the fire will catch. A value of 100 means it will always ignite, whilst a value of 0 means it will never ignite. Any integer value can be used inbetween.
Default Configuration:
block-ids:
- 5 #wood planks
- 125 #wooden double slab
- 126 #wooden slab
- 17 #wood
- 18 #leaves
- 106 #vines
- 31 #tall grass
- 35 #wool
- 85 #fence
- 53 #oak wood stairs
- 134 #spruce wood stairs
- 135 #birch wood stairs
- 136 #jungle wood stairs
- 47 #bookshelf
- 170 #hay
- 46 #tnt
chanceToSucceed: 100
version: 0.3.0
Comments
-
_ForgeUser7646157 Owner
-
View User Profile
-
Send Message
Posted Nov 26, 2013I've tested out the plugin and while the fire arrow effect works, the permission node seems to be broken; it only works when I'm OP, even though I've given myself the flamearrows.ignite permission node.
Also, the plugin doesn't appear to respect Towny, but that could be just because I'm OP. If not, could that be a feature? (ie, prevent the fire spread in regions protected by plugins such as Towny and Worldguard)
EDIT: Upon further experimentation (and looking at the code), I found that the actual perm node is "flamerarrow.ignite". However, I notice that the fire arrows can be used in areas where the player couldn't ordinarily build in, as I mentioned before. I'd like to put it out there as a feature request that players shouldn't be able to start fires in areas where they wouldn't be allowed to build in.
-
View User Profile
-
Send Message
Posted Nov 25, 2013Does this still work as of 1.6.4?
-
View User Profile
-
Send Message
Posted Aug 11, 2013@CommodoreAlpha
The mechanics are pretty simple: It uses a BlockIterator to find the block the arrow entity is stuck in, then determines what 'face' the block is in (using getRelative), and ignites the BlockFace. v 3 shouldn't have problems igniting sides, tops, or underneath blocks.
In regards to your suggestion, I'll try adding it as a config option for next version.
-
View User Profile
-
Send Message
Posted Aug 11, 2013@FlOppythp
You need to have the permission flamearrows.ignite to be able to set blocks on fire with a flaming arrow. Can you check your permissions? Also, sometimes the arrow doesn't set the block on fire, even with 100% chance to ignite. I think this is a limitation with Minecraft itself, but I've been testing 0.3.1 to try and get it right(er). Finally, the plugin can't ignite any blocks that aren't ignitable in vanilla. The only way I could make it do this is to set the block it hits as something flammable, and then ignite it, but I think that's a silly way to do it. All that will happen to a non-flammable block (that has been added to config) is it will burn briefly, and then go out, similar to if you used flint and steel on it.
-
View User Profile
-
Send Message
Posted Aug 10, 2013@FlOppythp
Wooden doors aren't naturally flammable, so you can't directly set it on fire, nor can fire burn it. And I don't think this plugin modifies fire mechanics at all (nor should it), otherwise that would bring in a whole slew of problems and potential incompatibilities. The way the plugin most likely works is that when a fire arrow hits a block, it checks the configuration file if the target block's material is in the list, and if it is, it spawns a fire block adjacent to the target block. If it's not on the list, the plugin does nothing.
Keep in mind due to the limitations Mojang set on fire blocks that this plugin might not work exactly as expected. It would be helpful to specify what block material you were shooting at, along with what object you were shooting at in general. (A tree, a single floating block, etc.) An example of why this plugin may not work, would be that you shot at a single floating log, and the plugin tries to spawn fire under the log, but it's floating, so the fire instantly disappears.
@hazsmix
I think I might recall Mojang implementing this feature for 1.5 or something. But for some reason, it never came. So thanks for covering what Mojang promised us, but never gave. :)
Also, would it be possible to make fire blocks that were spawned in by this plugin shorter in lifespan? (As in, they naturally go out quicker.) I think this can be accomplished by spawning in fire blocks with a different damage value, because the damage value determines the fire block's "age" (be sure not to set it at 15+, because that specifies an everlasting fire). You could also make this configurable via an integer representing this damage value. Specifying "0" should act like a fire placed by a "flint and steel", whereas specifying "14" should be the shortest in lifespan.
-
View User Profile
-
Send Message
Posted Aug 8, 2013@Den00
Done and done! Thankyou :)
-
View User Profile
-
Send Message
Posted Aug 8, 2013@FlOppythp
Updated to 1.6.2, should be pushed through soon.
-
View User Profile
-
Send Message
Posted May 1, 2013BTW, please make a config file with flammable blocks ids
-
View User Profile
-
Send Message
Posted May 1, 2013Love it. Thanks :)