Bukkit

@mantegudo It's not bugging it, it's overruling it. Upgrade to b6 (found here) and you can adjust what events are overruled.

@dBi1K A little explanation is perhaps needed :)

What most plugins (including Mobs before 1.9) do is listen for events, and when something happens, they look up the value in the config and change the result of the event.

For example, when a player breaks a block, an event is fired. In this event the author can find out what block it was, and if they want to they can cancel the event, so the block stays whole.

This is fine for simple plugins. When the plugin gets a bit more complicated though it leads to the author having to somehow link specific mobs to data held in memory, and keep track of whether the mob is dead, etc.

This was the reason for the whole purge_specials thing in earlier versions of Mobs - specials was a list of all mobs that would drop items different than other mobs of the same type. When the player killed the mob, I read the data, dropped the loot, and then removed the mob from the list.

Unfortunately, Minecraft regularly removes mobs on its own, and other plugins can remove mobs without me knowing, so the specials list was impossible to keep up-to-date.

When a plugin wants to make a mob have more HP, it usually listens for the damage event, and then reduces the damage done, so that to the player it looks like the mob has more HP.

This is necessary because Notch hardcoded many values directly into Minecraft itself, including the attack power and the maximum health.

So, with 1.9 I decided to take a different approach and substitute my own mobs for Notch's. This means that whenever the plugin is running and a mob spawns, it will be my mob and not the original. This gives me the power to change many aspects of the mob that are normally inaccessible.

The problem comes because Minecraft takes a lot of things for granted, and when the server starts it only loads the position of mobs because it expects every zombie to be identical to every other zombie. Therefore it doesn't bother to load what each zombie drops as it's always the same.

What I can do to fix it is either the simple version, which is to simply loop through all the mobs when the map loads and replace them with mine, or the complicated way which saves the mobs to a database and therefore keeps the data intact.

Probably I'll get the easy fix working very soon (later tonight) and the complicated way might take a bit longer.

Hopefully that makes some sense :)

1.9 b6 is up - direct link

Changes

• Fixed the spawning error seen below
• Added some more mob properties
  • can_be_tamed - stops wolves from being tamed
  • can_become_powered_creeper - stops creepers transforming
  • can_become_pig_zombie - stops pigs transforming
  • can_be_dyed - stops sheep from having their colour changed
  • can_be_sheared - stops sheep and mushroom_cows from being sheared
  • can_remove_grass - stops sheep from eating grass
• The overrule key has now been split into separate keys, and they are all now false by default.

  overrule:
    damaging: no
    burning: no
    spawning: no
    targeting: no
    exploding: no
    enderman_moving_blocks: no
    creating_portal: no
    splitting: no
    regrowing_wool: no
    dying_wool: no
    shearing: no
    changing_block: no
    taming: no
    becoming_powered_creeper: no
    becoming_pig_zombie: no
  

  changing_block is the event that controls sheep eating grass, and other things not yet implemented.

@dBi1K I'll have a look at the Vault thing tonight. It's only supposed to use Vault and an economy plugin if it's found.

As to the drops, it's supposed to be this way. Bukkit doesn't provide the framework to change a few of the fundamental mob properties (like damage or hp) so I had to work directly with Notchcode :(

This means that mobs spawned when the plugin is running are different to mobs spawned when it's not. I'll try and find a way of limiting this as much as possible though.

@tappestry Regarding your sword question, you would need to add a second action to the death_rules with the sword condition and drop.

If you want the sword to replace redstone, put the action after the redstone-dropping action and set replace_drops to yes.

I looked at the CreatureEggs plugin and the author blocks the item being used rather than the creature spawning. I might add the possibility to overrule it but as it's the only thing the plugin does I have to assume that anyone who installs it specifically wants that behaviour :)

@tappestry Percent is a bit confusing, and maybe I should change it or at least change the name.

It's better to think of it like a 100-sided dice.

This means that the chance of rolling a 1 is exactly the same as rolling a 79, or a 22, etc. However, the chance of percent: [above 50] being true is twice the chance of [above 75] being true. The previous example is identical to [below 51] and [below 26] (because there is no 0).

Here's a couple of examples

percent: [5]
percent: [10 to 20]
percent: [above 5]

The first condition has a 1 in 100 chance, the second 10 in 100 (1 in 10) and the third 95 in 100.

@xcoldfyrex As tappestry explained, this is supposed to happen.

Some plugins, either by mistake or by design, cancel some events. If overrule_other_plugins is set to yes Mobs will use its own condition rules (set by the admin) to decide whether to cancel the events. even if other plugins had already cancelled them.

Set it to false if you want other plugins to control their own events, but be aware that there might be conflicts (even before Mobs gets involved).

I think I'll change it to have overrule-per-event settings instead of one global one.

@wekerx12 There is no whole config. The plugin generates an example at the bottom of the config.yml file when it starts for the first time. or you can look at a little example here