GuidesOnly show guides for your app
GuidesGuidesHow custom-item plugins actually work — the server-side behavior versus the client-side textures, when you need a resource pack, and when a datapack does the job with no plugin at all.
"Custom items" covers a lot: a sword that shoots lightning, a wand with a right-click ability, a new crafting recipe, an item with its own texture and name. Before you install anything, it pays to understand that a custom item is really two things stacked together — behavior and appearance — and they're handled in completely different places. Get that split clear and everything else falls into place.
| At a glance | |
|---|---|
| You need | A plugin-capable server (Purpur, PaperSpigot, or similar) for plugin-based items |
| Plan | Any |
| Time | Ten minutes to grasp the pieces |
A custom item is behavior plus appearance, and each lives somewhere different:
| Layer | What it controls | Where it comes from |
|---|---|---|
| Behavior (server-side) | The name, lore, stats, abilities, recipe, what happens on click | The plugin (or a datapack) — runs on your server, no player download |
| Appearance (client-side) | A brand-new texture or 3D model | A resource pack every player downloads |
The important consequence: your server can create an item with a custom name, glowing enchant, lore text, and special powers, and every player sees it immediately — but if you want it to look different from a vanilla item (its own texture), that texture has to reach each player's game through a server resource pack. Without a pack, a custom item reuses a vanilla texture (often a base item like a stick or a paper, sometimes varied with custom model data). See Server resource packs for how the pack gets to players.
🎯 Good to know: You do not need a resource pack to make custom items with names, lore, and abilities. You only need one when you want an item to have its own texture or model.
1. Datapacks — no plugin, vanilla-friendly. Custom crafting recipes and some item behavior can be done with a datapack, which runs on vanilla too and needs no plugin. If all you want is "combine these into that", start here — it's the lightest option. See Datapacks.
2. Item-framework plugins. These let you define items — stats, lore, abilities, recipes, model data — in config files or an in-game GUI, then give them out with a command. This is the usual route for weapons, tools, and gear with special powers. They're config-heavy, so read YAML without tears before you dive in.
3. Recipe-only plugins. If you just want new or changed crafting recipes and nothing fancier, a small recipe plugin does that without the weight of a full item framework.
Pick the lightest tool that covers what you actually want.
Whichever plugin you land on, the shape is the same:
/plugins/<PluginName>/ or through the plugin's in-game creator. This is where name, lore, abilities, and recipe live.server.properties.⚠️ Heads up: Custom-item plugins evolve quickly and their config formats differ. Treat any example you find online as version-specific, and confirm it against the plugin's own docs before trusting it.
Give yourself the item with the plugin's command. You should see the custom name and lore in your hand, and its ability should fire when you use it. If you added a resource pack, the new texture appears once your client has accepted and loaded the pack.
/reload or restart to register; a plugin recipe may clash with a vanilla one. Check the plugin's console output on start.