Loots
Loots can be used to specify when to drop a particular item.
You can decide to create different loot types:
blocks
mobs
fishing
For example this is the loots category of a .yml file I created.
info:
namespace: my_loots
loots:
blocks:
ruby_ore:
type: iasurvival:ruby_ore
items:
ruby:
item: iasurvival:ruby
min_amount: 1
max_amount: 2
chance: 100
nether_quartz_ore:
type: NETHER_QUARTZ_ORE
drop_only_first: true
items:
crystal:
item: iasurvival:crystal
min_amount: 1
max_amount: 2
chance: 10
knowledge_fragment:
item: iasurvival:knowledge_fragment
min_amount: 1
max_amount: 2
chance: 15This example has two loots in blocks category.
First one is called ruby_ore (you can call them as you prefer), this will drop a itemsadder:ruby item when you break a custom block of type iasurvival:ruby_ore with a minimum amount of 1 and maximum amount of 2 with 100% chance.
The second one is a loot from a vanilla block. As you imagine it will drop a crystal or a knowledge_fragment when the player breaks a NETHER_QUARTZ_ORE.
These drops are decided by ItemsAdder based on chance you set.
Drop only in specific biomes
Ignore fortune enchant
You can make a loot ignore fortune enchant by adding the ignore_fortune property.
Other types of loots
As I said before there are other types of loots: mobs and fishing. These are some examples:
Fishing
Mobs
Custom mobs loots (old entities method)
In order to let ItemsAdder drop an item based on when you kill a custom mob (created with ItemsAdder) you have to use the ItemsAdderMob metadata attribute. Example:
As you can see I set ItemsAdderMob **** attribute and specified my custom mob namespace:id (in this example I used the creaturesplus:soul mob)
Custom entities loots
In order to let ItemsAdder drop an item based on when you kill a custom entity (created with ItemsAdder) you have to use the ItemsAdderEntity metadata attribute. Example:
As you can see I set ItemsAdderEntity **** attribute and specified my custom mob namespace:id (in this example I used the custom:ninja_skeleton mob)
Villager professions (and any other NBT attribute you want to match)
As you can see I set profession attribute and specified the NBT attribute path, which in this case is VillagerData.profession. Then I set value to minecraft:farmer, this tells ItemsAdder to match only villagers with attribute VillagerData.profession set to minecraft:farmer.
The type attribute of nbt and metadata are really important, don't forget them or matches could not occur.
Drop based on Tile entity NBT data (for example Spawner)
You have to enable this setting if you want to be able to get items from spawners by using an enchanted item with silktouch.
Per-world loots
Loots will drop in all worlds if you don't specify any world.
The special * character allows any world starting with a particular text.
In this example every world starting with world_ will match and will drop loots.
The special ! character denies the loot to be dropped in any world starting with a particular text.
In this example every world starting with private_ will match and won't allow dropping loots.
You can also specify precise world names, in this example example2 won't allow loots to be dropped.
You can also specify precise world names, in this example example1 will allow loots to be dropped.
Last updated
Was this helpful?