Difference between revisions of "Slot Data"

From wiki.vg
Jump to navigation Jump to search
(1.13.2)
m (Add type links.)
 
(7 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
The '''Slot''' data structure is how Minecraft represents an item and its associated data in the [[Protocol|Minecraft Protocol]].
 
The '''Slot''' data structure is how Minecraft represents an item and its associated data in the [[Protocol|Minecraft Protocol]].
  
=== [[Slot]] ===
+
=== Slot ===
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 9: Line 9:
 
  |-
 
  |-
 
  | Present
 
  | Present
  | Boolean
+
  | {{Type|Boolean}}
 
  | True if there is an item in this position; false if it is empty.
 
  | True if there is an item in this position; false if it is empty.
 
  |-
 
  |-
 
  | Item ID
 
  | Item ID
  | Optional VarInt
+
  | {{Type|Optional}} {{Type|VarInt}}
  | The {{Minecraft Wiki|Data values#Block IDs|item ID}}. Not present if present is false. Item IDs are distinct from block IDs; see [[Data Generators]] for more information
+
  | Omitted if present is false. The {{Minecraft Wiki|Java Edition data values#Blocks|item ID}}. Item IDs are distinct from block IDs; see [[Data Generators]] for more information
 
  |-
 
  |-
 
  | Item Count
 
  | Item Count
  | Optional Byte
+
  | {{Type|Optional}} {{Type|Byte}}
  | Not present if present is false.
+
  | Omitted if present is false.
 
  |-
 
  |-
 
  | NBT
 
  | NBT
  | Optional NBT
+
  | {{Type|Optional}} {{Type|NBT}}
  | Not present 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:
+
  | 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:
 
  |}
 
  |}
  
 
<pre>
 
<pre>
   COMPOUND <nowiki>''</nowiki>
+
   COMPOUND
 
     LIST 'StoredEnchantments'
 
     LIST 'StoredEnchantments'
 
       COMPOUND
 
       COMPOUND
         SHORT 'id'
+
         STRING 'id'
 
         SHORT 'lvl'
 
         SHORT 'lvl'
 
       END
 
       END
Line 41: Line 41:
 
   END
 
   END
 
</pre>
 
</pre>
 +
 +
Note that on old versions, the enchantment id was sent as a SHORT, and not as a STRING.
 +
 +
Since 1.20.2 the root compound also has no name anymore. The NBT data starts with one byte indicating the type, followed by the type-specific data.
  
 
See [[NBT]] for more information about the NBT format, and {{Minecraft Wiki|Player.dat format#Item structure|here}} for the contained information and its format.  Note that tool durability is included in NBT, among other things.
 
See [[NBT]] for more information about the NBT format, and {{Minecraft Wiki|Player.dat format#Item structure|here}} for the contained information and its format.  Note that tool durability is included in NBT, among other things.
Line 49: Line 53:
 
   00                      | empty slot
 
   00                      | empty slot
 
   01 01 01 00            | a stone block
 
   01 01 01 00            | a stone block
   01 01 01 04 CA FE BA BE | a stone block with (made-up) NBT data
+
   01 01 01 03 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]]

Latest revision as of 23:08, 24 February 2024

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 Omitted if present is false. The item ID. 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
        STRING 'id'
        SHORT 'lvl'
      END
      COMPOUND
        ...
      END
      ...
    END
    INT 'Unbreakable'
    ...
  END

Note that on old versions, the enchantment id was sent as a SHORT, and not as a STRING.

Since 1.20.2 the root compound also has no name anymore. The NBT data starts with one byte indicating the type, followed by the type-specific data.

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 12 34 56 78 | a stone block with (made-up) NBT data