-
Notifications
You must be signed in to change notification settings - Fork 17
Hecatonchyr's Tutorial
When you want to write a config with a specified tool, you can write it in two ways:
STONE:
- tool: DIAMOND_PICKAXE
chance: 20%
drop: STONE
STONE:
- tool: 278
chance: 20%
drop: STONE
Both methods work and you have 20% chance of getting stone instead of cobblestone with a diamond pickaxe, no matter the durability of it. You can also specify multiple tools:
STONE:
- tool: [IRON_PICKAXE, DIAMOND_PICKAXE]
chance: 20%
drop: STONE
OtherDrops also supports tools as ID number:
STONE:
- tool: [257, 278] # This syntax crashes Otherdrops prior to version 2.8b.221
chance: 20%
drop: STONE
Otherdrops also supports durability - eg. 257@0-20. It doesn't care if the interval is greater than the max data value a tool can get. For example an iron pickaxe has 251 uses. It means that data value can be from 0 (brand new) to 251 (broken). Setting 0-9999 is just being lazy (I don't want to check the max use of each tool, I will just put 0-9999 and it will cover all data values, since not a single tool in vanilla minecraft exceeds 9999 uses (max is 1562 for diamond tools)). But be careful with modded tools as some can exceed 9999 uses depending on the mod. Why is this feature interesting ? Because you can create configs where durability will trigger different results:
STONE:
- tool: [257@0-63, 278@0-390] # Brand new pickaxe quite efficient
chance: 20%
drop: STONE
- tool: [257@64-128, 278@391-780] # Average pickaxe, possible double drop
chance: 10%
drop: COBBLESTONE
quantity: 2
- tool: [257@129-192, 278@781-1170] # This pickaxe is damaged and not efficient
chance: 20%
drop: NOTHING
- tool: [257@193-251, 278@1171-1562] # Wasted pickaxe, use with caution
chance: 3%
message: "Your pickaxe broke and hurt you."
damageattacker: 8
damagetool: 400
CREATURE_UNDEAD: # The killing blow is the 777th use of the sword = insane drop occurs
- tool: 276@777
drop: DIAMOND_SWORD@!DAMAGE_UNDEAD#10,FIRE_ASPECT#5@!~Angelic Ray # Use enchantments_ignore_level: true in otherdrops-config.yml to allow any enchantment level to be set
message: "Lucky ! %p just dropped one of the Legendary Five: Angelic Ray !"
CREATURE_UNDEAD: # Angelic Ray really doesn't like undeads (need Essentials)
- action: LEFT_CLICK
tool: DIAMOND_SWORD
lorename: Angelic Ray
chance: 50%
command: "/!*butcher 3" # Unless you are surrounded by mobs, should only kill the undead you fight (kill anything within 3 block radius around you)
event: LIGHTNING@HARMLESS # Well, its an Angelic ray after all !
This concludes what I tested so far. I will edit in a few hours to add the use of data values to create "virtual" entities.