@MrMightyGnome

Do you have any suggestions? I honestly can't think of any way to prevent this efficiently by any programming means. You could just start right at the core of the problem: The players that do this... Either you have an Antigriefing plugin that prevents this problem entirely or you just have to deal with it. I don't have an AntiGriefing Plugin but I don't have players that do that kind of thing either.

The problem with stone is that you can obtain it from cobblestone which is very easy to get and breaking stone uses up your tools a lot faster than breaking obsidian which just takes you time.

http://i1232.photobucket.com/albums/ff375/D1emex/EHM/2013-02-04_021241_zps68e0cca6.png

This is why creepers shouldn't drop tnt on the surface xD. That hole as you might call it was home of a big complicated piston door, now it's just a hole. I actually find it very funny, especially because I just rebuild it today.

Don't worry I'm busy working on the code myself, I want to prevent creepers from dropping tnt on the surface. I'll probably have to add some more checks. I thought a check for natural light and checking the block under the creeper should be enough, but I might still add a check for the Y-Level....

@bigscary: I like OpenSource, I love it actually. I'm really thankful that your plugins are opensource, but please upload the sourcecode. I don't want to keep asking for it. If I can mess with the most up to date source of your code there might come something good out of it. Also it only takes like 30 sec to push a commit to github. Please don't skip versions either... Ps: I'm still using 2.5.1, because I don't have the source for the newer versions... Soooo nice with no messages spamming the chat :).

2.7 Updates!

• Added announcements for when players challenge the dragon, and when they lose (or possibly win).

• Made the dragon more vengeful - once you start fighting him, he won't stop attacking until one of you is dead.

• When the dragon defeats a player, which includes the player leaving the end or logging out as well as being slain, the dragon regains 25% of his health.

@CrypticArmy

That's already done. In the description above before features, it says you can limit all features to specific worlds.

@Carambaz

Yes, apparently mcpc has added a new type of monster, I guess? Or, it's not properly setting the EntityType for a monster it spawned. Generally, mods which introduce new monster types will be problematic for any Bukkit plugin, because Bukkit only knows about vanilla monsters.

@CorruptedHelix

Fixed.

@JoKosan

I could, but I don't think it's worth the testing headache for me to maintain in the future. I'm okay with pistons not causing stuff to fall. Mostly, I just want some building to be more difficult, and also I want players to have to think about possible cave-ins. Having pistons not trigger falling blocks doesn't seem to get in the way of either of these (not in a big way).

@revslaughter

Thanks, I think I have that fixed. It's was a mistake I made when updating the ender dragon.

@MrMightyGnome

I worry that allowing players to move lots of blocks around using physics (meaning not straight down, but up and to the side) will give griefers a new toy.

As for the other, I feel like we're going in circles on this topic. Please pick any number of plugins which limit explosions, if that's your concern. I'm not introducing explosions, so it's not a new problem (I'm just making them more frequent and bigger). I understand that you don't like craters everywhere on the surface, because I don't either, but it's a common issue that's easy to fix just the way you like by including an explosion control plugin that fits best for your tastes. Any changes I make here will just me nit-picked by someone who comes after you, who'd rather have it a slightly different way.

@Carambaz

Yes, you can lower the torch level or raise the extra monsters level. That's what those config options are for.

Yes, the health thing works fine with other plugins. That's why it's a health value and not a percent, because other plugins could potentially change the max health.

Item stacks forfeit is what percentage of item stacks you're carrying disappear permanently when you die.

@Diemex

I won't do a config for each world. It's hard for me to code and test, and complicated for everyone who wants to make config changes to have to deal with. Few have asked for it, and I so far believe few want it. Even if a lot asked for it, I probably still wouldn't do it for the first two reasons.

Like you, I don't feel great about any of the alternatives you presented. I'm not sure there's an all round "good" solution to this problem of offering unlimited flexibility for multiple worlds while not making life difficult for administrators.

@JoKosan

That would be a good idea and a bad idea at the same time :D. I always use pistons to move some blocks that would otherwise fall down. It's hard work but I like to have a possibility to repair damage, for example I place a wrong block and parts of a mountain collapses.

@all I was thinking about more advancved multiworld support... Where you can enable and disable certain features in certain worlds.

Idea

1. A config for each world.
2. One config and a worldattribute behind every option. "enabled_worlds=world1, world2". This is terrible if someone doesn't use multiple worlds, because the config would be cluttered.
3. Same as Idea 2, but an attribute to disable per world
4. Easiest approach from a coding perspective: Extend the bypass permission to have multiple nodes. I could give every feature a bypass permission. For example: "ehm.bypass.inhibitMonsterGrinders". As a user you would have to put all your worlds in the config and enable all the features that you are interested in. Then you could go into your favorite permissions plugin and disable certain things per world. This would remove the clutter from the config and move it to a permissions plugin instead. I just don't like to do this because I don't want any discussions in the comments because some doofus can't figure out how to use a permissions plugin.

I don't really like any of my ideas 100%, but the last one would be the easiest and cleanest because if you don't need the multiworld stuff your config is clean and if you do a permissions plugin is better for multiworld stuff in any case. There are only a few usecase scenario's I can think of, so it might not even worth my time.

I was also thinking of adding more config options in general. What do you think should be customizable?

@CorruptedHelix

Just not sure why you are complaining about going into the nether for gold. Just mine iron in natural caves?

@bigscary Any ideas on that console spam error?

@orodai

Hm?

@CorruptedHelix arent you supposed to go into natural formations for iron? Or take advantage of the tnt by killing creepers?

@SidRow

Hard to the point where it becomes impossible...? Good luck defeating a horde of zombie pigmen, let alone one, with a wood sword. Furthermore, even getting into the nether.

@SidRow

9 goldnuggets make one gold ingot, you need 27 gold nuggets to make a gold pick. Have you ever been to the nether with Ehm? There are blazes there, pigmen are always aggressive and ghasts are terryfying. You couldn't possibly send new players there, I don't go there either. There is only death and destruction awaiting you there.

@SidRow

Do you only want to be able to use a gold pickaxe to mine stone, or is that additional to iron and diamond? And I don't believe that going to the nether and killing pigzombies is a good way of getting gold. It's not in vanilla minecraft and it definetely isn't here. You would be using up more equipemnt than gaining. Like for armor, arrows and general equipment.

[7:39:47 PM] Icyene: " if (fireball.getShooter().getType() == EntityType.ENDER_DRAGON)" [7:39:58 PM] Icyene: assumes fireball.getShooter != null

[7:40:07 PM] Icyene: which it might, if the fireball was spawned by a plugin

You're assuming a fireball always has a shooter, essentially, which breaks plugins like Storm.