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
- Verify NBT: Check NBT data before ordering
- Match Exactly: Delivery items must match NBT exactly
- Test First: Test NBT items before large orders
- Document NBT: Note NBT requirements in order description
Related Documentation
- ItemsAdder Integration - Custom items
- Item Validation - API validation
- Order Creation - Creating orders