Difference between revisions of "Slot Data"
Jump to navigation
Jump to search
m (Replaced "Not present" with "Omitted" to avoid confusion between the field "Present" and weather the current field "is present" in the payload.) |
("04 CA FE BA BE" is not a valid NBT data) |
||
| Line 47: | Line 47: | ||
<pre> | <pre> | ||
| − | 00 | + | 00 | empty slot |
| − | 01 01 01 00 | + | 01 01 01 00 | a stone block |
| − | 01 01 01 | + | 01 01 01 03 00 00 12 34 56 78 | a stone block with (made-up) NBT data |
</pre> | </pre> | ||
[[Category:Protocol Details]] | [[Category:Protocol Details]] | ||
[[Category:Minecraft Modern]] | [[Category:Minecraft Modern]] | ||
Revision as of 05:03, 24 May 2021
The Slot data structure is how Minecraft represents an item and its associated data in the Minecraft Protocol.
Slot
| Name | Type | Meaning |
|---|---|---|
| Present | Boolean | True if there is an item in this position; false if it is empty. |
| Item ID | Optional VarInt | The item ID. Omitted if present is false. Item IDs are distinct from block IDs; see Data Generators for more information |
| Item Count | Optional Byte | Omitted if present is false. |
| NBT | Optional NBT | Omitted if present is false. If 0 (TAG_End), there is no NBT data, and no further data follows. Otherwise the byte is the start of an NBT blob as shown below: |
COMPOUND ''
LIST 'StoredEnchantments'
COMPOUND
SHORT 'id'
SHORT 'lvl'
END
COMPOUND
...
END
...
END
INT 'Unbreakable'
...
END
See NBT for more information about the NBT format, and here for the contained information and its format. Note that tool durability is included in NBT, among other things.
Examples
00 | empty slot 01 01 01 00 | a stone block 01 01 01 03 00 00 12 34 56 78 | a stone block with (made-up) NBT data
