Bukkit

@Lazorzz

Try using the section symbol, "§" instead of the ampersand because the plugin will most likely read that literally and display the ampersand instead of formatting it into a colour or chat effect. See the "chat" section of this page for more details.

I've never used this plugin for anything involving text formatting, so I'm not sure if that will fix your problem.

Don't use "@!" without "" because that's for specifying enchantments. Try "@!" instead, like "PAPER@!§l§5Homework Page".

And I know that WikiCreole formatting can be a pain, but you should look at this page to help you format better, especially when you want to write a snippet of your configuration into your comment without it looking a bit funny.

@Cutevalent

Documentation.

Here's how you can do it:

    CREATURE_HOSTILE:
    - drop: EMERALD/10%
    ENDERMAN:
    - drop: EMERALD/10%
    PIG_ZOMBIE:
    - drop: EMERALD/10%

Do note that any cause of death means a 10% chance of dropping an emerald, which includes mob spawner traps. If you want to force a player to kill the mob in order to have any chance at getting an emerald, you need to specify "tool: PLAYER" under each entry.

@LHammonds

I think the issue - concerning arrows on fire and this plugin - is that you can't currently specify an entity on fire, in the sense that you can specify a sheep as blue, or a zombie as "villager", or a creeper as charged. If you could, that would easily be possible (just specify "PROJECTILE_ARROW" being on fire as one of the tools).

Anyhow, have you tried any dev builds of OtherDrops (on a testing server first, to be safe) to see if that clears up the error which occurs in your console? It appears to have worked for @semirotta, as he stated in the comment below mine.

@semirotta

When you say you used another version of OtherDrops, did you mean you used a dev build, a custom build, or an earlier version? That might be helpful to know, because if other people complain with this problem, you can always point them to a build that fixes it.

@semirotta

Actually, if your issue spontaneously disappeared, it's not necessarily a "plugin conflict" per se. There's something else going on. Obviously the code within either plugin can't just autonomously change (unless you have a virus or other malware); something else on either or both sides had to change. It could be anything, really. Maybe even a third plugin! :P

@LHammonds

I've never done anything that complicated before. :P

Did you try adding the "UNIQUE" flag to the relevant portions of the configuration? You could also try moving the "chance: 50%" parameter around to see if that changes the logic/order of the plugin reading the configuration. Here's an example of your config, slightly modified:

  SHEEP:
      - tool: [ANY_WEAPON, ANY_AXE, PROJECTILE_ARROW]
        drop: DEFAULT
      - dropgroup: sheepfoodgroup
        drops:
          - tool: [DAMAGE_BURN, PROJECTILE_FIREBALL, ANY_EXPLOSION, ANY_WEAPON@!FIRE_ASPECT, PROJECTILE_ARROW@!ARROW_FIRE]
            drop: COOKED_BEEF
            quantity: 1
            chance: 50%
            flags: UNIQUE
          - tool: [ALL, -DAMAGE_BURN, -PROJECTILE_FIREBALL, -ANY_EXPLOSION, -ANY_WEAPON@!FIRE_ASPECT, -PROJECTILE_ARROW@!ARROW_FIRE]
            drop: RAW_BEEF
            quantity: 1
            chance: 50%
            flags: UNIQUE
      - tool: [ANY_WEAPON, ANY_AXE, PROJECTILE_ARROW]
        drop: BONE
        chance: 20
        quantity: 1-2
      - tool: ANY_WEAPON
        drop: SPAWN_EGG@THIS
        chance: 0.01
        quantity: 1

You can try that out, but I don't know if it will work. All I did was add the "UNIQUE" flag and move the "chance: 50%" around.

And on a side note, I did not know you could specify an arrow on fire as being "PROJECTILE_ARROW@!ARROW_FIRE". I thought that would be invalid because you can't technically enchant an arrow entity with fire... or can you? I also did not know you could specify "sub-entries" or "subgroups", which will be very helpful to me, so thanks for that.

As for your error, I believe that issue is similar to the one @semirotta had before. I don't know if it's related to switching or not, because other people can run CoreProtect and OtherDrops just fine.

@AlexSmith49

Unfortunately, I don't think it's currently possible. :(

However, that would be a great idea to add to the plugin (spawning fireworks upon a certain event triggering). Although, ZariusT has been away for awhile now.

Now, if you want to know the reasons for why I think it's not possible, I will list them here:

• There is no event (I think) for spawning fireworks.
• The "HIT" trigger doesn't work as intended; it is merely an alias of "LEFT_CLICK".
• I don't know if the "damage-reason" tools (like "PROJECTILE_SNOW_BALL") support parameters other than "BREAK".

And really, all you need are these three parameters to do something like what you asked for, but they don't currently work or aren't implemented yet.

@AlexSmith49

You didn't answer my second question. If you want the best help from people, in general, possible, make your question as unambiguous as possible.

But I'm going to assume (because I don't have any other information to go off of) you mean that if one were to hit any mob with any item, that person gets a firework star. Now, I'm only going to help you this one time with this type of question because the answer (in other words, how to do this) is pretty clear in the documentation. Before you ask a question, read the documentation. If you find it confusing, state that you found it confusing, otherwise it makes it look like you don't want to read, which implies laziness. For future reference, the most important pages are the newer features, parameters, tools, objects, and creatures.

Anyhow, here's how you could probably implement it:

    ANY_CREATURE:
    - tool: ANY
      drop: FIREWORK_CHARGE

Keep in mind that if you want extra data on the firework star (like patterns and colours), that will be more complicated, as it probably includes both the use of NBT tags and data values. And I'm not sure how to edit NBT data on firework stars and fireworks via this plugin.

@Arkatetk

Hmm, sorry, I can't find it anywhere myself either. I can find the "lorename" parameter which allows one to specify an item's name, but I can't find the parameter for specifying lore. There's probably someone else who knows this better than I, and can thus give a better answer.

Also, your syntax for the renaming of the stone pickaxe is wrong. It should be

STONE_PICKAXE@!~&6Test Pickaxe

not

STONE_PICKAXE@&6Test Pickaxe

@semirotta

This is probably one of the most important pages you will want to use when specifying Bukkit material names, always. Oh yeah, and this is also just as important. Just because something sounds intuitive doesn't mean it will work. :P

But yes, you need to use "CROPS" instead. "CROPS" is the actual block, "WHEAT" is the item. You can't "break" the item (in the sense that you break blocks), but you can break the "block-form" of the item, in this case, "CROPS". In hindsight, it doesn't make sense to break items in this game. :D

And from looking at those messages, it looks like some kind of debugging feature is on, and/or your verbosity level is set to higher than normal. Check your verbosity, and if it isn't already set to "low", then set it to "low" and see if that will "fix" it.