@bigscary

I do not mean completely disable the explosions, just have the possibility to exploit only of the layer 64 (or that you configure) to down.

I found that creeperheal infact DOES have support for this plugin (despite the fact the author denied it lol) All you have to do is go into the yml file generated for the world you want it on and set "magic" to true, and it heals the explosions made by this plugin :D

@Piginabag

No, but you can use this one alongside another plugin that lets you fine-tune scaling for specific monster health/damage/drops/etc. This plugin focuses on game-changing rules only, for tweaks you can use another plugin. :)

@Piginabag

Yes, as mentioned above the feature list. :)

@Invizibiz

It's a common problem with all plugin config files - if you make a formatting mistake while editing the file, you will lose all your changes. The most common mistake is accidentally inserting a TAB at the beginning of a line instead of spaces to indent.

@Lothrazar

Very glad you like it! Please do share with me if you decide to start a video series, and would you mind linking from your video posts to this page so others can find the plugin? Thanks!

@thatguynamedkevin

Yes, creeperheal and many other plugins (including worldguard) have a bug where they don't know how to handle plugins using a specific part of Bukkit. I recommend you upgrade your anti grief to GriefPrevention, which doesn't have that problem. I know upgrading anti grief is a big deal for any server, but I've already reported this issue to several plugin developers and no one takes action because they don't think a problem that impacts only a few servers (those running plugins which create explosions like this one) is important enough to fix. The only way I could "fix" it on my end would be to stop creating my own explosions entirely, which would be a big hit to the feature set.

@Q2Lummox

It's not just creepers. I'd have to disable all types of explosions - enhanced creepers, charged creepers, blazes, magma cubes, enhanced tnt, enhanced ghasts, and more. I really don't want everyone who uses this plugin to have to disable all that awesome just because another plugin has a bug.

@thatguynamedkevin

That's what he's doing already. He just has a minor bug. It's an extremely simple fix: "if entityExplodeEvent.getEntity() == null, then treat it like he treats all other creeper explosions".

@Q2Lummox

i was thinking somthing like that, but i also suggested to the creeperheal author that instead of (i'm assuming he does this) logging the creeper explosion event, it work more like coreprotect rollbacks, i.e. it saves how it was, changes it, then after a set amount of time(in place of a command or complemented with a command) it "rollsback" the explosion, as little as i know about java, it should be possible right?

I know I've suggested before, in fact I've been looking for plugins (besides GriefPrevention) to disable the "Creepers" break the world from a layer of my choice, but there is no way that any other plugin "anti Creeper "work.

It is very difficult for you, add an option of type (a suggestion):

Crepeer_explosions_damage_world: true / false
- Layer: 64 # Down, harms the world. Upward not damaged.

A greeting.

This doesn't seem to work with creeperheal, any reason for this (i really need them to work togeather)

2.0.4 Fixes

• No more null exception when a fresh enderman takes his first damage.

• No more buckets disappearing when a bucket from a stack of buckets is filled with water.

• The wither will now drop loot more often when monster grinders are disabled (his regenerative health was the reason for the issue).

@photocritic

It must be a problem with your permissions plugin, or your configuration of it. I'm only checking for the permission, not for op status, so it must be that you still have the permission. Try using a permissions dump or permission check slash command in-game to confirm that you don't have the permission.

@Zombiemold

It's a known issue, and impossible to fix on my end except to disable functionality. The bug is that many plugins don't know how to handle explosions created with Bukkit's world.createExplosion() method, which is the only way to safely generate your own explosions so that other plugins have a chance to handle them. You get that null exception because in this case, the "entity" is null, and those plugin developers haven't coded for that. I've reported the issue to the WorldGuard guy, but he's refusing to fix it (he changed it from "bug" to "feature request"). I recommend updating to a better anti grief plugin that doesn't have this bug, like GriefPrevention for example. You can also try reporting the details of the issue (as I've provided) to those plugin developers, but I've gotten little response from them myself.

Big issue with Explosions. They aren't firing the correct event it seems, and cause problems with Hawkeye or any logging plugin.

In addition, I believe they are also allowing explosions in areas where explosions are cancelled like towns or protected areas. Also, plugins that normally control creeper explosions like Towny or CreeperHeal, cease to function with these explosions.

The error it produces:

http://pastebin.com/uAweJwme

@lukecfairchild

No, I decided not to expand on the current cave-in mechanic. If you really want it badly, I have published the source code, so you or someone you know can modify it. :) Click the blue "repository" link above.

@Bluffer17

Okay, looking for the issue. :) Will try to clear it up for you.