Keep players from acquiring dragon egg blocks

So, my goal is to keep a dragon egg block from ending up as a dragon egg in a player's hand. I track the block in a list, and use metadata to mark the block as unavailable. Underneath them is a bedrock block.

I also stop pistons from pushing dragon eggs that are unavailable, and cancel click events as well.

Is there anything else I need to do in order to keep players from getting the eggs?

 

Ne0nx3r0 Does water / lava effect them?

 

-_Husky_-

Nope, but Pistons do

 

-_Husky_- I couldn't seem to get them to, and it's not listed on the dragon egg behavoirs:
http://www.minecraftwiki.net/wiki/Dragon_Egg

 

Explosions?

 

I've taken care of this with:

Code:

@EventHandler(priority=EventPriority.LOWEST, ignoreCancelled=true)
 
    public void onPistonExtend(BlockPistonExtendEvent e)
    {
        BlockFace bf = e.getDirection();
 
        for(int i=1;i<=12;i++)
        {
            if(plugin.bossManager.isBossEgg(e.getBlock().getRelative(bf,i)))
            {
                e.setCancelled(true);
 
                break;
            }
        }
    }

I'm not a fan of having to iterate all 12 blocks, but for some reason just using e.getBlocks() wouldn't return the dragon egg block.

Oh fair point. I suppose I should iterate the blocks in an explosion radius, presuming the egg would be dropped instead of just blown away.

Well I'm not fond of it, but this works for explosions:

Code:

@EventHandler(priority=EventPriority.HIGHEST, ignoreCancelled=true)
    public void onEntityExplode(EntityExplodeEvent e)
    {
        for(Block b : e.blockList())
        {
            if(plugin.bossManager.isBossEgg(b))
            {
                plugin.bossManager.removeBossEgg(b.getLocation());
            }
        }
    }

Sets the egg to air before the explosion to get rid of it.

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

Ne0nx3r0 My apologies, just throwing out ideas, never messed with Dragon eggs

 

-_Husky_- It was a good thing to check, I just wanted to document that it didn't seem to be an issue.