Bukkit

@drexel_levante

Glad to hear your enthusiasm. :)

As for triggering an event, a player walking on a block is not currently possible, and will probably be infeasible to add. Although, no one will stop you from making a ticket. ;) The problem with tracking down PlayerMoveEvents in conjunction with the player's location being on top of a specific type of block is, as you can infer, lag. This requires a lot of calculation, and wouldn't be a very feasible implementation. I'm sure ZariusT would have no objection to adding this feature - because OtherDrops doesn't lag unless it "has" to - but with the amount of tickets currently open and the lack of "utility" that can be derived from such a feature, I doubt it would be considered or added anytime soon.

(There's currently a PLAYER_MOVE trigger, but that only applies to a player moving in general, not over a specific block.)

Area is a different story. You need to use WorldGuard regions to be able to implement the idea of triggering events upon player movement within an area. Here's an example of how it can be achieved:

    PLAYER:
    - trigger: PLAYER_MOVE
      region: [WorldGuardRegion1, AnotherExample, RegionName, Etc]
      damage.attacker: 1

Here, every time a player moves within any of those four (poorly-named) regions, they will be damaged for one point of damage.

The idea here, is that the plugin looks for the trigger - every time a player moves at all - within, and only within any of the four specified regions. If both conditions are true, it will apply all "effect-parameters" - in this case, "damage.attacker:".

In a nutshell: walking over blocks is not possible, walking within areas is possible; see example.

@drexel_levante

When posting configurations, please specify it like so to make it easier to read:

<<code yaml>> insert lines of text here <</code>>

When you say "i have an axe set up to act like a hammer", there's a slight problem, in that Minecraft doesn't have hammers, so I'm not sure what you mean. But for simplicity's sake, I think you were referring to making stone bricks cracked.

The configuration you specified there should work for instantly cracking stone bricks. I don't know if actually works, because I don't know what you want exactly. Although, I can provide a "cleaner" version of your drop (copy and paste it if you want):

    SMOOTH_BRICK: #this is the bukkit name for stone bricks; also pay attention to indentation
    - trigger: LEFT_CLICK # use "trigger" instead of "action", because "action" is deprecated
      tool: GOLD_AXE~&6Hammer Axe # don't forget the ~ sign to specify names
      replacementblock: SMOOTH_BRICK@2 # you specify data values with @, not _

Also, specifying "drop: NOTHING" in this context is completely redundant, as nothing drops from left clicking stone bricks to begin with. And on another note - if you "crack" stone-brick, the axe's durability will not go down. If you want it to go down by one, add an extra line containing "damagetool: 1" within the same entry.

@drewch123

Did you try using colour codes within the lore you specified? (And is your configuration format correct? If you're not sure, please post your configurations.) If you have, and it still shows up as &5&o, chances are, colour codes don't currently work in specifying lore. If this is the case, it's going to have to be a "bugfix" (or feature?) that you'll have to wait on ZariusT to add.

@ALPHA_DEALER

I guess that should work, but I don't actually know. You should try it out yourself. :P

The only reason why I think it might not work is because the ampersands you put into the command are read as ampersands and not colour codes. But again, I don't know.

@JaffaMiner

The colour of stained clay is determined by damage value.

@drexel_levante

Thanks for helping out; these two pages, here and here have good examples of using lore/itemnames in conjunction with enchantments and such.

@ALPHA_DEALER

Well, you're not really changing the damage value itself. You can change damage output via OtherDrops, but not the damage value. You essentially have to specify something like the following:

    ZOMBIE:
    - trigger: HIT
      tool: DIAMOND_SWORD
      damage.victim: 3

This snippet of configuration means that upon hitting "ZOMBIE" with "DIAMOND_SWORD", the plugin will deal three points of damage to the victim, in this case, the object receiving the action which happens to be the "ZOMBIE". Now, why is the distinction between output and value important? Because they're not the same thing. When other plugins, mods, or mechanics have to alter damage, the damage added by this plugin will most likely not be altered because the damage-type/reason is different from that of getting hit by a DIAMOND_SWORD. So yes, you can use this to simulate changing the damage value, but you are only in effect, changing the output by compounding the original damage with the plugin's damage. One example where this won't work as well, is when you have to take armour into consideration - none of the "extra" damage will be factored in when reducing damage.

You can use numerical IDs (AKA Magic Values) even if you're using a version of Bukkit where that feature has been deprecated. Just be sure to set up an alias (as a number) for every item name within the material enum.

For the record, it's "- tool: DIAMOND_SWORD&0&rDiamond Sword". You can technically create "donor swords" that do different damage; just specify the tool as that specific diamond sword with that specific name. Just bear in mind, all diamond swords with the same name will have whatever ability you specify for it. So make sure it's a name that players cannot replicate via anvil.

@drexel_levante

What example are you referring to? Please provide a link to the example so I can correct it. It should be like this: "drop: STRINGFishing Line" if you're not specifying any enchantments.

Also, it's "drop:" not "drops:".

@elbowcod

Where has your internet etiquette gone?

That aside, I would recommend getting the gist of how this plugin works and becoming familiar with its format. I would start here and here. Short answer is, yes, OtherDrops can do what you wanted, namely ores into ingots, and increased drops from fortune enchanted pickaxes.

Normally, I'd provide a complete list of examples to help out, but I think I'll let you figure this one out based on only one example:

    IRON_ORE:
    - tool: [ANY_PICKAXE, -WOOD_PICKAXE, -STONE_PICKAXE, -GOLD_PICKAXE]
      drop: IRON_INGOT
    - tool: [IRON_PICKAXE@!LOOT_BONUS_BLOCKS#1, DIAMOND_PICKAXE@!LOOT_BONUS_BLOCKS#1]
      drop: IRON_INGOT/1-2
    - tool: [IRON_PICKAXE@!LOOT_BONUS_BLOCKS#2, DIAMOND_PICKAXE@!LOOT_BONUS_BLOCKS#2]
      drop: IRON_INGOT/1-3 # Keep in mind, you need to specify every level of "Fortune" by hand

@insome617

They should. Use the "FISH_CAUGHT:" condition when specifying a drop.

If it doesn't work for you, make sure there is no other plugin canceling any fishing-related events that should be fired, and also make sure you have a build of OtherDrops that supports this condition-parameter.