AntiCreeper

New Configuration

Configuration

AntiCreeper now has in-line commands. If you wish, you can use those and "save" the settings without editing.

Old configuration names

Versions 3.1.x and lower user the less flexible configuration fields, but version 3.2 has been built to be backward-compatible with the older config files. So you shouldn't have to change your config.yml if you don't want to change anything. But if you wanted the ability to set depth or yield or blocklist differently for creeper & TNT explosions, you have to use the new format.

Description

Allows control over explosions of type creeper, TNT, wither, and fireball. Each has a config section, named nerf_creeper, nerf_tnt, nerf_fireball, nerf_wither. These names must exist at the beginning of the line, have a colon at the end, and all the subsidiary controls must be indented exactly two spaces. For each type of explosion, the following controls are permitted:

  • .explodeblocks true|false Equivalent to old damageblocks (which form is still supported)
    • If false, the explosion occurs but doesn't damage any placed blocks, but would still damage players.
  • .depth: <integer>
    • if set, disables explodeblocks=false above the supplied depth. Hence, the explosion would not be nerfed. Typically used for "explode when underground".
    • alternative form now supports reverse logic
      • .explodeabove: true|false If true, reverses the logic so only explodes above provided depth
      • .value: sets the depth value
  • .fire true|false Sets whether or not this explosion type can start fires. Note that unless there are blocks being damaged, it is unlikely to find places to set fire.
  • .effects true|false If false, NO smoke or sound. Ignored if not nerfed nor filtered.
  • .power <number> Overrides default radius/power of the explosion.
    • Decimal points are allowed, as in 3.1415926535. Negatives not allowed
    • Explosion visual increases as power increases. Beware of increasing TNT power so much that you cannot run away far enough after lighting it.
    • If zero, no blocks will be damaged, nor entities. Equivalent to setting explodeblocks false and all entitydamage false.
    • Charged (electrocuted) creepers are still doubled in power.
Effective when the explosion is NOT nerfed

The following are only effective when the explosion still damages blocks (i.e. explodeblocks=true or above .depth or a blocklist active)

  • .yield <integer> Equivalent to old creeper_yield, but now possible to have different yields for each type.
    • If set to 0-100, determines the percentage of blocks dropped when explodeblocks=true.
  • .blocklist Equivalent to old creeper_list and tnt_list.
    • list of comma-separated decimal block IDs that the explosion will NOT impact
    • supports #:# form to specify certain types of blocks, like birch wood is 17:2
  • .whitelist true|false Equivalent to old block_whitelist, but now possible to set creepers & TNT differently
    • set to true to flip blocklist to be a list of the only blocks that will be affected
  • .blockphysics true|false If true, throws damaged blocks away from explosion center.
    • not randomized right now so things are evenly distributed
    • can cause lag if you set it for TNT and have large chained TNT explosions
    • not sure if it works for TNT cannons, but believe it does.

Wither

Note that wither skulls are controlled separately from nerf_wither; since they are a type of "fireball", they are controlled by nerf_fireball node. nerf_wither affects the initial explosion of the wither.

The wither has the ability to "walk through walls" or otherwise destroy blocks around it. These are not explosions, and are controlled by the node

  • .destroyblocks true|false If false, wither can still walk through walls, but won't destroy it.
  • .explodeblocks only applies to the initial spawning explosion
  • .blocklist applies to either activity, explosion or walking through walls.

Entity Damage

Because Bukkit classifies many things as entities, at your request I have split out .entitydamage so you can control damage to different entity types. Under entity damage, you may now add the following

  • .toplayer If false, NO damage to players.
  • .tomob If false, no other living entities (animals, mobs, NPCs) will take damage
  • .topainting If false, placed paintings or item frames (NEW) will not be dislodged
  • .todrops If false, dropped items on the ground will not disappear
  • .toitem if false, placed items (ex. vehicles, falling sand, primed TNT) will not take damage
  • .depth: <number> Below this depth, all items in .entitydamage are ignored
    • alternative form now supports reverse logic
      • .explodeabove: true|false If true, reverses the logic so only explodes above provided depth
      • .value: sets the depth value

If you don't use the new refined items above but still have an entry .entitydamage: true the following will set to true:

  • .toplayer
  • .tomob
  • .toitem

but todrops and topainting will be set false to retain backward compatibility, except for under nerf_lightning. Setting entitydamage: false will set all to false.

Do NOT simply add the above items under an .entitydamage: true statement, or load config will fail.

Nerfing Lightning

Lightning is not an explosion, so the only thing that applies to lightning is the entitydamage node as described above.

Nerfing Ender Dragon

The dragon actually "explodes" the blocks it passes through, so the following notes are supported under nerf_dragon:

  • blocklist, whitelist
  • explodeblocks

World names

  • nerfed_worlds: list of world names where above configuration is effective. Names here MUST MATCH world names on your server, or AntiCreeper will do nothing.

Enderman nerfing

Version 3.3 added the ability to nerf the following endermen behaviors, under the nerf_endermen node:

  • .blockliftok disallows block lifting when set false
    • configurably filter which blocks they can lift, similar to above blocklist and whitelist variables
    • Note that by default Minecraft already has a whitelist of only 14 block types, consisting of mostly things people don't build with.
    • For your convenience, see the commented out field below for nerf_endermen.blocklist. You can either leave the ones you want them to ignore, or set nerf_endermen.whitelist=true and delete the ones you want them to avoid.
  • .blockplaceok disallows block placement when set false, if you don't mind the holes but do mind the random placement of blocks.
    • didn't add a blocklist specific to block placement; they can place anything they pick up.
  • .teleportok can disable endermen teleporting if you want, but they end up looking glitchy (drawn moving away, then back) and really get upset if it's raining.

Exploding Beds

nerf_beds true will disable exploding beds in any nether environment/world.

Defaults

nerf_creeper:
  explodeblocks: false
  depth: 0   #that is, everywhere
#  yield:  not set; defaults to system default
#  blocklist:  not set
  entitydamage:
    toplayer: true
    tomob: true
    toitem: true
    todrops: false
    topainting: false
  effects: true
  whitelist: false
  fire: false

nerf_fireball:
  explodeblocks: false
  fire: true
# rest as creepers

nerf_wither:
  explodeblocks: false
  destroyblocks: true // because it makes this boss a bit easier to kill
  fire: false
  depth: 0   #that is, everywhere
#  rest as creepers

nerf_tnt:
  explodeblocks: false
  fire: false
# rest as creepers

nerf_endermen:
  teleportok: true
  blockliftok: true
  blockplaceok: true
  whitelist: false
#  blocklist: 2,3,12,13,37,38,39,40,46,81,82,86,103,110

nerf_lightning:
  entitydamage:
    toplayer: true
    tomob: true
    toitem: true
    todrops: true
    topainting: true

nerf_dragon:
  explodeblocks: true

nerf_beds: false

nerfed_worlds:
- world
- nether
- world_the_end

Examples

"Generous Creepers" Config

Allow creepers to damage blocks everywhere, but return 100% of blocks so players can rebuild

nerf_creeper:
  explodeblocks: true
  yield: 100

"No TNT chains" Config

Allow TNT to damage anything, anywhere, except another TNT block.

nerf_tnt:
  explodeblocks: true
  blocklist: 46

"Only TNT chains" Config

Allow TNT to damage only other TNT, anywhere, except another TNT block. Still will damage players and other living entities.

nerf_tnt:
  explodeblocks: true
  blocklist: 46
  whitelist: true

Nerf all Endermen pickups

nerf_endermen:
  blockliftok: false

Reverse depth on TNT

nerf_tnt:
  depth:
    value: 60
    explodeabove: true

Damage everything but paintings and dropped items

To do this, you have to configure a blocklist or else the entitydamage fields are not effective. If you really want all blocks to be damaged, select something mounted on another block; they will be dropped when their supporting block is dropped. I suggest flowers. Of course, paintings are subject to the same problem! Below example uses nerf_fireball, but could equally apply to any explosion. Also you need the nerf_lightning node if you want to nerf damage caused by lightning.

nerf_fireball:
  explodeblocks: true
  blocklist: 38
  entitydamage:
    toplayer: true
    tomob: true
    toitem: true
    todrops: false
    topainting: false
nerf_lightning:
  entitydamage:
    toplayer: true
    tomob: true
    toitem: true
    todrops: false
    topainting: false

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

  • 6 comments
  • Avatar of filbert66 filbert66 Nov 23, 2012 at 21:52 UTC - 0 likes

    If you've tried the new command "ac print" or "acp" and see a "nerf_tnt.ticks", yes, that is a hidden setting you can play with, only via your config file. (Refer to comment 45 and thank @RossGosling for the prodding)

    My plugins: Anticreeper, AntiFire, AutoIPBan; Contributor: Silence, Thor

    BFAK:67982,3d6540176e18ca75f0a204a87213d75a51e4b745f16c619b8fcef59ccfeab5cb

  • Avatar of Mysticaliptica Mysticaliptica Nov 11, 2012 at 23:08 UTC - 0 likes

    Dont worry, it suddenly worked fine =)

  • Avatar of filbert66 filbert66 Nov 10, 2012 at 01:10 UTC - 0 likes

    @Mysticaliptica: Go

    Hmm. Looks OK to me. Send me your actual file in a Ticket and I'll test it out.Maybe you have some whitespace issues?

  • Avatar of Mysticaliptica Mysticaliptica Nov 05, 2012 at 16:14 UTC - 0 likes

    Im running a Bukkit server 1.3.2-R3.0 (MC is 1.4.2)
    Downloaded lastest AntiCreeper: 3.6.3
    My world folder name and world name of my server is "Mundaka".

    The config file is inside: " {server}/plugins/AntiCreeper3 " folder

    My config looks like:

    # Example config.yml file for AntiCreeper3
    #  doesn't include all possible values, but leaves some at default
    #
    
    nerf_creeper:
      damageblocks: false
    #  depth: 0
    #  yield:  100
      entitydamage:
        toplayer: true
        tomob: true
        toitem: false
        todrops: false
        topainting: false
    	
    nerf_fireball:
      damageblocks: false
      entitydamage:
        toplayer: true
        tomob: true
        toitem: false
        todrops: false
        topainting: false
    
    nerf_tnt:
      damageblocks: true
      entitydamage:
        toplayer: true
        tomob: true
        toitem: false
        todrops: false
        topainting: false
    
    #  blocklist: 46
    # Default is blacklist, so this denies TNT chains
    
    # Save paintings from lightning
    nerf_lightning:
      entitydamage: 
        toplayer: true
        tomob: true
        toitem: false
        todrops: false
        topainting: false
    
    nerfed_worlds:
    - Mundaka
    - Mundaka_nether
    - Mundaka_the_end
    

    Creepers keep destroying blocks.
    (Didnt try anything else)
    Anything wrong?

  • Avatar of RuinedOne RuinedOne Oct 23, 2012 at 08:24 UTC - 0 likes

    @GuyPery: Go

    I don't think it's possible. I set this up on my tekkit server, the values do nothing to change the scope of the ruleset. Shame...

  • Avatar of GuyPery GuyPery Sep 18, 2012 at 12:18 UTC - 0 likes

    Is it possible to install on Tekkit? If so, what do I do to change the settings??

  • 6 comments

Facts

Date created
Mar 18, 2012
Last updated
Apr 15, 2013

Author