Itemsmith

An in-game item editor for Minecraft 1.21.1 on NeoForge, built for one job: making unique items to hand out to players after events.

Open the editor on the item in your hand, change what you like, give it an aura, abilities and a tooltip of its own, then save it to a library as a numbered limited edition. The journal records who received which number.

Everything is server-authoritative. The client draws the screens and proposes; the server charges every change to the permission nodes it touches and refuses the rest.

The editor

Seven tabs, opened with /itemsmith edit.

• Appearance — name, lore, rarity, display options, a 3D model, and colour gradients across a name or a lore line.
• Stats — durability, attribute modifiers, enchantments, each capped by the config.
• Components — food, potion, and item rules: soulbound, owner-lock, expiry.
• Abilities — composed as a trigger, a shape, actions and their tunings, with a plain-language reading of the result underneath so you can see what you just built.
• Aura — 17 patterns, 14 custom particles, 7 sound layers, and a choice of held, worn or dropped, with a live preview drawn from the same formulas the world uses.
• Tooltip — 9 ready-made panels and an editor that rearranges the rows they are built from, with the real tooltip rendered live underneath.
• Raw NBT — the custom_data tag, for whatever the tabs do not cover.

Twelve starting templates are included, so a reward can be one click away from finished.

Unique items

3D models. Ten original weapon models and five flat trophies. Each weapon is a stack of boxes following a drawn silhouette, with an animated layer carrying the glow and the ornaments. Nothing is borrowed: every asset shipped is original.

Auras. Drawn entirely client-side, so they cost the server nothing. Patterns can wrap tight along a blade, hang loose around a wearer, or halve themselves on the ground.

Tooltips. Panels are drawn from rectangles and the item's own accent colour, so nothing ships as a texture and any colour works. Rows can be reordered, aligned and switched off.

Library, journal and revocation

Save a finished item as a numbered edition, hand copies out by command or from the screen, and read back who got which number. Tooltips can show the number, or keep it a secret that only staff can see.

If a reward turns out to be a mistake, revoking it removes it from players who are online, from everyone else at their next login, and destroys any copy still sitting in a chest the next time somebody opens it. A ledger records what the enforcement actually caught, so "is it dealt with?" has an answer.

Permissions

Eight nodes, through LuckPerms or op levels as a fallback: edit, appearance, stats, components, abilities, visuals, library, nbt. An edit is charged to every node it touches, so somebody with itemsmith.appearance alone can rename an item and nothing else.

Commands

Performance

Three rules the server-side code follows: no work on a tick, nothing proportional to the size of the world, and an early exit for the case where nothing has been configured. Checking a container for a revoked item costs under a microsecond for a double chest, and nothing at all on a server where nothing has ever been revoked.

Requirements

Minecraft 1.21.1, NeoForge 21.1.0 or newer, Java 21. LuckPerms optional. Install on the server and on every client that should see the models, auras and tooltips.