@MrRandalP

It will appear under the files tab once it is approved. Sometimes it takes Bukkit a while.

I've uploaded a BETA version of 1.6.0 for those of you brave enough to alpha test Grief Prevention's Jenkin's builds (which are actually becoming pretty stable now). You MUST have a Jenkins build from the Grief Prevention CI, this WILL NOT FUNCTION with GP 7.7.

@LeChuuck

I can't seem to reproduce the problem. Exactly how big is your claim in blocks?

@LeChuuck

What version of GriefPrevention are you running?

@LeChuuck

Well another other possibility is you might have a plugin creating them or like ryan_the_leach says, they could just be walking in from outside the claim (something Bukkit doesn't give me the ability to stop FYI).

The code that handles it is a single conditional. Looking at it, I can't see how it could be a code problem.

What Bukkit implementation are you using? CraftBukkit?

@LeChuuck

I'm fairly certain they don't. Something else is causing your spawns. Look around for a mob spawner hidden somewhere.

@oliver989

I've tried this a couple of times, but been unsuccessful. The event is broken and any attempt to request a fix has been flagged as "won't fix". Simply put, they obviously don't care.

It's possible it's CraftBukkit, not Bukkit, so I could add it in and maybe Spigot or MCPC+ would work. But it appears as though it will never ever work in CraftBukkit.

Not as much as you might think. We only ask for information about a claim for any given location. Once we have that, everything else we do is our own code.

Well if your allowing explosions to cause damage in Grief Prevention and then be "healed" by CreeperHeal then we would merely need to cancel an event provided by CreeperHeal if player didn't want them to be healed in their claim.

If the player didn't want creeper damage at all in just their claim (and other claims could still have it), we could add a flag for that too. That's one of the advantages of GPFlags structure over GP's structure. The settings in GP are system wide, while ours are claim by claim. You would be telling GP not to handle that particular kind of grief so that we can do it instead. But if you were to leave GP's option turned on, ours would ignore the events because we don't ever undo what GP does.

The primary reason for this policy is that we want people to be aware of what they are doing. We don't want operators to be able to accidentally allow a grief because they don't realize what might happen. Trying to run a successful server is hard enough without plugins counteracting one another unexpectedly.

@ryan_the_leach

Well any new feature would be in the 1.6 GPFlags build, which is designed for GP 7.8. That GP 7.8 has added and incredible amount of customization so you can turn explosions on in claims, outside of claims, above sea level, below sea level. It really is shaping up to be an excellent GP expansion. You should check out their documentationpage.

As for re-enabling damage from explosions, that goes against our model of never undoing Grief Prevention's event cancellation, which is explained further in our own FAQ, so it isn't likely to occur quite that way. But there are other methods.