Items from other plugins¶
The short version¶
If you can hold it, the shop can sell it. Add held item and Drag and drop store the entire item stack, so anything from any plugin works with no setup — including custom model data, NBT and persistent data.
You only need a written reference when you cannot easily hold the item.
References¶
Used by /shop additem and by shift-clicking Set icon.
| Form | Example |
|---|---|
| Vanilla material | DIAMOND, minecraft:stone |
| HeadDatabase | hdb:1234 |
| ItemsAdder | itemsadder:mypack:ruby |
| Oraxen | oraxen:ruby |
| Nexo | nexo:ruby |
| MMOItems | mmoitems:SWORD:CUTLASS |
| EcoItems | eco:ruby |
Run /shop additem with no arguments and it lists which providers are
actually installed on your server.
How this works¶
Every integration goes through reflection rather than a compile-time dependency. That is deliberate: six item plugins would otherwise mean six repositories that must stay reachable for the plugin to build, and a jar that refuses to load when one of them changes a method signature.
A missing plugin is a reference that does not resolve — reported plainly — rather than a broken shop.
Selling matches on NBT
Selling uses isSimilar, so a vanilla diamond sword cannot be sold into a
listing for a custom one built on the same material. This is what stops
players laundering plain items into custom-item prices.