Skip to main content

NBT Support

Support for NBT (Named Binary Tag) data in items.

Overviewโ€‹

SigmaOrders fully supports NBT items, allowing players to order items with custom names, lore, enchantments, and other NBT data.

Supported NBT Dataโ€‹

Enchantmentsโ€‹

Items with enchantments are fully supported:

  • All enchantment types
  • Multiple enchantments
  • Custom enchantment levels
  • Stored in order as JSON

Custom Namesโ€‹

Items with custom names:

  • Display names preserved
  • Shown in order details
  • Validated on delivery

Loreโ€‹

Items with custom lore:

  • All lore lines preserved
  • Displayed in GUI
  • Validated on delivery

Other NBTโ€‹

Additional NBT data:

  • Custom model data
  • Attribute modifiers
  • Other item NBT

Order Creationโ€‹

When creating an order with NBT items:

  • NBT data is detected automatically
  • Enchantments are stored in database
  • Custom item data is preserved
  • Order shows NBT information

Delivery Validationโ€‹

When delivering items:

  • System validates NBT data matches
  • Enchantments must match exactly
  • Custom names must match
  • Lore must match (if applicable)

Storageโ€‹

NBT data is stored:

  • Enchantments: JSON format in database
  • Custom item ID: For ItemsAdder items
  • Other NBT: Preserved in item stack

Configurationโ€‹

NBT items are always allowed by default:

# NBT items are always enabled
# No configuration needed

Blocked Itemsโ€‹

Some items are hardcoded as blocked:

  • Shulker boxes (all variants)
  • Bundle

This prevents data loss and exploits.

Best Practicesโ€‹

  1. Verify NBT: Check NBT data before ordering
  2. Match Exactly: Delivery items must match NBT exactly
  3. Test First: Test NBT items before large orders
  4. Document NBT: Note NBT requirements in order description