ufocrossing
Jack in Box, Houston, According to a lawsuit filed by Houston attorney Randall Kallinen, Anthony Ramos and his family ordered a combo meal at the restaurant near Houston's Bush Intercontinental Airport
minecraft:enchantments
Stores a list of enchantments and their levels on an item
Replaces Enchantments tag
Format: object with fields
levels: object of enchantment (id string) to level (integer [0; 255])
show_in_tooltip: boolean (default: true)
If false, no enchantments will be shown in the item tooltip
Replaces 1st bit of HideFlags tag
e.g. enchantments={levels:{'minecraft:protection':2},show_in_tooltip:false}
Alternatively, can be defined as an inline map of enchantment id to level
e.g. enchantments={sharpness:1}
If not set, has an implicit default value of: {levels:{}}
Can be modified with the set_enchantments, enchant_randomly, and enchant_with_levels loot functions
minecraft:stored_enchantments
Stores list of enchantments and their levels for an Enchanted Book
Unlike minecraft:enchantments, the effects provided by enchantments do not apply from this component
Replaces StoredEnchantments tag on Enchanted Books
Format: same as minecraft:enchantments
show_in_tooltip value replaces 6th bit of HideFlags tag
On Enchanted Books, has an implicit default value of: {levels:{}}
Item Data Format
We have made some large changes to how Item Stack-specific properties are stored and represented in this release, replacing the current NBT 'tag' with structured 'components'.
This change has been made in order to:
Validate item properties at load time, enabling easier identification of invalid data in commands and data packs
This should avoid any 'silent' breakages in commands specifying custom item data for any potential future format changes
Continue to evolve the game to enable the creation of dynamic content
Improve performance in cases where the game needs to frequently look up some property of an item (e.g. Armor Trims rendering every frame)
We understand that this is a significant breaking change for many datapacks and custom maps which will require significant effort to upgrade
We do however believe that this builds critical foundations for future extensibility. We have taken care to ship these changes all at once, with the hope that this avoids future incremental changes requiring many small updates to packs.
The current NBT 'tag' has existed for quite some time, and we are aware that a lot of clever techniques have been developed with this for commands and data packs. Over the course of the snapshot series, we have hugely appreciated your feedback on these changes, allowing us to avoid (often undocumented) functionality being lost without suitable alternatives.
Unstructured NBT data attached to stacks of items (tag field) has been replaced with structured 'components'
This data is parsed and validated when the item is loaded
This should improve performance in certain scenarios (e.g. Armor Trim rendering) when item data was frequently compared or requested and parsed
Custom data can still be stored in the minecraft:custom_data component
Item types (e.g. minecraft:stick) hold a set of default components on an item that individual item stacks can override
The format of serialized items and items in data packs has been updated for consistency and to support components
Item syntax in commands has been updated to support components
When advanced tooltips are enabled (F3+H), the number of components will be displayed instead of number of tags
Default component values for items are now listed in items.json generated in reports directory
Block definitions are now added to blocks.json report (note: those definitions are not used yet and present only for informational purposes)
(edited)