-
Notifications
You must be signed in to change notification settings - Fork 15
Custom Item Plugins
Are you using a custom items plugin and want to drop some custom items? If so, this is the place for you. Custom items support the same parameters as Items. You can find examples of how to drop items from these plugins below.
The following custom item plugins are currently supported (Click the name to jump to the wiki section):
- CustomItems/ItemBridge (Link/Link)
- ItemsXL (Link)
- ItemsAdder (Link)
- MMOItems (Link)
- Knokko's CustomItems (Link)
- Oraxen (Link)
- ExecutableItems (Link)
- EcoItems (Link)
If you wish to drop items from the CustomItems plugin, you must also have ItemBridge installed. To drop an item from CustomItems, prefix the item ID with cui:
.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: itembridge
item: 'cui:emeraldHoe'
amount: 1
The item ID will be the .yml file name of the item.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: itemsxl
item: 'your_item'
amount: 1
Simply use the item ID as defined in the ItemsAdder configs. Some item IDs may require a prefix if they are added by an expansion.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: itemsadder
item: 'ruby_ore'
amount: 1
The item
field must contain a :
which separates the item type and the item ID. This field is case-sensitive, meaning it must match the item type and item ID exactly how it is in the MMOItems configs.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
rolls: 1
bonus-rolls: 0
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: mmoitems
item: 'BOW:MARKING_BOW'
amount: 1
The item ID will be the name of the item you defined in the editor.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: knokkocustomitems
item: 'your_item'
amount: 1
The item ID will be the name of the item in the .yml file.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: oraxen
item: 'bedrock_pickaxe'
amount: 1
Simply use the item ID as defined in the ExecutableItems configs.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: executableitems
item: 'world_teleporter'
amount: 1
The item
field supports any item ID that EcoItems normally would. The general format for items created by EcoItems is ecoitems:item_id
.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: ecoitems
item: 'ecoitems:enchanted_ender_eye'
amount: 1