-
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. If you would like direct support for another custom items plugin, please request it in our Discord server. 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)
- ItemEdit (Link)
- ItemsXL (Link)
- UberItems (Link)
- ItemsAdder (Link)
- MythicMobs (Link)
- MMOItems (Link)
- Knokko's CustomItems (Link)
- Oraxen (Link)
- ExecutableItems (Link)
- ExecutableBlocks (Link)
- Eco (Link)
- Slimefun (Link)
- CustomCrafting (Link)
- CustomFishing (Link)
- AdvancedItems (Link)
- Nexo (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
Use the item ID that is saved in server storage.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: itemedit
item: 'youritem'
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
The item ID will be the ID of the UberItem or UberMaterial as defined in the plugin or addon.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: uberitems
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
Simply use the item name as defined in the MythicMob item 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: mythicmobs
item: 'SkeletonKingSword'
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
Simply use the block ID as defined in the ExecutableBlocks configs.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: executableblocks
item: 'Free_Test'
amount: 1
The item
field supports any item ID that Eco normally would. Examples for Eco-supported plugins include ecoitems:enchanted_ender_eye
, ecoarmor:shard_angelic
, and ecobosses:steel_golem_spawn_egg
.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: eco
item: 'ecoitems:enchanted_ender_eye'
amount: 1
Use the item ID as defined by Slimefun or an addon.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: slimefun
item: 'fortune_cookie'
amount: 1
Use the namespaced key formatted like PluginName:folder/itemID
.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: customcrafting
item: 'customcrafting:customcrafting/recipe_book'
amount: 1
The item format goes as follows: category:name
. Available categories include bait
, hook
, item
, rod
, and util
.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: customfishing
item: 'bait:worm_bait'
amount: 1
Use the item ID as defined by the config files.
type: ENTITY
overwrite-existing: items
conditions:
- 'entity-type:villager'
pools:
0:
conditions: []
entries:
0:
conditions: []
items:
0:
type: custom_item
plugin: advanceditems
item: 'emerald_scythe'
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: nexo
item: 'sapphire_pickaxe'
amount: 1