Bukkit

@Faldonboy

Just as a heads up, if you see a page or a huge chunk of a page spontaneously missing, it means I most likely moved it to the wiki.

@CommodoreAlpha

I have lists of all of the changes made in the dev builds from when the dev server was still online memorized. :P

There are conditions for everything, even things like mcMMO levels. Although I can't seem to find the correct usage of that one now. o.O

EDIT: Heh, guess I deleted my example for using mcMMO levels as a condition, It stopped working after 1.6.4 anyways so oh well.

@Faldonboy

Where do you even find this stuff anyway? I can't find them anywhere. Makes me feel like I'm not doing my job well enough. :P

@CommodoreAlpha

Wait until I hunt down all of the conditions haha, I'm sure there will be quite a few you've never even heard of.

@Faldonboy

Man, I haven't touched my drops file (with 5000+ lines) in such a long time. Gonna have to update a lot of the triggers and variables and add all those ideas I've had circulating in my head since forever.

Anyway, I've a feeling we should remove the "2.0 features" and "2.8 features" pages once we're done moving all the information. Since they would just be taking up space afterwards.

Updated the Parameters page with all of the missing Triggers and Variables(there were a lot).

There are still a LOT of conditions that need to be added but they're going to be a pain to hunt all of them down since a few are widely unused and undocumented.

@sakura_blades

@CommodoreAlpha

They don't need to add up to 100% however, there does need to be something in that drop group that happens 100% of the time, so perhaps try changing your drop chances around to have "Thin Pigs" be the default pig that spawns or create a new pig that ALWAYS spawns when one of these other ones doesn't

The second thing that could be happening is that another plugin could be interfering with OtherDrops in the spawning process. try adding CUSTOM to your spawnedby reasons, also find one of the nameless mobs, look at it and do /od id mob and check the spawnedby reason. If it says "Not Set" then I have yet to find a solution/reason for these to be spawning because it occasionally happens to me too.

EDIT: Also, I suggest removing the !! from your mob names, it's pointless and just makes OtherDrops have to do a slight bit of extra work to parse the drop, the "!!" is mostly used for adding extra data to a drop(Mostly in the case of baby mobs, villagers, etc when there can be more then one type of data, so in the case of handling baby mobs or villager professions you will still need it)

Use this instead.

Pig@10h~&fHealthy_Pig

@sakura_blades

That drop group doesn't add up to 100%. 20% + 40% + 35% + 10% = 105%. You may need to set this to 100%. If this doesn't help, I'll have to think of other solutions...

For your second problem, use "consumetool: integer" which would be a far better alternative to "replacetool: AIR" for... many reasons. For example, "consumetool: 2" means that every time the trigger happens, you lose two of that item.

For the arrow problem, have you considered CraftArrows? It's like a continuation of Mo' Arrows, but it has more arrow types, better configurability per arrow, and the arrow type is based on the lore in the arrow, not the name or damage value.

@Faldonboy

I updated the damageattacker thing on the parameters page, but some ambiguities remain. Please check it out to verify it's not wrong.

@sakura_blades

Custom bows should work, for the tool just use something like this

    ANY_CREATURE:
        - trigger: HIT
          tool: BOW
          lorename: &aPoisonous Bow
          potioneffect.victim: POISON@600@1

An external plugin that I use can create custom arrows that work the way you want but it can't do potion effects, it can allow you to make arrows that have critical chances, critical damage, stun chances, extra damage, etc. It works very well with OtherDrops too since its all done by the lore on items. The plugin is ItemAttributes if you do use it I strongly recommend only using the release versions AND turning off all of the custom health settings(they're very buggy)

@sakura_blades

Unfortunately that poison arrow you're attempting won't work, its a problem with bukkit that's existed forever. Projectiles lose all of their extra data once they're fired so that "Poison Arrow" is seen as "Arrow" once its been fired from a bow.

@CommodoreAlpha

The @ symbol doesn't actually need to be used for naming things, I was unaware that you could even use it for naming haha. This would also work just fine and is slightly shorter.

drop: DIAMOND_SWORD~Excalibur

damageattacker was deprecated in favor of damage.attacker, damage.victim, damage.radius, etc iirc so its better to use the new ones instead.

@sakura_blades

For renaming items, you use a slightly different syntax from renaming mobs. You use the standard symbol to specify extra data, "@" then the symbols to specify item-name, "!".

So for instance,

    GIANT:
    - drop: DIAMOND_SWORD@!~Excalibur

You can actually change snowball damage with this plugin. Looking at more recent documentation, there is a difference between "HIT" and "LEFT_CLICK".

Here's an example pertaining to what you want:

    ANY_CREATURE:
    - trigger: HIT
      tool: PROJECTILE_SNOW_BALL
      damage.victim: 1 # this parameter is similar to damageattacker

This means that upon "HIT"-ing any creature with a snowball, the victim receives one point of damage. You can specify mor parameters if you want.

Examples of both of these are found on this page, which outlines the latest features added to OtherDrops. It's actually immensely helpful - expect me to move contenet their to their appropriate pages in a few days. I have college essays to right before the Jan 1st deadline, and my head is reaching critical mass. I'll be more friendly after a few days and some sleep, so sorry for any rudeness and bad spelling i may have.

@DivinityCraft

I hope you know what you're doing, by spawning blazes in the overworld. (Keep in mind that fireballs can travel a long distance.) :)

    CREEPER:
    - action: MOBSPAWN
      spawnedby: NATURAL
      biome: [DESERT, DESERT_HILLS]
      drop: [NOTHING, BLAZE]

A few important notes...

• If you're like me, and you have creeper mob spawners lying around, they will still spawn creepers in the desert. Plugins that spawn creepers in the desert will still spawn creepers.
• Creepers that spawn underground in a desert biome will be blazes.
• Those biome names may be incorrect... I'm not familiar with 1.7.x.

@DivinityCraft

Anything you want and more. :)

    SPIDER:
    - action: MOBSPAWN
      spawnedby: NATURAL
      height: "<65"
      drop: [NOTHING, CAVE_SPIDER]

If you want ALL spiders - even ones spawned by mob spawners and plugins - to become cave spiders instead, feel free to remove the line including "spawnedby:".