AntiFire

2 - Wool still burning

bukkit 2488
newest version of this plugin

Wool is catching on fire for a split second, then disaapearing

config:

# This is an example config file.
#  You really should read this config info first before you ask questions: http://bit.ly/MAxOu9
#  Make sure the world names match those on your server. Global search&replace is your friend.
nerf_fire:
  logstart:
    player:
    lightning:
  nospread: Zanith, Zanith_the_end
  blocklist: 17:1, 10, 5, 11, 17, 17:2, 18, 18:1, 18:2, 19, 26, 35, 35:1, 35:2, 35:3, 35:4, 35:5, 35:6, 35:7, 35:8, 35:9, 35:10, 35:11, 35:12, 35:13, 35:14, 35:15, 43:2, 44:2, 46, 47, 51, 53, 54, 63, 64, 65, 95, 96, 125, 126, 134, 135, 136, 143, 323, 324
# 17:1 is one type of wood, and 10 is grass, I think
  nostartby:
    op: false
    lightning: Zanith
#    lava:
#      - world_the_end
#      - nether
#    player:
#      - world
#    explosion: world, world_the_end
  nodamageto:
    block: Zanith
    player:
      fromlava:
      fromfire:
    nonplayer:
#      fromlava: nether, world_the_end, world
#      fromfire: world

permissions:
  antifire:
    startfire: deadmau6
    teleport: notch
#    logview:

User When Change
filbert66 Dec 04, 2012 at 18:55 UTC
filbert66 Dec 04, 2012 at 17:45 UTC
Dr_Proffesor Dec 04, 2012 at 17:29 UTC
filbert66 Dec 03, 2012 at 03:12 UTC
Dr_Proffesor Dec 03, 2012 at 02:23 UTC Create

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

  • 4 comments
  • Avatar of filbert66 filbert66 Dec 04, 2012 at 17:52 UTC - 0 likes

    @filbert66: Go

    OK, I've confirmed that it's the white spaces in your config. I'll release a patch that ignores whitespace, but for now you can simply edit your config.yml to replace ", " with ",".

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

    BFAK:67982,3d6540176e18ca75f0a204a87213d75a51e4b745f16c619b8fcef59ccfeab5cb

  • Avatar of filbert66 filbert66 Dec 04, 2012 at 17:37 UTC - 0 likes

    @Dr_Proffesor: Go

    Hmm. Ok, I'll have to look into it more. At first I just added 35 to my config's blocklist, and it prevented wool from burning. So it's either a problem with your config, or perhaps a bug dealing with a really long blocklist like yours.

    Is this problem only with wool? Are the other block types on your blocklist, such as logs, fireproof as expected?

  • Avatar of Dr_Proffesor Dr_Proffesor Dec 04, 2012 at 17:29 UTC - 0 likes

    @filbert66: Go

    no the wool doesnt remain it still gets burned and dsappears

  • Avatar of filbert66 filbert66 Dec 03, 2012 at 03:11 UTC - 0 likes

    The wool block remains, right? So are you just complaining about the brief appearance of fire? I don't think that is worth trying to remove; in fact, it is nice feedback to the user that his attempt succeeded but is now being ignored.

    BTW, you only need to add "35" and don't need to have all the ":1-16" on there.

  • 4 comments

Facts

Last updated
Dec 04, 2012
Reported
Dec 03, 2012
Status
Fixed - Developer made requested changes. QA should verify.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.
Votes
0

Reported by

Possible assignees