Difference between revisions of "Slot Data"

From wiki.vg
Jump to navigation Jump to search
(update format)
m (Add type links.)
 
(12 intermediate revisions by 9 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]].
  
== Format ==
+
=== Slot ===
  
The structure consists of at least a short, which gives the item/block ID [http://www.minecraftwiki.net/wiki/Block_ids]. A value of <code>-1</code> signifies that the slot is empty, and no further data follows.
+
{| class="wikitable"
 
+
! Name
If the block ID is not <code>-1</code>, three more fields follow. These fields are a byte (item count), a short (item damage) and at least another byte.
+
! Type
 
+
! Meaning
If the byte is <code>0</code>, there is no NBT data, and no further data follows. Otherwise the byte is the start of an NBT blob of the following format:
+
|-
 +
| Present
 +
| {{Type|Boolean}}
 +
| True if there is an item in this position; false if it is empty.
 +
|-
 +
| Item ID
 +
| {{Type|Optional}} {{Type|VarInt}}
 +
| 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
 +
| {{Type|Optional}} {{Type|Byte}}
 +
| Omitted if present is false.
 +
|-
 +
| NBT
 +
| {{Type|Optional}} {{Type|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:
 +
|}
  
 
<pre>
 
<pre>
   COMPOUND <nowiki>''</nowiki>
+
   COMPOUND
 
     LIST 'StoredEnchantments'
 
     LIST 'StoredEnchantments'
 
       COMPOUND
 
       COMPOUND
         SHORT 'id'
+
         STRING 'id'
 
         SHORT 'lvl'
 
         SHORT 'lvl'
 
       END
 
       END
Line 26: Line 42:
 
</pre>
 
</pre>
  
See [[NBT]] for more information about the NBT format, and [http://minecraft.gamepedia.com/Player.dat_format#Item_structure here] for the contained information and its format.
+
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.
  
 
== Examples ==
 
== Examples ==
  
 
<pre>
 
<pre>
   ff ff                            | empty slot
+
   00                      | empty slot
   01 16 01 00 00 00                | a diamond pickaxe
+
   01 01 01 00             | a stone block
   01 16 01 00 00 01 04 CA FE BA BE | a diamond pickaxe 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