Difference between revisions of "Protocol"

From wiki.vg
Jump to navigation Jump to search
m (→‎Close Window (clientbound): Removed unrelated note.)
(→‎Explosion: Radius/strength has been used since 12w34a (second snapshot for 1.4; it added withers); back then it used "largeexplode" for < 2.0 and "hugeexplosion" for >= 2.0.)
(120 intermediate revisions by 28 users not shown)
Line 5: Line 5:
 
   |ICON =  
 
   |ICON =  
 
   |HEADING = Heads up!
 
   |HEADING = Heads up!
   |CONTENT = This article is about the protocol for the latest '''stable''' release of Minecraft '''computer edition''' ([[Protocol version numbers|1.12, protocol 335]]). For the computer edition pre-releases, see [[Pre-release protocol]]. For Pocket Edition, see [[Pocket Edition Protocol Documentation]].
+
   |CONTENT = This article is about the protocol for the latest '''stable''' release of Minecraft '''computer edition''' ([[Protocol version numbers|1.15.2, protocol 578]]). For the computer edition pre-releases, see [[Pre-release protocol]]. For Pocket Edition, see [[Pocket Edition Protocol Documentation]].
 
}}
 
}}
  
 
This page presents a dissection of the current '''[https://minecraft.net/ Minecraft] protocol'''.
 
This page presents a dissection of the current '''[https://minecraft.net/ Minecraft] protocol'''.
  
If you're having trouble, check out the [[Protocol FAQ|FAQ]] or ask for help in the IRC channel [irc://irc.freenode.net/mcdevs #mcdevs on chat.freenode.net] ([http://wiki.vg/MCDevs More Information]).
+
If you're having trouble, check out the [[Protocol FAQ|FAQ]] or ask for help in the IRC channel [ircs://chat.freenode.net:6697/mcdevs #mcdevs on chat.freenode.net] ([http://wiki.vg/MCDevs More Information]).
  
 
'''Note:''' While you may use the contents of this page without restriction to create servers, clients, bots, etc… you still need to provide attribution to #mcdevs if you copy any of the contents of this page for publication elsewhere.
 
'''Note:''' While you may use the contents of this page without restriction to create servers, clients, bots, etc… you still need to provide attribution to #mcdevs if you copy any of the contents of this page for publication elsewhere.
Line 18: Line 18:
 
== Definitions ==
 
== Definitions ==
  
The Minecraft server accepts connections from TCP clients and communicates with them using ''packets''. A packet is a sequence of bytes sent over the TCP connection. The meaning of a packet depends both on its packet ID and the current state of the connection. The initial state of each connection is [[#Handshaking|Handshaking]], and state is switched using the packets [[#Handshake|Handshake]] ([[#Handshaking|Handshaking]], 0x00, serverbound) and [[#Login Success|Login Success]] ([[#Login|Login]], 0x02, clientbound).
+
The Minecraft server accepts connections from TCP clients and communicates with them using ''packets''. A packet is a sequence of bytes sent over the TCP connection. The meaning of a packet depends both on its packet ID and the current state of the connection. The initial state of each connection is [[#Handshaking|Handshaking]], and state is switched using the packets [[#Handshake|Handshake]] and [[#Login Success|Login Success]].
  
 
=== Data types ===
 
=== Data types ===
Line 47: Line 47:
 
  |-
 
  |-
 
  | Global palette
 
  | Global palette
  | A table/dictionary/palette mapping nonnegative integers to block states. The block state IDs can be constructed from {{Minecraft Wiki|Data values|this table}} by multiplying what the Minecraft Wiki calls “block IDs” by 16 and adding the metadata/damage value (or in most programming languages <code>block_id &lt;&lt; 4 <nowiki>|</nowiki> metadata</code>).
+
  | A table/dictionary/palette mapping nonnegative integers to block states. Block state IDs are created in a linear fashion based off of order of assignment.  One block state ID allocated for each unique block state for a block; if a block has multiple properties then the number of allocated states is the product of the number of values for each property.  A current list of properties and state ID ranges is found on [https://pokechu22.github.io/Burger/1.15.2.html burger].
 +
 
 +
Alternatively, the vanilla server now includes an option to export the current block state ID mapping, by running <code>java -cp minecraft_server.jar net.minecraft.data.Main --reports</code>.  See [[Data Generators]] for more information.
 
  |-
 
  |-
 
  | Notchian
 
  | Notchian
Line 97: Line 99:
 
  |rowspan="2"| Yes
 
  |rowspan="2"| Yes
 
  | Packet ID
 
  | Packet ID
  | Varint
+
  | VarInt
 
  | zlib compressed packet ID (see the sections below)
 
  | zlib compressed packet ID (see the sections below)
 
  |-
 
  |-
Line 109: Line 111:
 
If Data Length is set to zero, then the packet is uncompressed; otherwise it is the size of the uncompressed packet.
 
If Data Length is set to zero, then the packet is uncompressed; otherwise it is the size of the uncompressed packet.
  
If compressed, the uncompressed length of (Packet ID + Data) must be equal to or over the threshold set in the packet [[#Set Compression 2|Set Compression]] ([[#Login|Login]], 0x03, clientbound), otherwise the receiving party will disconnect.
+
If compressed, the uncompressed length of (Packet ID + Data) must be equal to or over the threshold set in the packet [[#Set Compression|Set Compression]], otherwise the receiving party will disconnect.
  
Compression can be disabled by sending the packet [[#Set Compression|Set Compression]] ([[#Login|Login]], 0x03, clientbound) with a negative Threshold, or not sending the Set Compression packet at all.
+
Compression can be disabled by sending the packet [[#Set Compression|Set Compression]] with a negative Threshold, or not sending the Set Compression packet at all.
  
 
== Handshaking ==
 
== Handshaking ==
Line 138: Line 140:
 
  | Protocol Version
 
  | Protocol Version
 
  | VarInt
 
  | VarInt
  | See [[protocol version numbers]] (currently 335 in Minecraft 1.12)
+
  | See [[protocol version numbers]] (currently 578 in Minecraft 1.15.2)
 
  |-
 
  |-
 
  | Server Address
 
  | Server Address
 
  | String (255)
 
  | String (255)
  | Hostname or IP, e.g. localhost or 127.0.0.1, that was used to connect. The Notchian server does not use this information.
+
  | Hostname or IP, e.g. localhost or 127.0.0.1, that was used to connect. The Notchian server does not use this information. Note that SRV records are a complete redirect, e.g. if _minecraft._tcp.example.com points to mc.example.org, users connecting to example.com will provide mc.example.org as server address in addition to connecting to it.
 
  |-  
 
  |-  
 
  | Server Port
 
  | Server Port
Line 205: Line 207:
 
  |-
 
  |-
 
  | Type
 
  | Type
  | Byte
+
  | VarInt
  | The type of object (see [[Entities#Objects]])
+
  | The type of object (same as in [[#Spawn Mob|Spawn Mob]])
 
  |-
 
  |-
 
  | X
 
  | X
Line 327: Line 329:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="13"| 0x03
+
  |rowspan="12"| 0x03
  |rowspan="13"| Play
+
  |rowspan="12"| Play
  |rowspan="13"| Client
+
  |rowspan="12"| Client
 
  | Entity ID
 
  | Entity ID
 
  | VarInt
 
  | VarInt
Line 377: Line 379:
 
  | Short
 
  | Short
 
  | Same units as [[#Entity Velocity|Entity Velocity]]
 
  | Same units as [[#Entity Velocity|Entity Velocity]]
|-
 
| Metadata
 
| [[Entities#Entity Metadata Format|Entity Metadata]]
 
|
 
 
  |}
 
  |}
  
Line 406: Line 404:
 
  |  
 
  |  
 
  |-
 
  |-
  | Title
+
  | Motive
  | String (13)
+
  | VarInt
  | Name of the painting. Max length 13
+
  | Panting's ID, see below
 
  |-
 
  |-
 
  | Location
 
  | Location
Line 425: Line 423:
 
{| class="wikitable"
 
{| class="wikitable"
 
  ! Name
 
  ! Name
 +
! ID
 
  ! x
 
  ! x
 
  ! y
 
  ! y
Line 430: Line 429:
 
  ! height
 
  ! height
 
  |-
 
  |-
  | <code>Kebab</code>
+
  | <code>minecraft:kebab</code>
 +
| 0
 
  | 0
 
  | 0
 
  | 0
 
  | 0
Line 436: Line 436:
 
  | 16
 
  | 16
 
  |-
 
  |-
  | <code>Aztec</code>
+
  | <code>minecraft:aztec</code>
 +
| 1
 
  | 16
 
  | 16
 
  | 0
 
  | 0
Line 442: Line 443:
 
  | 16
 
  | 16
 
  |-
 
  |-
  | <code>Alban</code>
+
  | <code>minecraft:alban</code>
 +
| 2
 
  | 32
 
  | 32
 
  | 0
 
  | 0
Line 448: Line 450:
 
  | 16
 
  | 16
 
  |-
 
  |-
  | <code>Aztec2</code>
+
  | <code>minecraft:aztec2</code>
 +
| 3
 
  | 48
 
  | 48
 
  | 0
 
  | 0
Line 454: Line 457:
 
  | 16
 
  | 16
 
  |-
 
  |-
  | <code>Bomb</code>
+
  | <code>minecraft:bomb</code>
 +
| 4
 
  | 64
 
  | 64
 
  | 0
 
  | 0
Line 460: Line 464:
 
  | 16
 
  | 16
 
  |-
 
  |-
  | <code>Plant</code>
+
  | <code>minecraft:plant</code>
 +
| 5
 
  | 80
 
  | 80
 
  | 0
 
  | 0
Line 466: Line 471:
 
  | 16
 
  | 16
 
  |-
 
  |-
  | <code>Wasteland</code>
+
  | <code>minecraft:wasteland</code>
 +
| 6
 
  | 96
 
  | 96
 
  | 0
 
  | 0
Line 472: Line 478:
 
  | 16
 
  | 16
 
  |-
 
  |-
  | <code>Pool</code>
+
  | <code>minecraft:pool</code>
 +
| 7
 
  | 0
 
  | 0
 
  | 32
 
  | 32
Line 478: Line 485:
 
  | 16
 
  | 16
 
  |-
 
  |-
  | <code>Courbet</code>
+
  | <code>minecraft:courbet</code>
 +
| 8
 
  | 32
 
  | 32
 
  | 32
 
  | 32
Line 484: Line 492:
 
  | 16
 
  | 16
 
  |-
 
  |-
  | <code>Sea</code>
+
  | <code>minecraft:sea</code>
 +
| 9
 
  | 64
 
  | 64
 
  | 32
 
  | 32
Line 490: Line 499:
 
  | 16
 
  | 16
 
  |-
 
  |-
  | <code>Sunset</code>
+
  | <code>minecraft:sunset</code>
 +
| 10
 
  | 96
 
  | 96
 
  | 32
 
  | 32
Line 496: Line 506:
 
  | 16
 
  | 16
 
  |-
 
  |-
  | <code>Creebet</code>
+
  | <code>minecraft:creebet</code>
 +
| 11
 
  | 128
 
  | 128
 
  | 32
 
  | 32
Line 502: Line 513:
 
  | 16
 
  | 16
 
  |-
 
  |-
  | <code>Wanderer</code>
+
  | <code>minecraft:wanderer</code>
 +
| 12
 
  | 0
 
  | 0
 
  | 64
 
  | 64
Line 508: Line 520:
 
  | 32
 
  | 32
 
  |-
 
  |-
  | <code>Graham</code>
+
  | <code>minecraft:graham</code>
 +
| 13
 
  | 16
 
  | 16
 
  | 64
 
  | 64
Line 514: Line 527:
 
  | 32
 
  | 32
 
  |-
 
  |-
  | <code>Match</code>
+
  | <code>minecraft:match</code>
 +
| 14
 
  | 0
 
  | 0
 
  | 128
 
  | 128
Line 520: Line 534:
 
  | 32
 
  | 32
 
  |-
 
  |-
  | <code>Bust</code>
+
  | <code>minecraft:bust</code>
 +
| 15
 
  | 32
 
  | 32
 
  | 128
 
  | 128
Line 526: Line 541:
 
  | 32
 
  | 32
 
  |-
 
  |-
  | <code>Stage</code>
+
  | <code>minecraft:stage</code>
 +
| 16
 
  | 64
 
  | 64
 
  | 128
 
  | 128
Line 532: Line 548:
 
  | 32
 
  | 32
 
  |-
 
  |-
  | <code>Void</code>
+
  | <code>minecraft:void</code>
 +
| 17
 
  | 96
 
  | 96
 
  | 128
 
  | 128
Line 538: Line 555:
 
  | 32
 
  | 32
 
  |-
 
  |-
  | <code>SkullAndRoses</code>
+
  | <code>skull_and_roses</code>
 +
| 18
 
  | 128
 
  | 128
 
  | 128
 
  | 128
Line 544: Line 562:
 
  | 32
 
  | 32
 
  |-
 
  |-
  | <code>Wither</code>
+
  | <code>minecraft:wither</code>
 +
| 19
 
  | 160
 
  | 160
 
  | 128
 
  | 128
Line 550: Line 569:
 
  | 32
 
  | 32
 
  |-
 
  |-
  | <code>Fighters</code>
+
  | <code>minecraft:fighters</code>
 +
| 20
 
  | 0
 
  | 0
 
  | 96
 
  | 96
Line 556: Line 576:
 
  | 32
 
  | 32
 
  |-
 
  |-
  | <code>Pointer</code>
+
  | <code>minecraft:pointer</code>
 +
| 21
 
  | 0
 
  | 0
 
  | 192
 
  | 192
Line 562: Line 583:
 
  | 64
 
  | 64
 
  |-
 
  |-
  | <code>Pigscene</code>
+
  | <code>minecraft:pigscene</code>
 +
| 22
 
  | 64
 
  | 64
 
  | 192
 
  | 192
Line 568: Line 590:
 
  | 64
 
  | 64
 
  |-
 
  |-
  | <code>BurningSkull</code>
+
  | <code>minecraft:burning_skull</code>
 +
| 23
 
  | 128
 
  | 128
 
  | 192
 
  | 192
Line 574: Line 597:
 
  | 64
 
  | 64
 
  |-
 
  |-
  | <code>Skeleton</code>
+
  | <code>minecraft:skeleton</code>
 +
| 24
 
  | 192
 
  | 192
 
  | 64
 
  | 64
Line 580: Line 604:
 
  | 48
 
  | 48
 
  |-
 
  |-
  | <code>DonkeyKong</code>
+
  | <code>minecraft:donkey_kong</code>
 +
| 25
 
  | 192
 
  | 192
 
  | 112
 
  | 112
Line 593: Line 618:
 
This packet is sent by the server when a player comes into visible range, ''not'' when a player joins.
 
This packet is sent by the server when a player comes into visible range, ''not'' when a player joins.
  
This packet must be sent after the [[#Player List Item|Player List Item]] ([[#Play|Play]], 0x38, clientbound) packet that adds the player data for the client to use when spawning a player. If the Player List Item for the player spawned by this packet is not present when this packet arrives, Notchian clients will not spawn the player entity. The Player List Item packet includes skin/cape data.
+
This packet must be sent after the [[#Player Info|Player Info]] packet that adds the player data for the client to use when spawning a player. If the Player Info for the player spawned by this packet is not present when this packet arrives, Notchian clients will not spawn the player entity. The Player Info packet includes skin/cape data.
  
 
Servers can, however, safely spawn player entities for players not in visible range. The client appears to handle it correctly.
 
Servers can, however, safely spawn player entities for players not in visible range. The client appears to handle it correctly.
Line 605: Line 630:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="8"| 0x05
+
  |rowspan="7"| 0x05
  |rowspan="8"| Play
+
  |rowspan="7"| Play
  |rowspan="8"| Client
+
  |rowspan="7"| Client
 
  | Entity ID
 
  | Entity ID
 
  | VarInt
 
  | VarInt
Line 634: Line 659:
 
  | Pitch
 
  | Pitch
 
  | Angle
 
  | Angle
|
 
|-
 
| Metadata
 
| [[Entities#Entity Metadata Format|Entity Metadata]]
 
 
  |  
 
  |  
 
  |}
 
  |}
Line 651: Line 672:
 
In an example UUID, <code>xxxxxxxx-xxxx-Yxxx-xxxx-xxxxxxxxxxxx</code>, the UUID version is specified by <code>Y</code>. So, for UUID v3, <code>Y</code> will always be <code>3</code>, and for UUID v2, <code>Y</code> will always be <code>2</code>.
 
In an example UUID, <code>xxxxxxxx-xxxx-Yxxx-xxxx-xxxxxxxxxxxx</code>, the UUID version is specified by <code>Y</code>. So, for UUID v3, <code>Y</code> will always be <code>3</code>, and for UUID v2, <code>Y</code> will always be <code>2</code>.
  
==== Animation (clientbound) ====
+
==== Entity Animation (clientbound) ====
  
 
Sent whenever an entity should change animation.
 
Sent whenever an entity should change animation.
Line 712: Line 733:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="3"| 0x07
+
  |rowspan="4"| 0x07
  |rowspan="3"| Play
+
  |rowspan="4"| Play
  |rowspan="3"| Client
+
  |rowspan="4"| Client
 
  |colspan="2"| Count
 
  |colspan="2"| Count
 
  |colspan="2"| VarInt
 
  |colspan="2"| VarInt
Line 720: Line 741:
 
  |-
 
  |-
 
  |rowspan="2"| Statistic
 
  |rowspan="2"| Statistic
  | Name
+
  | Category ID
 
  |rowspan="2"| Array
 
  |rowspan="2"| Array
  | String (32767)
+
  | VarInt
  | [https://gist.github.com/Alvin-LB/8d0d13db00b3c00fd0e822a562025eff https://gist.github.com/Alvin-LB/8d0d13db00b3c00fd0e822a562025eff]
+
  | See below
 
  |-
 
  |-
  | Value
+
  | Statistic ID
 
  | VarInt
 
  | VarInt
 +
| See below
 +
|-
 +
|colspan="2"| Value
 +
|colspan="2"| VarInt
 
  | The amount to set it to
 
  | The amount to set it to
 
  |}
 
  |}
  
==== Block Break Animation ====
+
Categories (these are namespaced, but with <code>:</code> replaced with <code>.</code>):
  
0–9 are the displayable destroy stages and each other number means that there is no animation on this coordinate.
+
{| class="wikitable"
 +
! Name
 +
! ID
 +
! Registry
 +
|-
 +
| <code>minecraft.mined</code>
 +
| 0
 +
| Blocks
 +
|-
 +
| <code>minecraft.crafted</code>
 +
| 1
 +
| Items
 +
|-
 +
| <code>minecraft.used</code>
 +
| 2
 +
| Items
 +
|-
 +
| <code>minecraft.broken</code>
 +
| 3
 +
| Items
 +
|-
 +
| <code>minecraft.picked_up</code>
 +
| 4
 +
| Items
 +
|-
 +
| <code>minecraft.dropped</code>
 +
| 5
 +
| Items
 +
|-
 +
| <code>minecraft.killed</code>
 +
| 6
 +
| Entities
 +
|-
 +
| <code>minecraft.killed_by</code>
 +
| 7
 +
| Entities
 +
|-
 +
| <code>minecraft.custom</code>
 +
| 8
 +
| Custom
 +
|}
  
Block break animations can still be applied on air; the animation will remain visible although there is no block being broken.  However, if this is applied to a transparent block, odd graphical effects may happen, including water losing its transparency. (An effect similar to this can be seen in normal gameplay when breaking ice blocks)
+
Blocks, Items, and Entities use block (not block state), item, and entity ids.
  
If you need to display several break animations at the same time you have to give each of them a unique Entity ID.
+
Custom has the following (unit only matters for clients):
  
 
{| class="wikitable"
 
{| class="wikitable"
  ! Packet ID
+
  ! Name
  ! State
+
! ID
  ! Bound To
+
  ! Unit
  ! Field Name
+
  |-
  ! Field Type
+
  | <code>minecraft.leave_game</code>
  ! Notes
+
  | 0
 +
  | None
 
  |-
 
  |-
  |rowspan="3"| 0x08
+
  | <code>minecraft.play_one_minute</code>
  |rowspan="3"| Play
+
| 1
  |rowspan="3"| Client
+
| Time
  | Entity ID
+
|-
  | VarInt
+
| <code>minecraft.time_since_death</code>
  | Entity ID of the entity breaking the block
+
| 2
 +
| Time
 +
  |-
 +
| <code>minecraft.sneak_Time</code>
 +
  | 3
 +
| Time
 +
|-
 +
  | <code>minecraft.walk_one_cm</code>
 +
  | 4
 +
  | Distance
 
  |-
 
  |-
  | Location
+
  | <code>minecraft.crouch_one_cm</code>
  | Position
+
  | 5
  | Block Position
+
  | Distance
 
  |-
 
  |-
  | Destroy Stage
+
  | <code>minecraft.sprint_one_cm</code>
| Byte
+
  | 6
  | 0–9 to set it, any other value to remove it
+
  | Distance
  |}
 
 
 
==== Update Block Entity ====
 
 
 
Sets tile entity associated with the block at the given location.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="3"| 0x09
+
  | <code>minecraft.swim_one_cm</code>
|rowspan="3"| Play
+
  | 7
|rowspan="3"| Client
+
  | Distance
| Location
 
  | Position
 
  |  
 
 
  |-
 
  |-
  | Action
+
  | <code>minecraft.fall_one_cm</code>
  | Unsigned Byte
+
  | 8
  | The type of update to perform, see below
+
  | Distance
 
  |-
 
  |-
  | NBT Data
+
  | <code>minecraft.climb_one_cm</code>
  | [[NBT|NBT Tag]]
+
  | 9
  | Data to set.  May be a TAG_END (0), in which case the block entity at the given location is removed (though this is not required since the client will remove the block entity automatically on chunk unload or block removal)
+
| Distance
  |}
+
  |-
 
+
  | <code>minecraft.fly_one_cm</code>
''Action'' field:
+
| 10
 
+
| Distance
* '''1''': Set data of a mob spawner (everything except for SpawnPotentials: current delay, min/max delay, mob to be spawned, spawn count, spawn range, etc.)
+
|-
* '''2''': Set command block text (command and last execution status)
+
| <code>minecraft.dive_one_cm</code>
* '''3''': Set the level, primary, and secondary powers of a beacon
+
| 11
* '''4''': Set rotation and skin of mob head
+
  | Distance
* '''5''': Set type of flower in flower pot
+
  |-
* '''6''': Set base color and patterns on a banner
+
  | <code>minecraft.minecart_one_cm</code>
* '''7''': Set the data for a Structure tile entity
+
  | 12
* '''8''': Set the destination for a end gateway
+
  | Distance
* '''9''': Set the text on a sign
 
* '''10''': Declare a shulker box, no data appears to be sent and the client seems to do fine without this packet. Perhaps it is a leftover from earlier versions?
 
* '''11''': Set the color of a bed
 
 
 
==== Block Action ====
 
 
 
This packet is used for a number of actions and animations performed by blocks, usually non-persistent.
 
 
 
See [[Block Actions]] for a list of values.
 
 
 
{| class="wikitable"
 
  ! Packet ID
 
  ! State
 
  ! Bound To
 
  ! Field Name
 
  ! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="4"| 0x0A
+
  | <code>minecraft.boat_one_cm</code>
|rowspan="4"| Play
+
  | 13
|rowspan="4"| Client
+
  | Distance
| Location
 
  | Position
 
  | Block coordinates
 
 
  |-
 
  |-
  | Action ID (Byte 1)
+
  | <code>minecraft.pig_one_cm</code>
  | Unsigned Byte
+
  | 14
  | Varies depending on block — see [[Block Actions]]
+
  | Distance
 
  |-
 
  |-
  | Action Param (Byte 2)
+
  | <code>minecraft.horse_one_cm</code>
  | Unsigned Byte
+
  | 15
  | Varies depending on block — see [[Block Actions]]
+
  | Distance
 
  |-
 
  |-
  | Block Type
+
  | <code>minecraft.aviate_one_cm</code>
  | VarInt
+
  | 16
  | The block type ID for the block, not including metadata/damage value. This must match the block at the given coordinates.
+
  | Distance
  |}
+
  |-
 
+
  | <code>minecraft.jump</code>
==== Block Change ====
+
  | 17
 
+
  | None
Fired whenever a block is changed within the render distance.
 
 
 
{{Warning2|Changing a block in a chunk that is not loaded is not a stable action.  The Notchian client currently uses a ''shared'' empty chunk which is modified for all block changes in unloaded chunks; while in 1.9 this chunk never renders in older versions the changed block will appear in all copies of the empty chunk. Servers should avoid sending block changes in unloaded chunks and clients should ignore such packets.}}
 
 
 
{| class="wikitable"
 
  ! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="2"| 0x0B
+
  | <code>minecraft.drop</code>
|rowspan="2"| Play
+
  | 18
|rowspan="2"| Client
+
  | None
| Location
 
  | Position
 
  | Block Coordinates
 
 
  |-
 
  |-
  | Block ID
+
  | <code>minecraft.damage_dealt</code>
| VarInt
+
  | 19
| The new block state ID for the block as given in the {{Minecraft Wiki|Data values#Block IDs|global palette}} (When reading data: <code>type = id &gt;&gt; 4</code>, <code>meta = id & 15</code>, when writing data: <code>id = type &lt;&lt; 4 &#124; (meta &amp; 15)</code>)
+
  | Damage
  |}
 
 
 
==== Boss Bar ====
 
 
 
{| class="wikitable"
 
! Packet ID
 
  ! State
 
! Bound To
 
!colspan="2"| Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="15"| 0x0C
+
  | <code>minecraft.damage_taken</code>
|rowspan="15"| Play
+
  | 20
|rowspan="15"| Client
+
  | Damage
|colspan="2"| UUID
 
  | UUID
 
  | Unique ID for this bar
 
 
  |-
 
  |-
  |colspan="2"| Action
+
  | <code>minecraft.deaths</code>
  | VarInt Enum
+
  | 21
  | Determines the layout of the remaining packet
+
  | None
 
  |-
 
  |-
  ! Action
+
  | <code>minecraft.mob_kills</code>
  ! Field Name
+
  | 22
  !
+
  | None
!
 
 
  |-
 
  |-
  |rowspan="5"| 0: add
+
  | <code>minecraft.animals_bred</code>
| Title
+
  | 23
  | [[Chat]]
+
  | None
  |  
 
 
  |-
 
  |-
  | Health
+
  | <code>minecraft.player_kills</code>
  | Float
+
  | 24
  | From 0 to 1. Values greater than 1 do not crash a Notchian client, and start [https://i.johni0702.de/nA.png rendering part of a second health bar] at around 1.5.
+
  | None
 
  |-
 
  |-
  | Color
+
  | <code>minecraft.fish_caught</code>
  | VarInt Enum
+
  | 25
  | Color ID (see below)
+
  | None
 
  |-
 
  |-
  | Division
+
  | <code>minecraft.talked_to_villager</code>
  | VarInt Enum
+
  | 26
  | Type of division (see below)
+
  | None
 
  |-
 
  |-
  | Flags
+
  | <code>minecraft.traded_with_villager</code>
  | Unsigned Byte
+
  | 27
  | Bit mask. 0x1: should darken sky, 0x2: is dragon bar (used to play end music)
+
  | None
 
  |-
 
  |-
  | 1: remove
+
  | <code>minecraft.eat_cake_slice</code>
  | ''no fields''
+
  | 28
  | ''no fields''
+
  | None
| Removes this boss bar
 
 
  |-
 
  |-
  | 2: update health
+
  | <code>minecraft.fill_cauldron</code>
  | Health
+
  | 29
  | Float
+
  | None
| as above
 
 
  |-
 
  |-
  | 3: update title
+
  | <code>minecraft.use_cauldron</code>
  | Title
+
  | 30
| [[Chat]]
+
  | None
  |  
 
 
  |-
 
  |-
  |rowspan="2"| 4: update style
+
  | <code>minecraft.clean_armor</code>
| Color
+
  | 31
  | VarInt Enum
+
  | None
  | Color ID (see below)
 
 
  |-
 
  |-
  | Dividers
+
  | <code>minecraft.clean_banner</code>
  | VarInt Enum
+
  | 32
  | as above
+
  | None
 
  |-
 
  |-
  | 5: update flags
+
  | <code>minecraft.interact_with_brewingstand</code>
  | Flags
+
  | 33
  | Unsigned Byte
+
  | None
| as above
 
 
  |-
 
  |-
  |}
+
  | <code>minecraft.interact_with_beacon</code>
 
+
| 34
{| class="wikitable"
+
| None
  ! ID
+
|-
  ! Color
+
| <code>minecraft.inspect_dropper</code>
 +
  | 35
 +
  | None
 +
|-
 +
| <code>minecraft.inspect_hopper</code>
 +
| 36
 +
| None
 
  |-
 
  |-
  | 0
+
  | <code>minecraft.inspect_dispenser</code>
  | Pink
+
  | 37
 +
| None
 
  |-
 
  |-
  | 1
+
  | <code>minecraft.play_noteblock</code>
  | Blue
+
  | 38
 +
| None
 
  |-
 
  |-
  | 2
+
  | <code>minecraft.tune_noteblock</code>
  | Red
+
  | 39
 +
| None
 
  |-
 
  |-
  | 3
+
  | <code>minecraft.pot_flower</code>
  | Green
+
  | 40
 +
| None
 
  |-
 
  |-
  | 4
+
  | <code>minecraft.trigger_trapped_chest</code>
  | Yellow
+
  | 41
 +
| None
 
  |-
 
  |-
  | 5
+
  | <code>minecraft.open_enderchest</code>
  | Purple
+
  | 42
 +
| None
 
  |-
 
  |-
  | 6
+
  | <code>minecraft.enchant_item</code>
  | White
+
  | 43
  |}
+
  | None
 
 
{| class="wikitable"
 
! ID
 
! Type of division
 
 
  |-
 
  |-
  | 0
+
  | <code>minecraft.play_record</code>
  | No division
+
  | 44
 +
| None
 
  |-
 
  |-
  | 1
+
  | <code>minecraft.interact_with_furnace</code>
  | 6 notches
+
  | 45
 +
| None
 
  |-
 
  |-
  | 2
+
  | <code>minecraft.interact_with_crafting_table</code>
  | 10 notches
+
  | 46
 +
| None
 
  |-
 
  |-
  | 3
+
  | <code>minecraft.open_chest</code>
  | 12 notches
+
  | 47
 +
| None
 
  |-
 
  |-
  | 4
+
  | <code>minecraft.sleep_in_bed</code>
  | 20 notches
+
  | 48
  |}
+
| None
 +
|-
 +
| <code>minecraft.open_shulker_box</code>
 +
| 49
 +
| None
 +
  |}
  
==== Server Difficulty ====
+
Units:
 +
 
 +
* None: just a normal number (formatted with 0 decimal places)
 +
* Damage: value is 10 times the normal amount
 +
* Distance: a distance in centimeters (hundredths of blocks)
 +
* Time: a time span in ticks
  
Changes the difficulty setting in the client's option menu
+
==== Acknowledge Player Digging ====
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,000: Line 1,026:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="1"| 0x0D
+
  |rowspan="4"| 0x08
  |rowspan="1"| Play
+
  |rowspan="4"| Play
  |rowspan="1"| Client
+
  |rowspan="4"| Client
  | Difficulty
+
  | Location
  | Unsigned Byte
+
| Position
  | 0: peaceful, 1: easy, 2: normal, 3: hard
+
| Position where the digging was happening
 +
|-
 +
| Block
 +
| VarInt
 +
| Block state ID of the block that should be at that position now.
 +
|-
 +
  | Status
 +
  | VarInt enum
 +
| Same as Player Digging.  Only Started digging (0), Cancelled digging (1), and Finished digging (2) are used.
 +
|-
 +
| Successful
 +
| Boolean
 +
| True if the digging succeeded; false if the client should undo any changes it made locally.  (How does this work?)
 
  |}
 
  |}
  
==== Tab-Complete (clientbound) ====
+
==== Block Break Animation ====
 +
 
 +
0–9 are the displayable destroy stages and each other number means that there is no animation on this coordinate.
 +
 
 +
Block break animations can still be applied on air; the animation will remain visible although there is no block being broken.  However, if this is applied to a transparent block, odd graphical effects may happen, including water losing its transparency.  (An effect similar to this can be seen in normal gameplay when breaking ice blocks)
  
The server responds with a list of auto-completions of the last word sent to it. In the case of regular chat, this is a player username. Command names and parameters are also supported. The client sorts these alphabetically before listing them.
+
If you need to display several break animations at the same time you have to give each of them a unique Entity ID. The entity ID does not need to correspond to an actual entity on the client. It is valid to use a randomly generated number.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,020: Line 1,062:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x0E
+
  |rowspan="3"| 0x09
  |rowspan="2"| Play
+
  |rowspan="3"| Play
  |rowspan="2"| Client
+
  |rowspan="3"| Client
  | Count
+
  | Entity ID
 
  | VarInt
 
  | VarInt
  | Number of elements in the following array
+
  | Entity ID of the entity breaking the block
 +
|-
 +
| Location
 +
| Position
 +
| Block Position
 
  |-
 
  |-
  | Matches
+
  | Destroy Stage
  | Array of String (32767)
+
  | Byte
  | One eligible command, note that each command is sent separately instead of in a single string, hence the need for Count
+
  | 0–9 to set it, any other value to remove it
 
  |}
 
  |}
  
==== Chat Message (clientbound) ====  
+
==== Update Block Entity ====
  
Identifying the difference between Chat/System Message is important as it helps respect the user's chat visibility options.  See [[Chat#Processing chat|processing chat]] for more info about these positions.
+
Sets the block entity associated with the block at the given location.
 
 
{{warning2|Game info accepts json formatting but does not display it, although the deprecated §-based formatting works.  This is not an issue when using the [[#Title|Title]] packet, so prefer that packet for displaying information in that slot.  See [https://bugs.mojang.com/browse/MC-119145 MC-119145] for more information.}}
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,046: Line 1,090:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x0F
+
  |rowspan="3"| 0x0A
  |rowspan="2"| Play
+
  |rowspan="3"| Play
  |rowspan="2"| Client
+
  |rowspan="3"| Client
  | JSON Data
+
  | Location
  | [[Chat]]
+
  | Position
  | Limited to 32767 bytes
+
  |  
 +
|-
 +
| Action
 +
| Unsigned Byte
 +
| The type of update to perform, see below
 
  |-
 
  |-
  | Position
+
  | NBT Data
  | Byte
+
  | [[NBT|NBT Tag]]
  | 0: chat (chat box), 1: system message (chat box), 2: game info (above hotbar).
+
  | Data to set.  May be a TAG_END (0), in which case the block entity at the given location is removed (though this is not required since the client will remove the block entity automatically on chunk unload or block removal)
 
  |}
 
  |}
  
==== Multi Block Change ====
+
''Action'' field:
 +
 
 +
* '''1''': Set data of a mob spawner (everything except for SpawnPotentials: current delay, min/max delay, mob to be spawned, spawn count, spawn range, etc.)
 +
* '''2''': Set command block text (command and last execution status)
 +
* '''3''': Set the level, primary, and secondary powers of a beacon
 +
* '''4''': Set rotation and skin of mob head
 +
* '''5''': Declare a conduit
 +
* '''6''': Set base color and patterns on a banner
 +
* '''7''': Set the data for a Structure tile entity
 +
* '''8''': Set the destination for a end gateway
 +
* '''9''': Set the text on a sign
 +
* '''10''': Unused
 +
* '''11''': Declare a bed
 +
* '''12''': Set data of a jigsaw block
 +
* '''13''': Set items in a campfire
 +
* '''14''': Behive information
 +
 
 +
==== Block Action ====
 +
 
 +
This packet is used for a number of actions and animations performed by blocks, usually non-persistent.
  
Fired whenever 2 or more blocks are changed within the same chunk on the same tick.
+
See [[Block Actions]] for a list of values.
  
{{Warning|Changing blocks in chunks not loaded by the client is unsafe (see note on [[#Block Change|Block Change]]).}}
+
{{Warning2|This packet uses a block ID, not a block state.  Unfortunately, block IDs are not directly included in the output from [[Data Generators]], but can manually be calculated.}}
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,068: Line 1,135:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  !colspan="2"| Field Name
+
  ! Field Name
  !colspan="2"| Field Type
+
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="6"| 0x10
+
  |rowspan="4"| 0x0B
  |rowspan="6"| Play
+
  |rowspan="4"| Play
  |rowspan="6"| Client
+
  |rowspan="4"| Client
  |colspan="2"| Chunk X
+
  | Location
  |colspan="2"| Int
+
  | Position
  | Chunk X coordinate
+
  | Block coordinates
 
  |-
 
  |-
  |colspan="2"| Chunk Z
+
  | Action ID (Byte 1)
|colspan="2"| Int
 
| Chunk Z coordinate
 
|-
 
|colspan="2"| Record Count
 
|colspan="2"| VarInt
 
| Number of elements in the following array, i.e. the number of blocks affected
 
|-
 
|rowspan="3"| Record
 
| Horizontal Position
 
|rowspan="3"| Array
 
 
  | Unsigned Byte
 
  | Unsigned Byte
  | The 4 most significant bits (<code>0xF0</code>) encode the X coordinate, relative to the chunk. The 4 least significant bits (<code>0x0F</code>) encode the Z coordinate, relative to the chunk.
+
  | Varies depending on block — see [[Block Actions]]
 
  |-
 
  |-
  | Y Coordinate
+
  | Action Param (Byte 2)
 
  | Unsigned Byte
 
  | Unsigned Byte
  | Y coordinate of the block
+
  | Varies depending on block — see [[Block Actions]]
 
  |-
 
  |-
  | Block ID
+
  | Block Type
 
  | VarInt
 
  | VarInt
  | The new block state ID for the block as given in the {{Minecraft Wiki|Data values#Block IDs|global palette}} (When reading data: <code>type = id &gt;&gt; 4</code>, <code>meta = id & 15</code>, when writing data: <code>id = type &lt;&lt; 4 &#124; (meta &amp; 15)</code>)
+
  | The block type ID for the block.  This must match the block at the given coordinates.
 
  |}
 
  |}
  
To decode the position into a world position:
+
==== Block Change ====
  
<syntaxhighlight lang="java">
+
Fired whenever a block is changed within the render distance.
worldX = (horizPos >> 4 & 15) + (chunkX * 16);
 
worldY = vertPos;
 
worldZ = (horizPos & 15) + (chunkZ * 16);
 
</syntaxhighlight>
 
  
==== Confirm Transaction (clientbound) ====
+
{{Warning2|Changing a block in a chunk that is not loaded is not a stable action.  The Notchian client currently uses a ''shared'' empty chunk which is modified for all block changes in unloaded chunks; while in 1.9 this chunk never renders in older versions the changed block will appear in all copies of the empty chunk.  Servers should avoid sending block changes in unloaded chunks and clients should ignore such packets.}}
 
 
A packet from the server indicating whether a request from the client was accepted, or whether there was a conflict (due to lag). If the packet was not accepted, the client must respond with a [[#Confirm Transaction (serverbound)|serverbound confirm transaction]] packet.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,122: Line 1,173:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="3"| 0x11
+
  |rowspan="2"| 0x0C
  |rowspan="3"| Play
+
  |rowspan="2"| Play
  |rowspan="3"| Client
+
  |rowspan="2"| Client
  | Window ID
+
  | Location
  | Byte
+
  | Position
  | The ID of the window that the action occurred in
+
  | Block Coordinates
 
  |-
 
  |-
  | Action Number
+
  | Block ID
  | Short
+
  | VarInt
  | Every action that is to be accepted has a unique number. This number is an incrementing integer (starting at 0) with separate counts for each window ID.
+
  | The new block state ID for the block as given in the {{Minecraft Wiki|Data values#Block IDs|global palette}}. See that section for more information.
|-
 
| Accepted
 
| Boolean
 
| Whether the action was accepted
 
 
  |}
 
  |}
  
==== Close Window (clientbound) ====
+
==== Boss Bar ====  
 
 
This packet is sent from the server to the client when a window is forcibly closed, such as when a chest is destroyed while it's open.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,146: Line 1,191:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  ! Field Name
+
  !colspan="2"| Field Name
 
  ! Field Type
 
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  | 0x12
+
  |rowspan="14"| 0x0D
  | Play
+
  |rowspan="14"| Play
  | Client
+
  |rowspan="14"| Client
  | Window ID
+
  |colspan="2"| UUID
  | Unsigned Byte
+
  | UUID
  | This is the ID of the window that was closed. 0 for inventory.
+
  | Unique ID for this bar
|}
 
 
 
==== Open Window ====
 
 
 
This is sent to the client when it should open an inventory, such as a chest, workbench, or furnace. This message is not sent anywhere for clients opening their own inventory.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="5"| 0x13
+
  |colspan="2"| Action
  |rowspan="5"| Play
+
  | VarInt Enum
  |rowspan="5"| Client
+
  | Determines the layout of the remaining packet
| Window ID
 
| Unsigned Byte
 
| A unique id number for the window to be displayed. Notchian server implementation is a counter, starting at 1.
 
 
  |-
 
  |-
  | Window Type
+
  ! Action
  | String (32)
+
  ! Field Name
  | The window type to use for display. See [[Inventory]] for a list.
+
  !
 +
!
 
  |-
 
  |-
  | Window Title
+
  |rowspan="5"| 0: add
 +
| Title
 
  | [[Chat]]
 
  | [[Chat]]
  | The title of the window
+
  |  
 +
|-
 +
| Health
 +
| Float
 +
| From 0 to 1. Values greater than 1 do not crash a Notchian client, and start [https://i.johni0702.de/nA.png rendering part of a second health bar] at around 1.5.
 
  |-
 
  |-
  | Number Of Slots
+
  | Color
  | Unsigned Byte
+
  | VarInt Enum
  | Number of slots in the window (excluding the number of slots in the player inventory)
+
  | Color ID (see below)
 
  |-
 
  |-
  | Entity ID
+
  | Division
  | Optional Int
+
  | VarInt Enum
  | EntityHorse's EID. Only sent when Window Type is “EntityHorse”
+
  | Type of division (see below)
|}
 
 
 
See [[Inventory]] for further information.
 
 
 
==== Window Items ====
 
[[File:Inventory-slots.png|thumb|The inventory slots]]
 
 
 
Sent by the server when items in multiple slots (in a window) are added/removed. This includes the main inventory, equipped armour and crafting slots.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="3"| 0x14
+
  | Flags
|rowspan="3"| Play
 
|rowspan="3"| Client
 
| Window ID
 
 
  | Unsigned Byte
 
  | Unsigned Byte
  | The ID of window which items are being sent for. 0 for player inventory.
+
  | Bit mask. 0x1: should darken sky, 0x2: is dragon bar (used to play end music), 0x04: create fog (previously was also controlled by 0x02)
 
  |-
 
  |-
  | Count
+
  | 1: remove
  | Short
+
  | ''no fields''
  | Number of elements in the following array
+
  | ''no fields''
 +
| Removes this boss bar
 
  |-
 
  |-
  | Slot Data
+
  | 2: update health
  | Array of [[Slot Data|Slot]]
+
  | Health
  |  
+
  | Float
  |}
+
  | as above
 
 
See [[Inventory#Windows|inventory windows]] for further information about how slots are indexed.
 
 
 
==== Window Property ====
 
 
 
This packet is used to inform the client that part of a GUI window should be updated.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="3"| 0x15
+
  | 3: update title
|rowspan="3"| Play
+
  | Title
|rowspan="3"| Client
+
  | [[Chat]]
  | Window ID
 
  | Unsigned Byte
 
 
  |  
 
  |  
 
  |-
 
  |-
  | Property
+
  |rowspan="2"| 4: update style
  | Short
+
| Color
  | The property to be updated, see below
+
  | VarInt Enum
 +
  | Color ID (see below)
 +
|-
 +
| Dividers
 +
| VarInt Enum
 +
| as above
 +
|-
 +
| 5: update flags
 +
| Flags
 +
| Unsigned Byte
 +
| as above
 
  |-
 
  |-
| Value
 
| Short
 
| The new value for the property, see below
 
 
  |}
 
  |}
 
The meaning of the Property field depends on the type of the window. The following table shows the known combinations of window type and property, and how the value is to be interpreted.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
 +
! ID
 +
! Color
 
  |-
 
  |-
  ! Window type
+
  | 0
  ! Property
+
  | Pink
! Value
 
 
  |-
 
  |-
  |rowspan="4"| Furnace
+
  | 1
| 0: Fire icon (fuel left)
+
  | Blue
  | counting from fuel burn time down to 0 (in-game ticks)
 
 
  |-
 
  |-
  | 1: Maximum fuel burn time
+
  | 2
  | fuel burn time or 0 (in-game ticks)
+
  | Red
 
  |-
 
  |-
  | 2: Progress arrow
+
  | 3
  | counting from 0 to maximum progress (in-game ticks)
+
  | Green
 
  |-
 
  |-
  | 3: Maximum progress
+
  | 4
  | always 200 on the notchian server
+
  | Yellow
 
  |-
 
  |-
  |rowspan="10"| Enchantment Table
+
  | 5
  | 0: Level requirement for top enchantment slot
+
  | Purple
|rowspan="3"| The enchantment's xp level requirement
 
 
  |-
 
  |-
  | 1: Level requirement for middle enchantment slot
+
  | 6
 +
| White
 +
|}
 +
 
 +
{| class="wikitable"
 +
! ID
 +
! Type of division
 
  |-
 
  |-
  | 2: Level requirement for bottom enchantment slot
+
  | 0
 +
| No division
 
  |-
 
  |-
  | 3: The enchantment seed
+
  | 1
  | Used for drawing the enchantment names (in [[Wikipedia:Standard Galactic Alphabet|SGA]]) clientside.  The same seed ''is'' used to calculate enchantments, but some of the data isn't sent to the client to prevent easily guessing the entire list (the seed value here is the regular seed bitwise and <code>0xFFFFFFF0</code>).
+
  | 6 notches
 
  |-
 
  |-
  | 4: Enchantment ID shown on mouse hover over top enchantment slot
+
  | 2
  |rowspan="3"| The enchantment id (set to -1 to hide it)
+
  | 10 notches
 
  |-
 
  |-
  | 5: Enchantment ID shown on mouse hover over middle enchantment slot
+
  | 3
 +
| 12 notches
 
  |-
 
  |-
  | 6: Enchantment ID shown on mouse hover over bottom enchantment slot
+
  | 4
  |-
+
  | 20 notches
  | 7: Enchantment level shown on mouse hover over the top slot
+
  |}
|rowspan="3"| The enchantment level (1 = I, 2 = II, 6 = VI, etc.), or -1 if no enchant
+
 
 +
==== Server Difficulty ====
 +
 
 +
Changes the difficulty setting in the client's option menu
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | 8: Enchantment level shown on mouse hover over the middle slot
+
  |rowspan="2"| 0x0E
 +
|rowspan="2"| Play
 +
|rowspan="2"| Client
 +
| Difficulty
 +
| Unsigned Byte
 +
| 0: peaceful, 1: easy, 2: normal, 3: hard
 
  |-
 
  |-
  | 9: Enchantment level shown on mouse hover over the bottom slot
+
  | Difficulty locked?
  |-
+
  | Boolean
  |rowspan="3"| Beacon
+
  |
| 0: Power level
 
| 0-4, controls what effect buttons are enabled
 
|-
 
| 1: First potion effect
 
| {{Minecraft Wiki|Data values#Status effects|Potion effect ID}} for the first effect, or -1 if no effect
 
|-
 
| 2: Second potion effect
 
| {{Minecraft Wiki|Data values#Status effects|Potion effect ID}} for the second effect, or -1 if no effect
 
|-
 
| Anvil
 
| 0: Repair cost
 
| The repair's cost in xp levels
 
|-
 
| Brewing Stand
 
| 0: Brew time
 
| 0–400, with 400 making the arrow empty, and 0 making the arrow full
 
 
  |}
 
  |}
  
==== Set Slot ====
+
==== Chat Message (clientbound) ====  
 +
 
 +
Identifying the difference between Chat/System Message is important as it helps respect the user's chat visibility options.  See [[Chat#Processing chat|processing chat]] for more info about these positions.
  
Sent by the server when an item in a slot (in a window) is added/removed.
+
{{warning2|Game info accepts json formatting but does not display it, although the deprecated §-based formatting works.  This is not an issue when using the [[#Title|Title]] packet, so prefer that packet for displaying information in that slot.  See [https://bugs.mojang.com/browse/MC-119145 MC-119145] for more information.}}
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,332: Line 1,347:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="3"| 0x16
+
  |rowspan="2"| 0x0F
  |rowspan="3"| Play
+
  |rowspan="2"| Play
  |rowspan="3"| Client
+
  |rowspan="2"| Client
  | Window ID
+
  | JSON Data
 +
| [[Chat]]
 +
| Limited to 32767 bytes
 +
|-
 +
| Position
 
  | Byte
 
  | Byte
  | The window which is being updated. 0 for player inventory. Note that all known window types include the player inventory. This packet will only be sent for the currently opened window while the player is performing actions, even if it affects the player inventory. After the window is closed, a number of these packets are sent to update the player's inventory window (0).
+
  | 0: chat (chat box), 1: system message (chat box), 2: game info (above hotbar).
|-
 
| Slot
 
| Short
 
| The slot that should be updated
 
|-
 
| Slot Data
 
| [[Slot Data|Slot]]
 
|
 
 
  |}
 
  |}
  
To set the cursor (the item currently dragged with the mouse), use -1 as Window ID and as Slot.
+
==== Multi Block Change ====
  
This packet can only be used to edit the hotbar of the player's inventory if window ID is set to 0 (slots 36 through 44).  If the window ID is set to -2, then any slot in the inventory can be used but no add item animation will be played.
+
Fired whenever 2 or more blocks are changed within the same chunk on the same tick.
  
==== Set Cooldown ====
+
{{Warning|Changing blocks in chunks not loaded by the client is unsafe (see note on [[#Block Change|Block Change]]).}}
 
 
Applies a cooldown period to all items with the given type.  Used by the Notchian server with enderpearls.  This packet should be sent when the cooldown starts and also when the cooldown ends (to compensate for lag), although the client will end the cooldown automatically.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,360: Line 1,369:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  ! Field Name
+
  !colspan="2"| Field Name
  ! Field Type
+
  !colspan="2"| Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x17
+
  |rowspan="6"| 0x10
  |rowspan="2"| Play
+
  |rowspan="6"| Play
  |rowspan="2"| Client
+
  |rowspan="6"| Client
  | Item ID
+
|colspan="2"| Chunk X
  | VarInt
+
|colspan="2"| Int
  | Numeric ID of the item to apply a cooldown to.
+
| Chunk X coordinate
 +
  |-
 +
  |colspan="2"| Chunk Z
 +
|colspan="2"| Int
 +
  | Chunk Z coordinate
 
  |-
 
  |-
  | Cooldown Ticks
+
  |colspan="2"| Record Count
  | VarInt
+
  |colspan="2"| VarInt
  | Number of ticks to apply a cooldown for, or 0 to clear the cooldown.
+
  | Number of elements in the following array, i.e. the number of blocks affected
  |}
+
|-
 +
|rowspan="3"| Record
 +
| Horizontal Position
 +
|rowspan="3"| Array
 +
| Unsigned Byte
 +
| The 4 most significant bits (<code>0xF0</code>) encode the X coordinate, relative to the chunk. The 4 least significant bits (<code>0x0F</code>) encode the Z coordinate, relative to the chunk.
 +
|-
 +
| Y Coordinate
 +
| Unsigned Byte
 +
| Y coordinate of the block
 +
|-
 +
| Block ID
 +
| VarInt
 +
| The new block state ID for the block as given in the {{Minecraft Wiki|Data values#Block IDs|global palette}}. See that section for more information.
 +
  |}
  
==== Plugin Message (clientbound) ====
+
To decode the position into a world position:
  
{{Main|Plugin channels}}
+
<syntaxhighlight lang="java">
 +
worldX = (horizPos >> 4 & 15) + (chunkX * 16);
 +
worldY = vertPos;
 +
worldZ = (horizPos & 15) + (chunkZ * 16);
 +
</syntaxhighlight>
  
Mods and plugins can use this to send their data. Minecraft itself uses a number of [[plugin channel]]s. These internal channels are prefixed with <code>MC|</code>.
+
==== Tab-Complete (clientbound) ====
  
More documentation on this: [http://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/ http://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/]
+
The server responds with a list of auto-completions of the last word sent to it. In the case of regular chat, this is a player username. Command names and parameters are also supported. The client sorts these alphabetically before listing them.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,388: Line 1,419:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  ! Field Name
+
  !colspan="2"| Field Name
  ! Field Type
+
  !colspan="2"| Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x18
+
  |rowspan="8"| 0x11
  |rowspan="2"| Play
+
  |rowspan="8"| Play
  |rowspan="2"| Client
+
  |rowspan="8"| Client
  | Channel
+
|-
  | String (20)
+
|colspan="2"| ID
  | Name of the [[plugin channel]] used to send the data
+
|colspan="2"| VarInt
 +
| Transaction ID
 +
  |-
 +
  |colspan="2"| Start
 +
  |colspan="2"| VarInt
 +
| Start of the text to replace
 
  |-
 
  |-
  | Data
+
  |colspan="2"| Length
  | Byte Array
+
  |colspan="2"| VarInt
  | Any data, depending on the channel. <code><nowiki>MC|</nowiki></code> channels are documented [[plugin channel|here]].  The length of this array must be inferred from the packet length.
+
  | Length of the text to replace
|}
 
 
 
==== Named Sound Effect ====
 
{{See also|#Sound Effect}}
 
 
 
Used to play a sound effect on the client. Custom sounds may be added by resource packs.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="7"| 0x19
+
  |colspan="2"| Count
  |rowspan="7"| Play
+
  |colspan="2"| VarInt
  |rowspan="7"| Client
+
  | Number of elements in the following array
| Sound Name
 
| String (256)
 
| All sound effect names as of 1.12.0 can be seen [http://pokechu22.github.io/Burger/1.12.html#sounds here].
 
 
  |-
 
  |-
  | Sound Category
+
  |rowspan="3"| Matches
  | VarInt Enum
+
  | Match
  | The category that this sound will be played from ([https://gist.github.com/konwboj/7c0c380d3923443e9d55 current categories])
+
|rowspan="3"| Array
 +
| String (32767)
 +
  | One eligible value to insert, note that each command is sent separately instead of in a single string, hence the need for Count.  Note that for instance this doesn't include a leading <code>/</code> on commands.
 
  |-
 
  |-
  | Effect Position X
+
  | Has tooltip
  | Int
+
  | Boolean
  | Effect X multiplied by 8 ([[Data types#Fixed-point numbers|fixed-point number]] with only 3 bits dedicated to the fractional part)
+
  | True if the following is present
|-
 
| Effect Position Y
 
| Int
 
| Effect Y multiplied by 8 ([[Data types#Fixed-point numbers|fixed-point number]] with only 3 bits dedicated to the fractional part)
 
|-
 
| Effect Position Z
 
| Int
 
| Effect Z multiplied by 8 ([[Data types#Fixed-point numbers|fixed-point number]] with only 3 bits dedicated to the fractional part)
 
|-
 
| Volume
 
| Float
 
| 1 is 100%, can be more
 
 
  |-
 
  |-
  | Pitch
+
  | Tooltip
  | Float
+
  | Optional [[Chat]]
  | Float between 0.5 and 2.0 by Notchian clients
+
  | Tooltip to display; only present if previous boolean is true
 
  |}
 
  |}
  
==== Disconnect (play) ====
+
==== Declare Commands ====
 +
 
 +
Lists all of the commands on the server, and how they are parsed.
  
Sent by the server before it disconnects a client. The client assumes that the server has already closed the connection by the time the packet arrives.
+
This is a directed graph, with one root node. Each redirect or child node must refer only to nodes that have already been declared.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,461: Line 1,472:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  | 0x1A
+
  |rowspan="3"| 0x12
  | Play
+
  |rowspan="3"| Play
  | Client
+
  |rowspan="3"| Client
  | Reason
+
  | Count
  | [[Chat]]
+
| VarInt
  | Displayed to the client when the connection terminates.
+
  | Number of elements in the following array
 +
|-
 +
| Nodes
 +
| Array of [[Command Data|Node]]
 +
  | An array of nodes
 +
|-
 +
| Root index
 +
| VarInt
 +
| Index of the <code>root</code> node in the previous array
 
  |}
 
  |}
  
==== Entity Status ====
+
For more information on this packet, see the [[Command Data]] article.
 +
 
 +
==== Window Confirmation (clientbound) ====
  
Entity statuses generally trigger an animation for an entityThe available statuses vary by the entity's type (and are available to subclasses of that type as well).
+
A packet from the server indicating whether a request from the client was accepted, or whether there was a conflict (due to lag)If the packet was not accepted, the client must respond with a [[#Window Confirmation (serverbound)|serverbound window confirmation]] packet.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,481: Line 1,502:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x1B
+
  |rowspan="3"| 0x13
  |rowspan="2"| Play
+
  |rowspan="3"| Play
  |rowspan="2"| Client
+
  |rowspan="3"| Client
  | Entity ID
+
  | Window ID
  | Int
+
  | Byte
  |  
+
  | The ID of the window that the action occurred in
 +
|-
 +
| Action Number
 +
| Short
 +
| Every action that is to be accepted has a unique number. This number is an incrementing integer (starting at 0) with separate counts for each window ID.
 
  |-
 
  |-
  | Entity Status
+
  | Accepted
  | Byte Enum
+
  | Boolean
  | See below
+
  | Whether the action was accepted
 
  |}
 
  |}
  
See [[entities]] for a list of which statuses are valid for each type of entity.
+
==== Close Window (clientbound) ====
  
==== Explosion ====
+
This packet is sent from the server to the client when a window is forcibly closed, such as when a chest is destroyed while it's open.
 
 
Sent when an explosion occurs (creepers, TNT, and ghast fireballs).
 
 
 
Each block in Records is set to air. Coordinates for each axis in record is int(X) + record.x
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,509: Line 1,530:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="9"| 0x1C
+
  | 0x14
  |rowspan="9"| Play
+
  | Play
  |rowspan="9"| Client
+
  | Client
  | X
+
  | Window ID
| Float
+
  | Unsigned Byte
|
+
  | This is the ID of the window that was closed. 0 for inventory.
|-
 
| Y
 
| Float
 
|
 
|-
 
| Z
 
| Float
 
|
 
|-
 
| Radius
 
| Float
 
| Currently unused in the client
 
|-
 
| Record Count
 
| Int
 
| Number of elements in the following array
 
|-
 
| Records
 
  | Array of (Byte, Byte, Byte)
 
  | Each record is 3 signed bytes long, each bytes are the XYZ (respectively) offsets of affected blocks.
 
|-
 
| Player Motion X
 
| Float
 
| X velocity of the player being pushed by the explosion
 
|-
 
| Player Motion Y
 
| Float
 
| Y velocity of the player being pushed by the explosion
 
|-
 
| Player Motion Z
 
| Float
 
| Z velocity of the player being pushed by the explosion
 
 
  |}
 
  |}
  
==== Unload Chunk ====
+
==== Window Items ====
 +
[[File:Inventory-slots.png|thumb|The inventory slots]]
  
Tells the client to unload a chunk column.
+
Sent by the server when items in multiple slots (in a window) are added/removed. This includes the main inventory, equipped armour and crafting slots.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,561: Line 1,551:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x1D
+
  |rowspan="3"| 0x15
  |rowspan="2"| Play
+
  |rowspan="3"| Play
  |rowspan="2"| Client
+
  |rowspan="3"| Client
  | Chunk X
+
  | Window ID
  | Int
+
  | Unsigned Byte
  | Block coordinate divided by 16, rounded down
+
  | The ID of window which items are being sent for. 0 for player inventory.
 
  |-
 
  |-
  | Chunk Z
+
  | Count
  | Int
+
  | Short
  | Block coordinate divided by 16, rounded down
+
| Number of elements in the following array
 +
|-
 +
| Slot Data
 +
| Array of [[Slot Data|Slot]]
 +
  |  
 
  |}
 
  |}
  
It is legal to send this packet even if the given chunk is not currently loaded.
+
See [[Inventory#Windows|inventory windows]] for further information about how slots are indexed.
  
==== Change Game State ====
+
==== Window Property ====
  
Used for a wide variety of game state things, from whether to bed use to gamemode to demo messages.
+
This packet is used to inform the client that part of a GUI window should be updated.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,587: Line 1,581:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x1E
+
  |rowspan="3"| 0x16
  |rowspan="2"| Play
+
  |rowspan="3"| Play
  |rowspan="2"| Client
+
  |rowspan="3"| Client
  | Reason
+
  | Window ID
 
  | Unsigned Byte
 
  | Unsigned Byte
  | See below
+
  |  
 +
|-
 +
| Property
 +
| Short
 +
| The property to be updated, see below
 
  |-
 
  |-
 
  | Value
 
  | Value
  | Float
+
  | Short
  | Depends on Reason
+
  | The new value for the property, see below
 
  |}
 
  |}
  
''Reason codes'':
+
The meaning of the Property field depends on the type of the window. The following table shows the known combinations of window type and property, and how the value is to be interpreted.
  
 
{| class="wikitable"
 
{| class="wikitable"
  ! Reason
+
|-
  ! Effect
+
  ! Window type
 +
  ! Property
 
  ! Value
 
  ! Value
 
  |-
 
  |-
  | 0
+
  |rowspan="4"| Furnace
  | Invalid Bed
+
  | 0: Fire icon (fuel left)
  | Would be used to switch between messages, but the only used message is 0 for invalid bed
+
  | counting from fuel burn time down to 0 (in-game ticks)
 
  |-
 
  |-
  | 1
+
  | 1: Maximum fuel burn time
  | End raining
+
  | fuel burn time or 0 (in-game ticks)
  |  
+
  |-
 +
| 2: Progress arrow
 +
| counting from 0 to maximum progress (in-game ticks)
 +
|-
 +
| 3: Maximum progress
 +
| always 200 on the notchian server
 +
|-
 +
|rowspan="10"| Enchantment Table
 +
| 0: Level requirement for top enchantment slot
 +
|rowspan="3"| The enchantment's xp level requirement
 
  |-
 
  |-
  | 2
+
  | 1: Level requirement for middle enchantment slot
| Begin raining
 
|
 
 
  |-
 
  |-
  | 3
+
  | 2: Level requirement for bottom enchantment slot
| Change gamemode
 
| 0: Survival, 1: Creative, 2: Adventure, 3: Spectator
 
 
  |-
 
  |-
  | 4
+
  | 3: The enchantment seed
  | Exit end
+
  | Used for drawing the enchantment names (in [[Wikipedia:Standard Galactic Alphabet|SGA]]) clientsideThe same seed ''is'' used to calculate enchantments, but some of the data isn't sent to the client to prevent easily guessing the entire list (the seed value here is the regular seed bitwise and <code>0xFFFFFFF0</code>).
| 0: Immediately send Client Status of respawn without showing end credits; 1: Show end credits and respawn at the end (or when esc is pressed).  1 is sent if the player has not yet received the "The end?" achievement, while if they do have it 0 is used.
 
 
  |-
 
  |-
  | 5
+
  | 4: Enchantment ID shown on mouse hover over top enchantment slot
  | Demo message
+
  |rowspan="3"| The enchantment id (set to -1 to hide it), see below for values
| 0: Show welcome to demo screen, 101: Tell movement controls, 102: Tell jump control, 103: Tell inventory control
 
|-  
 
| 6
 
| Arrow hitting player
 
| Appears to be played when an arrow strikes another player in Multiplayer
 
 
  |-
 
  |-
  | 7
+
  | 5: Enchantment ID shown on mouse hover over middle enchantment slot
| Fade value
 
| The current darkness value. 1 = Dark, 0 = Bright, Setting the value higher causes the game to change color and freeze
 
 
  |-
 
  |-
  | 8
+
  | 6: Enchantment ID shown on mouse hover over bottom enchantment slot
| Fade time
 
| Time in ticks for the sky to fade
 
 
  |-
 
  |-
  | 10
+
  | 7: Enchantment level shown on mouse hover over the top slot
  | Play elder guardian mob appearance (effect and sound)
+
  |rowspan="3"| The enchantment level (1 = I, 2 = II, 6 = VI, etc.), or -1 if no enchant
  |  
+
|-
  |}
+
| 8: Enchantment level shown on mouse hover over the middle slot
 
+
  |-
==== Keep Alive (clientbound) ====
+
  | 9: Enchantment level shown on mouse hover over the bottom slot
 
+
|-
The server will frequently send out a keep-alive, each containing a random ID. The client must respond with the same packet. If the client does not respond to them for over 30 seconds, the server kicks the client. Vice versa, if the server does not send any keep-alives for 20 seconds, the client will disconnect and yields a "Timed out" exception.
+
|rowspan="3"| Beacon
 
+
| 0: Power level
{| class="wikitable"
+
| 0-4, controls what effect buttons are enabled
  ! Packet ID
+
|-
  ! State
+
| 1: First potion effect
  ! Bound To
+
| {{Minecraft Wiki|Data values#Status effects|Potion effect ID}} for the first effect, or -1 if no effect
  ! Field Name
+
|-
  ! Field Type
+
| 2: Second potion effect
  ! Notes
+
| {{Minecraft Wiki|Data values#Status effects|Potion effect ID}} for the second effect, or -1 if no effect
 +
|-
 +
| Anvil
 +
  | 0: Repair cost
 +
  | The repair's cost in xp levels
 +
  |-
 +
  |rowspan="2"| Brewing Stand
 +
  | 0: Brew time
 +
  | 0 – 400, with 400 making the arrow empty, and 0 making the arrow full
 
  |-
 
  |-
  |rowspan="1"| 0x1F
+
  | 1: Fuel time
|rowspan="1"| Play
+
  | 0 - 20, with 0 making the arrow empty, and 20 making the arrow full
|rowspan="1"| Client
 
| Keep Alive ID
 
| VarInt
 
  |  
 
 
  |}
 
  |}
  
==== Chunk Data ====
+
For an enchanting table, the following numerical IDs are used:
{{Main|Chunk Format}}
 
{{See also|#Unload Chunk}}
 
 
 
The server only sends skylight information for chunk pillars in the {{Minecraft Wiki|Overworld}}, it's up to the client to know in which dimenison the player is currently located. You can also infer this information from the primary bitmask and the amount of uncompressed bytes sent.  This packet also sends all block entities in the chunk (though sending them is not required; it is still legal to send them with [[#Update Block Entity|Update Block Entity]] later).
 
  
 
{| class="wikitable"
 
{| class="wikitable"
  ! Packet ID
+
  ! Numerical ID
  ! State
+
  ! Enchantment ID
  ! Bound To
+
  ! Enchantment Name
  ! Field Name
+
|-
  ! Field Type
+
  | 0
  ! Notes
+
  | minecraft:protection
 +
  | Protection
 
  |-
 
  |-
  |rowspan="9"| 0x20
+
  | 1
  |rowspan="9"| Play
+
| minecraft:fire_protection
  |rowspan="9"| Client
+
  | Fire Protection
  | Chunk X
+
  |-
  | Int
+
  | 2
  | Chunk coordinate (block coordinate divided by 16, rounded down)
+
  | minecraft:feather_falling
 +
  | Feather Falling
 
  |-
 
  |-
  | Chunk Z
+
  | 3
  | Int
+
  | minecraft:blast_protection
  | Chunk coordinate (block coordinate divided by 16, rounded down)
+
  | Blast Protection
 
  |-
 
  |-
  | Ground-Up Continuous
+
  | 4
  | Boolean
+
  | minecraft:projectile_protection
  | See [[Chunk Format#Ground-up continuous|Chunk Format]]
+
  | Projectile Protection
 
  |-
 
  |-
  | Primary Bit Mask
+
  | 5
  | VarInt
+
  | minecraft:respiration
  | Bitmask with bits set to 1 for every 16×16×16 chunk section whose data is included in Data. The least significant bit represents the chunk section at the bottom of the chunk column (from y=0 to y=15).
+
  | Respiration
|-
 
| Size
 
| VarInt
 
| Size of Data in bytes
 
 
  |-
 
  |-
  | Data
+
  | 6
  | Byte array
+
  | minecraft:aqua_affinity
  | See [[Chunk Format#Data structure|data structure]] in Chunk Format
+
  | Aqua Affinity
 
  |-
 
  |-
  | Number of block entities
+
  | 7
  | VarInt
+
  | minecraft:thorns
  | Length of the following array
+
  | Thorns
 
  |-
 
  |-
  | Block entities
+
  | 8
  | Array of [[NBT|NBT Tag]]
+
  | minecraft:depth_strider
  | All block entities in the chunk.  Use the x, y, and z tags in the NBT to determine their positions.
+
  | Depth Strider
|}
 
 
 
==== Effect ====
 
 
 
Sent when a client is to play a sound or particle effect.
 
 
 
By default, the Minecraft client adjusts the volume of sound effects based on distance. The final boolean field is used to disable this, and instead the effect is played from 2 blocks away in the correct direction. Currently this is only used for effect 1023 (wither spawn) and effect 1028 (enderdragon death); it is ignored on other effects.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="4"| 0x21
+
  | 9
|rowspan="4"| Play
+
  | minecraft:frost_walker
|rowspan="4"| Client
+
  | Frost Walker
| Effect ID
 
  | Int
 
  | The ID of the effect, see below
 
 
  |-
 
  |-
  | Location
+
  | 10
  | Position
+
  | minecraft:binding_curse
  | The location of the effect
+
  | Curse of Binding
 
  |-
 
  |-
  | Data
+
  | 11
  | Int
+
  | minecraft:sharpness
  | Extra data for certain effects, see below
+
  | Sharpness
 
  |-
 
  |-
  | Disable Relative Volume
+
  | 12
  | Boolean
+
  | minecraft:smite
| See above
+
  | Smite
  |}
 
 
 
Effect IDs:
 
 
 
{| class="wikitable"
 
! ID
 
! Name
 
! Data
 
 
  |-
 
  |-
  !colspan="3"| Sound
+
  | 13
 +
| minecraft:bane_of_arthropods
 +
| Bane of Arthropods
 
  |-
 
  |-
  | 1000
+
  | 14
  | Dispenser dispenses
+
  | minecraft:knockback
  |  
+
  | Knockback
 
  |-
 
  |-
  | 1001
+
  | 15
  | Dispenser fails to dispense
+
  | minecraft:fire_aspect
  |  
+
  | Fire Aspect
 
  |-
 
  |-
  | 1002
+
  | 16
  | Dispenser shoots
+
  | minecraft:looting
  |  
+
  | Looting
 
  |-
 
  |-
  | 1003
+
  | 17
  | Ender eye launched
+
  | minecraft:sweeping
  |  
+
  | Sweeping Edge
 
  |-
 
  |-
  | 1004
+
  | 18
  | Firework shot
+
  | minecraft:efficiency
  |  
+
  | Efficiency
 
  |-
 
  |-
  | 1005
+
  | 19
  | Iron door opened
+
  | minecraft:silk_touch
  |  
+
  | Silk Touch
 
  |-
 
  |-
  | 1006
+
  | 20
  | Wooden door opened
+
  | minecraft:unbreaking
  |  
+
  | Unbreaking
 
  |-
 
  |-
  | 1007
+
  | 21
  | Wooden trapdoor opened
+
  | minecraft:fortune
  |  
+
  | Fortune
 
  |-
 
  |-
  | 1008
+
  | 22
  | Fence gate opened
+
  | minecraft:power
  |  
+
  | Power
 
  |-
 
  |-
  | 1009
+
  | 23
  | Fire extinguished
+
  | minecraft:punch
  |  
+
  | Punch
 
  |-
 
  |-
  | 1010
+
  | 24
  | Play record
+
  | minecraft:flame
  | Special case, see below for more info
+
  | Flame
 
  |-
 
  |-
  | 1011
+
  | 25
  | Iron door closed
+
  | minecraft:infinity
  |  
+
  | Infinity
 
  |-
 
  |-
  | 1012
+
  | 26
  | Wooden door closed
+
  | minecraft:luck_of_the_sea
  |  
+
  | Luck of the Sea
 
  |-
 
  |-
  | 1013
+
  | 27
  | Wooden trapdoor closed
+
  | minecraft:lure
  |  
+
  | Lure
 
  |-
 
  |-
  | 1014
+
  | 28
  | Fence gate closed
+
  | minecraft:loyalty
  |  
+
  | Loyalty
 
  |-
 
  |-
  | 1015
+
  | 29
  | Ghast warns
+
  | minecraft:impaling
  |  
+
  | Impaling
 
  |-
 
  |-
  | 1016
+
  | 30
  | Ghast shoots
+
  | minecraft:riptide
  |  
+
  | Riptide
 
  |-
 
  |-
  | 1017
+
  | 31
  | Enderdragon shoots
+
  | minecraft:channeling
  |  
+
  | Channeling
 
  |-
 
  |-
  | 1018
+
  | 32
  | Blaze shoots
+
  | minecraft:mending
  |  
+
  | Mending
 
  |-
 
  |-
  | 1019
+
  | 33
  | Zombie attacks wood door
+
  | minecraft:vanishing_curse
  |  
+
  | Curse of Vanishing
 +
|}
 +
 
 +
==== Set Slot ====
 +
 
 +
Sent by the server when an item in a slot (in a window) is added/removed.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | 1020
+
  |rowspan="3"| 0x17
  | Zombie attacks iron door
+
|rowspan="3"| Play
  |  
+
|rowspan="3"| Client
 +
| Window ID
 +
  | Byte
 +
  | The window which is being updated. 0 for player inventory. Note that all known window types include the player inventory. This packet will only be sent for the currently opened window while the player is performing actions, even if it affects the player inventory. After the window is closed, a number of these packets are sent to update the player's inventory window (0).
 
  |-
 
  |-
  | 1021
+
  | Slot
  | Zombie breaks wood door
+
  | Short
  |
+
  | The slot that should be updated
 
  |-
 
  |-
  | 1022
+
  | Slot Data
  | Wither breaks block
+
  | [[Slot Data|Slot]]
|
 
|-
 
| 1023
 
| Wither spawned
 
 
  |  
 
  |  
 +
|}
 +
 +
To set the cursor (the item currently dragged with the mouse), use -1 as Window ID and as Slot.
 +
 +
This packet can only be used to edit the hotbar of the player's inventory if window ID is set to 0 (slots 36 through 44).  If the window ID is set to -2, then any slot in the inventory can be used but no add item animation will be played.
 +
 +
==== Set Cooldown ====
 +
 +
Applies a cooldown period to all items with the given type.  Used by the Notchian server with enderpearls.  This packet should be sent when the cooldown starts and also when the cooldown ends (to compensate for lag), although the client will end the cooldown automatically. Can be applied to any item, note that interactions still get sent to the server with the item but the client does not play the animation nor attempt to predict results (i.e block placing).
 +
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | 1024
+
  |rowspan="2"| 0x18
  | Wither shoots
+
  |rowspan="2"| Play
  |
+
  |rowspan="2"| Client
|-
+
  | Item ID
  | 1025
+
  | VarInt
  | Bat takes off
+
  | Numeric ID of the item to apply a cooldown to.
  |
 
 
  |-
 
  |-
  | 1026
+
  | Cooldown Ticks
  | Zombie infects
+
  | VarInt
  |
+
  | Number of ticks to apply a cooldown for, or 0 to clear the cooldown.
 +
|}
 +
 
 +
==== Plugin Message (clientbound) ====
 +
 
 +
{{Main|Plugin channels}}
 +
 
 +
Mods and plugins can use this to send their data. Minecraft itself uses several [[plugin channel]]s. These internal channels are in the <code>minecraft</code> namespace.
 +
 
 +
More documentation on this: [http://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/ http://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/]
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | 1027
+
  |rowspan="2"| 0x19
  | Zombie villager converted
+
|rowspan="2"| Play
  |
+
|rowspan="2"| Client
 +
| Channel
 +
  | Identifier
 +
  | Name of the [[plugin channel]] used to send the data
 
  |-
 
  |-
  | 1028
+
  | Data
  | Ender dragon death
+
  | Byte Array
  |
+
  | Any data, depending on the channel. <code>minecraft:</code> channels are documented [[plugin channel|here]].  The length of this array must be inferred from the packet length.
 +
|}
 +
 
 +
==== Named Sound Effect ====
 +
{{See also|#Sound Effect}}
 +
 
 +
Used to play a sound effect on the client. Custom sounds may be added by resource packs.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | 1029
+
  |rowspan="7"| 0x1A
  | Anvil destroyed
+
|rowspan="7"| Play
  |  
+
|rowspan="7"| Client
 +
| Sound Name
 +
  | Identifier
 +
  | All sound effect names as of 1.15.2 can be seen [https://pokechu22.github.io/Burger/1.15.2.html#sounds here].
 
  |-
 
  |-
  | 1030
+
  | Sound Category
  | Anvil used
+
  | VarInt Enum
  |  
+
  | The category that this sound will be played from ([https://gist.github.com/konwboj/7c0c380d3923443e9d55 current categories])
 
  |-
 
  |-
  | 1031
+
  | Effect Position X
  | Anvil landed
+
  | Int
  |
+
  | Effect X multiplied by 8 ([[Data types#Fixed-point numbers|fixed-point number]] with only 3 bits dedicated to the fractional part)
 
  |-
 
  |-
  | 1032
+
  | Effect Position Y
  | Portal travel
+
  | Int
  |  
+
  | Effect Y multiplied by 8 ([[Data types#Fixed-point numbers|fixed-point number]] with only 3 bits dedicated to the fractional part)
 
  |-
 
  |-
  | 1033
+
  | Effect Position Z
  | Chorus flower grown
+
  | Int
  |
+
  | Effect Z multiplied by 8 ([[Data types#Fixed-point numbers|fixed-point number]] with only 3 bits dedicated to the fractional part)
 
  |-
 
  |-
  | 1034
+
  | Volume
  | Chorus flower died
+
  | Float
  |  
+
  | 1 is 100%, can be more
 
  |-
 
  |-
  | 1035
+
  | Pitch
  | Brewing stand brewed
+
  | Float
  |
+
  | Float between 0.5 and 2.0 by Notchian clients
 +
|}
 +
 
 +
==== Disconnect (play) ====
 +
 
 +
Sent by the server before it disconnects a client. The client assumes that the server has already closed the connection by the time the packet arrives.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | 1036
+
  | 0x1B
  | Iron trapdoor opened
+
  | Play
  |  
+
  | Client
  |-
+
  | Reason
  | 1037
+
  | [[Chat]]
  | Iron trapdoor closed
+
  | Displayed to the client when the connection terminates.
  |
+
  |}
  |-
+
 
  !colspan="3"| Particle
+
==== Entity Status ====
 +
 
 +
Entity statuses generally trigger an animation for an entity. The available statuses vary by the entity's type (and are available to subclasses of that type as well).
 +
 
 +
{| class="wikitable"
 +
  ! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | 2000
+
  |rowspan="2"| 0x1C
| Spawns 10 smoke particles, e.g. from a fire
+
  |rowspan="2"| Play
  | Direction, see below
+
  |rowspan="2"| Client
|-
+
  | Entity ID
  | 2001
+
  | Int
| Block break + block break sound
 
  | {{Minecraft Wiki|Data values|Block ID}}
 
|-
 
| 2002/2007
 
| Splash potion. Particle effect + glass break sound.
 
| [http://minecraft.gamepedia.com/Data_values#Potions Potion ID]
 
|-
 
| 2003
 
  | Eye of Ender entity break animation — particles and sound
 
 
  |  
 
  |  
 
  |-
 
  |-
  | 2004
+
  | Entity Status
  | Mob spawn particle effect: smoke + flames
+
  | Byte Enum
|
+
  | See below
|-
 
| 2005
 
| Bonemeal particles
 
| How many particles to spawn (if set to 0, 15 are spawned)
 
|-
 
| 2006
 
| Dragon breath
 
|
 
|-
 
| 3000
 
| End gateway spawn
 
|
 
|-
 
| 3001
 
| Enderdragon growl
 
  |
 
 
  |}
 
  |}
  
Smoke directions:
+
See [[Entity statuses]] for a list of which statuses are valid for each type of entity.
 +
 
 +
==== Explosion ====
  
{| class="wikitable"
+
Sent when an explosion occurs (creepers, TNT, and ghast fireballs).
! ID
 
! Direction
 
|-
 
| 0
 
| South-East
 
|-
 
| 1
 
| South
 
|-
 
| 2
 
| South-West
 
|-
 
| 3
 
| East
 
|-
 
| 4
 
| (Up or middle ?)
 
|-
 
| 5
 
| West
 
|-
 
| 6
 
| North-East
 
|-
 
| 7
 
| North
 
|-
 
| 8
 
| North-West
 
|}
 
  
Play record: This is actually a special case within this packet. You can start/stop a record at a specific location. Use a valid {{Minecraft Wiki|Music Discs|Record ID}} to start a record (or overwrite a currently playing one), any other value will stop the record.
+
Each block in Records is set to air. Coordinates for each axis in record is int(X) + record.x
 
 
==== Particle ====
 
 
 
Displays the named particle
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 1,999: Line 1,998:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="11"| 0x22
+
  |rowspan="9"| 0x1D
  |rowspan="11"| Play
+
  |rowspan="9"| Play
  |rowspan="11"| Client
+
  |rowspan="9"| Client
| Particle ID
 
| Int
 
| See below
 
|-
 
| Long Distance
 
| Boolean
 
| If true, particle distance increases from 256 to 65536
 
|-
 
 
  | X
 
  | X
 
  | Float
 
  | Float
  | X position of the particle
+
  |  
 
  |-
 
  |-
 
  | Y
 
  | Y
 
  | Float
 
  | Float
  | Y position of the particle
+
  |  
 
  |-
 
  |-
 
  | Z
 
  | Z
 
  | Float
 
  | Float
  | Z position of the particle
+
  |  
 
  |-
 
  |-
  | Offset X
+
  | Strength
 
  | Float
 
  | Float
  | This is added to the X position after being multiplied by random.nextGaussian()
+
  | A strength greater than or equal to 2.0 spawns a <code>minecraft:explosion_emitter</code> particle, while a lesser strength spawns a <code>minecraft:explosion</code> particle.
 +
|-
 +
| Record Count
 +
| Int
 +
| Number of elements in the following array
 +
|-
 +
| Records
 +
| Array of (Byte, Byte, Byte)
 +
| Each record is 3 signed bytes long; the 3 bytes are the XYZ (respectively) signed offsets of affected blocks.
 
  |-
 
  |-
  | Offset Y
+
  | Player Motion X
 
  | Float
 
  | Float
  | This is added to the Y position after being multiplied by random.nextGaussian()
+
  | X velocity of the player being pushed by the explosion
 
  |-
 
  |-
  | Offset Z
+
  | Player Motion Y
 
  | Float
 
  | Float
  | This is added to the Z position after being multiplied by random.nextGaussian()
+
  | Y velocity of the player being pushed by the explosion
 
  |-
 
  |-
  | Particle Data
+
  | Player Motion Z
 
  | Float
 
  | Float
  | The data of each particle
+
  | Z velocity of the player being pushed by the explosion
|-
 
| Particle Count
 
| Int
 
| The number of particles to create
 
|-
 
| Data
 
| Array of VarInt
 
| Length depends on particle. "iconcrack" has length of 2, "blockcrack", and "blockdust" have lengths of 1, the rest have 0.
 
 
  |}
 
  |}
  
Particle IDs:
+
==== Unload Chunk ====
 +
 
 +
Tells the client to unload a chunk column.
  
 
{| class="wikitable"
 
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  ! Particle Name
+
|rowspan="2"| 0x1E
  ! Particle ID
+
|rowspan="2"| Play
 +
|rowspan="2"| Client
 +
| Chunk X
 +
| Int
 +
| Block coordinate divided by 16, rounded down
 +
|-
 +
| Chunk Z
 +
| Int
 +
| Block coordinate divided by 16, rounded down
 +
|}
 +
 
 +
It is legal to send this packet even if the given chunk is not currently loaded.
 +
 
 +
==== Change Game State ====
 +
 
 +
Used for a wide variety of game state things, from whether to bed use to gamemode to demo messages.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
  ! Bound To
 +
! Field Name
 +
  ! Field Type
 +
! Notes
 +
|-
 +
|rowspan="2"| 0x1F
 +
|rowspan="2"| Play
 +
|rowspan="2"| Client
 +
| Reason
 +
| Unsigned Byte
 +
| See below
 +
|-
 +
| Value
 +
| Float
 +
| Depends on Reason
 +
|}
 +
 
 +
''Reason codes'':
 +
 
 +
{| class="wikitable"
 +
! Reason
 +
! Effect
 +
! Value
 
  |-
 
  |-
| explode
 
 
  | 0
 
  | 0
 +
| Invalid Bed
 +
| Would be used to switch between messages, but the only used message is 0 for invalid bed
 
  |-
 
  |-
| largeexplode
 
 
  | 1
 
  | 1
 +
| Begin raining
 +
|
 
  |-
 
  |-
| hugeexplosion
 
 
  | 2
 
  | 2
 +
| End raining
 +
|
 
  |-
 
  |-
| fireworksSpark
 
 
  | 3
 
  | 3
 +
| Change gamemode
 +
| 0: Survival, 1: Creative, 2: Adventure, 3: Spectator
 
  |-
 
  |-
| bubble
 
 
  | 4
 
  | 4
 +
| Exit end
 +
| 0: Immediately send Client Status of respawn without showing end credits; 1: Show end credits and respawn at the end (or when esc is pressed).  1 is sent if the player has not yet received the "The end?" advancement, while if they do have it 0 is used.
 
  |-
 
  |-
| splash
 
 
  | 5
 
  | 5
  |-
+
  | Demo message
  | wake
+
| 0: Show welcome to demo screen, 101: Tell movement controls, 102: Tell jump control, 103: Tell inventory control, 104: Tell that the demo is over and print a message about how to take a screenshot
 +
  |-
 
  | 6
 
  | 6
 +
| Arrow hitting player
 +
| Appears to be played when an arrow strikes another player in Multiplayer
 
  |-
 
  |-
| suspended
 
 
  | 7
 
  | 7
 +
| Fade value
 +
| The current darkness value. 1 = Dark, 0 = Bright, Setting the value higher causes the game to change color and freeze
 
  |-
 
  |-
| depthsuspend
 
 
  | 8
 
  | 8
 +
| Fade time
 +
| Time in ticks for the sky to fade
 
  |-
 
  |-
| crit
 
 
  | 9
 
  | 9
 +
| Play pufferfish sting sound
 
  |-
 
  |-
| magicCrit
 
 
  | 10
 
  | 10
 +
| Play elder guardian mob appearance (effect and sound)
 +
|
 
  |-
 
  |-
| smoke
 
 
  | 11
 
  | 11
 +
| Enable respawn screen
 +
|  0: Enable respawn screen, 1: Immediately respawn (sent when the doImmediateRespawn gamerule changes)
 +
|}
 +
 +
==== Open Horse Window ====
 +
 +
This packet is used exclusively for opening the horse GUI.  [[#Open Window|Open Window]] is used for all other GUIs.
 +
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | largesmoke
+
  |rowspan="3"| 0x20
  | 12
+
|rowspan="3"| Play
 +
|rowspan="3"| Client
 +
| Window ID?
 +
| Byte
 +
  |
 
  |-
 
  |-
  | spell
+
  | Number of slots?
  | 13
+
| VarInt
 +
  |
 
  |-
 
  |-
  | instantSpell
+
  | Entity ID?
  | 14
+
  | Integer
 +
|
 +
|}
 +
 
 +
==== Keep Alive (clientbound) ====
 +
 
 +
The server will frequently send out a keep-alive, each containing a random ID. The client must respond with the same packet. If the client does not respond to them for over 30 seconds, the server kicks the client. Vice versa, if the server does not send any keep-alives for 20 seconds, the client will disconnect and yields a "Timed out" exception.
 +
 
 +
The Notchian server uses a system-dependent time in milliseconds to generate the keep alive ID value.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | mobSpell
+
  |rowspan="1"| 0x21
  | 15
+
|rowspan="1"| Play
  |-
+
|rowspan="1"| Client
  | mobSpellAmbient
+
| Keep Alive ID
  | 16
+
  | Long
 +
  |  
 +
  |}
 +
 
 +
==== Chunk Data ====
 +
{{Main|Chunk Format}}
 +
{{See also|#Unload Chunk}}
 +
 
 +
{{Need Info|How do biomes work now?  The biome change happened at the same time as the seed change, but it's not clear how/if biomes could be computed given that it's not the actual seed...  ([https://www.reddit.com/r/Mojira/comments/e5at6i/a_discussion_for_the_changes_to_how_biomes_are/ /r/mojira discussion] which notes that it seems to be some kind of interpolation, and 3D biomes are only used in the nether)}}
 +
 
 +
The server only sends skylight information for chunk pillars in the {{Minecraft Wiki|Overworld}}, it's up to the client to know in which dimenison the player is currently located. You can also infer this information from the primary bitmask and the amount of uncompressed bytes sent. This packet also sends all block entities in the chunk (though sending them is not required; it is still legal to send them with [[#Update Block Entity|Update Block Entity]] later).
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | witchMagic
+
  |rowspan="10"| 0x22
  | 17
+
|rowspan="10"| Play
 +
|rowspan="10"| Client
 +
| Chunk X
 +
| Int
 +
  | Chunk coordinate (block coordinate divided by 16, rounded down)
 
  |-
 
  |-
  | dripWater
+
  | Chunk Z
  | 18
+
  | Int
 +
| Chunk coordinate (block coordinate divided by 16, rounded down)
 
  |-
 
  |-
  | dripLava
+
  | Full chunk
  | 19
+
  | Boolean
 +
| See [[Chunk Format#Full chunk|Chunk Format]]
 
  |-
 
  |-
  | angryVillager
+
  | Primary Bit Mask
  | 20
+
  | VarInt
 +
| Bitmask with bits set to 1 for every 16×16×16 chunk section whose data is included in Data. The least significant bit represents the chunk section at the bottom of the chunk column (from y=0 to y=15).
 
  |-
 
  |-
  | happyVillager
+
  | Heightmaps
  | 21
+
  | [[NBT]]
 +
| Compound containing one long array named <code>MOTION_BLOCKING</code>, which is a heightmap for the highest solid block at each position in the chunk (as a compacted long array with 256 entries at 9 bits per entry totaling 36 longs). The Notchian server also adds a <code>WORLD_SURFACE</code> long array, the purpose of which is unknown, but it's not required for the chunk to be accepted.
 
  |-
 
  |-
  | townaura
+
  | Biomes
  | 22
+
  | Optional array of Integer
 +
| 1024 biome IDs, ordered by x then z then y, in 4&times;4&times;4 blocks.  Not present if full chunk is false.
 +
|-
 +
| Size
 +
| VarInt
 +
| Size of Data in bytes
 
  |-
 
  |-
  | note
+
  | Data
  | 23
+
  | Byte array
 +
| See [[Chunk Format#Data structure|data structure]] in Chunk Format
 
  |-
 
  |-
  | portal
+
  | Number of block entities
  | 24
+
  | VarInt
 +
| Number of elements in the following array
 
  |-
 
  |-
  | enchantmenttable
+
  | Block entities
  | 25
+
  | Array of [[NBT|NBT Tag]]
 +
| All block entities in the chunk.  Use the x, y, and z tags in the NBT to determine their positions.
 +
|}
 +
 
 +
Note that the Notchian client requires an [[#Update View Position|Update View Position]] packet when it crosses a chunk border, otherwise it'll only display render distance + 2 chunks around the chunk it spawned in.
 +
 
 +
==== Effect ====
 +
 
 +
Sent when a client is to play a sound or particle effect.
 +
 
 +
By default, the Minecraft client adjusts the volume of sound effects based on distance. The final boolean field is used to disable this, and instead the effect is played from 2 blocks away in the correct direction. Currently this is only used for effect 1023 (wither spawn) and effect 1028 (enderdragon death); it is ignored on other effects.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | flame
+
  |rowspan="4"| 0x23
  | 26
+
|rowspan="4"| Play
 +
|rowspan="4"| Client
 +
| Effect ID
 +
| Int
 +
  | The ID of the effect, see below
 
  |-
 
  |-
  | lava
+
  | Location
  | 27
+
  | Position
 +
| The location of the effect
 
  |-
 
  |-
  | footstep
+
  | Data
  | 28
+
  | Int
 +
| Extra data for certain effects, see below
 
  |-
 
  |-
  | cloud
+
  | Disable Relative Volume
  | 29
+
  | Boolean
 +
| See above
 +
|}
 +
 
 +
Effect IDs:
 +
 
 +
{| class="wikitable"
 +
! ID
 +
! Name
 +
! Data
 
  |-
 
  |-
  | reddust
+
  !colspan="3"| Sound
| 30
 
 
  |-
 
  |-
  | snowballpoof
+
  | 1000
  | 31
+
| Dispenser dispenses
 +
  |  
 
  |-
 
  |-
  | snowshovel
+
  | 1001
  | 32
+
| Dispenser fails to dispense
 +
  |  
 
  |-
 
  |-
  | slime
+
  | 1002
  | 33
+
| Dispenser shoots
 +
  |  
 
  |-
 
  |-
  | heart
+
  | 1003
  | 34
+
| Ender eye launched
 +
  |  
 
  |-
 
  |-
  | barrier
+
  | 1004
  | 35
+
| Firework shot
 +
  |  
 
  |-
 
  |-
  | iconcrack_(id)_(data)
+
  | 1005
  | 36
+
| Iron door opened
 +
  |  
 
  |-
 
  |-
  | blockcrack_(id+(data<<12))
+
  | 1006
  | 37
+
| Wooden door opened
 +
  |  
 
  |-
 
  |-
  | blockdust_(id)
+
  | 1007
  | 38
+
| Wooden trapdoor opened
 +
  |  
 
  |-
 
  |-
  | droplet
+
  | 1008
  | 39
+
| Fence gate opened
 +
  |  
 
  |-
 
  |-
  | take
+
  | 1009
  | 40
+
| Fire extinguished
 +
  |  
 
  |-
 
  |-
  | mobappearance
+
  | 1010
  | 41
+
  | Play record
 +
| Special case, see below for more info
 
  |-
 
  |-
  | dragonbreath
+
  | 1011
  | 42
+
| Iron door closed
 +
  |  
 
  |-
 
  |-
  | endrod
+
  | 1012
  | 43
+
| Wooden door closed
 +
  |  
 
  |-
 
  |-
  | damageindicator
+
  | 1013
  | 44
+
| Wooden trapdoor closed
 +
  |  
 
  |-
 
  |-
  | sweepattack
+
  | 1014
  | 45
+
| Fence gate closed
 +
  |  
 
  |-
 
  |-
  | fallingdust
+
  | 1015
  | 46
+
  | Ghast warns
  |}
+
  |  
 
 
==== Join Game ====
 
 
 
See [[Protocol Encryption]] for information on logging in.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="7"| 0x23
+
  | 1016
|rowspan="7"| Play
+
  | Ghast shoots
|rowspan="7"| Client
+
  |  
| Entity ID
 
  | Int
 
  | The player's Entity ID (EID)
 
 
  |-
 
  |-
  | Gamemode
+
  | 1017
  | Unsigned Byte
+
  | Enderdragon shoots
  | 0: Survival, 1: Creative, 2: Adventure, 3: Spectator. Bit 3 (0x8) is the hardcore flag.
+
  |  
 
  |-
 
  |-
  | Dimension
+
  | 1018
  | Int Enum
+
  | Blaze shoots
  | -1: Nether, 0: Overworld, 1: End; also, note that this is not a VarInt but instead a regular int.
+
  |  
 
  |-
 
  |-
  | Difficulty
+
  | 1019
  | Unsigned Byte
+
  | Zombie attacks wood door
  | 0: peaceful, 1: easy, 2: normal, 3: hard
+
|
 +
|-
 +
| 1020
 +
| Zombie attacks iron door
 +
  |  
 
  |-
 
  |-
  | Max Players
+
  | 1021
  | Unsigned Byte
+
  | Zombie breaks wood door
  | Was once used by the client to draw the player list, but now is ignored
+
  |
 
  |-
 
  |-
  | Level Type
+
  | 1022
  | String Enum (16)
+
  | Wither breaks block
  | default, flat, largeBiomes, amplified, default_1_1
+
  |
 
  |-
 
  |-
  | Reduced Debug Info
+
  | 1023
  | Boolean
+
  | Wither spawned
  | If true, a Notchian client shows reduced information on the {{Minecraft Wiki|debug screen}}.  For servers in development, this should almost always be false.
+
  |  
|}
 
 
 
==== Map ====
 
 
 
Updates a rectangular area on a {{Minecraft Wiki|map}} item.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
!colspan="2"| Field Name
 
!colspan="2"| Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="13"| 0x24
+
  | 1024
|rowspan="13"| Play
+
  | Wither shoots
|rowspan="13"| Client
+
  |
  |colspan="2"| Item Damage
 
|colspan="2"| VarInt
 
  | The damage value (map ID) of the map being modified
 
 
  |-
 
  |-
  |colspan="2"| Scale
+
  | 1025
  |colspan="2"| Byte
+
  | Bat takes off
  | From 0 for a fully zoomed-in map (1 block per pixel) to 4 for a fully zoomed-out map (16 blocks per pixel)
+
  |
  |-  
+
  |-
  |colspan="2"| Tracking Position
+
  | 1026
  |colspan="2"| Boolean
+
  | Zombie infects
  | Specifies whether the icons are shown
+
  |
  |-  
+
  |-
  |colspan="2"| Icon Count
+
  | 1027
  |colspan="2"| VarInt
+
  | Zombie villager converted
  | Number of elements in the following array
+
  |
 
  |-
 
  |-
  |rowspan="3"| Icon
+
  | 1028
| Direction And Type
+
  | Ender dragon death
|rowspan="3"| Array
+
  |
  | Byte
 
  | 0xF0 = Direction, 0x0F = Type
 
 
  |-
 
  |-
  | X
+
  | 1029
  | Byte
+
  | Anvil destroyed
 
  |  
 
  |  
 
  |-
 
  |-
  | Z
+
  | 1030
  | Byte
+
  | Anvil used
 
  |  
 
  |  
|-
 
|colspan="2"| Columns
 
|colspan="2"| Byte
 
| Number of columns updated
 
 
  |-
 
  |-
  |colspan="2"| Rows
+
  | 1031
  |colspan="2"| Optional Byte
+
  | Anvil landed
  | Only if Columns is more than 0; number of rows updated
+
  |
 
  |-
 
  |-
  |colspan="2"| X
+
  | 1032
  |colspan="2"| Optional Byte
+
  | Portal travel
  | Only if Columns is more than 0; x offset of the westernmost column
+
  |  
 
  |-
 
  |-
  |colspan="2"| Z
+
  | 1033
  |colspan="2"| Optional Byte
+
  | Chorus flower grown
  | Only if Columns is more than 0; z offset of the northernmost row
+
  |
 
  |-
 
  |-
  |colspan="2"| Length
+
  | 1034
  |colspan="2"| Optional VarInt
+
  | Chorus flower died
  | Only if Columns is more than 0; length of the following array
+
  |  
 
  |-
 
  |-
  |colspan="2"| Data
+
  | 1035
  |colspan="2"| Optional Array of Unsigned Byte
+
  | Brewing stand brewed
  | Only if Columns is more than 0; see {{Minecraft Wiki|Map item format}}
+
  |
|}
 
 
 
For icons, a direction of 0 is a vertical icon and increments by 22.5&deg; (360/16).
 
 
 
Types are based off of rows and columns in <code>map_icons.png</code>:
 
 
 
{| class="wikitable"
 
 
  |-
 
  |-
  ! Icon type
+
  | 1036
  ! Result
+
  | Iron trapdoor opened
 +
|
 
  |-
 
  |-
  | 0
+
  | 1037
  | White arrow (players)
+
| Iron trapdoor closed
 +
  |
 
  |-
 
  |-
  | 1
+
  !colspan="3"| Particle
| Green arrow (item frames)
 
 
  |-
 
  |-
  | 2
+
  | 2000
  | Red arrow
+
  | Spawns 10 smoke particles, e.g. from a fire
 +
| Direction, see below
 
  |-
 
  |-
  | 3
+
  | 2001
  | Blue arrow
+
  | Block break + block break sound
 +
| Block state, as an index into the global palette
 
  |-
 
  |-
  | 4
+
  | 2002
  | White cross
+
  | Splash potion. Particle effect + glass break sound.
 +
| [http://minecraft.gamepedia.com/Data_values#Potions Potion ID]
 
  |-
 
  |-
  | 5
+
  | 2003
  | Red pointer
+
| Eye of Ender entity break animation — particles and sound
 +
  |  
 
  |-
 
  |-
  | 6
+
  | 2004
  | White circle (off-map players)
+
  | Mob spawn particle effect: smoke + flames
 +
|
 +
|-
 +
| 2005
 +
| Bonemeal particles
 +
| How many particles to spawn (if set to 0, 15 are spawned)
 
  |-
 
  |-
  | 7
+
  | 2006
  | Small white circle (far-off-map players)
+
| Dragon breath
 +
  |
 
  |-
 
  |-
  | 8
+
  | 2007
  | Mansion
+
  | Instant splash potion
 +
| [http://minecraft.gamepedia.com/Data_values#Potions Potion ID]
 
  |-
 
  |-
  | 9
+
  | 3000
  | Temple
+
| End gateway spawn
 +
  |  
 
  |-
 
  |-
  | 10-15
+
  | 3001
  | Unused (blue square)
+
| Enderdragon growl
 +
  |
 
  |}
 
  |}
  
==== Entity ====
+
Smoke directions:
 
 
This packet may be used to initialize an entity.
 
 
 
For player entities, either this packet or any move/look packet is sent every game tick. So the meaning of this packet is basically that the entity did not move/look since the last such packet.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
  ! Packet ID
+
  ! ID
  ! State
+
  ! Direction
  ! Bound To
+
  |-
! Field Name
+
  | 0
  ! Field Type
+
  | South-East
  ! Notes
 
 
  |-
 
  |-
  |rowspan="1"| 0x25
+
  | 1
  |rowspan="1"| Play
+
  | South
  |rowspan="1"| Client
+
  |-
  | Entity ID
+
  | 2
  | VarInt
+
  | South-West
  |  
+
  |-
  |}
+
  | 3
 
+
| East
==== Entity Relative Move ====
 
 
 
This packet is sent by the server when an entity moves less then 8 blocks; if an entity moves more than 8 blocks [[#Entity Teleport|Entity Teleport]] ([[#Play|Play]], 0x4A, clientbound) should be sent instead.
 
 
 
This packet allows at most 8 blocks movement in any direction, because short range is from -32768 to 32767. And <code>32768 / (128 * 32)</code> = 8.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="5"| 0x26
+
  | 4
|rowspan="5"| Play
+
  | (Up or middle ?)
|rowspan="5"| Client
 
| Entity ID
 
| VarInt
 
  |  
 
 
  |-
 
  |-
  | Delta X
+
  | 5
  | Short
+
  | West
| Change in X position as <code>(currentX * 32 - prevX * 32) * 128</code>
 
 
  |-
 
  |-
  | Delta Y
+
  | 6
  | Short
+
  | North-East
| Change in Y position as <code>(currentY * 32 - prevY * 32) * 128</code>
 
 
  |-
 
  |-
  | Delta Z
+
  | 7
  | Short
+
  | North
| Change in Z position as <code>(currentZ * 32 - prevZ * 32) * 128</code>
 
 
  |-
 
  |-
  | On Ground
+
  | 8
| Boolean
+
  | North-West
  |  
 
 
  |}
 
  |}
  
==== Entity Look And Relative Move ====
+
Play record: This is actually a special case within this packet. You can start/stop a record at a specific location. Use a valid {{Minecraft Wiki|Music Discs|Record ID}} to start a record (or overwrite a currently playing one), any other value will stop the record.  See [[Data Generators]] for information on item IDs.
 +
 
 +
==== Particle ====
  
This packet is sent by the server when an entity rotates and moves. Since a short range is limited from -32768 to 32767, and movement is offset of fixed-point numbers, this packet allows at most 8 blocks movement in any direction. (<code>-32768 / (32 * 128) == -8</code>)
+
Displays the named particle
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,425: Line 2,541:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="7"| 0x27
+
  |rowspan="11"| 0x24
  |rowspan="7"| Play
+
  |rowspan="11"| Play
  |rowspan="7"| Client
+
  |rowspan="11"| Client
  | Entity ID
+
  | Particle ID
  | VarInt
+
  | Int
  |  
+
  | The particle ID listed in [[#Particle|the particle data type]].
 +
|-
 +
| Long Distance
 +
| Boolean
 +
| If true, particle distance increases from 256 to 65536
 
  |-
 
  |-
  | Delta X
+
  | X
  | Short
+
  | Double
  | Change in X position as <code>(currentX * 32 - prevX * 32) * 128</code>
+
  | X position of the particle
 
  |-
 
  |-
  | Delta Y
+
  | Y
  | Short
+
  | Double
  | Change in Y position as <code>(currentY * 32 - prevY * 32) * 128</code>
+
  | Y position of the particle
 
  |-
 
  |-
  | Delta Z
+
  | Z
  | Short
+
  | Double
  | Change in Z position as <code>(currentZ * 32 - prevZ * 32) * 128</code>
+
  | Z position of the particle
 
  |-
 
  |-
  | Yaw
+
  | Offset X
  | Angle
+
  | Float
  | New angle, not a delta
+
  | This is added to the X position after being multiplied by random.nextGaussian()
 
  |-
 
  |-
  | Pitch
+
  | Offset Y
  | Angle
+
  | Float
  | New angle, not a delta
+
  | This is added to the Y position after being multiplied by random.nextGaussian()
 
  |-
 
  |-
  | On Ground
+
  | Offset Z
  | Boolean
+
  | Float
  |  
+
  | This is added to the Z position after being multiplied by random.nextGaussian()
|}
 
 
 
==== Entity Look ====
 
 
 
This packet is sent by the server when an entity rotates.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="4"| 0x28
+
  | Particle Data
|rowspan="4"| Play
+
  | Float
|rowspan="4"| Client
+
  | The data of each particle
| Entity ID
 
  | VarInt
 
  |  
 
 
  |-
 
  |-
  | Yaw
+
  | Particle Count
  | Angle
+
  | Int
  | New angle, not a delta
+
  | The number of particles to create
 
  |-
 
  |-
  | Pitch
+
  | Data
  | Angle
+
  | Varies
  | New angle, not a delta
+
  | The variable data listed in [[#Particle|the particle data type]].
|-
 
| On Ground
 
| Boolean
 
|  
 
 
  |}
 
  |}
  
==== Vehicle Move (clientbound) ====
+
==== Update Light ====
  
Note that all fields use absolute positioning and do not allow for relative positioning.
+
Updates light levels for a chunk.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,497: Line 2,597:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  ! Field Name
+
  !colspan="2"| Field Name
  ! Field Type
+
  !colspan="2"| Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="7"| 0x29
+
  |rowspan="10"| 0x25
  |rowspan="7"| Play
+
  |rowspan="10"| Play
  |rowspan="7"| Client
+
  |rowspan="10"| Client
  | X
+
  |colspan="2"| Chunk X
  | Double
+
  |colspan="2"| VarInt
  | Absolute position (X coordinate)
+
  | Chunk coordinate (block coordinate divided by 16, rounded down)  
 
  |-
 
  |-
  | Y
+
  |colspan="2"| Chunk Z
  | Double
+
  |colspan="2"| VarInt
  | Absolute position (Y coordinate)
+
  | Chunk coordinate (block coordinate divided by 16, rounded down)
 +
|-
 +
|colspan="2"| Sky Light Mask
 +
|colspan="2"| VarInt
 +
| Mask containing 18 bits, with the lowest bit corresponding to chunk section -1 (in the void, y=-16 to y=-1) and the highest bit for chunk section 16 (above the world, y=256 to y=271)
 +
|-
 +
|colspan="2"| Block Light Mask
 +
|colspan="2"| VarInt
 +
| Mask containing 18 bits, with the same order as sky light
 +
|-
 +
|colspan="2"| Empty Sky Light Mask
 +
|colspan="2"| VarInt
 +
| Mask containing 18 bits, which indicates sections that have 0 for all their sky light values.  If a section is set in both this mask and the main sky light mask, it is ignored for this mask and it is included in the sky light arrays (the notchian server does not create such masks).  If it is only set in this mask, it is not included in the sky light arrays.
 +
|-
 +
|colspan="2"| Empty Block Light Mask
 +
|colspan="2"| VarInt
 +
| Mask containing 18 bits, which indicates sections that have 0 for all their block light values.  If a section is set in both this mask and the main block light mask, it is ignored for this mask and it is included in the block light arrays (the notchian server does not create such masks).  If it is only set in this mask, it is not included in the block light arrays.
 +
|-
 +
|rowspan="2"| Sky Light arrays
 +
| Length
 +
|rowspan="2"| Array
 +
| VarInt
 +
| Length of the following array in bytes (always 2048)
 
  |-
 
  |-
  | Z
+
  | Sky Light array
  | Double
+
  | Array of 2048 bytes
  | Absolute position (Z coordinate)
+
  | There is 1 array for each bit set to true in the sky light mask, starting with the lowest value.  Half a byte per light value.
 
  |-
 
  |-
  | Yaw
+
  |rowspan="2"| Block Light arrays
  | Float
+
| Length
  | Absolute rotation on the vertical axis, in degrees
+
|rowspan="2"| Array
 +
  | VarInt
 +
  | Length of the following array in bytes (always 2048)
 
  |-
 
  |-
  | Pitch
+
  | Block Light array
  | Float
+
  | Array of 2048 bytes
  | Absolute rotation on the horizontal axis, in degrees
+
  | There is 1 array for each bit set to true in the block light mask, starting with the lowest value.  Half a byte per light value.
 
  |}
 
  |}
  
==== Open Sign Editor ====
+
Individual block or sky light arrays are is given for each block with increasing x coordinates, within rows of increasing z coordinates, within layers of increasing y coordinates. Even-indexed items (those with an even x coordinate, starting at 0) are packed into the low bits, odd-indexed into the high bits.
 +
 
 +
==== Join Game ====
  
Sent when the client has placed a sign and is allowed to send [[#Update Sign|Update Sign]].
+
See [[Protocol Encryption]] for information on logging in.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,537: Line 2,663:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="1"| 0x2A
+
  |rowspan="9"| 0x26
  |rowspan="1"| Play
+
  |rowspan="9"| Play
  |rowspan="1"| Client
+
  |rowspan="9"| Client
  | Location
+
  | Entity ID
  | Position
+
| Int
  |  
+
| The player's Entity ID (EID)
  |}
+
|-
 
+
| Gamemode
==== Player Abilities (clientbound) ====
+
| Unsigned Byte
 +
| 0: Survival, 1: Creative, 2: Adventure, 3: Spectator. Bit 3 (0x8) is the hardcore flag.
 +
|-
 +
| Dimension
 +
| Int Enum
 +
| -1: Nether, 0: Overworld, 1: End; also, note that this is not a VarInt but instead a regular int.
 +
|-
 +
| Hashed seed
 +
| Long
 +
| First 8 bytes of the SHA-256 hash of the world's seed.
 +
|-
 +
| Max Players
 +
| Unsigned Byte
 +
| Was once used by the client to draw the player list, but now is ignored
 +
|-
 +
| Level Type
 +
| String Enum (16)
 +
  | default, flat, largeBiomes, amplified, customized, buffet, default_1_1
 +
  |-
 +
  | View Distance
 +
| VarInt
 +
| Render distance (2-32)
 +
|-
 +
| Reduced Debug Info
 +
| Boolean
 +
| If true, a Notchian client shows reduced information on the {{Minecraft Wiki|debug screen}}.  For servers in development, this should almost always be false.
 +
|-
 +
| Enable respawn screen
 +
| Boolean
 +
| Set to false when the doImmediateRespawn gamerule is true
 +
|}
  
The latter 2 floats are used to indicate the field of view and flying speed respectively, while the first byte is used to determine the value of 4 booleans.
+
==== Map Data ====
 +
 
 +
Updates a rectangular area on a {{Minecraft Wiki|map}} item.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,553: Line 2,711:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  ! Field Name
+
  !colspan="2"| Field Name
  ! Field Type
+
  !colspan="2"| Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="3"| 0x2B
+
  |rowspan="17"| 0x27
  |rowspan="3"| Play
+
  |rowspan="17"| Play
  |rowspan="3"| Client
+
  |rowspan="17"| Client
  | Flags
+
  |colspan="2"| Map ID
  | Byte
+
  |colspan="2"| VarInt
  | Bit field, see below
+
  | Map ID of the map being modified
 
  |-
 
  |-
  | Flying Speed
+
  |colspan="2"| Scale
  | Float
+
|colspan="2"| Byte
  |  
+
| From 0 for a fully zoomed-in map (1 block per pixel) to 4 for a fully zoomed-out map (16 blocks per pixel)
 +
|-
 +
|colspan="2"| Tracking Position
 +
  |colspan="2"| Boolean
 +
  | Specifies whether player and item frame icons are shown
 
  |-
 
  |-
  | Field of View Modifier
+
  |colspan="2"| Locked
  | Float
+
  |colspan="2"| Boolean
  | Modifies the field of view, like a speed potion. A Notchian server will use the same value as the movement speed (send in the [[Protocol#Entity_Properties|Entity Properties]] packet).
+
  | True if the map has been locked in a cartography table
  |}
+
|-
 
+
  |colspan="2"| Icon Count
About the flags:
+
|colspan="2"| VarInt
 
+
| Number of elements in the following array
{| class="wikitable"
 
 
  |-
 
  |-
  ! Field
+
  |rowspan="6"| Icon
  ! Bit
+
  | Type
 +
|rowspan="6"| Array
 +
| VarInt enum
 +
| See below
 
  |-
 
  |-
  | Invulnerable
+
  | X
  | 0x01
+
  | Byte
 +
| Map coordinates: -128 for furthest left, +127 for furthest right
 
  |-
 
  |-
  | Flying
+
  | Z
  | 0x02
+
  | Byte
 +
| Map coordinates: -128 for highest, +127 for lowest
 
  |-
 
  |-
  | Allow Flying
+
  | Direction
  | 0x04
+
  | Byte
 +
| 0-15
 
  |-
 
  |-
  | Creative Mode
+
  | Has Display Name
  | 0x08
+
  | Boolean
|}
+
  |
 
 
==== Combat Event ====
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
  !colspan="2"| Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="8"| 0x2C
+
  | Display Name
  |rowspan="8"| Play
+
| Optional [[Chat]]
  |rowspan="8"| Client
+
  | Only present if previous Boolean is true
  |colspan="2"| Event
+
|-
| VarInt Enum
+
  |colspan="2"| Columns
  | Determines the layout of the remaining packet
+
  |colspan="2"| Unsigned Byte
 +
  | Number of columns updated
 
  |-
 
  |-
  ! Event
+
  |colspan="2"| Rows
  ! Field Name
+
  |colspan="2"| Optional Byte
  !
+
  | Only if Columns is more than 0; number of rows updated
!
 
 
  |-
 
  |-
  | 0: enter combat
+
  |colspan="2"| X
  | ''no fields''
+
  |colspan="2"| Optional Byte
| ''no fields''
+
  | Only if Columns is more than 0; x offset of the westernmost column
  |  
 
 
  |-
 
  |-
  |rowspan="2"| 1: end combat
+
  |colspan="2"| Z
  | Duration
+
  |colspan="2"| Optional Byte
| VarInt
+
  | Only if Columns is more than 0; z offset of the northernmost row
  |  
 
 
  |-
 
  |-
  | Entity ID
+
  |colspan="2"| Length
  | Int
+
  |colspan="2"| Optional VarInt
  |  
+
  | Only if Columns is more than 0; length of the following array
 
  |-
 
  |-
  |rowspan="3"| 2: entity dead
+
  |colspan="2"| Data
  | Player ID
+
  |colspan="2"| Optional Array of Unsigned Byte
| VarInt
+
  | Only if Columns is more than 0; see {{Minecraft Wiki|Map item format}}
|
 
|-
 
  | Entity ID
 
| Int
 
|
 
|-
 
| Message
 
| [[Chat]]
 
|  
 
 
  |}
 
  |}
  
==== Player List Item ====
+
For icons, a direction of 0 is a vertical icon and increments by 22.5&deg; (360/16).
  
Sent by the server to update the user list (<tab> in the client).
+
Types are based off of rows and columns in <code>map_icons.png</code>:
  
 
{| class="wikitable"
 
{| class="wikitable"
! Packet ID
 
! State
 
! Bound To
 
!colspan="4"| Field Name
 
!colspan="3"| Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="19"| 0x2D
+
  ! Icon type
|rowspan="19"| Play
+
  ! Result
  |rowspan="19"| Client
+
  |-
  |colspan="4"| Action
+
  | 0
  |colspan="3"| VarInt
+
  | White arrow (players)
  | Determines the rest of the Player format after the UUID
 
 
  |-
 
  |-
  |colspan="4"| Number Of Players
+
  | 1
|colspan="3"| VarInt
+
  | Green arrow (item frames)
  | Number of elements in the following array
 
 
  |-
 
  |-
  |rowspan="17"| Player
+
  | 2
|colspan="3"| UUID
+
  | Red arrow
|rowspan="17"| Array
 
|colspan="2"| UUID
 
  |  
 
 
  |-
 
  |-
  ! Action
+
  | 3
!colspan="2"| Field Name
+
  | Blue arrow
  !colspan="2"|  
 
!
 
 
  |-
 
  |-
  |rowspan="10"| 0: add player
+
  | 4
|colspan="2"| Name
+
  | White cross
|colspan="2"| String (16)
 
  |  
 
 
  |-
 
  |-
  |colspan="2"| Number Of Properties
+
  | 5
|colspan="2"| VarInt
+
  | Red pointer
  | Number of elements in the following array
 
 
  |-
 
  |-
  |rowspan="4"| Property
+
  | 6
| Name
+
  | White circle (off-map players)
  |rowspan="4"| Array
 
| String (32767)
 
|
 
 
  |-
 
  |-
  | Value
+
  | 7
  | String (32767)
+
  | Small white circle (far-off-map players)
|
 
|-
 
| Is Signed
 
| Boolean
 
|
 
 
  |-
 
  |-
  | Signature
+
  | 8
  | Optional String (32767)
+
  | Mansion
| Only if Is Signed is true
 
 
  |-
 
  |-
  |colspan="2"| Gamemode
+
  | 9
|colspan="2"| VarInt
+
  | Temple
  |  
 
 
  |-
 
  |-
  |colspan="2"| Ping
+
  | 10
|colspan="2"| VarInt
+
  | White Banner
  |  
 
 
  |-
 
  |-
  |colspan="2"| Has Display Name
+
  | 11
|colspan="2"| Boolean
+
  | Orange Banner
  |  
 
 
  |-
 
  |-
  |colspan="2"| Display Name
+
  | 12
|colspan="2"| Optional [[Chat]]
+
  | Magenta Banner
  | Only if Has Display Name is true
 
 
  |-
 
  |-
  | 1: update gamemode
+
  | 13
|colspan="2"| Gamemode
+
  | Light Blue Banner
|colspan="2"| VarInt
 
|
 
|-
 
| 2: update latency
 
|colspan="2"| Ping
 
|colspan="2"| VarInt
 
  |  
 
 
  |-
 
  |-
  |rowspan="2"| 3: update display name
+
  | 14
|colspan="2"| Has Display Name
+
  | Yellow Banner
|colspan="2"| Boolean
 
  |  
 
 
  |-
 
  |-
  |colspan="2"| Display Name
+
  | 15
|colspan="2"| Optional [[Chat]]
+
  | Lime Banner
  | Only send if Has Display Name is true
 
 
  |-
 
  |-
  | 4: remove player
+
  | 16
  |colspan="2"| ''no fields''
+
  | Pink Banner
  |colspan="2"| ''no fields''
+
|-
  |  
+
| 17
 +
| Gray Banner
 +
|-
 +
| 18
 +
| Light Gray Banner
 +
|-
 +
| 19
 +
| Cyan Banner
 +
|-
 +
| 20
 +
| Purple Banner
 +
|-
 +
| 21
 +
| Blue Banner
 +
  |-
 +
| 22
 +
| Brown Banner
 +
|-
 +
| 23
 +
| Green Banner
 +
|-
 +
| 24
 +
| Red Banner
 +
|-
 +
| 25
 +
| Black Banner
 +
|-
 +
| 26
 +
  | Treasure marker
 
  |}
 
  |}
  
The Property field looks as in the response of [[Mojang API#UUID -> Profile + Skin/Cape]], except of course using the protocol format instead of JSON. That is, each player will usually have one property with Name “textures” and Value being a base64-encoded JSON string as documented at [[Mojang API#UUID -> Profile + Skin/Cape]]. An empty properties array is also acceptable, and will cause clients to display the player with one of the two default skins depending on UUID.
+
==== Trade List ====
  
==== Player Position And Look (clientbound) ====
+
The list of trades a villager NPC is offering.
 
 
Updates the player's position on the server. This packet will also close the “Downloading Terrain” screen when joining/respawning.
 
 
 
If the distance between the last known position of the player on the server and the new position set by this packet is greater than 100 meters, the client will be kicked for “You moved too quickly :( (Hacking?)”.
 
 
 
Also if the fixed-point number of X or Z is set greater than <code>3.2E7D</code> the client will be kicked for “Illegal position”.
 
 
 
Yaw is measured in degrees, and does not follow classical trigonometry rules. The unit circle of yaw on the XZ-plane starts at (0, 1) and turns counterclockwise, with 90 at (-1, 0), 180 at (0, -1) and 270 at (1, 0). Additionally, yaw is not clamped to between 0 and 360 degrees; any number is valid, including negative numbers and numbers greater than 360.
 
 
 
Pitch is measured in degrees, where 0 is looking straight ahead, -90 is looking straight up, and 90 is looking straight down.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,763: Line 2,888:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  ! Field Name
+
  !colspan="2"| Field Name
  ! Field Type
+
  !colspan="2"| Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="7"| 0x2E
+
  |rowspan="18"| 0x28
  |rowspan="7"| Play
+
  |rowspan="18"| Play
  |rowspan="7"| Client
+
  |rowspan="18"| Client
  | X
+
  |-
  | Double
+
  | colspan="2" | Window ID
  | Absolute or relative position, depending on Flags
+
| colspan="2" | VarInt
 +
  | The ID of the window that is open; this is an int rather than a byte.
 
  |-
 
  |-
  | Y
+
  | colspan="2" | Size
  | Double
+
| colspan="2" | Byte
  | Absolute or relative position, depending on Flags
+
| The number of trades in the following array
 +
|-
 +
| rowspan="11" | Trades
 +
| Input item 1
 +
| rowspan="11" | Array
 +
  | [[Slot]]
 +
  | The first item the villager is buying
 
  |-
 
  |-
  | Z
+
  | Output item
  | Double
+
  | [[Slot]]
  | Absolute or relative position, depending on Flags
+
  | The item the villager is selling
 
  |-
 
  |-
  | Yaw
+
  | Has second item
  | Float
+
  | Boolean
  | Absolute or relative rotation on the X axis, in degrees
+
  | Whether there is a second item
 
  |-
 
  |-
  | Pitch
+
  | Input item 2
  | Float
+
  | Optional [[Slot]]
  | Absolute or relative rotation on the Y axis, in degrees
+
  | The second item the villager is buying; only present if they have a second item.
 
  |-
 
  |-
  | Flags
+
  | Trade disabled
  | Byte
+
  | Boolean
  | Bit field, see below
+
  | True if the trade is disabled; false if the trade is enabled.
 
  |-
 
  |-
  | Teleport ID
+
  | Number of trade uses
  | VarInt
+
  | Integer
  | Client should confirm this packet with [[#Teleport Confirm|Teleport Confirm]] containing the same Teleport ID
+
  | Number of times the trade has been used so far
|}
 
 
 
About the Flags field:
 
 
 
<Dinnerbone> It's a bitfield, X/Y/Z/Y_ROT/X_ROT. If X is set, the x value is relative and not absolute.
 
 
 
{| class="wikitable"
 
 
  |-
 
  |-
  ! Field
+
  | Maximum number of trade uses
  ! Bit
+
  | Integer
 +
| Number of times this trade can be used
 
  |-
 
  |-
  | X
+
  | XP
  | 0x01
+
| Integer
 +
  |
 
  |-
 
  |-
  | Y
+
  | Special Price
  | 0x02
+
| Integer
 +
  |
 
  |-
 
  |-
  | Z
+
  | Price Multiplier
  | 0x04
+
| Float
 +
  |
 
  |-
 
  |-
  | Y_ROT
+
  | Demand
  | 0x08
+
| Integer
 +
  |
 
  |-
 
  |-
  | X_ROT
+
  |colspan="2"| Villager level
  | 0x10
+
|colspan="2"| VarInt
 +
| Appears on the trade GUI; meaning comes from the translation key <code>merchant.level.</code> + level.
 +
1: Novice, 2: Apprentice, 3: Journeyman, 4: Expert, 5: Master
 +
|-
 +
|colspan="2"| Experience
 +
|colspan="2"| VarInt
 +
| Total experience for this villager (always 0 for the wandering trader)
 +
|-
 +
  |colspan="2"| Is regular villager
 +
|colspan="2"| Boolean
 +
| True if this is a regular villager; false for the wandering trader.  When false, hides the villager level and some other GUI elements.
 +
|-
 +
|colspan="2"| Can restock
 +
|colspan="2"| Boolean
 +
| True for regular villagers and false for the wandering trader.  If true, the "Villagers restock up to two times per day." message is displayed when hovering over disabled trades.
 
  |}
 
  |}
  
==== Use Bed ====
+
[[File:1.14-merchant-slots.png|thumb|The merchant UI, for reference]]
 +
{{-}}
  
This packet tells that a player goes to bed.
+
==== Entity Position ====
  
The client with the matching Entity ID will go into bed mode.
+
This packet is sent by the server when an entity moves less then 8 blocks; if an entity moves more than 8 blocks [[#Entity Teleport|Entity Teleport]] should be sent instead.
  
This Packet is sent to all nearby players including the one sent to bed.
+
This packet allows at most 8 blocks movement in any direction, because short range is from -32768 to 32767. And <code>32768 / (128 * 32)</code> = 8.
 
 
Any packets sent with a location not currently occupied by a bed will be ignored by clients.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,842: Line 2,985:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x2F
+
  |rowspan="5"| 0x29
  |rowspan="2"| Play
+
  |rowspan="5"| Play
  |rowspan="2"| Client
+
  |rowspan="5"| Client
 
  | Entity ID
 
  | Entity ID
 
  | VarInt
 
  | VarInt
  | Sleeping player's EID
+
  |  
 +
|-
 +
| Delta X
 +
| Short
 +
| Change in X position as <code>(currentX * 32 - prevX * 32) * 128</code>
 +
|-
 +
| Delta Y
 +
| Short
 +
| Change in Y position as <code>(currentY * 32 - prevY * 32) * 128</code>
 
  |-
 
  |-
  | Location
+
  | Delta Z
  | Position
+
  | Short
  | Block location of the head part of the bed
+
| Change in Z position as <code>(currentZ * 32 - prevZ * 32) * 128</code>
 +
|-
 +
| On Ground
 +
| Boolean
 +
  |  
 
  |}
 
  |}
  
==== Unlock Recipes ====
+
==== Entity Position and Rotation ====
 +
 
 +
This packet is sent by the server when an entity rotates and moves. Since a short range is limited from -32768 to 32767, and movement is offset of fixed-point numbers, this packet allows at most 8 blocks movement in any direction. (<code>-32768 / (32 * 128) == -8</code>)
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,864: Line 3,021:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="8"| 0x30
+
  |rowspan="7"| 0x2A
  |rowspan="8"| Play
+
  |rowspan="7"| Play
  |rowspan="8"| Client
+
  |rowspan="7"| Client
  |-
+
  | Entity ID
| Action
 
 
  | VarInt
 
  | VarInt
  | 0: init, 1: add, 2: remove
+
  |  
 
  |-
 
  |-
  | Crafting Book Open
+
  | Delta X
  | Boolean
+
  | Short
  | If true, then the crafting book will be open when the player opens its inventory.
+
  | Change in X position as <code>(currentX * 32 - prevX * 32) * 128</code>
 
  |-
 
  |-
  | Filtering Craftable
+
  | Delta Y
  | Boolean
+
  | Short
  | If true, then the filtering option is active when the players opens its inventory.
+
  | Change in Y position as <code>(currentY * 32 - prevY * 32) * 128</code>
 
  |-
 
  |-
  | Array size 1
+
  | Delta Z
  | VarInt
+
  | Short
  | Number of elements in the following array
+
  | Change in Z position as <code>(currentZ * 32 - prevZ * 32) * 128</code>
 
  |-
 
  |-
  | Recipe IDs
+
  | Yaw
  | Array of VarInt
+
  | Angle
  |
+
  | New angle, not a delta
 
  |-
 
  |-
  | Array size 2
+
  | Pitch
  | Optional VarInt
+
  | Angle
  | Number of elements in the following array, only present if mode is 0 (init)
+
  | New angle, not a delta
 
  |-
 
  |-
  | Recipe IDs
+
  | On Ground
  | Optional Array of VarInt, only present if mode is 0 (init)
+
  | Boolean
  |
+
  |  
 
  |}
 
  |}
Action:
 
* 0 (init) = All the recipes in the list 2 will added to the recipe book. All the recipes in list 1 will be tagged as displayed, recipes that aren't tagged will be shown in the notification. VERIFY LIST ORDER?
 
* 1 (add) = All the recipes in the list are added and their icon will be shown in the notification.
 
* 2 (remove) = Remove all the recipes in the list. This allows them to re-displayed when they are readded.
 
  
Recipe ID:
+
==== Entity Rotation ====
These are hardcoded values in the client and server, all the recipe json files will be loaded in a specific order (alphabetical, like sounds) and internal ids will be assigned in that order. There are also inbuilt recipes like fireworks, banners, etc., these are the first recipes to have their id assigned. Due the fact that the recipes are loaded in a specific order will the ids very likely change when recipes get added. [https://twitter.com/dinnerbone/status/856505341479145472 Custom recipes are scheduled for Minecraft 1.13], so most likely will things change a bit in that version.
 
  
==== Destroy Entities ====
+
This packet is sent by the server when an entity rotates.
 
 
Sent by the server when a list of entities is to be destroyed on the client.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,916: Line 3,065:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x31
+
  |rowspan="4"| 0x2B
  |rowspan="2"| Play
+
  |rowspan="4"| Play
  |rowspan="2"| Client
+
  |rowspan="4"| Client
  | Count
+
  | Entity ID
 
  | VarInt
 
  | VarInt
  | Number of elements in the following array
+
  |  
 
  |-
 
  |-
  | Entity IDs
+
  | Yaw
  | Array of VarInt
+
  | Angle
  | The list of entities of destroy
+
| New angle, not a delta
 +
|-
 +
| Pitch
 +
| Angle
 +
| New angle, not a delta
 +
|-
 +
| On Ground
 +
| Boolean
 +
  |  
 
  |}
 
  |}
  
==== Remove Entity Effect ====
+
==== Entity Movement ====
 +
 
 +
This packet may be used to initialize an entity.
 +
 
 +
For player entities, either this packet or any move/look packet is sent every game tick. So the meaning of this packet is basically that the entity did not move/look since the last such packet.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,938: Line 3,099:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x32
+
  |rowspan="1"| 0x2C
  |rowspan="2"| Play
+
  |rowspan="1"| Play
  |rowspan="2"| Client
+
  |rowspan="1"| Client
 
  | Entity ID
 
  | Entity ID
 
  | VarInt
 
  | VarInt
 
  |  
 
  |  
|-
 
| Effect ID
 
| Byte
 
| See {{Minecraft Wiki|Status effect#List of effects|this table}}
 
 
  |}
 
  |}
  
==== Resource Pack Send ====  
+
==== Vehicle Move (clientbound) ====
 +
 
 +
Note that all fields use absolute positioning and do not allow for relative positioning.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,960: Line 3,119:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x33
+
  |rowspan="5"| 0x2D
  |rowspan="2"| Play
+
  |rowspan="5"| Play
  |rowspan="2"| Client
+
  |rowspan="5"| Client
  | URL
+
  | X
  | String (32767)
+
  | Double
  | The URL to the resource pack.
+
| Absolute position (X coordinate)
 +
  |-
 +
| Y
 +
| Double
 +
| Absolute position (Y coordinate)
 
  |-
 
  |-
  | Hash
+
  | Z
  | String (40)
+
  | Double
  | A 40 character hexadecimal and lowercase [[wikipedia:SHA-1|SHA-1]] hash of the resource pack file. (must be lower case in order to work)<br />If it's not a 40 character hexadecimal string, the client will not use it for hash verification and likely waste bandwidth — but it will still treat it as a unique id
+
| Absolute position (Z coordinate)
  |}
+
  |-
 
+
| Yaw
==== Respawn ====
+
| Float
 
+
| Absolute rotation on the vertical axis, in degrees
To change the player's dimension (overworld/nether/end), send them a respawn packet with the appropriate dimension, followed by prechunks/chunks for the new dimension, and finally a position and look packet. You do not need to unload chunks, the client will do it automatically.
+
|-
 +
| Pitch
 +
| Float
 +
| Absolute rotation on the horizontal axis, in degrees
 +
  |}
 +
 
 +
==== Open Book ====
 +
 
 +
Sent when a player right clicks with a signed book. This tells the client to open the book GUI.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 2,984: Line 3,155:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="4"| 0x34
+
  |rowspan="1"| 0x2E
  |rowspan="4"| Play
+
  |rowspan="1"| Play
  |rowspan="4"| Client
+
  |rowspan="1"| Client
  | Dimension
+
  | Hand
  | Int Enum
+
  | VarInt enum
  | -1: The Nether, 0: The Overworld, 1: The End
+
  | 0: Main hand, 1: Off hand
|-
 
| Difficulty
 
| Unsigned Byte
 
| 0: Peaceful, 1: Easy, 2: Normal, 3: Hard
 
|-
 
| Gamemode
 
| Unsigned Byte
 
| 0: survival, 1: creative, 2: adventure, 3: spectator. The hardcore flag is not included
 
|-
 
| Level Type
 
| String (16)
 
| Same as [[#Join Game|Join Game]]
 
 
  |}
 
  |}
  
{{Warning2|Avoid changing player's dimension to same dimension they were already in unless they are dead. If you change the dimension to one they are already in, weird bugs can occur, such as the player being unable to attack other players in new world (until they die and respawn).
+
==== Open Window ====
 
 
If you must respawn a player in the same dimension without killing them, send two respawn packets, one to a different world and then another to the world you want. You do not need to complete the first respawn; it only matters that you send two packets.}}
 
 
 
==== Entity Head Look ====
 
  
Changes the direction an entity's head is facing.
+
This is sent to the client when it should open an inventory, such as a chest, workbench, or furnace. This message is not sent anywhere for clients opening their own inventory.  For horses, use [[#Open Horse Window|Open Horse Window]].
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,020: Line 3,175:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x35
+
  |rowspan="3"| 0x2F
  |rowspan="2"| Play
+
  |rowspan="3"| Play
  |rowspan="2"| Client
+
  |rowspan="3"| Client
  | Entity ID
+
  | Window ID
 
  | VarInt
 
  | VarInt
  |  
+
  | A unique id number for the window to be displayed. Notchian server implementation is a counter, starting at 1.
 
  |-
 
  |-
  | Head Yaw
+
  | Window Type
  | Angle
+
  | VarInt
  | New angle, not a delta
+
  | The window type to use for display. Contained in the <code>minecraft:menu</code> regisry; see [[Inventory]] for the different values.
 +
|-
 +
| Window Title
 +
| [[Chat]]
 +
| The title of the window
 
  |}
 
  |}
  
==== Select Advancement Tab ====
+
==== Open Sign Editor ====
  
Sent by the server to indicate that the client should switch advancement tab. Sent either when the client switches tab in the GUI or when an advancement in another tab is made.
+
Sent when the client has placed a sign and is allowed to send [[#Update Sign|Update Sign]].  There must already be a sign at the given location (which the client does not do automatically) - send a [[#Block Change|Block Change]] first.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,044: Line 3,203:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x36
+
  |rowspan="1"| 0x30
  |rowspan="2"| Play
+
  |rowspan="1"| Play
  |rowspan="2"| Client
+
  |rowspan="1"| Client
  | Has id
+
  | Location
  | Boolean
+
  | Position
  | Indicates if the next field is present
+
  |  
|-
 
| Optional Identifier
 
| String (32767)
 
| See below
 
|}
 
 
 
The Identifier can be one of the following:
 
 
 
{| class="wikitable"
 
! Optional Identifier
 
|-
 
| minecraft:story/root
 
|-
 
| minecraft:nether/root
 
|-
 
| minecraft:end/root
 
|-
 
| minecraft:adventure/root
 
|-
 
| minecraft:husbandry/root
 
 
  |}
 
  |}
  
If no or an invalid identifier is sent, the client will switch to the first tab in the GUI.
+
==== Craft Recipe Response ====
  
==== World Border ====
+
Response to the serverbound packet ([[#Craft Recipe Request|Craft Recipe Request]]), with the same recipe ID.  Appears to be used to notify the UI.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,080: Line 3,219:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  !colspan="2"| Field Name
+
  ! Field Name
 
  ! Field Type
 
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="18"| 0x37
+
  |rowspan="2"| 0x31
  |rowspan="18"| Play
+
  |rowspan="2"| Play
  |rowspan="18"| Client
+
  |rowspan="2"| Client
  |colspan="2"| Action
+
  | Window ID
  | VarInt Enum
+
  | Byte
  | Determines the format of the rest of the packet
+
  |
 
  |-
 
  |-
  ! Action
+
| Recipe
 +
| Identifier
 +
| A recipe ID
 +
|}
 +
 
 +
==== Player Abilities (clientbound) ====
 +
 
 +
The latter 2 floats are used to indicate the field of view and flying speed respectively, while the first byte is used to determine the value of 4 booleans.
 +
 
 +
{| class="wikitable"
 +
  ! Packet ID
 +
! State
 +
! Bound To
 
  ! Field Name
 
  ! Field Name
  !  
+
  ! Field Type
  !  
+
  ! Notes
 
  |-
 
  |-
  | 0: set size
+
  |rowspan="3"| 0x32
  | Diameter
+
|rowspan="3"| Play
  | Double
+
|rowspan="3"| Client
  | Length of a single side of the world border, in meters
+
  | Flags
 +
  | Byte
 +
  | Bit field, see below
 
  |-
 
  |-
  |rowspan="3"| 1: lerp size
+
  | Flying Speed
| Old Diameter
+
  | Float
  | Double
+
  | 0.05 by default
  | Current length of a single side of the world border, in meters
 
 
  |-
 
  |-
  | New Diameter
+
  | Field of View Modifier
  | Double
+
  | Float
  | Target length of a single side of the world border, in meters
+
  | Modifies the field of view, like a speed potion. A Notchian server will use the same value as the movement speed sent in the [[Protocol#Entity_Properties|Entity Properties]] packet, which defaults to 0.1 for players.
 +
|}
 +
 
 +
About the flags:
 +
 
 +
{| class="wikitable"
 
  |-
 
  |-
  | Speed
+
  ! Field
  | VarLong
+
  ! Bit
| Number of real-time ''milli''seconds until New Diameter is reached. It appears that Notchian server does not sync world border speed to game ticks, so it gets out of sync with server lag. If the world border is not moving, this is set to 0.
 
 
  |-
 
  |-
  |rowspan="2"| 2: set center
+
  | Invulnerable
| X
+
  | 0x01
| Double
 
  |  
 
 
  |-
 
  |-
  | Z
+
  | Flying
| Double
+
  | 0x02
  |  
 
 
  |-
 
  |-
  |rowspan="8"| 3: initialize
+
  | Allow Flying
| X
+
  | 0x04
| Double
 
  |  
 
 
  |-
 
  |-
  | Z
+
  | Creative Mode (Instant Break)
  | Double
+
  | 0x08
  |  
+
  |}
 +
 
 +
==== Combat Event ====
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
!colspan="2"| Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | Old Diameter
+
  |rowspan="8"| 0x33
  | Double
+
|rowspan="8"| Play
  | Current length of a single side of the world border, in meters
+
  |rowspan="8"| Client
 +
  |colspan="2"| Event
 +
| VarInt Enum
 +
| Determines the layout of the remaining packet
 
  |-
 
  |-
  | New Diameter
+
  ! Event
  | Double
+
  ! Field Name
  | Target length of a single side of the world border, in meters
+
  !
 +
!
 
  |-
 
  |-
  | Speed
+
  | 0: enter combat
  | VarLong
+
  | ''no fields''
  | Number of real-time ''milli''seconds until New Diameter is reached. It appears that Notchian server does not sync world border speed to game ticks, so it gets out of sync with server lag. If the world border is not moving, this is set to 0.
+
  | ''no fields''
 +
|
 
  |-
 
  |-
  | Portal Teleport Boundary
+
  |rowspan="2"| 1: end combat
 +
| Duration
 
  | VarInt
 
  | VarInt
  | Resulting coordinates from a portal teleport are limited to ±value. Usually 29999984.
+
  |  
 
  |-
 
  |-
  | Warning Time
+
  | Entity ID
  | VarInt
+
  | Int
  | In seconds as set by <code>/worldborder warning time</code>
+
  |  
 
  |-
 
  |-
  | Warning Blocks
+
  |rowspan="3"| 2: entity dead
 +
| Player ID
 
  | VarInt
 
  | VarInt
  | In meters
+
  |  
 
  |-
 
  |-
  |rowspan="1"| 4: set warning time
+
  | Entity ID
| Warning Time
+
  | Int
  | VarInt
+
  |  
  | In seconds as set by <code>/worldborder warning time</code>
 
 
  |-
 
  |-
  |rowspan="1"| 5: set warning blocks
+
  | Message
| Warning Blocks
+
  | [[Chat]]
  | VarInt
+
  |  
  | In meters
 
 
  |}
 
  |}
  
The Notchian client determines how solid to display the warning by comparing to whichever is higher, the warning distance or whichever is lower, the distance from the current diameter to the target diameter or the place the border will be after warningTime seconds. In pseudocode:
+
==== Player Info ====
 +
 
 +
Sent by the server to update the user list (<tab> in the client).
  
<syntaxhighlight lang="java">
+
{| class="wikitable"
distance = max(min(resizeSpeed * 1000 * warningTime, abs(targetDiameter - currentDiameter)), warningDistance);
+
  ! Packet ID
if (playerDistance < distance) {
 
    warning = 1.0 - playerDistance / distance;
 
} else {
 
    warning = 0.0;
 
}
 
</syntaxhighlight>
 
 
 
==== Camera ====
 
 
 
Sets the entity that the player renders from. This is normally used when the player left-clicks an entity while in spectator mode.
 
 
 
The player's camera will move with the entity and look where it is looking. The entity is often another player, but can be any type of entity.  The player is unable to move this entity (move packets will act as if they are coming from the other entity).
 
 
 
If the given entity is not loaded by the player, this packet is ignored.  To return control to the player, send this packet with their entity ID.
 
 
 
The Notchian server resets this (sends it back to the default entity) whenever the spectated entity is killed or the player sneaks, but only if they were spectating an entity. It also sends this packet whenever the player switches out of spectator mode (even if they weren't spectating an entity).
 
 
 
{| class="wikitable"
 
  ! Packet ID
 
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  ! Field Name
+
  !colspan="4"| Field Name
  ! Field Type
+
  !colspan="3"| Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="1"| 0x38
+
  |rowspan="19"| 0x34
  |rowspan="1"| Play
+
  |rowspan="19"| Play
  |rowspan="1"| Client
+
  |rowspan="19"| Client
  | Camera ID
+
  |colspan="4"| Action
  | VarInt
+
  |colspan="3"| VarInt
  | ID of the entity to set the client's camera to
+
  | Determines the rest of the Player format after the UUID
  |}
+
  |-
 
+
|colspan="4"| Number Of Players
The notchian also loads certain shaders for given entities:
+
|colspan="3"| VarInt
 
+
| Number of elements in the following array
* Creeper &rarr; <code>shaders/post/creeper.json</code>
+
|-
* Spider (and cave spider) &rarr; <code>shaders/post/spider.json</code>
+
|rowspan="17"| Player
* Enderman &rarr; <code>shaders/post/invert.json</code>
+
  |colspan="3"| UUID
* Anything else &rarr; the current shader is unloaded
+
  |rowspan="17"| Array
 
+
  |colspan="2"| UUID
==== Held Item Change (clientbound) ====
+
  |
 
 
Sent to change the player's slot selection.
 
 
 
{| class="wikitable"
 
  ! Packet ID
 
  ! State
 
  ! Bound To
 
  ! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="1"| 0x39
+
  ! Action
  |rowspan="1"| Play
+
  !colspan="2"| Field Name
  |rowspan="1"| Client
+
  !colspan="2"|  
| Slot
+
  !  
| Byte
 
| The slot which the player has selected (0–8)
 
|}
 
 
 
==== Display Scoreboard ====
 
 
 
This is sent to the client when it should display a scoreboard.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
  ! Notes
 
 
  |-
 
  |-
  |rowspan="2"| 0x3A
+
  |rowspan="10"| 0: add player
  |rowspan="2"| Play
+
  |colspan="2"| Name
  |rowspan="2"| Client
+
  |colspan="2"| String (16)
| Position
+
  |  
| Byte
 
  | The position of the scoreboard. 0: list, 1: sidebar, 2: below name.
 
 
  |-
 
  |-
  | Score Name
+
  |colspan="2"| Number Of Properties
  | String (16)
+
  |colspan="2"| VarInt
| The unique name for the scoreboard to be displayed.
+
  | Number of elements in the following array
  |}
 
 
 
==== Entity Metadata ====
 
 
 
Updates one or more [[Entities#Entity Metadata Format|metadata]] properties for an existing entity. Any properties not included in the Metadata field are left unchanged.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="2"| 0x3B
+
  |rowspan="4"| Property
  |rowspan="2"| Play
+
  | Name
  |rowspan="2"| Client
+
  |rowspan="4"| Array
| Entity ID
+
  | String (32767)
  | VarInt
 
 
  |  
 
  |  
 
  |-
 
  |-
  | Metadata
+
  | Value
  | [[Entities#Entity Metadata Format|Entity Metadata]]
+
  | String (32767)
 +
|
 +
|-
 +
| Is Signed
 +
| Boolean
 
  |  
 
  |  
|}
 
 
==== Attach Entity ====
 
 
This packet is sent when an entity has been {{Minecraft Wiki|Lead|leashed}} to another entity.
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="2"| 0x3C
+
| Signature
  |rowspan="2"| Play
+
| Optional String (32767)
  |rowspan="2"| Client
+
| Only if Is Signed is true
  | Attached Entity ID
+
|-
  | Int
+
|colspan="2"| Gamemode
  | Attached entity's EID
+
|colspan="2"| VarInt
 +
|
 +
|-
 +
|colspan="2"| Ping
 +
|colspan="2"| VarInt
 +
| Measured in milliseconds
 +
|-
 +
|colspan="2"| Has Display Name
 +
|colspan="2"| Boolean
 +
|
 +
|-
 +
|colspan="2"| Display Name
 +
|colspan="2"| Optional [[Chat]]
 +
| Only if Has Display Name is true
 +
|-
 +
| 1: update gamemode
 +
|colspan="2"| Gamemode
 +
|colspan="2"| VarInt
 +
|
 +
|-
 +
| 2: update latency
 +
|colspan="2"| Ping
 +
|colspan="2"| VarInt
 +
| Measured in milliseconds
 +
|-
 +
  |rowspan="2"| 3: update display name
 +
  |colspan="2"| Has Display Name
 +
  |colspan="2"| Boolean
 +
  |  
 +
  |-
 +
|colspan="2"| Display Name
 +
|colspan="2"| Optional [[Chat]]
 +
  | Only send if Has Display Name is true
 
  |-
 
  |-
  | Holding Entity ID
+
  | 4: remove player
  | Int
+
  |colspan="2"| ''no fields''
  | ID of the entity holding the lead. Set to -1 to detach.
+
|colspan="2"| ''no fields''
 +
  |  
 
  |}
 
  |}
  
==== Entity Velocity ====
+
The Property field looks as in the response of [[Mojang API#UUID -> Profile + Skin/Cape]], except of course using the protocol format instead of JSON. That is, each player will usually have one property with Name “textures” and Value being a base64-encoded JSON string as documented at [[Mojang API#UUID -> Profile + Skin/Cape]]. An empty properties array is also acceptable, and will cause clients to display the player with one of the two default skins depending on UUID.
 +
 
 +
Ping values correspond with icons in the following way:
 +
* A ping that negative (i.e. not known to the server yet) will result in the no connection icon.
 +
* A ping under 150 milliseconds will result in 5 bars
 +
* A ping under 300 milliseconds will result in 4 bars
 +
* A ping under 600 milliseconds will result in 3 bars
 +
* A ping under 1000 milliseconds (1 second) will result in 2 bars
 +
* A ping greater than or equal to 1 second will result in 1 bar.
 +
 
 +
==== Face Player ====
  
Velocity is believed to be in units of 1/8000 of a block per server tick (50ms); for example, -1343 would move (-1343 / 8000) = −0.167875 blocks per tick (or −3,3575 blocks per second).
+
Used to rotate the client player to face the given location or entity (for <code>/teleport [<targets>] <x> <y> <z> facing</code>).
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,315: Line 3,457:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="4"| 0x3D
+
  |rowspan="8"| 0x35
  |rowspan="4"| Play
+
  |rowspan="8"| Play
  |rowspan="4"| Client
+
  |rowspan="8"| Client
  | Entity ID
+
  |-
  | VarInt
+
| Feet/eyes
  |  
+
  | VarInt enum
 +
| Values are feet=0, eyes=1.  If set to eyes, aims using the head position; otherwise aims using the feet position.
 +
|-
 +
| Target x
 +
| Double
 +
| x coordinate of the point to face towards
 +
|-
 +
| Target y
 +
| Double
 +
| y coordinate of the point to face towards
 +
|-
 +
| Target z
 +
| Double
 +
  | z coordinate of the point to face towards
 
  |-
 
  |-
  | Velocity X
+
  | Is entity
  | Short
+
  | Boolean
  | Velocity on the X axis
+
  | If true, additional information about an entity is provided.
 
  |-
 
  |-
  | Velocity Y
+
  | Entity ID
  | Short
+
  | Optional VarInt
  | Velocity on the Y axis
+
  | Only if is entity is true &mdash; the entity to face towards
 
  |-
 
  |-
  | Velocity Z
+
  | Entity feet/eyes
  | Short
+
  | Optional VarInt enum
  | Velocity on the Z axis
+
  | Whether to look at the entity's eyes or feet.  Same values and meanings as before, just for the entity's head/feet.
 
  |}
 
  |}
  
==== Entity Equipment ====
+
If the entity given by entity ID cannot be found, this packet should be treated as if is entity was false.
 +
 
 +
==== Player Position And Look (clientbound) ====  
 +
 
 +
Updates the player's position on the server. This packet will also close the “Downloading Terrain” screen when joining/respawning.
 +
 
 +
If the distance between the last known position of the player on the server and the new position set by this packet is greater than 100 meters, the client will be kicked for “You moved too quickly :( (Hacking?)”.
 +
 
 +
Also if the fixed-point number of X or Z is set greater than <code>3.2E7D</code> the client will be kicked for “Illegal position”.
 +
 
 +
Yaw is measured in degrees, and does not follow classical trigonometry rules. The unit circle of yaw on the XZ-plane starts at (0, 1) and turns counterclockwise, with 90 at (-1, 0), 180 at (0, -1) and 270 at (1, 0). Additionally, yaw is not clamped to between 0 and 360 degrees; any number is valid, including negative numbers and numbers greater than 360.
 +
 
 +
Pitch is measured in degrees, where 0 is looking straight ahead, -90 is looking straight up, and 90 is looking straight down.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,345: Line 3,512:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="3"| 0x3E
+
  |rowspan="7"| 0x36
  |rowspan="3"| Play
+
  |rowspan="7"| Play
  |rowspan="3"| Client
+
  |rowspan="7"| Client
  | Entity ID
+
  | X
  | VarInt
+
  | Double
  | Entity's EID
+
  | Absolute or relative position, depending on Flags
 
  |-
 
  |-
  | Slot
+
  | Y
  | VarInt Enum
+
  | Double
  | Equipment slot. 0: main hand, 1: off hand, 2–5: armor slot (2: boots, 3: leggings, 4: chestplate, 5: helmet)
+
  | Absolute or relative position, depending on Flags
 +
|-
 +
| Z
 +
| Double
 +
| Absolute or relative position, depending on Flags
 
  |-
 
  |-
  | Item
+
  | Yaw
| [[Slot Data|Slot]]
+
  | Float
  |  
+
  | Absolute or relative rotation on the X axis, in degrees
  |}
 
 
 
==== Set Experience ====
 
 
 
Sent by the server when the client should change experience levels.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="3"| 0x3F
+
  | Pitch
|rowspan="3"| Play
 
|rowspan="3"| Client
 
| Experience bar
 
 
  | Float
 
  | Float
  | Between 0 and 1
+
  | Absolute or relative rotation on the Y axis, in degrees
 
  |-
 
  |-
  | Level
+
  | Flags
  | VarInt
+
  | Byte
  |  
+
  | Bit field, see below
 
  |-
 
  |-
  | Total Experience
+
  | Teleport ID
 
  | VarInt
 
  | VarInt
  | See {{Minecraft Wiki|Experience#Leveling up}} on the Minecraft Wiki for Total Experience to Level conversion
+
  | Client should confirm this packet with [[#Teleport Confirm|Teleport Confirm]] containing the same Teleport ID
 
  |}
 
  |}
  
==== Update Health ====
+
About the Flags field:
  
Sent by the server to update/set the health of the player it is sent to.
+
<Dinnerbone> It's a bitfield, X/Y/Z/Y_ROT/X_ROT. If X is set, the x value is relative and not absolute.
  
Food {{Minecraft Wiki|Food#Hunger vs. Saturation|saturation}} acts as a food “overcharge”. Food values will not decrease while the saturation is over zero. Players logging in automatically get a saturation of 5.0. Eating food increases the saturation as well as the food bar.
+
{| class="wikitable"
 
+
|-
{| class="wikitable"
+
  ! Field
  ! Packet ID
+
  ! Bit
  ! State
+
  |-
  ! Bound To
+
| X
  ! Field Name
+
| 0x01
  ! Field Type
+
|-
  ! Notes
+
| Y
 +
| 0x02
 +
  |-
 +
  | Z
 +
  | 0x04
 
  |-
 
  |-
  |rowspan="3"| 0x40
+
  | Y_ROT
|rowspan="3"| Play
+
  | 0x08
|rowspan="3"| Client
 
| Health
 
| Float
 
  | 0 or less = dead, 20 = full HP
 
 
  |-
 
  |-
  | Food
+
  | X_ROT
  | VarInt
+
  | 0x10
| 0–20
 
|-
 
| Food Saturation
 
| Float
 
| Seems to vary from 0.0 to 5.0 in integer increments
 
 
  |}
 
  |}
  
==== Scoreboard Objective ====
+
==== Unlock Recipes ====
 
 
This is sent to the client when it should create a new {{Minecraft Wiki|scoreboard}} objective or remove one.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,431: Line 3,579:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="4"| 0x41
+
  |rowspan="10"| 0x37
  |rowspan="4"| Play
+
  |rowspan="10"| Play
  |rowspan="4"| Client
+
  |rowspan="10"| Client
| Objective Name
 
| String (16)
 
| An unique name for the objective
 
 
  |-
 
  |-
  | Mode
+
  | Action
  | Byte
+
  | VarInt
  | 0 to create the scoreboard. 1 to remove the scoreboard. 2 to update the display text.  
+
  | 0: init, 1: add, 2: remove
 +
|-
 +
| Crafting Recipe Book Open
 +
| Boolean
 +
| If true, then the crafting recipe book will be open when the player opens its inventory.
 +
|-
 +
| Crafting Recipe Book Filter Active
 +
| Boolean
 +
| If true, then the filtering option is active when the players opens its inventory.
 +
|-
 +
| Smelting Recipe Book Open
 +
| Boolean
 +
| If true, then the smelting recipe book will be open when the player opens its inventory.
 +
|-
 +
| Smelting Recipe Book Filter Active
 +
| Boolean
 +
| If true, then the filtering option is active when the players opens its inventory.
 +
|-
 +
| Array size 1
 +
| VarInt
 +
| Number of elements in the following array
 +
|-
 +
| Recipe IDs
 +
| Array of Identifier
 +
|
 
  |-
 
  |-
  | Objective Value
+
  | Array size 2
  | Optional String (32)
+
  | Optional VarInt
  | Only if mode is 0 or 2. The text to be displayed for the score
+
  | Number of elements in the following array, only present if mode is 0 (init)
 
  |-
 
  |-
  | Type
+
  | Recipe IDs
  | Optional String (16)
+
  | Optional Array of Identifier, only present if mode is 0 (init)
  | Only if mode is 0 or 2. “integer” or “hearts”
+
  |
 
  |}
 
  |}
 +
Action:
 +
* 0 (init) = All the recipes in the list 2 will added to the recipe book. All the recipes in list 1 will be tagged as displayed, recipes that aren't tagged will be shown in the notification. VERIFY LIST ORDER?
 +
* 1 (add) = All the recipes in the list are added and their icon will be shown in the notification.
 +
* 2 (remove) = Remove all the recipes in the list. This allows them to re-displayed when they are readded.
 +
 +
==== Destroy Entities ====
  
==== Set Passengers ====
+
Sent by the server when a list of entities is to be destroyed on the client.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,461: Line 3,636:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="3"| 0x42
+
  |rowspan="2"| 0x38
  |rowspan="3"| Play
+
  |rowspan="2"| Play
  |rowspan="3"| Client
+
  |rowspan="2"| Client
  | Entity ID
+
  | Count
| VarInt
 
| Vehicle's EID
 
|-
 
| Passenger Count
 
 
  | VarInt
 
  | VarInt
 
  | Number of elements in the following array
 
  | Number of elements in the following array
 
  |-
 
  |-
  | Passengers
+
  | Entity IDs
 
  | Array of VarInt
 
  | Array of VarInt
  | EIDs of entity's passengers
+
  | The list of entities of destroy
 
  |}
 
  |}
  
==== Teams ====
+
==== Remove Entity Effect ====
 
 
Creates and updates teams.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,485: Line 3,654:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  !colspan="2"| Field Name
+
  ! Field Name
 
  ! Field Type
 
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="23"| 0x43
+
  |rowspan="2"| 0x39
  |rowspan="23"| Play
+
  |rowspan="2"| Play
  |rowspan="23"| Client
+
  |rowspan="2"| Client
  |colspan="2"| Team Name
+
  | Entity ID
  | String (16)
+
  | VarInt
  | A unique name for the team. (Shared with scoreboard).
+
  |  
 
  |-
 
  |-
  |colspan="2"| Mode
+
  | Effect ID
 
  | Byte
 
  | Byte
  | Determines the layout of the remaining packet
+
  | See {{Minecraft Wiki|Status effect#List of effects|this table}}
 +
|}
 +
 
 +
==== Resource Pack Send ====
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  |rowspan="9"| 0: create team
+
  |rowspan="2"| 0x3A
  | Team Display Name
+
  |rowspan="2"| Play
  | String (32)
+
|rowspan="2"| Client
  |  
+
| URL
 +
  | String (32767)
 +
  | The URL to the resource pack.
 
  |-
 
  |-
  | Team Prefix
+
  | Hash
  | String (16)
+
  | String (40)
  | Displayed before the names of players that are part of this team
+
  | A 40 character hexadecimal and lowercase [[wikipedia:SHA-1|SHA-1]] hash of the resource pack file. (must be lower case in order to work)<br />If it's not a 40 character hexadecimal string, the client will not use it for hash verification and likely waste bandwidth — but it will still treat it as a unique id
  |-
+
  |}
  | Team Suffix
+
 
  | String (16)
+
==== Respawn ====
  | Displayed after the names of players that are part of this team
+
 
 +
To change the player's dimension (overworld/nether/end), send them a respawn packet with the appropriate dimension, followed by prechunks/chunks for the new dimension, and finally a position and look packet. You do not need to unload chunks, the client will do it automatically.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
  ! Field Name
 +
  ! Field Type
 +
  ! Notes
 
  |-
 
  |-
  | Friendly Flags
+
  |rowspan="4"| 0x3B
  | Byte
+
|rowspan="4"| Play
  | Bit mask. 0x01: Allow friendly fire, 0x02: can see invisible players on same team
+
|rowspan="4"| Client
 +
  | Dimension
 +
  | Int Enum
 +
| -1: The Nether, 0: The Overworld, 1: The End
 
  |-
 
  |-
  | Name Tag Visibility
+
  | Hashed seed
  | String Enum (32)
+
  | Long
  | <code>always</code>, <code>hideForOtherTeams</code>, <code>hideForOwnTeam</code>, <code>never</code>
+
  | First 8 bytes of the SHA-256 hash of the world's seed.
 
  |-
 
  |-
  | Collision Rule
+
  | Gamemode
  | String Enum (32)
+
  | Unsigned Byte
  | <code>always</code>, <code>pushOtherTeams</code>, <code>pushOwnTeam</code>, <code>never</code>
+
  | 0: survival, 1: creative, 2: adventure, 3: spectator. The hardcore flag is not included
 
  |-
 
  |-
  | Color
+
  | Level Type
  | Byte
+
  | String (16)
  | For colors, the same [[Chat]] colors (0-15). -1 indicates RESET/no color.
+
  | Same as [[#Join Game|Join Game]]
|-
+
|}
| Entity Count
+
 
| VarInt
+
{{Warning2|Avoid changing player's dimension to same dimension they were already in unless they are dead. If you change the dimension to one they are already in, weird bugs can occur, such as the player being unable to attack other players in new world (until they die and respawn).
  | Number of elements in the following array
+
 
  |-
+
If you must respawn a player in the same dimension without killing them, send two respawn packets, one to a different world and then another to the world you want. You do not need to complete the first respawn; it only matters that you send two packets.}}
  | Entities
+
 
  | Array of String (40)
+
==== Entity Head Look ====
  | Identifiers for the entities in this team. For players, this is their username; for other entities, it is their UUID.
+
 
 +
Changes the direction an entity's head is facing.
 +
 
 +
While sending the Entity Look packet changes the vertical rotation of the head, sending this packet appears to be necessary to rotate the head horizontally.
 +
 
 +
{| class="wikitable"
 +
  ! Packet ID
 +
  ! State
 +
  ! Bound To
 +
  ! Field Name
 +
  ! Field Type
 +
  ! Notes
 
  |-
 
  |-
  | 1: remove team
+
  |rowspan="2"| 0x3C
  | ''no fields''
+
|rowspan="2"| Play
  | ''no fields''
+
|rowspan="2"| Client
 +
  | Entity ID
 +
  | VarInt
 
  |  
 
  |  
 
  |-
 
  |-
  |rowspan="7"| 2: update team info
+
  | Head Yaw
  | Team Display Name
+
| Angle
  | String (32)
+
| New angle, not a delta
  |
+
|}
 +
 
 +
==== Select Advancement Tab ====
 +
 
 +
Sent by the server to indicate that the client should switch advancement tab. Sent either when the client switches tab in the GUI or when an advancement in another tab is made.
 +
 
 +
{| class="wikitable"
 +
  ! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
  ! Field Type
 +
  ! Notes
 
  |-
 
  |-
  | Team Prefix
+
  |rowspan="2"| 0x3D
  | String (16)
+
|rowspan="2"| Play
  | Displayed before the names of entities that are part of this team
+
|rowspan="2"| Client
 +
| Has id
 +
  | Boolean
 +
  | Indicates if the next field is present
 
  |-
 
  |-
  | Team Suffix
+
  | Optional Identifier
  | String (16)
+
  | String (32767)
  | Displayed after the names of entities that are part of this team
+
  | See below
 +
|}
 +
 
 +
The Identifier can be one of the following:
 +
 
 +
{| class="wikitable"
 +
! Optional Identifier
 
  |-
 
  |-
  | Friendly Flags
+
  | minecraft:story/root
| Byte
 
| Bit mask. 0x01: Allow friendly fire, 0x02: can see invisible entities on same team
 
 
  |-
 
  |-
  | Name Tag Visibility
+
  | minecraft:nether/root
| String Enum (32)
 
| <code>always</code>, <code>hideForOtherTeams</code>, <code>hideForOwnTeam</code>, <code>never</code>
 
 
  |-
 
  |-
  | Collision Rule
+
  | minecraft:end/root
| String Enum (32)
 
| <code>always</code>, <code>pushOtherTeams</code>, <code>pushOwnTeam</code>, <code>never</code>
 
 
  |-
 
  |-
  | Color
+
  | minecraft:adventure/root
| Byte
 
| For colors, the same [[Chat]] colors (0-15).  -1 indicates RESET/no color.
 
 
  |-
 
  |-
  |rowspan="2"| 3: add players to team
+
  | minecraft:husbandry/root
| Entity Count
 
| VarInt
 
| Number of elements in the following array
 
|-
 
| Entities
 
| Array of String (40)
 
| Identifiers for the entities added.  For players, this is their username; for other entities, it is their UUID.
 
|-
 
|rowspan="2"| 4: remove players from team
 
| Entity Count
 
| VarInt
 
| Number of elements in the following array
 
|-
 
| Entities
 
| Array of String (40)
 
| Identifiers for the entities removed.  For players, this is their username; for other entities, it is their UUID.
 
 
  |}
 
  |}
  
==== Update Score ====
+
If no or an invalid identifier is sent, the client will switch to the first tab in the GUI.
  
This is sent to the client when it should update a scoreboard item.
+
==== World Border ====
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,598: Line 3,802:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  ! Field Name
+
  !colspan="2"| Field Name
 
  ! Field Type
 
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="4"| 0x44
+
  |rowspan="18"| 0x3E
  |rowspan="4"| Play
+
  |rowspan="18"| Play
  |rowspan="4"| Client
+
  |rowspan="18"| Client
  | Entity Name
+
  |colspan="2"| Action
  | String (40)
+
  | VarInt Enum
  | The entity whose score this is.  For players, this is their username; for other entities, it is their UUID.
+
  | Determines the format of the rest of the packet
 
  |-
 
  |-
  | Action
+
  ! Action
  | Byte
+
  ! Field Name
  | 0 to create/update an item. 1 to remove an item.
+
  !
 +
!
 
  |-
 
  |-
  | Objective Name
+
  | 0: set size
  | String (16)
+
  | Diameter
  | The name of the objective the score belongs to
+
  | Double
 +
| Length of a single side of the world border, in meters
 
  |-
 
  |-
  | Value
+
  |rowspan="3"| 1: lerp size
  | Optional VarInt
+
  | Old Diameter
  | The score to be displayed next to the entry. Only sent when Action does not equal 1.
+
  | Double
  |}
+
  | Current length of a single side of the world border, in meters
 
 
==== Spawn Position ====
 
 
 
Sent by the server after login to specify the coordinates of the spawn point (the point at which players spawn at, and which the compass points to). It can be sent at any time to update the point compasses point at.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="1"| 0x45
+
  | New Diameter
  |rowspan="1"| Play
+
  | Double
  |rowspan="1"| Client
+
  | Target length of a single side of the world border, in meters
| Location
 
| Position
 
| Spawn location
 
|}
 
 
 
==== Time Update ====
 
 
 
Time is based on ticks, where 20 ticks happen every second. There are 24000 ticks in a day, making Minecraft days exactly 20 minutes long.
 
 
 
The time of day is based on the timestamp modulo 24000. 0 is sunrise, 6000 is noon, 12000 is sunset, and 18000 is midnight.
 
 
 
The default SMP server increments the time by <code>20</code> every second.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="2"| 0x46
+
  | Speed
  |rowspan="2"| Play
+
  | VarLong
  |rowspan="2"| Client
+
  | Number of real-time ''milli''seconds until New Diameter is reached. It appears that Notchian server does not sync world border speed to game ticks, so it gets out of sync with server lag. If the world border is not moving, this is set to 0.
| World Age
 
| Long
 
| In ticks; not changed by server commands
 
 
  |-
 
  |-
  | Time of day
+
  |rowspan="2"| 2: set center
| Long
+
  | X
  | The world (or region) time, in ticks. If negative the sun will stop moving at the Math.abs of the time
+
  | Double
  |}
+
  |  
 
 
==== Title ====
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
  !colspan="2"| Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="10"| 0x47
+
  | Z
|rowspan="10"| Play
+
  | Double
|rowspan="10"| Client
 
|colspan="2"| Action
 
  | VarInt Enum
 
 
  |  
 
  |  
 
  |-
 
  |-
! Action
+
  |rowspan="8"| 3: initialize
! Field Name
+
  | X
!
+
  | Double
!
 
  |-
 
| 0: set title
 
  | Title Text
 
  | [[Chat]]
 
 
  |  
 
  |  
 
  |-
 
  |-
  | 1: set subtitle
+
  | Z
  | Subtitle Text
+
  | Double
| [[Chat]]
 
 
  |  
 
  |  
|-
 
| 2: set action bar
 
| Action bar text
 
| [[Chat]]
 
| Displays a message above the hotbar (the same as position 2 in [[#Chat Message (clientbound)|Chat Message (clientbound)]], except that it correctly renders formatted chat. See [https://bugs.mojang.com/browse/MC-119145 MC-119145] for more information.)
 
 
  |-
 
  |-
  |rowspan="3"| 3: set times and display
+
  | Old Diameter
| Fade In
+
  | Double
  | Int
+
  | Current length of a single side of the world border, in meters
  | Ticks to spend fading in
 
 
  |-
 
  |-
  | Stay
+
  | New Diameter
  | Int
+
  | Double
  | Ticks to keep the title displayed
+
  | Target length of a single side of the world border, in meters
 
  |-
 
  |-
  | Fade Out
+
  | Speed
  | Int
+
  | VarLong
  | Ticks to spend out, not when to start fading out
+
  | Number of real-time ''milli''seconds until New Diameter is reached. It appears that Notchian server does not sync world border speed to game ticks, so it gets out of sync with server lag. If the world border is not moving, this is set to 0.
 
  |-
 
  |-
  | 4: hide
+
  | Portal Teleport Boundary
  | ''no fields''
+
| VarInt
  | ''no fields''
+
| Resulting coordinates from a portal teleport are limited to ±value. Usually 29999984.
  |  
+
|-
 +
| Warning Time
 +
| VarInt
 +
| In seconds as set by <code>/worldborder warning time</code>
 +
|-
 +
| Warning Blocks
 +
| VarInt
 +
| In meters
 +
|-
 +
|rowspan="1"| 4: set warning time
 +
  | Warning Time
 +
  | VarInt
 +
  | In seconds as set by <code>/worldborder warning time</code>
 
  |-
 
  |-
  | 5: reset
+
  |rowspan="1"| 5: set warning blocks
  | ''no fields''
+
  | Warning Blocks
  | ''no fields''
+
  | VarInt
  |  
+
  | In meters
 
  |}
 
  |}
  
“Hide” makes the title disappear, but if you run times again the same title will appear. “Reset” erases the text.
+
The Notchian client determines how solid to display the warning by comparing to whichever is higher, the warning distance or whichever is lower, the distance from the current diameter to the target diameter or the place the border will be after warningTime seconds. In pseudocode:
 +
 
 +
<syntaxhighlight lang="java">
 +
distance = max(min(resizeSpeed * 1000 * warningTime, abs(targetDiameter - currentDiameter)), warningDistance);
 +
if (playerDistance < distance) {
 +
    warning = 1.0 - playerDistance / distance;
 +
} else {
 +
    warning = 0.0;
 +
}
 +
</syntaxhighlight>
 +
 
 +
==== Camera ====
  
The title is visible on screen for Fade In + Stay + Fade Out ticks.
+
Sets the entity that the player renders from. This is normally used when the player left-clicks an entity while in spectator mode.
  
==== Sound Effect ====
+
The player's camera will move with the entity and look where it is looking. The entity is often another player, but can be any type of entity.  The player is unable to move this entity (move packets will act as if they are coming from the other entity).
  
This packet is used to play a number of hardcoded sound events. For custom sounds, use [[#Named Sound Effect|Named Sound Effect]] ([[#Play|Play]], 0x19, clientbound).
+
If the given entity is not loaded by the player, this packet is ignored.  To return control to the player, send this packet with their entity ID.
  
{{Warning|Numeric sound effect IDs are liable to change between versions}}
+
The Notchian server resets this (sends it back to the default entity) whenever the spectated entity is killed or the player sneaks, but only if they were spectating an entity. It also sends this packet whenever the player switches out of spectator mode (even if they weren't spectating an entity).
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,749: Line 3,918:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="7"| 0x48
+
  |rowspan="1"| 0x3F
  |rowspan="7"| Play
+
  |rowspan="1"| Play
  |rowspan="7"| Client
+
  |rowspan="1"| Client
  | Sound ID
+
  | Camera ID
 
  | VarInt
 
  | VarInt
  | ID of hardcoded sound event ([http://pokechu22.github.io/Burger/1.12.html#sounds events] as of 1.12.0)
+
  | ID of the entity to set the client's camera to
|-
+
  |}
| Sound Category
+
 
| VarInt Enum
+
The notchian also loads certain shaders for given entities:
| The category that this sound will be played from ([https://gist.github.com/konwboj/7c0c380d3923443e9d55 current categories])
 
|-
 
| Effect Position X
 
| Int
 
| Effect X multiplied by 8 ([[Data types#Fixed-point numbers|fixed-point number]] with only 3 bits dedicated to the fractional part)
 
|-
 
| Effect Position Y
 
| Int
 
| Effect Y multiplied by 8 ([[Data types#Fixed-point numbers|fixed-point number]] with only 3 bits dedicated to the fractional part)
 
|-
 
| Effect Position Z
 
| Int
 
| Effect Z multiplied by 8 ([[Data types#Fixed-point numbers|fixed-point number]] with only 3 bits dedicated to the fractional part)
 
|-
 
  | Volume
 
| Float
 
| 1.0 is 100%, capped between 0.0 and 1.0 by Notchian clients
 
|-
 
| Pitch
 
| Float
 
| Float between 0.5 and 2.0 by Notchian clients
 
  
|}
+
* Creeper &rarr; <code>shaders/post/creeper.json</code>
 +
* Spider (and cave spider) &rarr; <code>shaders/post/spider.json</code>
 +
* Enderman &rarr; <code>shaders/post/invert.json</code>
 +
* Anything else &rarr; the current shader is unloaded
  
==== Player List Header And Footer ====
+
==== Held Item Change (clientbound) ====
  
This packet may be used by custom servers to display additional information above/below the player list. It is never sent by the Notchian server.
+
Sent to change the player's slot selection.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,794: Line 3,945:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x49
+
  |rowspan="1"| 0x40
  |rowspan="2"| Play
+
  |rowspan="1"| Play
  |rowspan="2"| Client
+
  |rowspan="1"| Client
  | Header
+
  | Slot
  | [[Chat]]
+
  | Byte
  | To remove the header, send a empty translatable component: {"translate":""}
+
  | The slot which the player has selected (0–8)
|-
 
| Footer
 
| [[Chat]]
 
| To remove the footer, send a empty translatable component: {"translate":""}
 
 
  |}
 
  |}
  
==== Collect Item ====
+
==== Update View Position ====
 +
 
 +
{{Need Info|Why is this even needed?  Is there a better name for it?  My guess is that it's something to do with logical behavior with latency, but it still seems weird.}}
 +
 
 +
Updates the client's location.  This is used to determine what chunks should remain loaded and if a chunk load should be ignored; chunks outside of the view distance may be unloaded.
  
Sent by the server when someone picks up an item lying on the ground — its sole purpose appears to be the animation of the item flying towards you. It doesn't destroy the entity in the client memory, and it doesn't add it to your inventory. The server only checks for items to be picked up after each [[#Player Position|Player Position]] (and [[#Player Position And Look|Player Position And Look]]) packet sent by the client.
+
Sent whenever the player moves across a chunk border horizontally, and also (according to testing) for any integer change in the vertical axis, even if it doesn't go across a chunk section border.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,818: Line 3,969:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="3"| 0x4A
+
  |rowspan="2"| 0x41
  |rowspan="3"| Play
+
  |rowspan="2"| Play
  |rowspan="3"| Client
+
  |rowspan="2"| Client
  | Collected Entity ID
+
  | Chunk X
 
  | VarInt
 
  | VarInt
  |  
+
  | Chunk X coordinate of the player's position
  |-  
+
  |-
  | Collector Entity ID
+
  | Chunk Z
| VarInt
 
|
 
|-
 
| Pickup Item Count
 
 
  | VarInt
 
  | VarInt
  | Seems to be 1 for XP orbs, otherwise the number of items in the stack.
+
  | Chunk Z coordinate of the player's position
 
  |}
 
  |}
  
==== Entity Teleport ====
+
==== Update View Distance ====
  
This packet is sent by the server when an entity moves more than 4 blocks.
+
Sent by the integrated singleplayer server when changing render distance.  Does not appear to be used by the dedicated server, as <code>view-distance</code> in server.properties cannot be changed at runtime.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,846: Line 3,993:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="7"| 0x4B
+
  |rowspan="1"| 0x42
  |rowspan="7"| Play
+
  |rowspan="1"| Play
  |rowspan="7"| Client
+
  |rowspan="1"| Client
  | Entity ID
+
  | View Distance
 
  | VarInt
 
  | VarInt
  |  
+
  | Render distance (2-32)
 +
|}
 +
 
 +
==== Display Scoreboard ====
 +
 
 +
This is sent to the client when it should display a scoreboard.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | X
+
  |rowspan="2"| 0x43
  | Double
+
|rowspan="2"| Play
  |  
+
|rowspan="2"| Client
 +
| Position
 +
  | Byte
 +
  | The position of the scoreboard. 0: list, 1: sidebar, 2: below name, 3 - 18: team specific sidebar, indexed as 3 + team color.
 
  |-
 
  |-
  | Y
+
  | Score Name
  | Double
+
  | String (16)
  |  
+
  | The unique name for the scoreboard to be displayed.
 +
|}
 +
 
 +
==== Entity Metadata ====
 +
 
 +
Updates one or more [[Entities#Entity Metadata Format|metadata]] properties for an existing entity. Any properties not included in the Metadata field are left unchanged.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | Z
+
  |rowspan="2"| 0x44
  | Double
+
|rowspan="2"| Play
 +
|rowspan="2"| Client
 +
| Entity ID
 +
  | VarInt
 
  |  
 
  |  
 
  |-
 
  |-
  | Yaw
+
  | Metadata
  | Angle
+
  | [[Entities#Entity Metadata Format|Entity Metadata]]
| New angle, not a delta
 
|-
 
| Pitch
 
| Angle
 
| New angle, not a delta
 
|-
 
| On Ground
 
| Boolean
 
 
  |  
 
  |  
 
  |}
 
  |}
  
==== Advancements ====
+
==== Attach Entity ====
 +
 
 +
This packet is sent when an entity has been {{Minecraft Wiki|Lead|leashed}} to another entity.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 3,884: Line 4,057:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  !colspan="2"| Field Name
+
  ! Field Name
  !colspan="2"| Field Type
+
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="9"| 0x4C
+
  |rowspan="2"| 0x45
  |rowspan="9"| Play
+
  |rowspan="2"| Play
  |rowspan="9"| Client
+
  |rowspan="2"| Client
  |colspan="2"| Reset/Clear
+
  | Attached Entity ID
  |colspan="2"| Boolean
+
  | Int
  | Whether to reset/clear the current advancements
+
  | Attached entity's EID
 
  |-
 
  |-
  |colspan="2"| Mapping size
+
  | Holding Entity ID
  |colspan="2"| VarInt
+
| Int
  | Size of the following array
+
| ID of the entity holding the lead. Set to -1 to detach.
 +
  |}
 +
 
 +
==== Entity Velocity ====
 +
 
 +
Velocity is believed to be in units of 1/8000 of a block per server tick (50ms); for example, -1343 would move (-1343 / 8000) = −0.167875 blocks per tick (or −3,3575 blocks per second).
 +
 
 +
{| class="wikitable"
 +
  ! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  |rowspan="2"| Advancement mapping
+
  |rowspan="4"| 0x46
  | Key
+
  |rowspan="4"| Play
  |rowspan="2"| Array
+
  |rowspan="4"| Client
  | Identifier
+
| Entity ID
  | The identifier of the advancement
+
  | VarInt
 +
  |  
 
  |-
 
  |-
  | Value
+
  | Velocity X
  | Advancement
+
  | Short
  | See below
+
  | Velocity on the X axis
 
  |-
 
  |-
  |colspan="2"| List size
+
  | Velocity Y
  |colspan="2"| VarInt
+
  | Short
  | Size of the following array
+
  | Velocity on the Y axis
 
  |-
 
  |-
  |colspan="2"| Identifiers
+
  | Velocity Z
|colspan="2"| Array of Identifier
+
  | Short
| The identifiers of the advancements that should be removed
+
  | Velocity on the Z axis
|-
 
|colspan="2"| Progress size
 
|colspan="2"| VarInt
 
| Size of the following array
 
|-
 
  |rowspan="2"| Progress mapping
 
  | Key
 
|rowspan="2"| Array
 
| Identifier
 
| The identifier of the advancement
 
|-
 
| Value
 
| Advancement progress
 
| See below
 
 
  |}
 
  |}
  
Advancement structure:
+
==== Entity Equipment ====
  
 
{| class="wikitable"
 
{| class="wikitable"
  !colspan="2"| Field Name
+
  ! Packet ID
  !colspan="2"| Field Type
+
! State
 +
! Bound To
 +
! Field Name
 +
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |colspan="2"| Has parent
+
  |rowspan="3"| 0x47
  |colspan="2"| Boolean
+
  |rowspan="3"| Play
  | Indicates whether the next field exists.
+
  |rowspan="3"| Client
 +
| Entity ID
 +
| VarInt
 +
| Entity's EID
 
  |-
 
  |-
  |colspan="2"| Parent id
+
  | Slot
  |colspan="2"| Optional Identifier
+
  | VarInt Enum
  | The identifier of the parent advancement.
+
  | Equipment slot. 0: main hand, 1: off hand, 2–5: armor slot (2: boots, 3: leggings, 4: chestplate, 5: helmet)
 
  |-
 
  |-
  |colspan="2"| Has display
+
  | Item
|colspan="2"| Boolean
+
  | [[Slot Data|Slot]]
| Indicates whether the next field exists
+
  |  
|-
 
|colspan="2"| Display data
 
|colspan="2"| Optional advancement display
 
| See below.
 
|-
 
|colspan="2"| Number of criteria
 
|colspan="2"| VarInt
 
| Size of the following array
 
|-
 
|rowspan="2"| Criteria
 
| Key
 
|rowspan="2"| Array
 
| Identifier
 
| The identifier of the criterion
 
|-
 
| Value
 
| '''Void'''
 
| There is ''no'' content written here.  Perhaps this will be expanded in the future?
 
|-
 
|colspan="2"| Array length
 
|colspan="2"| VarInt
 
| Number of arrays in the following array
 
|-
 
|rowspan="2"| Requirements
 
  | Array length 2
 
|rowspan="2"| Array
 
| VarInt
 
| Number of elements in the following array
 
|-
 
| Requirement
 
| Array of String
 
  | Array of required criteria
 
 
  |}
 
  |}
  
Advancement display:
+
==== Set Experience ====
 +
 
 +
Sent by the server when the client should change experience levels.
  
 
{| class="wikitable"
 
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 
  ! Field Name
 
  ! Field Name
 
  ! Field Type
 
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  | Title
+
  |rowspan="3"| 0x48
  | Chat
+
|rowspan="3"| Play
  |
+
|rowspan="3"| Client
 +
| Experience bar
 +
  | Float
 +
  | Between 0 and 1
 
  |-
 
  |-
  | Description
+
  | Level
| Chat
+
  | VarInt
|
 
|-
 
| Icon
 
| [[Slot]]
 
|
 
|-
 
| Frame type
 
  | VarInt enum
 
| 0 = <code>task</code>, 1 = <code>challenge</code>, 2 = <code>goal</code>
 
|-
 
| Flags
 
| Integer
 
| 0x1: has background texture; 0x2: <code>show_toast</code>; 0x4: <code>hidden</code>
 
|-
 
| Background texture
 
| Optional Identifier
 
| Background texture location.  Only if flags indicates it.
 
|-
 
| X coord
 
| Float
 
 
  |  
 
  |  
 
  |-
 
  |-
  | Y coord
+
  | Total Experience
  | Float
+
  | VarInt
  |  
+
  | See {{Minecraft Wiki|Experience#Leveling up}} on the Minecraft Wiki for Total Experience to Level conversion
 
  |}
 
  |}
  
Advancement progress:
+
==== Update Health ====
 +
 
 +
Sent by the server to update/set the health of the player it is sent to.
 +
 
 +
Food {{Minecraft Wiki|Food#Hunger vs. Saturation|saturation}} acts as a food “overcharge”. Food values will not decrease while the saturation is over zero. Players logging in automatically get a saturation of 5.0. Eating food increases the saturation as well as the food bar.
  
 
{| class="wikitable"
 
{| class="wikitable"
  !colspan="2"| Field Name
+
  ! Packet ID
  !colspan="2"| Field Type
+
! State
 +
! Bound To
 +
! Field Name
 +
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |colspan="2"| Size
+
  |rowspan="3"| 0x49
  |colspan="2"| VarInt
+
  |rowspan="3"| Play
  | Size of the following array
+
  |rowspan="3"| Client
 +
| Health
 +
| Float
 +
| 0 or less = dead, 20 = full HP
 
  |-
 
  |-
  |rowspan="2"| Criteria
+
  | Food
| Criterion identifier
+
  | VarInt
  |rowspan="2"| Array
+
  | 0–20
  | Identifier
+
  |-  
| The identifier of the criterion.
+
  | Food Saturation
  |-
+
  | Float
  | Criterion progress
+
  | Seems to vary from 0.0 to 5.0 in integer increments
  | Criterion progress
 
  |
 
 
  |}
 
  |}
  
Criterion progress:
+
==== Scoreboard Objective ====
 +
 
 +
This is sent to the client when it should create a new {{Minecraft Wiki|scoreboard}} objective or remove one.
  
 
{| class="wikitable"
 
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 
  ! Field Name
 
  ! Field Name
 
  ! Field Type
 
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  | Achieved
+
  |rowspan="4"| 0x4A
  | Boolean
+
|rowspan="4"| Play
  | If true, next field is present
+
|rowspan="4"| Client
 +
| Objective Name
 +
| String (16)
 +
| An unique name for the objective
 +
|-
 +
| Mode
 +
| Byte
 +
| 0 to create the scoreboard. 1 to remove the scoreboard. 2 to update the display text.
 +
|-
 +
| Objective Value
 +
  | Optional Chat
 +
  | Only if mode is 0 or 2. The text to be displayed for the score
 
  |-
 
  |-
  | Date of achieving
+
  | Type
  | Optional Long
+
  | Optional VarInt enum
  | As returned by [https://docs.oracle.com/javase/6/docs/api/java/util/Date.html#getTime() <code>Date.getTime</code>]
+
  | Only if mode is 0 or 2. 0 = "integer", 1 = "hearts".
 
  |}
 
  |}
  
==== Entity Properties ====
+
==== Set Passengers ====
 
 
Sets {{Minecraft Wiki|Attribute|attributes}} on the given entity.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 4,070: Line 4,227:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  !colspan="2"| Field Name
+
  ! Field Name
  !colspan="2"| Field Type
+
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="6"| 0x4D
+
  |rowspan="3"| 0x4B
  |rowspan="6"| Play
+
  |rowspan="3"| Play
  |rowspan="6"| Client
+
  |rowspan="3"| Client
  |colspan="2"| Entity ID
+
  | Entity ID
  |colspan="2"| VarInt
+
  | VarInt
  |  
+
  | Vehicle's EID
 
  |-
 
  |-
  |colspan="2"| Number Of Properties
+
  | Passenger Count
|colspan="2"| Int
 
| Number of elements in the following array
 
|-
 
|rowspan="4"| Property
 
| Key
 
|rowspan="4"| Array
 
| String (64)
 
| See below
 
|-
 
| Value
 
| Double
 
| See below
 
|-
 
| Number Of Modifiers
 
 
  | VarInt
 
  | VarInt
 
  | Number of elements in the following array
 
  | Number of elements in the following array
 
  |-
 
  |-
  | Modifiers
+
  | Passengers
  | Array of Modifier Data
+
  | Array of VarInt
  | See {{Minecraft Wiki|Attribute#Modifiers}}. Modifier Data defined below.
+
  | EIDs of entity's passengers
 
  |}
 
  |}
  
Known Key values (see also {{Minecraft Wiki|Attribute#Modifiers}}):
+
==== Teams ====
 +
 
 +
Creates and updates teams.
  
 
{| class="wikitable"
 
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
!colspan="2"| Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  ! Key
+
  |rowspan="23"| 0x4C
  ! Default
+
  |rowspan="23"| Play
  ! Min
+
  |rowspan="23"| Client
  ! Max
+
  |colspan="2"| Team Name
  ! Label
+
  | String (16)
 +
| A unique name for the team. (Shared with scoreboard).
 +
|-
 +
|colspan="2"| Mode
 +
| Byte
 +
| Determines the layout of the remaining packet
 
  |-
 
  |-
  | generic.maxHealth
+
  |rowspan="9"| 0: create team
| 20.0
+
  | Team Display Name
  | 0.0
+
  | Chat
  | 1024.0
+
  |  
  | Max Health
 
 
  |-
 
  |-
  | generic.followRange
+
  | Friendly Flags
  | 32.0
+
  | Byte
  | 0.0
+
  | Bit mask. 0x01: Allow friendly fire, 0x02: can see invisible players on same team
| 2048.0
 
| Follow Range
 
 
  |-
 
  |-
  | generic.knockbackResistance
+
  | Name Tag Visibility
  | 0.0
+
  | String Enum (32)
  | 0.0
+
  | <code>always</code>, <code>hideForOtherTeams</code>, <code>hideForOwnTeam</code>, <code>never</code>
| 1.0
 
| Knockback Resistance
 
 
  |-
 
  |-
  | generic.movementSpeed
+
  | Collision Rule
  | 0.699999988079071
+
  | String Enum (32)
  | 0.0
+
  | <code>always</code>, <code>pushOtherTeams</code>, <code>pushOwnTeam</code>, <code>never</code>
| 1024.0
 
| Movement Speed
 
 
  |-
 
  |-
  | generic.attackDamage
+
  | Team Color
  | 2.0
+
  | VarInt enum
  | 0.0
+
  | Used to color the name of players on the team; see below
| 2048.0
 
| Attack Damage
 
 
  |-
 
  |-
  | generic.attackSpeed
+
  | Team Prefix
  | 4.0
+
  | Chat
  | 0.0
+
  | Displayed before the names of players that are part of this team
| 1024.0
 
| Attack Speed
 
 
  |-
 
  |-
  | generic.flyingSpeed
+
  | Team Suffix
  | 0.4000000059604645
+
  | Chat
  | 0.0
+
  | Displayed after the names of players that are part of this team
| 1024.0
 
| Flying Speed
 
 
  |-
 
  |-
  | horse.jumpStrength
+
  | Entity Count
  | 0.7
+
  | VarInt
  | 0.0
+
  | Number of elements in the following array
| 2.0
 
| Jump Strength
 
 
  |-
 
  |-
  | zombie.spawnReinforcements
+
  | Entities
  | 0.0
+
  | Array of String (40)
  | 0.0
+
  | Identifiers for the entities in this teamFor players, this is their username; for other entities, it is their UUID.
  | 1.0
 
| Spawn Reinforcements Chance
 
|}
 
 
 
''Modifier Data'' structure:
 
 
 
{| class="wikitable"
 
 
  |-
 
  |-
  ! Field Name
+
  | 1: remove team
  ! Field Type
+
  | ''no fields''
  ! Notes
+
  | ''no fields''
 +
|
 
  |-
 
  |-
  | UUID
+
  |rowspan="7"| 2: update team info
  | UUID
+
| Team Display Name
 +
  | Chat
 
  |  
 
  |  
 
  |-
 
  |-
  | Amount
+
  | Friendly Flags
| Double
 
| May be positive or negative
 
|-
 
| Operation
 
 
  | Byte
 
  | Byte
  | See below
+
  | Bit mask. 0x01: Allow friendly fire, 0x02: can see invisible entities on same team
|}
 
 
 
The operation controls how the base value of the modifier is changed.
 
 
 
* 0: Add/subtract amount
 
* 1: Add/subtract amount percent of the current value
 
* 2: Multiply by amount percent
 
 
 
All of the 0's are applied first, and then the 1's, and then the 2's.
 
 
 
==== Entity Effect ====
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="5"| 0x4E
+
  | Name Tag Visibility
|rowspan="5"| Play
+
  | String Enum (32)
|rowspan="5"| Client
+
  | <code>always</code>, <code>hideForOtherTeams</code>, <code>hideForOwnTeam</code>, <code>never</code>
| Entity ID
 
  | VarInt
 
  |  
 
 
  |-
 
  |-
  | Effect ID
+
  | Collision Rule
  | Byte
+
  | String Enum (32)
  | See {{Minecraft Wiki|Status effect#List of effects|this table}}
+
  | <code>always</code>, <code>pushOtherTeams</code>, <code>pushOwnTeam</code>, <code>never</code>
 
  |-
 
  |-
  | Amplifier
+
  | Team Color
  | Byte
+
  | VarInt enum
  | Notchian client displays effect level as Amplifier + 1
+
  | Used to color the name of players on the team; see below
 
  |-
 
  |-
  | Duration
+
  | Team Prefix
  | VarInt
+
  | Chat
  | Seconds
+
  | Displayed before the names of players that are part of this team
 
  |-
 
  |-
  | Flags
+
  | Team Suffix
  | Byte
+
  | Chat
  | Bit field, see below.
+
  | Displayed after the names of players that are part of this team
 +
|-
 +
|rowspan="2"| 3: add players to team
 +
| Entity Count
 +
| VarInt
 +
| Number of elements in the following array
 +
|-
 +
| Entities
 +
| Array of String (40)
 +
| Identifiers for the entities added.  For players, this is their username; for other entities, it is their UUID.
 +
|-
 +
|rowspan="2"| 4: remove players from team
 +
| Entity Count
 +
| VarInt
 +
| Number of elements in the following array
 +
|-
 +
| Entities
 +
| Array of String (40)
 +
| Identifiers for the entities removed.  For players, this is their username; for other entities, it is their UUID.
 
  |}
 
  |}
  
Within flags:
+
Team Color: The color of a team defines how the names of the team members are visualized; any formatting code can be used. The following table lists all the possible values.
  
* 0x01: Is ambient - was the effect spawned from a beacon? All beacon-generated effects are ambient. Ambient effects use a different icon in the HUD (blue border rather than gray).  If all effects on an entity are ambient, the [[Entities#Living|"Is potion effect ambient" living metadata field]] should be set to trueUsually should not be enabled.
+
{| class="wikitable"
* 0x02: Show particles - should all particles from this effect be hidden? Effects with particles hidden are not included in the calculation of the effect color, and are not rendered on the HUD (but are still rendered within the inventory). Usually should be enabled.
+
! ID
 +
! Formatting
 +
|-
 +
  | 0-15
 +
  | Color formatting, same values as [[Chat]] colors.
 +
|-
 +
| 16
 +
| Obfuscated
 +
|-
 +
| 17
 +
| Bold
 +
|-
 +
  | 18
 +
| Strikethrough
 +
|-
 +
| 19
 +
| Underlined
 +
|-
 +
| 20
 +
| Italic
 +
|-
 +
  | 21
 +
| Reset
 +
  |}
  
=== Serverbound ===
+
==== Update Score ====
  
==== Teleport Confirm ====
+
This is sent to the client when it should update a scoreboard item.  
 
 
Sent by client as confirmation of [[#Player Position And Look (clientbound)|Player Position And Look]] ([[#Play|Play]], 0x2E, clientbound).
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 4,251: Line 4,400:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  | 0x00
+
  |rowspan="4"| 0x4D
  | Play
+
  |rowspan="4"| Play
  | Server
+
  |rowspan="4"| Client
  | Teleport ID
+
  | Entity Name
  | VarInt
+
  | String (40)
  | The ID given by the [[#Player Position And Look (clientbound)|Player Position And Look]] packet
+
  | The entity whose score this is.  For players, this is their username; for other entities, it is their UUID.
 +
|-
 +
| Action
 +
| Byte
 +
| 0 to create/update an item. 1 to remove an item.
 +
|-
 +
| Objective Name
 +
| String (16)
 +
| The name of the objective the score belongs to
 +
|-
 +
| Value
 +
| Optional VarInt
 +
| The score to be displayed next to the entry. Only sent when Action does not equal 1.
 
  |}
 
  |}
  
==== Prepare Crafting Grid ====
+
==== Spawn Position ====
 +
 
 +
Sent by the server after login to specify the coordinates of the spawn point (the point at which players spawn at, and which the compass points to). It can be sent at any time to update the point compasses point at.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 4,265: Line 4,428:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  !colspan="2"| Field Name
+
  ! Field Name
  !colspan="2"| Field Type
+
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="12"| 0x01
+
  |rowspan="1"| 0x4E
  |rowspan="12"| Play
+
  |rowspan="1"| Play
  |rowspan="12"| Server
+
  |rowspan="1"| Client
  |colspan="2"| Window ID
+
  | Location
  |colspan="2"| Byte
+
  | Position
  | The window id.
+
  | Spawn location
  |-
+
  |}
|colspan="2"| Action number
+
 
|colspan="2"| Short
+
==== Time Update ====
| The transaction number. Will be send to the client in a Confirm Transaction packet.
+
 
|-
+
Time is based on ticks, where 20 ticks happen every second. There are 24000 ticks in a day, making Minecraft days exactly 20 minutes long.
|colspan="2"| Array size
 
|colspan="2"| Short
 
| Number of elements in the following array
 
|-
 
|rowspan="3"| Return Entry
 
| Item
 
|rowspan="3"| Array
 
| Slot
 
| The item stack that will be put in the inventory slot
 
|-
 
| Crafting Slot
 
| Byte
 
| The crafting slot index in the active container
 
|-
 
| Player Slot
 
| Byte
 
| The player slot index in the player inventory
 
|-
 
|colspan="2"| Array Size
 
|colspan="2"| Short
 
| Number of elements in the following array
 
|-
 
|rowspan="3"| Prepare Entry
 
| Item
 
|rowspan="3"| Array
 
| Slot
 
| The item stack that will be put in the crafting slot
 
|-
 
| Crafting Slot
 
| Byte
 
| The crafting slot index in the active container
 
|-
 
| Player Slot
 
| Byte
 
| The player slot index in the player inventory
 
|}
 
  
This packet is send when a player clicks a recipe in the crafting book that is craftable (white border).
+
The time of day is based on the timestamp modulo 24000. 0 is sunrise, 6000 is noon, 12000 is sunset, and 18000 is midnight.
  
1. Return Entries:
+
The default SMP server increments the time by <code>20</code> every second.
* All the items on the crafting slot are set to null/empty.
 
* Every entry item stack will be added to the player inventory, to the specific player slot.
 
 
 
2. Prepare Entries:
 
* All the items on the player inventory slots their quantity is decreased by 1.
 
* Every entry item stack will be put in the proper crafting grid slot.
 
 
 
The server will send a Confirm Transaction packet back to the client with the provided transaction id.
 
 
 
 
 
==== Tab-Complete (serverbound) ====
 
 
 
Sent when the user presses ''tab'' while writing text.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 4,342: Line 4,456:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="4"| 0x02
+
  |rowspan="2"| 0x4F
  |rowspan="4"| Play
+
  |rowspan="2"| Play
  |rowspan="4"| Server
+
  |rowspan="2"| Client
  | Text
+
  | World Age
  | String (32767)
+
  | Long
  | All text behind the cursor (e.g. to the left of the cursor in left-to-right languages like English)
+
  | In ticks; not changed by server commands
 
  |-
 
  |-
  | Assume Command
+
  | Time of day
  | Boolean
+
  | Long
  | If true, the server will parse Text as a command even if it doesn't start with a <code>/</code>. Used in the command block GUI.
+
  | The world (or region) time, in ticks. If negative the sun will stop moving at the Math.abs of the time
|-
 
| Has Position
 
| Boolean
 
|
 
|-
 
| Looked At Block
 
| Optional Position
 
| The position of the block being looked at. Only sent if Has Position is true.
 
 
  |}
 
  |}
  
==== Chat Message (serverbound) ====
+
==== Title ====
 
 
Used to send a chat message to the server.  The message may not be longer than 256 characters or else the server will kick the client.
 
 
 
If the message starts with a <code>/</code>, the server will attempt to interpret it as a command.  Otherwise, the server will broadcast the same chat message to all players on the server (including the player that sent the message), prepended with player's name.  Specifically, it will respond with a translate [[chat]] component, "<code>chat.type.text</code>" with the first parameter set to the display name of the player (including some chat component logic to support clicking the name to send a PM) and the second parameter set to the message.  See [[Chat#Processing chat|processing chat]] for more information.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 4,372: Line 4,474:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  ! Field Name
+
  !colspan="2"| Field Name
 
  ! Field Type
 
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="1"| 0x03
+
  |rowspan="10"| 0x50
  |rowspan="1"| Play
+
  |rowspan="10"| Play
  |rowspan="1"| Server
+
  |rowspan="10"| Client
| Message
+
  |colspan="2"| Action
| String (256)
 
| The client sends the raw input, not a [[Chat]] component
 
|}
 
 
 
==== Client Status ====
 
 
 
Sent when the client is ready to complete login and when the client is ready to respawn after death.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
  |-
 
|rowspan="1"| 0x04
 
|rowspan="1"| Play
 
|rowspan="1"| Server
 
| Action ID
 
 
  | VarInt Enum
 
  | VarInt Enum
  | See below
+
  |  
|}
 
 
 
''Action ID'' values:
 
 
 
{| class="wikitable"
 
 
  |-
 
  |-
! Action ID
 
 
  ! Action
 
  ! Action
 +
! Field Name
 +
!
 +
!
 
  |-
 
  |-
  | 0
+
  | 0: set title
  | Perform respawn
+
| Title Text
 +
| [[Chat]]
 +
  |  
 
  |-
 
  |-
  | 1
+
  | 1: set subtitle
  | Request stats
+
| Subtitle Text
  |}
+
| [[Chat]]
 
+
|
==== Client Settings ====
+
|-
 +
| 2: set action bar
 +
| Action bar text
 +
| [[Chat]]
 +
| Displays a message above the hotbar (the same as position 2 in [[#Chat Message (clientbound)|Chat Message (clientbound)]], except that it correctly renders formatted chat. See [https://bugs.mojang.com/browse/MC-119145 MC-119145] for more information.)
 +
|-
 +
|rowspan="3"| 3: set times and display
 +
| Fade In
 +
| Int
 +
| Ticks to spend fading in
 +
|-
 +
| Stay
 +
| Int
 +
| Ticks to keep the title displayed
 +
|-
 +
| Fade Out
 +
| Int
 +
| Ticks to spend out, not when to start fading out
 +
|-
 +
| 4: hide
 +
| ''no fields''
 +
| ''no fields''
 +
|
 +
|-
 +
| 5: reset
 +
| ''no fields''
 +
| ''no fields''
 +
  |  
 +
  |}
 +
 
 +
“Hide” makes the title disappear, but if you run times again the same title will appear. “Reset” erases the text.
 +
 
 +
The title is visible on screen for Fade In + Stay + Fade Out ticks.
 +
 
 +
==== Entity Sound Effect ====
  
Sent when the player connects, or when settings are changed.
+
Plays a sound effect from an entity.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 4,430: Line 4,545:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="6"| 0x05
+
  |rowspan="5"| 0x51
  |rowspan="6"| Play
+
  |rowspan="5"| Play
  |rowspan="6"| Server
+
  |rowspan="5"| Client
  | Locale
+
  | Sound ID
  | String (16)
+
  | VarInt
  | e.g. en_GB
+
  | ID of hardcoded sound event ([https://pokechu22.github.io/Burger/1.15.2.html#sounds events] as of 1.15.2)
 
  |-
 
  |-
  | View Distance
+
  | Sound Category
  | Byte
+
  | VarInt Enum
  | Client-side render distance, in chunks
+
  | The category that this sound will be played from ([https://gist.github.com/konwboj/7c0c380d3923443e9d55 current categories])
 
  |-
 
  |-
  | Chat Mode
+
  | Entity ID
  | VarInt Enum
+
  | VarInt
  | 0: enabled, 1: commands only, 2: hidden.  See [[Chat#Processing chat|processing chat]] for more information.
+
  |
 
  |-
 
  |-
  | Chat Colors
+
  | Volume
  | Boolean
+
  | Float
  | “Colors” multiplayer setting
+
  | 1.0 is 100%, capped between 0.0 and 1.0 by Notchian clients
 
  |-
 
  |-
  | Displayed Skin Parts
+
  | Pitch
  | Unsigned Byte
+
  | Float
| Bit mask, see below
+
  | Float between 0.5 and 2.0 by Notchian clients
|-
 
| Main Hand
 
| VarInt Enum
 
  | 0: Left, 1: Right
 
 
  |}
 
  |}
  
''Displayed Skin Parts'' flags:
+
==== Sound Effect ====
 
 
* Bit 0 (0x01): Cape enabled
 
* Bit 1 (0x02): Jacket enabled
 
* Bit 2 (0x04): Left Sleeve enabled
 
* Bit 3 (0x08): Right Sleeve enabled
 
* Bit 4 (0x10): Left Pants Leg enabled
 
* Bit 5 (0x20): Right Pants Leg enabled
 
* Bit 6 (0x40): Hat enabled
 
  
The most significant bit (bit 7, 0x80) appears to be unused.
+
This packet is used to play a number of hardcoded sound events. For custom sounds, use [[#Named Sound Effect|Named Sound Effect]].
  
==== Confirm Transaction (serverbound) ====
+
{{Warning|Numeric sound effect IDs are liable to change between versions}}
 
 
If a transaction sent by the client was not accepted, the server will reply with a [[#Confirm Transaction (clientbound)|Confirm Transaction (clientbound)]] packet with the Accepted field set to false. When this happens, the client must send this packet to apologize (as with movement), otherwise the server ignores any successive transactions.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 4,482: Line 4,583:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="3"| 0x06
+
  |rowspan="7"| 0x52
  |rowspan="3"| Play
+
  |rowspan="7"| Play
  |rowspan="3"| Server
+
  |rowspan="7"| Client
  | Window ID
+
  | Sound ID
  | Byte
+
  | VarInt
  | The ID of the window that the action occurred in
+
  | ID of hardcoded sound event ([https://pokechu22.github.io/Burger/1.15.2.html#sounds events] as of 1.15.2)
 
  |-
 
  |-
  | Action Number
+
  | Sound Category
  | Short
+
  | VarInt Enum
  | Every action that is to be accepted has a unique number. This number is an incrementing integer (starting at 1) with separate counts for each window ID.
+
  | The category that this sound will be played from ([https://gist.github.com/konwboj/7c0c380d3923443e9d55 current categories])
 +
|-
 +
| Effect Position X
 +
| Int
 +
| Effect X multiplied by 8 ([[Data types#Fixed-point numbers|fixed-point number]] with only 3 bits dedicated to the fractional part)
 +
|-
 +
| Effect Position Y
 +
| Int
 +
| Effect Y multiplied by 8 ([[Data types#Fixed-point numbers|fixed-point number]] with only 3 bits dedicated to the fractional part)
 +
|-
 +
| Effect Position Z
 +
| Int
 +
| Effect Z multiplied by 8 ([[Data types#Fixed-point numbers|fixed-point number]] with only 3 bits dedicated to the fractional part)
 +
|-
 +
| Volume
 +
| Float
 +
| 1.0 is 100%, capped between 0.0 and 1.0 by Notchian clients
 
  |-
 
  |-
  | Accepted
+
  | Pitch
  | Boolean
+
  | Float
  | Whether the action was accepted
+
  | Float between 0.5 and 2.0 by Notchian clients
 
  |}
 
  |}
  
==== Enchant Item ====
+
==== Stop Sound ====
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 4,508: Line 4,625:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x07
+
  |rowspan="3"| 0x53
  |rowspan="2"| Play
+
  |rowspan="3"| Play
  |rowspan="2"| Server
+
  |rowspan="3"| Client
  | Window ID
+
  | Flags
 
  | Byte
 
  | Byte
  | The ID of the enchantment table window sent by [[#Open Window|Open Window]]
+
  | Controls which fields are present.
 +
|-
 +
| Source
 +
| Optional VarInt enum
 +
| Only if flags is 3 or 1 (bit mask 0x1).  See below.  If not present, then sounds from all sources are cleared.
 
  |-
 
  |-
  | Enchantment
+
  | Sound
  | Byte
+
  | Optional Identifier
  | The position of the enchantment on the enchantment table window, starting with 0 as the topmost one
+
  | Only if flags is 2 or 3 (bit mask 0x2).  A sound effect name, see [[#Named Sound Effect|Named Sound Effect]].  If not present, then all sounds are cleared.
 
  |}
 
  |}
  
==== Click Window ====
+
Categories:
 
 
This packet is sent by the player when it clicks on a slot in a window.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
  ! Packet ID
+
  ! Name !! Value
! State
+
  |-
  ! Bound To
+
  | master || 0
  ! Field Name
+
  |-
  ! Field Type
+
  | music || 1
  ! Notes
 
 
  |-
 
  |-
  |rowspan="6"| 0x08
+
  | record || 2
  |rowspan="6"| Play
+
  |-
  |rowspan="6"| Server
+
  | weather || 3
  | Window ID
+
  |-
  | Unsigned Byte
+
  | block || 4
| The ID of the window which was clicked. 0 for player inventory.
 
 
  |-
 
  |-
  | Slot
+
  | hostile || 5
| Short
 
| The clicked slot number, see below
 
 
  |-
 
  |-
  | Button
+
  | neutral || 6
| Byte
 
| The button used in the click, see below
 
 
  |-
 
  |-
  | Action Number
+
  | player || 7
| Short
 
| A unique number for the action, implemented by Notchian as a counter, starting at 1 (different counter for every window ID). Used by the server to send back a [[#Confirm Transaction (clientbound)|Confirm Transaction (clientbound)]].
 
 
  |-
 
  |-
  | Mode
+
  | ambient || 8
| VarInt Enum
 
| Inventory operation mode, see below
 
 
  |-
 
  |-
  | Clicked item
+
  | voice || 9
| [[Slot Data|Slot]]
 
| The clicked slot. Has to be empty (item ID = -1) for drop mode.
 
 
  |}
 
  |}
  
See [[Inventory]] for further information about how slots are indexed.
+
==== Player List Header And Footer ====
  
When right-clicking on a stack of items, half the stack will be picked up and half left in the slot. If the stack is an odd number, the half left in the slot will be smaller of the amounts.
+
This packet may be used by custom servers to display additional information above/below the player list. It is never sent by the Notchian server.
 
 
The distinct type of click performed by the client is determined by the combination of the Mode and Button fields.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
  ! Mode
+
  ! Packet ID
  ! Button
+
  ! State
  ! Slot
+
  ! Bound To
  ! Trigger
+
  ! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  !rowspan="2"| 0
+
  |rowspan="2"| 0x54
  | 0
+
  |rowspan="2"| Play
  | Normal
+
  |rowspan="2"| Client
  | Left mouse click
+
| Header
 +
  | [[Chat]]
 +
| To remove the header, send a empty translatable component: {"translate":""}
 
  |-
 
  |-
  | 1
+
  | Footer
  | Normal
+
  | [[Chat]]
  | Right mouse click
+
  | To remove the footer, send a empty translatable component: {"translate":""}
 +
|}
 +
 
 +
==== NBT Query Response ====
 +
 
 +
Sent in response to [[#Query Block NBT|Query Block NBT]] or [[#Query Entity NBT|Query Entity NBT]].
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  !rowspan="2"| 1
+
  |rowspan="2"| 0x55
  | 0
+
|rowspan="2"| Play
  | Normal
+
|rowspan="2"| Client
  | Shift + left mouse click
+
  | Transaction ID
 +
  | VarInt
 +
  | Can be compared to the one sent in the original query packet.
 
  |-
 
  |-
  | 1
+
  | NBT
  | Normal
+
  | [[NBT|NBT Tag]]
  | Shift + right mouse click ''(identical behavior)''
+
| The NBT of the block or entity.  May be a TAG_END (0) in which case no NBT is present.
 +
  |}
 +
 
 +
==== Collect Item ====
 +
 
 +
Sent by the server when someone picks up an item lying on the ground — its sole purpose appears to be the animation of the item flying towards you. It doesn't destroy the entity in the client memory, and it doesn't add it to your inventory. The server only checks for items to be picked up after each [[#Player Position|Player Position]] (and [[#Player Position And Look|Player Position And Look]]) packet sent by the client. The collector entity can be any entity; it does not have to be a player. The collected entity also can be any entity, but the Notchian server only uses this for items, experience orbs, and the different varieties of arrows.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  !rowspan="5"| 2
+
  |rowspan="3"| 0x56
  | 0
+
|rowspan="3"| Play
  | Normal
+
|rowspan="3"| Client
  | Number key 1
+
  | Collected Entity ID
  |-
+
  | VarInt
  | 1
+
|
  | Normal
+
|-
  | Number key 2
+
| Collector Entity ID
 +
| VarInt
 +
  |  
 +
  |-  
 +
  | Pickup Item Count
 +
| VarInt
 +
| Seems to be 1 for XP orbs, otherwise the number of items in the stack.
 +
  |}
 +
 
 +
==== Entity Teleport ====
 +
 
 +
This packet is sent by the server when an entity moves more than 8 blocks.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
  ! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | 2
+
  |rowspan="7"| 0x57
  | Normal
+
|rowspan="7"| Play
  | Number key 3
+
|rowspan="7"| Client
 +
| Entity ID
 +
  | VarInt
 +
  |  
 
  |-
 
  |-
  |
+
  | X
  |
+
  | Double
  |
+
  |  
 
  |-
 
  |-
  | 8
+
  | Y
  | Normal
+
  | Double
  | Number key 9
+
  |  
 
  |-
 
  |-
  !rowspan="1"| 3
+
  | Z
  | 2
+
  | Double
  | Normal
+
  |  
| Middle click, only defined for creative players in non-player inventories.
 
 
  |-
 
  |-
  !rowspan="4"| 4
+
  | Yaw
  | 0
+
  | Angle
  | Normal*
+
  | New angle, not a delta
| Drop key (Q) (* Clicked item is different, see above)
 
 
  |-
 
  |-
  | 1
+
  | Pitch
  | Normal*
+
  | Angle
  | Ctrl + Drop key (Ctrl-Q) ''(drops full stack)''
+
  | New angle, not a delta
 
  |-
 
  |-
  | 0
+
  | On Ground
  | -999
+
  | Boolean
  | Left click outside inventory holding nothing ''(no-op)''
+
  |  
 +
|}
 +
 
 +
==== Advancements ====
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
!colspan="2"| Field Name
 +
!colspan="2"| Field Type
 +
! Notes
 
  |-
 
  |-
  | 1
+
  |rowspan="9"| 0x58
  | -999
+
|rowspan="9"| Play
  | Right click outside inventory holding nothing ''(no-op)''
+
|rowspan="9"| Client
 +
  |colspan="2"| Reset/Clear
 +
|colspan="2"| Boolean
 +
  | Whether to reset/clear the current advancements
 
  |-
 
  |-
  !rowspan="9"| 5
+
  |colspan="2"| Mapping size
  | 0
+
  |colspan="2"| VarInt
| -999
+
  | Size of the following array
  | Starting left mouse drag
 
 
  |-
 
  |-
  | 4
+
  |rowspan="2"| Advancement mapping
  | -999
+
| Key
  | Starting right mouse drag
+
|rowspan="2"| Array
 +
  | Identifier
 +
  | The identifier of the advancement
 
  |-
 
  |-
  | 8
+
  | Value
  | -999
+
  | Advancement
  | Starting middle mouse drag, only defined for creative players in non-player inventories.  (Note: the vanilla client will still incorrectly send this for non-creative players - see [https://bugs.mojang.com/browse/MC-46584 MC-46584])
+
  | See below
 
  |-
 
  |-
  | 1
+
  |colspan="2"| List size
  | Normal
+
  |colspan="2"| VarInt
  | Add slot for left-mouse drag
+
  | Size of the following array
 
  |-
 
  |-
  | 5
+
  |colspan="2"| Identifiers
  | Normal
+
  |colspan="2"| Array of Identifier
  | Add slot for right-mouse drag
+
  | The identifiers of the advancements that should be removed
 
  |-
 
  |-
  | 9
+
  |colspan="2"| Progress size
  | Normal
+
  |colspan="2"| VarInt
  | Add slot for middle-mouse drag, only defined for creative players in non-player inventories.  (Note: the vanilla client will still incorrectly send this for non-creative players - see [https://bugs.mojang.com/browse/MC-46584 MC-46584])
+
  | Size of the following array
 
  |-
 
  |-
  | 2
+
  |rowspan="2"| Progress mapping
  | -999
+
| Key
  | Ending left mouse drag
+
|rowspan="2"| Array
 +
  | Identifier
 +
  | The identifier of the advancement
 
  |-
 
  |-
  | 6
+
  | Value
  | -999
+
  | Advancement progress
  | Ending right mouse drag
+
  | See below
|-
 
| 10
 
| -999
 
| Ending middle mouse drag, only defined for creative players in non-player inventories.  (Note: the vanilla client will still incorrectly send this for non-creative players - see [https://bugs.mojang.com/browse/MC-46584 MC-46584])
 
|-
 
! 6
 
| 0
 
| Normal
 
| Double click
 
 
  |}
 
  |}
  
Starting from version 1.5, “painting mode” is available for use in inventory windows. It is done by picking up stack of something (more than 1 item), then holding mouse button (left, right or middle) and dragging held stack over empty (or same type in case of right button) slots. In that case client sends the following to server after mouse button release (omitting first pickup packet which is sent as usual):
+
Advancement structure:
 
 
# packet with mode 5, slot -999, button (0 for left | 4 for right);
 
# packet for every slot painted on, mode is still 5, button (1 | 5);
 
# packet with mode 5, slot -999, button (2 | 6);
 
 
 
If any of the painting packets other than the “progress” ones are sent out of order (for example, a start, some slots, then another start; or a left-click in the middle) the painting status will be reset.
 
 
 
The server will send back a [[#Confirm Transaction (clientbound)|Confirm Transaction]] packet. If the click was not accepted, the client must send a matching [[#Confirm Transaction (serverbound)|serverbound confirm transaction]] packet before sending more [[#Click Window|Click Window]] packets, otherwise the server will reject them silently. The Notchian server also sends a [[#Window Items|Window Items]] packet for the open window and [[#Set Slot|Set Slot]] packets for the clicked and cursor slot, but only when the click was not accepted, probably to resynchronize client and server.
 
 
 
==== Close Window (serverbound) ====
 
 
 
This packet is sent by the client when closing a window.
 
 
 
Notchian clients send a Close Window packet with Window ID 0 to close their inventory even though there is never an [[#Open Window|Open Window]] packet for the inventory.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
  ! Packet ID
+
  !colspan="2"| Field Name
! State
+
  !colspan="2"| Field Type
! Bound To
 
! Field Name
 
  ! Field Type
 
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  | 0x09
+
  |colspan="2"| Has parent
| Play
+
  |colspan="2"| Boolean
  | Server
+
  | Indicates whether the next field exists.
| Window ID
 
| Unsigned Byte
 
  | This is the ID of the window that was closed. 0 for player inventory.
 
|}
 
 
 
==== Plugin Message (serverbound) ====
 
 
 
{{Main|Plugin channels}}
 
 
 
Mods and plugins can use this to send their data. Minecraft itself uses a number of [[plugin channel]]s. These internal channels are prefixed with <code>MC|</code>.
 
 
 
More documentation on this: [http://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/ http://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/]
 
 
 
Note that the length of Data is known only from the packet length, since the packet has no length field of any kind.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="2"| 0x0A
+
  |colspan="2"| Parent id
  |rowspan="2"| Play
+
  |colspan="2"| Optional Identifier
  |rowspan="2"| Server
+
  | The identifier of the parent advancement.
  | Channel
+
|-
| String (20)
+
|colspan="2"| Has display
  | Name of the [[plugin channel]] used to send the data
+
  |colspan="2"| Boolean
 +
  | Indicates whether the next field exists
 
  |-
 
  |-
  | Data
+
  |colspan="2"| Display data
| Byte Array
+
  |colspan="2"| Optional advancement display
| Any data, depending on the channel. <code><nowiki>MC|</nowiki></code> channels are documented [[plugin channel|here]].  The length of this array must be inferred from the packet length.
+
  | See below.
  |}
 
 
 
==== Use Entity ====
 
 
 
This packet is sent from the client to the server when the client attacks or right-clicks another entity (a player, minecart, etc).
 
 
 
A Notchian server only accepts this packet if the entity being attacked/used is visible without obstruction and within a 4-unit radius of the player's position.
 
 
 
Note that middle-click in creative mode is interpreted by the client and sent as a [[#Creative Inventory Action|Creative Inventory Action]] packet instead.
 
 
 
{| class="wikitable"
 
  ! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="6"| 0x0B
+
  |colspan="2"| Number of criteria
  |rowspan="6"| Play
+
  |colspan="2"| VarInt
|rowspan="6"| Server
+
  | Size of the following array
| Target
 
| VarInt
 
  |  
 
 
  |-
 
  |-
  | Type
+
  |rowspan="2"| Criteria
  | VarInt Enum
+
  | Key
  | 0: interact, 1: attack, 2: interact at
+
  |rowspan="2"| Array
 +
| Identifier
 +
| The identifier of the criterion
 
  |-
 
  |-
  | Target X
+
  | Value
  | Optional Float
+
  | '''Void'''
  | Only if Type is interact at
+
  | There is ''no'' content written here.  Perhaps this will be expanded in the future?
 
  |-
 
  |-
  | Target Y
+
  |colspan="2"| Array length
  | Optional Float
+
  |colspan="2"| VarInt
  | Only if Type is interact at
+
  | Number of arrays in the following array
 
  |-
 
  |-
  | Target Z
+
  |rowspan="2"| Requirements
  | Optional Float
+
| Array length 2
  | Only if Type is interact at
+
|rowspan="2"| Array
 +
  | VarInt
 +
  | Number of elements in the following array
 
  |-
 
  |-
  | Hand
+
  | Requirement
  | Optional VarInt Enum
+
  | Array of String
  | Only if Type is interact or interact at; 0: main hand, 1: off hand
+
  | Array of required criteria
 
  |}
 
  |}
  
==== Keep Alive (serverbound) ====
+
Advancement display:
 
 
The server will frequently send out a keep-alive, each containing a random ID. The client must respond with the same packet.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
! Packet ID
 
! State
 
! Bound To
 
 
  ! Field Name
 
  ! Field Name
 
  ! Field Type
 
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  | 0x0C
+
  | Title
  | Play
+
  | Chat
  | Server
+
  |
  | Keep Alive ID
+
  |-
  | VarInt
+
  | Description
  |  
+
  | Chat
  |}
+
  |
 
+
|-
==== Player ====
+
| Icon
 
+
| [[Slot]]
This packet as well as [[#Player Position|Player Position]] ([[#Play|Play]], 0x04, serverbound), [[#Player Look|Player Look]] ([[#Play|Play]], 0x05, serverbound), and [[#Player Position And Look 2|Player Position And Look]] ([[#Play|Play]], 0x06, serverbound) are called the “serverbound movement packets”. Vanilla clients will send Player Position once every 20 ticks even for a stationary player.
+
|
 +
|-
 +
| Frame type
 +
| VarInt enum
 +
| 0 = <code>task</code>, 1 = <code>challenge</code>, 2 = <code>goal</code>
 +
|-
 +
| Flags
 +
| Integer
 +
| 0x1: has background texture; 0x2: <code>show_toast</code>; 0x4: <code>hidden</code>
 +
|-
 +
| Background texture
 +
| Optional Identifier
 +
| Background texture location. Only if flags indicates it.
 +
|-
 +
| X coord
 +
| Float
 +
|
 +
|-
 +
| Y coord
 +
| Float
 +
|
 +
|}
  
This packet is used to indicate whether the player is on ground (walking/swimming), or airborne (jumping/falling).
+
Advancement progress:
 
 
When dropping from sufficient height, fall damage is applied when this state goes from false to true. The amount of damage applied is based on the point where it last changed from true to false. Note that there are several movement related packets containing this state.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
  ! Packet ID
+
  !colspan="2"| Field Name
! State
+
  !colspan="2"| Field Type
! Bound To
 
! Field Name
 
  ! Field Type
 
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="1"| 0x0D
+
  |colspan="2"| Size
  |rowspan="1"| Play
+
|colspan="2"| VarInt
  |rowspan="1"| Server
+
| Size of the following array
  | On Ground
+
|-
  | Boolean
+
  |rowspan="2"| Criteria
  | True if the client is on the ground, false otherwise
+
| Criterion identifier
  |}
+
  |rowspan="2"| Array
 
+
| Identifier
==== Player Position ====
+
  | The identifier of the criterion.
 +
  |-
 +
  | Criterion progress
 +
  | Criterion progress
 +
|
 +
|}
  
Updates the player's XYZ position on the server.
+
Criterion progress:
 
 
Checking for moving too fast is achieved like this:
 
 
 
* Each server tick, the player's current position is stored
 
* When a player moves, the changes in x, y, and z coordinates are compared with the positions from the previous tick (&Delta;x, &Delta;y, &Delta;z)
 
* Total movement distance squared is computed as &Delta;x&sup2; + &Delta;y&sup2; + &Delta;z&sup2;
 
* The expected movement distance squared is computed as velocityX&sup2; + veloctyY&sup2; + velocityZ&sup2;
 
* If the total movement distance squared value minus the expected movement distance squared value is more than 100 (300 if the player is using an elytra), they are moving too fast.
 
 
 
If the player is moving too fast, it will be logged that "<player> moved too quickly! " followed by the change in x, y, and z, and the player will be teleported back to their current (before this packet) serverside position.
 
 
 
Also, if the absolute value of X or the absolute value of Z is a value greater than 3.2×10<sup>7</sup>, or X, Y, or Z are not finite (either positive infinity, negative infinity, or NaN), the client will be kicked for “Invalid move player packet received”.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
! Packet ID
 
! State
 
! Bound To
 
 
  ! Field Name
 
  ! Field Name
 
  ! Field Type
 
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="4"| 0x0E
+
  | Achieved
|rowspan="4"| Play
+
  | Boolean
|rowspan="4"| Server
+
  | If true, next field is present
| X
 
  | Double
 
  | Absolute position
 
 
  |-
 
  |-
  | Feet Y
+
  | Date of achieving
  | Double
+
  | Optional Long
  | Absolute feet position, normally Head Y - 1.62
+
  | As returned by [https://docs.oracle.com/javase/6/docs/api/java/util/Date.html#getTime() <code>Date.getTime</code>]
|-
 
| Z
 
| Double
 
| Absolute position
 
|-
 
| On Ground
 
| Boolean
 
| True if the client is on the ground, false otherwise
 
 
  |}
 
  |}
  
==== Player Position And Look (serverbound) ====
+
==== Entity Properties ====
  
A combination of [[#Player Look|Player Look]] and [[#Player Position|Player Position]].
+
Sets {{Minecraft Wiki|Attribute|attributes}} on the given entity.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 4,878: Line 4,979:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  ! Field Name
+
  !colspan="2"| Field Name
  ! Field Type
+
  !colspan="2"| Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="6"| 0x0F
+
  |rowspan="6"| 0x59
 
  |rowspan="6"| Play
 
  |rowspan="6"| Play
  |rowspan="6"| Server
+
  |rowspan="6"| Client
  | X
+
  |colspan="2"| Entity ID
  | Double
+
|colspan="2"| VarInt
  | Absolute position
+
|
 +
|-
 +
|colspan="2"| Number Of Properties
 +
  |colspan="2"| Int
 +
  | Number of elements in the following array
 
  |-
 
  |-
  | Feet Y
+
  |rowspan="4"| Property
  | Double
+
| Key
  | Absolute feet position, normally Head Y - 1.62
+
|rowspan="4"| Array
 +
  | String (64)
 +
  | See below
 
  |-
 
  |-
  | Z
+
  | Value
 
  | Double
 
  | Double
  | Absolute position
+
  | See below
 
  |-
 
  |-
  | Yaw
+
  | Number Of Modifiers
  | Float
+
  | VarInt
  | Absolute rotation on the X Axis, in degrees
+
  | Number of elements in the following array
 
  |-
 
  |-
  | Pitch
+
  | Modifiers
  | Float
+
  | Array of Modifier Data
  | Absolute rotation on the Y Axis, in degrees
+
  | See {{Minecraft Wiki|Attribute#Modifiers}}. Modifier Data defined below.
|-
 
| On Ground
 
| Boolean
 
| True if the client is on the ground, false otherwise
 
 
  |}
 
  |}
  
==== Player Look ====
+
Known Key values (see also {{Minecraft Wiki|Attribute#Modifiers}}):
[[File:Minecraft-trig-yaw.png|thumb|The unit circle for yaw]]
 
[[File:Yaw.png|thumb|The unit circle of yaw, redrawn]]
 
  
Updates the direction the player is looking in.
+
{| class="wikitable"
 
+
  |-
Yaw is measured in degrees, and does not follow classical trigonometry rules. The unit circle of yaw on the XZ-plane starts at (0, 1) and turns counterclockwise, with 90 at (-1, 0), 180 at (0,-1) and 270 at (1, 0). Additionally, yaw is not clamped to between 0 and 360 degrees; any number is valid, including negative numbers and numbers greater than 360.
+
  ! Key
 
+
  ! Default
Pitch is measured in degrees, where 0 is looking straight ahead, -90 is looking straight up, and 90 is looking straight down.
+
  ! Min
 
+
  ! Max
The yaw and pitch of player (in degrees), standing at point (x0, y0, z0) and looking towards point (x, y, z) can be calculated with:
+
  ! Label
 
 
dx = x-x0
 
dy = y-y0
 
dz = z-z0
 
r = sqrt( dx*dx + dy*dy + dz*dz )
 
yaw = -atan2(dx,dz)/PI*180
 
if yaw < 0 then
 
    yaw = 360 - yaw
 
pitch = -arcsin(dy/r)/PI*180
 
 
 
You can get a unit vector from a given yaw/pitch via:
 
 
 
x = -cos(pitch) * sin(yaw)
 
y = -sin(pitch)
 
z =  cos(pitch) * cos(yaw)
 
 
 
{| class="wikitable"
 
  ! Packet ID
 
  ! State
 
  ! Bound To
 
  ! Field Name
 
  ! Field Type
 
  ! Notes
 
 
  |-
 
  |-
  |rowspan="3"| 0x10
+
  | generic.maxHealth
|rowspan="3"| Play
+
  | 20.0
  |rowspan="3"| Server
+
  | 0.0
  | Yaw
+
  | 1024.0
  | Float
+
  | Max Health
  | Absolute rotation on the X Axis, in degrees
 
 
  |-
 
  |-
  | Pitch
+
  | generic.followRange
  | Float
+
  | 32.0
  | Absolute rotation on the Y Axis, in degrees
+
  | 0.0
 +
| 2048.0
 +
| Follow Range
 
  |-
 
  |-
  | On Ground
+
  | generic.knockbackResistance
  | Boolean
+
  | 0.0
  | True if the client is on the ground, False otherwise
+
  | 0.0
  |}
+
  | 1.0
 
+
| Knockback Resistance
==== Vehicle Move (serverbound) ====
 
 
 
Sent when a player moves in a vehicle. Fields are the same as in [[#Player Position And Look (serverbound)|Player Position And Look]] ([[#Play|Play]], 0x2E, serverbound). Note that all fields use absolute positioning and do not allow for relative positioning.
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="7"| 0x11
+
  | generic.movementSpeed
|rowspan="7"| Play
+
  | 0.699999988079071
  |rowspan="7"| Server
+
  | 0.0
  | X
+
  | 1024.0
  | Double
+
  | Movement Speed
  | Absolute position (X coordinate)
 
 
  |-
 
  |-
  | Y
+
  | generic.attackDamage
  | Double
+
  | 2.0
  | Absolute position (Y coordinate)
+
  | 0.0
 +
| 2048.0
 +
| Attack Damage
 
  |-
 
  |-
  | Z
+
  | generic.attackSpeed
  | Double
+
  | 4.0
  | Absolute position (Z coordinate)
+
  | 0.0
 +
| 1024.0
 +
| Attack Speed
 
  |-
 
  |-
  | Yaw
+
  | generic.flyingSpeed
  | Float
+
  | 0.4000000059604645
  | Absolute rotation on the vertical axis, in degrees
+
  | 0.0
 +
| 1024.0
 +
| Flying Speed
 +
|-
 +
| horse.jumpStrength
 +
| 0.7
 +
| 0.0
 +
| 2.0
 +
| Jump Strength
 +
|-
 +
| zombie.spawnReinforcements
 +
| 0.0
 +
| 0.0
 +
| 1.0
 +
| Spawn Reinforcements Chance
 +
|-
 +
| generic.reachDistance
 +
| 5.0
 +
| 0.0
 +
| 1024.0
 +
| Player Reach Distance (Forge only)
 
  |-
 
  |-
  | Pitch
+
  | forge.swimSpeed
  | Float
+
  | 1.0
  | Absolute rotation on the horizontal axis, in degrees
+
  | 0.0
 +
| 1024.0
 +
| Swimming Speed (Forge only)
 
  |}
 
  |}
  
==== Steer Boat ====
+
''Modifier Data'' structure:
 
 
Used to ''visually'' update whether boat paddles are turning.  The server will update the [[Entities#Boat|Boat entity metadata]] to match the values here.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
  ! Packet ID
+
  |-
! State
 
! Bound To
 
 
  ! Field Name
 
  ! Field Name
 
  ! Field Type
 
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x12
+
  | UUID
|rowspan="2"| Play
+
  | UUID
|rowspan="2"| Server
+
  |  
| Right paddle turning
 
  | Boolean
 
  |
 
 
  |-
 
  |-
  | Left paddle turning
+
  | Amount
  | Boolean
+
  | Double
  |
+
  | May be positive or negative
 +
|-
 +
| Operation
 +
| Byte
 +
| See below
 
  |}
 
  |}
  
Right paddle turning is set to true when the left button or forward button is held; left paddle turning is set to true when the right button or forward button is set to true.
+
The operation controls how the base value of the modifier is changed.
  
==== Player Abilities (serverbound) ====
+
* 0: Add/subtract amount
 +
* 1: Add/subtract amount percent of the current value
 +
* 2: Multiply by amount percent
  
The latter 2 bytes are used to indicate the walking and flying speeds respectively, while the first byte is used to determine the value of 4 booleans.
+
All of the 0's are applied first, and then the 1's, and then the 2's.
  
The vanilla client sends this packet when the player starts/stops flying with the Flags parameter changed accordingly. All other parameters are ignored by the vanilla server.
+
==== Entity Effect ====
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,037: Line 5,129:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="3"| 0x13
+
  |rowspan="5"| 0x5A
  |rowspan="3"| Play
+
  |rowspan="5"| Play
  |rowspan="3"| Server
+
  |rowspan="5"| Client
  | Flags
+
  | Entity ID
 +
| VarInt
 +
|
 +
|-
 +
| Effect ID
 +
| Byte
 +
| See {{Minecraft Wiki|Status effect#List of effects|this table}}
 +
|-
 +
| Amplifier
 
  | Byte
 
  | Byte
  | Bit mask. 0x08: damage disabled (god mode), 0x04: can fly, 0x02: is flying, 0x01: is Creative
+
  | Notchian client displays effect level as Amplifier + 1
 
  |-
 
  |-
  | Flying Speed
+
  | Duration
  | Float
+
  | VarInt
  |  
+
  | Seconds
 
  |-
 
  |-
  | Walking Speed
+
  | Flags
  | Float
+
  | Byte
  |  
+
  | Bit field, see below.
 
  |}
 
  |}
  
==== Player Digging ====
+
Within flags:
 +
 
 +
* 0x01: Is ambient - was the effect spawned from a beacon?  All beacon-generated effects are ambient.  Ambient effects use a different icon in the HUD (blue border rather than gray).  If all effects on an entity are ambient, the [[Entities#Living|"Is potion effect ambient" living metadata field]] should be set to true.  Usually should not be enabled.
 +
* 0x02: Show particles - should all particles from this effect be hidden?  Effects with particles hidden are not included in the calculation of the effect color, and are not rendered on the HUD (but are still rendered within the inventory).  Usually should be enabled.
 +
* 0x04: Show icon - should the icon be displayed on the client?  Usually should be enabled.
  
Sent when the player mines a block. A Notchian server only accepts digging packets with coordinates within a 6-unit radius between the center of the block and 1.5 units from the player's feet (''not'' their eyes).
+
==== Declare Recipes ====
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,061: Line 5,165:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  ! Field Name
+
  !colspan="2"| Field Name
  ! Field Type
+
  !colspan="2"| Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="3"| 0x14
+
  |rowspan="4"| 0x5B
  |rowspan="3"| Play
+
  |rowspan="4"| Play
  |rowspan="3"| Server
+
  |rowspan="4"| Client
  | Status
+
  |colspan="2"| Num Recipes
  | VarInt Enum
+
  |colspan="2"| VarInt
  | The action the player is taking against the block (see below)
+
  | Number of elements in the following array
 +
|-
 +
|rowspan="3"| Recipe
 +
| Recipe ID
 +
|rowspan="3"| Array
 +
| Identifier
 +
|
 
  |-
 
  |-
  | Location
+
  | Type
  | Position
+
  | String
  | Block position
+
  | The recipe type, see below
 
  |-
 
  |-
  | Face
+
  | Data
  | Byte Enum
+
  | Optional, varies
  | The face being hit (see below)
+
  | Additional data for the recipe.  For some types, there will be no data.
 
  |}
 
  |}
  
Status can be one of seven values:
+
Recipe types:
  
 
{| class="wikitable"
 
{| class="wikitable"
  ! Value
+
  ! Type
  ! Meaning
+
  ! Description
  ! Notes
+
  ! Data
 
  |-
 
  |-
  | 0
+
  | <code>crafting_shapeless</code>
  | Started digging
+
  | Shapeless crafting recipe.  All items in the ingredient list must be present, but in any order/slot.
  |  
+
  | As follows:
 +
  {| class="wikitable"
 +
    ! Name
 +
    ! Type
 +
    ! Description
 +
    |-
 +
    | Group
 +
    | String
 +
    | Used to group similar recipes together in the recipe book.  Tag is present in recipe JSON.
 +
    |-
 +
    | Ingredient count
 +
    | VarInt
 +
    | Number of elements in the following array
 +
    |-
 +
    | Ingredients
 +
    | Array of Ingredient
 +
    |
 +
    |-
 +
    | Result
 +
    | [[Slot]]
 +
    |
 +
    |}
 
  |-
 
  |-
  | 1
+
  | <code>crafting_shaped</code>
  | Cancelled digging
+
  | Shaped crafting recipe.  All items must be present in the same pattern (which may be flipped horizontally or translated)
  | Sent when the player lets go of the Mine Block key (default: left click)
+
  | As follows:
 +
  {| class="wikitable"
 +
    ! Name
 +
    ! Type
 +
    ! Description
 +
    |-
 +
    | Width
 +
    | VarInt
 +
    |
 +
    |-
 +
    | Height
 +
    | VarInt
 +
    |
 +
    |-
 +
    | Group
 +
    | String
 +
    | Used to group similar recipes together in the recipe book.  Tag is present in recipe JSON.
 +
    |-
 +
    | Ingredients
 +
    | Array of Ingredient
 +
    | Length is width * height.  Indexed by x + (y * width).
 +
    |-
 +
    | Result
 +
    | [[Slot]]
 +
    |
 +
    |}
 
  |-
 
  |-
  | 2
+
  | <code>crafting_special_armordye</code>
  | Finished digging
+
  | Recipe for dying leather armor
  | Sent when the client thinks it is finished
+
  | None
 
  |-
 
  |-
  | 3
+
  | <code>crafting_special_bookcloning</code>
  | Drop item stack
+
  | Recipe for copying contents of written books
  | Triggered by using the Drop Item key (default: Q) with the modifier to drop the entire selected stack (default: depends on OS). Location is always set to 0/0/0, Face is always set to -Y.
+
  | None
 
  |-
 
  |-
  | 4
+
  | <code>crafting_special_mapcloning</code>
  | Drop item
+
  | Recipe for copying maps
  | Triggered by using the Drop Item key (default: Q). Location is always set to 0/0/0, Face is always set to -Y.
+
  | None
 
  |-
 
  |-
  | 5
+
  | <code>crafting_special_mapextending</code>
  | Shoot arrow / finish eating
+
  | Recipe for adding paper to maps
  | Location is always set to 0/0/0, Face is always set to Special.
+
  | None
 
  |-
 
  |-
  | 6
+
  | <code>crafting_special_firework_rocket</code>
  | Swap item in hand
+
  | Recipe for making firework rockets
  | Used to swap or assign an item to the second hand. Location is always set to 0/0/0, Face is always set to -Y.
+
| None
  |}
+
  |-
 
+
  | <code>crafting_special_firework_star</code>
The Face field can be one of the following values, representing the face being hit (or the Special value used for “shoot arrow / finish eating”):
+
| Recipe for making firework stars
 
+
| None
{| class="wikitable"
 
 
  |-
 
  |-
  ! Value
+
  | <code>crafting_special_firework_star_fade</code>
  ! Offset
+
  | Recipe for making firework stars fade between multiple colors
  ! Face
+
  | None
 
  |-
 
  |-
  | 0
+
  | <code>crafting_special_repairitem</code>
  | -Y
+
  | Recipe for repairing items via crafting
  | Bottom
+
  | None
 
  |-
 
  |-
  | 1
+
  | <code>crafting_special_tippedarrow</code>
  | +Y
+
  | Recipe for crafting tipped arrows
  | Top
+
  | None
 
  |-
 
  |-
  | 2
+
  | <code>crafting_special_bannerduplicate</code>
  | -Z
+
  | Recipe for copying banner patterns
  | North
+
  | None
 
  |-
 
  |-
  | 3
+
  | <code>crafting_special_banneraddpattern</code>
  | +Z
+
  | Recipe for adding patterns to banners
  | South
+
  | None
 
  |-
 
  |-
  | 4
+
  | <code>crafting_special_shielddecoration</code>
  | -X
+
  | Recipe for applying a banner's pattern to a shield
  | West
+
  | None
 
  |-
 
  |-
  | 5
+
  | <code>crafting_special_shulkerboxcoloring</code>
  | +X
+
  | Recipe for recoloring a shulker box
  | East
+
  | None
 
  |-
 
  |-
  | 255
+
  | <code>smelting</code>
  |
+
  | Smelting recipe
  | Special
+
  | As follows:
 +
  {| class="wikitable"
 +
    ! Name
 +
    ! Type
 +
    ! Description
 +
    |-
 +
    | Group
 +
    | String
 +
    | Used to group similar recipes together in the recipe book.
 +
    |-
 +
    | Ingredient
 +
    | Ingredient
 +
    |
 +
    |-
 +
    | Result
 +
    | [[Slot]]
 +
    |
 +
    |-
 +
    | Experience
 +
    | Float
 +
    |
 +
    |-
 +
    | Cooking time
 +
    | VarInt
 +
    |
 +
    |}
 
  |}
 
  |}
  
==== Entity Action ====
+
Ingredient is defined as:
 +
 
 +
{| class="wikitable"
 +
! Name
 +
! Type
 +
! Description
 +
|-
 +
| Count
 +
| VarInt
 +
| Number of elements in the following array
 +
|-
 +
| Items
 +
| Array of [[Slot]]
 +
| Any item in this array may be used for the recipe.  The count of each item should be 1.
 +
|}
  
Sent by the client to indicate that it has performed certain actions: sneaking (crouching), sprinting, exiting a bed, jumping with a horse, and opening a horse's inventory while riding it.
+
==== Tags ====
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,166: Line 5,360:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="3"| 0x15
+
  |rowspan="4"| 0x5C
  |rowspan="3"| Play
+
  |rowspan="4"| Play
  |rowspan="3"| Server
+
  |rowspan="4"| Client
  | Entity ID
+
  | Block Tags
  | VarInt
+
  | (See below)
  | Player ID
+
  | IDs are block IDs
 
  |-
 
  |-
  | Action ID
+
  | Item Tags
  | VarInt Enum
+
  | (See below)
  | The ID of the action, see below
+
| IDs are item IDs
 +
  |-
 +
| Fluid Tags
 +
| (See below)
 +
| IDs are fluid IDs
 
  |-
 
  |-
  | Jump Boost
+
  | Entity Tags
  | VarInt
+
  | (See below)
  | Only used by the “start jump with horse” action, in which case it ranges from 0 to 100. In all other cases it is 0.
+
  | IDs are entity IDs
 
  |}
 
  |}
  
Action ID can be one of the following values:
+
Tags look like:
  
 
{| class="wikitable"
 
{| class="wikitable"
  ! ID
+
  !colspan="2"| Field Name
  ! Action
+
  !colspan="2"| Field Type
 +
! Notes
 
  |-
 
  |-
  | 0
+
  |colspan="2"| Length
  | Start sneaking
+
|colspan="2"| VarInt
 +
  | Number of elements in the following array
 
  |-
 
  |-
  | 1
+
  |rowspan="3"| Tags
  | Stop sneaking
+
| Tag name
 +
|rowspan="3"| Array
 +
| Identifier
 +
  |
 
  |-
 
  |-
  | 2
+
  | Count
  | Leave bed
+
  | VarInt
 +
| Number of elements in the following array
 
  |-
 
  |-
  | 3
+
  | Entries
  | Start sprinting
+
  | Array of VarInt
  |-
+
  | Numeric ID of the block/item.
| 4
 
| Stop sprinting
 
|-
 
| 5
 
| Start jump with horse
 
|-
 
| 6
 
| Stop jump with horse
 
|-
 
| 7
 
| Open horse inventory
 
|-
 
| 8
 
| Start flying with elytra
 
 
  |}
 
  |}
  
Leave bed is only sent when the “Leave Bed” button is clicked on the sleep GUI, not when waking up due today time.
+
=== Serverbound ===
  
Open horse inventory is only sent when pressing the inventory key (default: E) while on a horse — all other methods of opening a horse's inventory (involving right-clicking or shift-right-clicking it) do not use this packet.
+
==== Teleport Confirm ====
  
==== Steer Vehicle ====
+
Sent by client as confirmation of [[#Player Position And Look (clientbound)|Player Position And Look]].
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,230: Line 5,420:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="3"| 0x16
+
  | 0x00
  |rowspan="3"| Play
+
  | Play
  |rowspan="3"| Server
+
  | Server
  | Sideways
+
  | Teleport ID
  | Float
+
  | VarInt
  | Positive to the left of the player
+
  | The ID given by the [[#Player Position And Look (clientbound)|Player Position And Look]] packet
|-
 
| Forward
 
| Float
 
| Positive forward
 
|-
 
| Flags
 
| Unsigned Byte
 
| Bit mask. 0x1: jump, 0x2: unmount
 
 
  |}
 
  |}
  
Also known as 'Input' packet.
+
==== Query Block NBT ====
  
==== Crafting Book Data ====
+
Used when <kbd>Shift</kbd>+<kbd>F3</kbd>+<kbd>I</kbd> is pressed while looking at a block.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,254: Line 5,436:
 
  ! State
 
  ! State
 
  ! Bound To
 
  ! Bound To
  !colspan="2"| Field Name
+
  ! Field Name
 
  ! Field Type
 
  ! Field Type
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="5"| 0x17
+
  |rowspan="2"| 0x01
  |rowspan="5"| Play
+
  |rowspan="2"| Play
  |rowspan="5"| Server
+
  |rowspan="2"| Server
  |colspan="2"| Type
+
  | Transaction ID
 
  | VarInt
 
  | VarInt
  | Determines the format of the rest of the packet
+
  | An incremental ID so that the client can verify that the response matches.
 
  |-
 
  |-
! Type
+
  | Location
! Field Name
+
  | Position
!
+
  | The location of the block to check.
!
 
|-
 
  | 0: Displayed Recipe
 
  | Recipe ID
 
| Int
 
  | The internal id of the displayed recipe.
 
|-
 
|rowspan="2"| 1: Crafting Book Status
 
| Crafting Book Open
 
| Boolean
 
| Whether the player has the crafting book currently openened/active.
 
|-
 
| Crafting Filter
 
| Boolean
 
| Whether the player has the crafting filter option currently active.
 
 
  |}
 
  |}
  
The Crafting Book Status type is send when the player closes its inventory.
+
==== Set Difficulty ====
  
==== Resource Pack Status ====
+
Must have at least op level 2 to use.  Appears to only be used on singleplayer; the difficulty buttons are still disabled in multiplayer.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,297: Line 5,464:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x18
+
  |rowspan="1"| 0x02
  |rowspan="2"| Play
+
  |rowspan="1"| Play
  |rowspan="2"| Server
+
  |rowspan="1"| Server
  | Result
+
  | New difficulty
  | VarInt Enum
+
  | Byte
  | 0: successfully loaded, 1: declined, 2: failed download, 3: accepted
+
  | 0: peaceful, 1: easy, 2: normal, 3: hard
 
  |}
 
  |}
  
==== Advancement Tab ====
+
==== Chat Message (serverbound) ====
 +
 
 +
Used to send a chat message to the server.  The message may not be longer than 256 characters or else the server will kick the client.
 +
 
 +
If the message starts with a <code>/</code>, the server will attempt to interpret it as a command.  Otherwise, the server will broadcast the same chat message to all players on the server (including the player that sent the message), prepended with player's name.  Specifically, it will respond with a translate [[chat]] component, "<code>chat.type.text</code>" with the first parameter set to the display name of the player (including some chat component logic to support clicking the name to send a PM) and the second parameter set to the message.  See [[Chat#Processing chat|processing chat]] for more information.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,315: Line 5,486:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x19
+
  |rowspan="1"| 0x03
  |rowspan="2"| Play
+
  |rowspan="1"| Play
  |rowspan="2"| Server
+
  |rowspan="1"| Server
  | Action
+
  | Message
  | VarInt enum
+
  | String (256)
  | 0: Opened tab, 1: Closed screen
+
  | The client sends the raw input, not a [[Chat]] component
|-
 
| Tab ID
 
| Optional identifier
 
| Only present if action is Opened tab
 
 
  |}
 
  |}
  
==== Held Item Change (serverbound) ====
+
==== Client Status ====
 
 
Sent when the player changes the slot selection
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,339: Line 5,504:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="1"| 0x1A
+
  |rowspan="1"| 0x04
 
  |rowspan="1"| Play
 
  |rowspan="1"| Play
 
  |rowspan="1"| Server
 
  |rowspan="1"| Server
  | Slot
+
  | Action ID
  | Short
+
  | VarInt Enum
  | The slot which the player has selected (0–8)
+
  | See below
 
  |}
 
  |}
  
==== Creative Inventory Action ====
+
''Action ID'' values:
 
 
While the user is in the standard inventory (i.e., not a crafting bench) in Creative mode, the player will send this packet.
 
 
 
Clicking in the creative inventory menu is quite different from non-creative inventory management. Picking up an item with the mouse actually deletes the item from the server, and placing an item into a slot or dropping it out of the inventory actually tells the server to create the item from scratch. (This can be verified by clicking an item that you don't mind deleting, then severing the connection to the server; the item will be nowhere to be found when you log back in.) As a result of this implementation strategy, the "Destroy Item" slot is just a client-side implementation detail that means "I don't intend to recreate this item.". Additionally, the long listings of items (by category, etc.) are a client-side interface for choosing which item to create. Picking up an item from such listings sends no packets to the server; only when you put it somewhere does it tell the server to create the item in that location.
 
 
 
This action can be described as "set inventory slot". Picking up an item sets the slot to item ID -1. Placing an item into an inventory slot sets the slot to the specified item. Dropping an item (by clicking outside the window) effectively sets slot -1 to the specified item, which causes the server to spawn the item entity, etc.. All other inventory slots are numbered the same as the non-creative inventory (including slots for the 2x2 crafting menu, even though they aren't visible in the vanilla client).
 
  
 
{| class="wikitable"
 
{| class="wikitable"
  ! Packet ID
+
  |-
  ! State
+
  ! Action ID
! Bound To
+
  ! Action
! Field Name
 
  ! Field Type
 
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x1B
+
  | 0
|rowspan="2"| Play
+
  | Perform respawn
|rowspan="2"| Server
+
  | Sent when the client is ready to complete login and when the client is ready to respawn after death.
| Slot
 
  | Short
 
  | Inventory slot
 
 
  |-
 
  |-
  | Clicked Item
+
  | 1
  | [[Slot Data|Slot]]
+
  | Request stats
  |  
+
  | Sent when the client opens the Statistics menu
 
  |}
 
  |}
  
==== Update Sign ====
+
==== Client Settings ====
  
{{anchor|Update Sign (serverbound)}}This message is sent from the client to the server when the “Done” button is pushed after placing a sign.
+
Sent when the player connects, or when settings are changed.
 
 
The server only accepts this packet after [[#Open Sign Editor|Open Sign Editor]] ([[#Play|Play]], 0x2A, clientbound), otherwise this packet is silently ignored.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,389: Line 5,541:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="5"| 0x1C
+
  |rowspan="6"| 0x05
  |rowspan="5"| Play
+
  |rowspan="6"| Play
  |rowspan="5"| Server
+
  |rowspan="6"| Server
  | Location
+
  | Locale
  | Position
+
  | String (16)
  | Block Coordinates
+
  | e.g. en_GB
 
  |-
 
  |-
  | Line 1
+
  | View Distance
  | String (384)
+
  | Byte
  | First line of text in the sign
+
  | Client-side render distance, in chunks
 
  |-
 
  |-
  | Line 2
+
  | Chat Mode
  | String (384)
+
  | VarInt Enum
  | Second line of text in the sign
+
  | 0: enabled, 1: commands only, 2: hidden.  See [[Chat#Processing chat|processing chat]] for more information.
 
  |-
 
  |-
  | Line 3
+
  | Chat Colors
  | String (384)
+
  | Boolean
  | Third line of text in the sign
+
  | “Colors” multiplayer setting
 +
|-
 +
| Displayed Skin Parts
 +
| Unsigned Byte
 +
| Bit mask, see below
 
  |-
 
  |-
  | Line 4
+
  | Main Hand
  | String (384)
+
  | VarInt Enum
  | Fourth line of text in the sign
+
  | 0: Left, 1: Right
 
  |}
 
  |}
  
==== Animation (serverbound) ====
+
''Displayed Skin Parts'' flags:
 +
 
 +
* Bit 0 (0x01): Cape enabled
 +
* Bit 1 (0x02): Jacket enabled
 +
* Bit 2 (0x04): Left Sleeve enabled
 +
* Bit 3 (0x08): Right Sleeve enabled
 +
* Bit 4 (0x10): Left Pants Leg enabled
 +
* Bit 5 (0x20): Right Pants Leg enabled
 +
* Bit 6 (0x40): Hat enabled
 +
 
 +
The most significant bit (bit 7, 0x80) appears to be unused.
 +
 
 +
==== Tab-Complete (serverbound) ====
  
Sent when the player's arm swings.
+
Sent when the client needs to tab-complete a <code>minecraft:ask_server</code> suggestion type.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,425: Line 5,593:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  | 0x1D
+
  |rowspan="5"| 0x06
  | Play
+
  |rowspan="5"| Play
  | Server
+
  |rowspan="5"| Server
  | Hand
+
  | Transaction Id
  | VarInt Enum
+
  | VarInt
  | Hand used for the animation. 0: main hand, 1: off hand.
+
  | The id received in the tab completion request packet, must match or the client will ignore this packet. Client generates this and increments it each time it sends another tab completion that doesn't get a response.
 +
|-
 +
| Text
 +
| String (32500)
 +
| All text behind the cursor without the <code>/</code> (e.g. to the left of the cursor in left-to-right languages like English)
 
  |}
 
  |}
  
==== Spectate ====
+
==== Window Confirmation (serverbound) ====
 
 
Teleports the player to the given entity.  The player must be in spectator mode.
 
  
The Notchian client only uses this to teleport to players, but it appears to accept any type of entity.  The entity does not need to be in the same dimension as the player; if necessary, the player will be respawned in the right world. If the given entity cannot be found (or isn't loaded), this packet will be ignored.  It will also be ignored if the player attempts to teleport to themselves.
+
If a confirmation sent by the client was not accepted, the server will reply with a [[#Window Confirmation (clientbound)|Window Confirmation (clientbound)]] packet with the Accepted field set to false. When this happens, the client must send this packet to apologize (as with movement), otherwise the server ignores any successive confirmations.
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,447: Line 5,617:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="1"| 0x1E
+
  |rowspan="3"| 0x07
  |rowspan="1"| Play
+
  |rowspan="3"| Play
  |rowspan="1"| Server
+
  |rowspan="3"| Server
  | Target Player
+
  | Window ID
  | UUID
+
  | Byte
  | UUID of the player to teleport to (can also be an entity UUID)
+
  | The ID of the window that the action occurred in
 +
|-
 +
| Action Number
 +
| Short
 +
| Every action that is to be accepted has a unique number. This number is an incrementing integer (starting at 1) with separate counts for each window ID.
 +
|-
 +
| Accepted
 +
| Boolean
 +
| Whether the action was accepted
 
  |}
 
  |}
  
==== Player Block Placement ====
+
==== Click Window Button ====
 +
 
 +
Used when clicking on window buttons.  Until 1.14, this was only used by enchantment tables.
  
 
{| class="wikitable"
 
{| class="wikitable"
|-
 
 
  ! Packet ID
 
  ! Packet ID
 
  ! State
 
  ! State
Line 5,466: Line 5,645:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="6"| 0x1F
+
  |rowspan="2"| 0x07
  |rowspan="6"| Play
+
  |rowspan="2"| Play
  |rowspan="6"| Server
+
  |rowspan="2"| Server
  | Location
+
  | Window ID
  | Position
+
  | Byte
  | Block position
+
  | The ID of the window sent by [[#Open Window|Open Window]]
 +
|-
 +
| Button ID
 +
| Byte
 +
| Meaning depends on window type; see below
 +
|}
 +
 
 +
{| class="wikitable"
 +
! Window type
 +
! ID
 +
! Meaning
 +
|-
 +
|rowspan="3"| Enchantment Table
 +
| 0 || Topmost enchantment
 
  |-
 
  |-
  | Face
+
  | 1 || Middle enchantment
| VarInt Enum
 
| The face on which the block is placed (as documented at [[#Player Digging|Player Digging]])
 
 
  |-
 
  |-
  | Hand
+
  | 2 || Bottom enchantment
| VarInt Enum
 
| The hand from which the block is placed; 0: main hand, 1: off hand
 
 
  |-
 
  |-
  | Cursor Position X
+
  |rowspan="4"| Lectern
| Float
+
  | 1 || Previous page (which does give a redstone output)
  | The position of the crosshair on the block, from 0 to 1 increasing from west to east
 
 
  |-
 
  |-
  | Cursor Position Y
+
  | 2 || Next page
| Float
 
| The position of the crosshair on the block, from 0 to 1 increasing from bottom to top
 
 
  |-
 
  |-
  | Cursor Position Z
+
  | 3 || Take Book
  | Float
+
  |-
  | The position of the crosshair on the block, from 0 to 1 increasing from north to south
+
  | 100+page || Opened page number - 100 + number
  |}
+
  |-
 
+
| Stonecutter
In normal operation (i.e. placing a block), this packet is sent once, with the values set normally.
+
|colspan="2"| Recipe button number - 4*row + col.  Depends on the item.
 
+
|-
The Cursor Position X/Y/Z fields (also known as in-block coordinates) are calculated using raytracing. The unit corresponds to sixteen pixel in the default resource pack. For example, let's say a slab is being placed against the south face of a full block. The Cursor Position X will be higher if the player was pointing near the right (east) edge of the face, lower if pointing near the left. The Cursor Position Y will be used to determine whether it will appear as a bottom slab (values 0.0–0.5) or as a top slab (values 0.5-1.0). The Cursor Position Z should be 1.0 since the player was looking at the southernmost part of the block.
+
| Loom
 
+
|colspan="2"| Recipe button number - 4*row + col. Depends on the item.
This packet has a special case where X, Y, Z, and Face are all -1. (Note that Y is unsigned so set to 255.) This special packet indicates that the currently held item for the player should have its state updated such as eating food, pulling back bows, using buckets, etc.
+
|}
 
+
 
Special note on using buckets: When using buckets, the Notchian client might send two packets: first a normal and then a special case. The first normal packet is sent when you're looking at a block (e.g. the water you want to scoop up). This normal packet does not appear to do anything with a Notchian server. The second, special case packet appears to perform the action — based on current position/orientation and with a distance check — it appears that buckets can only be used within a radius of 6 units.
+
==== Click Window ====
 
+
 
==== Use Item ====
+
This packet is sent by the player when it clicks on a slot in a window.
 
+
 
Sent when pressing the Use Item key (default: right click) with an item in hand.
+
{| class="wikitable"
 
+
! Packet ID
{| class="wikitable"
+
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="6"| 0x09
 +
|rowspan="6"| Play
 +
|rowspan="6"| Server
 +
| Window ID
 +
| Unsigned Byte
 +
| The ID of the window which was clicked. 0 for player inventory.
 +
|-
 +
| Slot
 +
| Short
 +
| The clicked slot number, see below
 +
|-
 +
| Button
 +
| Byte
 +
| The button used in the click, see below
 +
|-
 +
| Action Number
 +
| Short
 +
| A unique number for the action, implemented by Notchian as a counter, starting at 1 (different counter for every window ID). Used by the server to send back a [[#Confirm Transaction (clientbound)|Confirm Transaction (clientbound)]].
 +
|-
 +
| Mode
 +
| VarInt Enum
 +
| Inventory operation mode, see below
 +
|-
 +
| Clicked item
 +
| [[Slot Data|Slot]]
 +
| The clicked slot. Has to be empty (item ID = -1) for drop mode.
 +
|}
 +
 
 +
See [[Inventory]] for further information about how slots are indexed.
 +
 
 +
When right-clicking on a stack of items, half the stack will be picked up and half left in the slot. If the stack is an odd number, the half left in the slot will be smaller of the amounts.
 +
 
 +
The distinct type of click performed by the client is determined by the combination of the Mode and Button fields.
 +
 
 +
{| class="wikitable"
 +
! Mode
 +
! Button
 +
! Slot
 +
! Trigger
 +
|-
 +
!rowspan="2"| 0
 +
| 0
 +
| Normal
 +
| Left mouse click
 +
|-
 +
| 1
 +
| Normal
 +
| Right mouse click
 +
|-
 +
!rowspan="2"| 1
 +
| 0
 +
| Normal
 +
| Shift + left mouse click
 +
|-
 +
| 1
 +
| Normal
 +
| Shift + right mouse click ''(identical behavior)''
 +
|-
 +
!rowspan="5"| 2
 +
| 0
 +
| Normal
 +
| Number key 1
 +
|-
 +
| 1
 +
| Normal
 +
| Number key 2
 +
|-
 +
| 2
 +
| Normal
 +
| Number key 3
 +
|-
 +
| ⋮
 +
| ⋮
 +
| ⋮
 +
|-
 +
| 8
 +
| Normal
 +
| Number key 9
 +
|-
 +
!rowspan="1"| 3
 +
| 2
 +
| Normal
 +
| Middle click, only defined for creative players in non-player inventories.
 +
|-
 +
!rowspan="4"| 4
 +
| 0
 +
| Normal*
 +
| Drop key (Q) (* Clicked item is different, see above)
 +
|-
 +
| 1
 +
| Normal*
 +
| Ctrl + Drop key (Ctrl-Q) ''(drops full stack)''
 +
|-
 +
| 0
 +
| -999
 +
| Left click outside inventory holding nothing ''(no-op)''
 +
|-
 +
| 1
 +
| -999
 +
| Right click outside inventory holding nothing ''(no-op)''
 +
|-
 +
!rowspan="9"| 5
 +
| 0
 +
| -999
 +
| Starting left mouse drag
 +
|-
 +
| 4
 +
| -999
 +
| Starting right mouse drag
 +
|-
 +
| 8
 +
| -999
 +
| Starting middle mouse drag, only defined for creative players in non-player inventories.  (Note: the vanilla client will still incorrectly send this for non-creative players - see [https://bugs.mojang.com/browse/MC-46584 MC-46584])
 +
|-
 +
| 1
 +
| Normal
 +
| Add slot for left-mouse drag
 +
|-
 +
| 5
 +
| Normal
 +
| Add slot for right-mouse drag
 +
|-
 +
| 9
 +
| Normal
 +
| Add slot for middle-mouse drag, only defined for creative players in non-player inventories.  (Note: the vanilla client will still incorrectly send this for non-creative players - see [https://bugs.mojang.com/browse/MC-46584 MC-46584])
 +
|-
 +
| 2
 +
| -999
 +
| Ending left mouse drag
 +
|-
 +
| 6
 +
| -999
 +
| Ending right mouse drag
 +
|-
 +
| 10
 +
| -999
 +
| Ending middle mouse drag, only defined for creative players in non-player inventories.  (Note: the vanilla client will still incorrectly send this for non-creative players - see [https://bugs.mojang.com/browse/MC-46584 MC-46584])
 +
|-
 +
! 6
 +
| 0
 +
| Normal
 +
| Double click
 +
|}
 +
 
 +
Starting from version 1.5, “painting mode” is available for use in inventory windows. It is done by picking up stack of something (more than 1 item), then holding mouse button (left, right or middle) and dragging held stack over empty (or same type in case of right button) slots. In that case client sends the following to server after mouse button release (omitting first pickup packet which is sent as usual):
 +
 
 +
# packet with mode 5, slot -999, button (0 for left | 4 for right);
 +
# packet for every slot painted on, mode is still 5, button (1 | 5);
 +
# packet with mode 5, slot -999, button (2 | 6);
 +
 
 +
If any of the painting packets other than the “progress” ones are sent out of order (for example, a start, some slots, then another start; or a left-click in the middle) the painting status will be reset.
 +
 
 +
The server will send back a [[#Confirm Transaction (clientbound)|Confirm Transaction]] packet. If the click was not accepted, the client must send a matching [[#Confirm Transaction (serverbound)|serverbound confirm transaction]] packet before sending more [[#Click Window|Click Window]] packets, otherwise the server will reject them silently. The Notchian server also sends a [[#Window Items|Window Items]] packet for the open window and [[#Set Slot|Set Slot]] packets for the clicked and cursor slot, but only when the click was not accepted, probably to resynchronize client and server.
 +
 
 +
==== Close Window (serverbound) ====
 +
 
 +
This packet is sent by the client when closing a window.
 +
 
 +
Notchian clients send a Close Window packet with Window ID 0 to close their inventory even though there is never an [[#Open Window|Open Window]] packet for the inventory.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
| 0x0A
 +
| Play
 +
| Server
 +
| Window ID
 +
| Unsigned Byte
 +
| This is the ID of the window that was closed. 0 for player inventory.
 +
|}
 +
 
 +
==== Plugin Message (serverbound) ====
 +
 
 +
{{Main|Plugin channels}}
 +
 
 +
Mods and plugins can use this to send their data. Minecraft itself uses some [[plugin channel]]s. These internal channels are in the <code>minecraft</code> namespace.
 +
 
 +
More documentation on this: [http://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/ http://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/]
 +
 
 +
Note that the length of Data is known only from the packet length, since the packet has no length field of any kind.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="2"| 0x0B
 +
|rowspan="2"| Play
 +
|rowspan="2"| Server
 +
| Channel
 +
| Identifier
 +
| Name of the [[plugin channel]] used to send the data
 +
|-
 +
| Data
 +
| Byte Array
 +
| Any data, depending on the channel. <code>minecraft:</code> channels are documented [[plugin channel|here]].  The length of this array must be inferred from the packet length.
 +
|}
 +
 
 +
==== Edit Book ====
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="3"| 0x0C
 +
|rowspan="3"| Play
 +
|rowspan="3"| Server
 +
| New book
 +
| [[Slot]]
 +
|
 +
|-
 +
| Is signing
 +
| Boolean
 +
| True if the player is signing the book; false if the player is saving a draft.
 +
|-
 +
| Hand
 +
| VarInt enum
 +
| 0: Main hand, 1: Off hand
 +
|}
 +
 
 +
When editing a draft, the [[NBT]] section of the Slot contains this:
 +
 
 +
<pre>
 +
TAG_Compound(<nowiki>''</nowiki>): 1 entry
 +
{
 +
  TAG_List('pages'): 2 entries
 +
  {
 +
    TAG_String(0): 'Something on Page 1'
 +
    TAG_String(1): 'Something on Page 2'
 +
  }
 +
}
 +
</pre>
 +
 
 +
When signing the book, it instead looks like this:
 +
 
 +
<pre>
 +
TAG_Compound(<nowiki>''</nowiki>): 3 entires
 +
{
 +
  TAG_String('author'): 'Steve'
 +
  TAG_String('title'): 'A Wonderful Book'
 +
  TAG_List('pages'): 2 entries
 +
  {
 +
    TAG_String(0): 'Something on Page 1'
 +
    TAG_String(1): 'Something on Page 2'
 +
  }
 +
}
 +
</pre>
 +
 
 +
==== Entity NBT Request ====
 +
 
 +
Used when <kbd>Shift</kbd>+<kbd>F3</kbd>+<kbd>I</kbd> is pressed while looking at an entity.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="2"| 0x0D
 +
|rowspan="2"| Play
 +
|rowspan="2"| Server
 +
| Transaction ID
 +
| VarInt
 +
| An incremental ID so that the client can verify that the response matches.
 +
|-
 +
| Entity ID
 +
| VarInt
 +
| The ID of the entity to query.
 +
|}
 +
 
 +
==== Interact Entity ====
 +
 
 +
This packet is sent from the client to the server when the client attacks or right-clicks another entity (a player, minecart, etc).
 +
 
 +
A Notchian server only accepts this packet if the entity being attacked/used is visible without obstruction and within a 4-unit radius of the player's position.
 +
 
 +
Note that middle-click in creative mode is interpreted by the client and sent as a [[#Creative Inventory Action|Creative Inventory Action]] packet instead.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="6"| 0x0E
 +
|rowspan="6"| Play
 +
|rowspan="6"| Server
 +
| Entity ID
 +
| VarInt
 +
| The ID of the entity to interact
 +
|-
 +
| Type
 +
| VarInt Enum
 +
| 0: interact, 1: attack, 2: interact at
 +
|-
 +
| Target X
 +
| Optional Float
 +
| Only if Type is interact at
 +
|-
 +
| Target Y
 +
| Optional Float
 +
| Only if Type is interact at
 +
|-
 +
| Target Z
 +
| Optional Float
 +
| Only if Type is interact at
 +
|-
 +
| Hand
 +
| Optional VarInt Enum
 +
| Only if Type is interact or interact at; 0: main hand, 1: off hand
 +
|}
 +
 
 +
==== Keep Alive (serverbound) ====
 +
 
 +
The server will frequently send out a keep-alive, each containing a random ID. The client must respond with the same packet.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
| 0x0F
 +
| Play
 +
| Server
 +
| Keep Alive ID
 +
| Long
 +
|
 +
|}
 +
 
 +
==== Lock Difficulty ====
 +
 
 +
Must have at least op level 2 to use.  Appears to only be used on singleplayer; the difficulty buttons are still disabled in multiplayer.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="1"| 0x10
 +
|rowspan="1"| Play
 +
|rowspan="1"| Server
 +
| Locked
 +
| Boolean
 +
|
 +
|}
 +
 
 +
==== Player Position ====
 +
 
 +
Updates the player's XYZ position on the server.
 +
 
 +
Checking for moving too fast is achieved like this:
 +
 
 +
* Each server tick, the player's current position is stored
 +
* When a player moves, the changes in x, y, and z coordinates are compared with the positions from the previous tick (&Delta;x, &Delta;y, &Delta;z)
 +
* Total movement distance squared is computed as &Delta;x&sup2; + &Delta;y&sup2; + &Delta;z&sup2;
 +
* The expected movement distance squared is computed as velocityX&sup2; + veloctyY&sup2; + velocityZ&sup2;
 +
* If the total movement distance squared value minus the expected movement distance squared value is more than 100 (300 if the player is using an elytra), they are moving too fast.
 +
 
 +
If the player is moving too fast, it will be logged that "<player> moved too quickly! " followed by the change in x, y, and z, and the player will be teleported back to their current (before this packet) serverside position.
 +
 
 +
Also, if the absolute value of X or the absolute value of Z is a value greater than 3.2×10<sup>7</sup>, or X, Y, or Z are not finite (either positive infinity, negative infinity, or NaN), the client will be kicked for “Invalid move player packet received”.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="4"| 0x11
 +
|rowspan="4"| Play
 +
|rowspan="4"| Server
 +
| X
 +
| Double
 +
| Absolute position
 +
|-
 +
| Feet Y
 +
| Double
 +
| Absolute feet position, normally Head Y - 1.62
 +
|-
 +
| Z
 +
| Double
 +
| Absolute position
 +
|-
 +
| On Ground
 +
| Boolean
 +
| True if the client is on the ground, false otherwise
 +
|}
 +
 
 +
==== Player Position And Rotation (serverbound) ====
 +
 
 +
A combination of [[#Player Rotation|Player Rotation]] and [[#Player Position|Player Position]].
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="6"| 0x12
 +
|rowspan="6"| Play
 +
|rowspan="6"| Server
 +
| X
 +
| Double
 +
| Absolute position
 +
|-
 +
| Feet Y
 +
| Double
 +
| Absolute feet position, normally Head Y - 1.62
 +
|-
 +
| Z
 +
| Double
 +
| Absolute position
 +
|-
 +
| Yaw
 +
| Float
 +
| Absolute rotation on the X Axis, in degrees
 +
|-
 +
| Pitch
 +
| Float
 +
| Absolute rotation on the Y Axis, in degrees
 +
|-
 +
| On Ground
 +
| Boolean
 +
| True if the client is on the ground, false otherwise
 +
|}
 +
 
 +
==== Player Rotation ====
 +
[[File:Minecraft-trig-yaw.png|thumb|The unit circle for yaw]]
 +
[[File:Yaw.png|thumb|The unit circle of yaw, redrawn]]
 +
 
 +
Updates the direction the player is looking in.
 +
 
 +
Yaw is measured in degrees, and does not follow classical trigonometry rules. The unit circle of yaw on the XZ-plane starts at (0, 1) and turns counterclockwise, with 90 at (-1, 0), 180 at (0,-1) and 270 at (1, 0). Additionally, yaw is not clamped to between 0 and 360 degrees; any number is valid, including negative numbers and numbers greater than 360.
 +
 
 +
Pitch is measured in degrees, where 0 is looking straight ahead, -90 is looking straight up, and 90 is looking straight down.
 +
 
 +
The yaw and pitch of player (in degrees), standing at point (x0, y0, z0) and looking towards point (x, y, z) can be calculated with:
 +
 
 +
dx = x-x0
 +
dy = y-y0
 +
dz = z-z0
 +
r = sqrt( dx*dx + dy*dy + dz*dz )
 +
yaw = -atan2(dx,dz)/PI*180
 +
if yaw < 0 then
 +
    yaw = 360 + yaw
 +
pitch = -arcsin(dy/r)/PI*180
 +
 
 +
You can get a unit vector from a given yaw/pitch via:
 +
 
 +
x = -cos(pitch) * sin(yaw)
 +
y = -sin(pitch)
 +
z =  cos(pitch) * cos(yaw)
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="3"| 0x13
 +
|rowspan="3"| Play
 +
|rowspan="3"| Server
 +
| Yaw
 +
| Float
 +
| Absolute rotation on the X Axis, in degrees
 +
|-
 +
| Pitch
 +
| Float
 +
| Absolute rotation on the Y Axis, in degrees
 +
|-
 +
| On Ground
 +
| Boolean
 +
| True if the client is on the ground, False otherwise
 +
|}
 +
 
 +
==== Player Movement ====
 +
 
 +
This packet as well as [[#Player Position|Player Position]], [[#Player Look|Player Look]], and [[#Player Position And Look 2|Player Position And Look]] are called the “serverbound movement packets”. Vanilla clients will send Player Position once every 20 ticks even for a stationary player.
 +
 
 +
This packet is used to indicate whether the player is on ground (walking/swimming), or airborne (jumping/falling).
 +
 
 +
When dropping from sufficient height, fall damage is applied when this state goes from false to true. The amount of damage applied is based on the point where it last changed from true to false. Note that there are several movement related packets containing this state.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="1"| 0x14
 +
|rowspan="1"| Play
 +
|rowspan="1"| Server
 +
| On Ground
 +
| Boolean
 +
| True if the client is on the ground, false otherwise
 +
|}
 +
 
 +
==== Vehicle Move (serverbound) ====
 +
 
 +
Sent when a player moves in a vehicle. Fields are the same as in [[#Player Position And Look (serverbound)|Player Position And Look]]. Note that all fields use absolute positioning and do not allow for relative positioning.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="5"| 0x15
 +
|rowspan="5"| Play
 +
|rowspan="5"| Server
 +
| X
 +
| Double
 +
| Absolute position (X coordinate)
 +
|-
 +
| Y
 +
| Double
 +
| Absolute position (Y coordinate)
 +
|-
 +
| Z
 +
| Double
 +
| Absolute position (Z coordinate)
 +
|-
 +
| Yaw
 +
| Float
 +
| Absolute rotation on the vertical axis, in degrees
 +
|-
 +
| Pitch
 +
| Float
 +
| Absolute rotation on the horizontal axis, in degrees
 +
|}
 +
 
 +
==== Steer Boat ====
 +
 
 +
Used to ''visually'' update whether boat paddles are turning.  The server will update the [[Entities#Boat|Boat entity metadata]] to match the values here.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="2"| 0x16
 +
|rowspan="2"| Play
 +
|rowspan="2"| Server
 +
| Left paddle turning
 +
| Boolean
 +
|
 +
|-
 +
| Right paddle turning
 +
| Boolean
 +
|
 +
|}
 +
 
 +
Right paddle turning is set to true when the left button or forward button is held; left paddle turning is set to true when the right button or forward button is set to true.
 +
 
 +
==== Pick Item ====
 +
 
 +
Used to swap out an empty space on the hotbar with the item in the given inventory slot.  The Notchain client uses this for pick block functionality (middle click) to retrieve items from the inventory.
 +
 
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="1"| 0x17
 +
|rowspan="1"| Play
 +
|rowspan="1"| Server
 +
| Slot to use
 +
| VarInt
 +
| See [[Inventory]]
 +
|}
 +
 
 +
The server will first search the player's hotbar for an empty slot, starting from the current slot and looping around to the slot before it.  If there are no empty slots, it will start a second search from the current slot and find the first slot that does not contain an enchanted item.  If there still are no slots that meet that criteria, then the server will use the currently selected slot.
 +
 
 +
After finding the appropriate slot, the server swaps the items and then send 3 packets:
 +
 
 +
* [[Protocol#Set slot|Set Slot]], with window ID set to -2 and slot set to the newly chosen slot and the item set to the item that is now in that slot (which was previously at the slot the client requested)
 +
* Set Slot, with window ID set to -2 and slot set to the slot the player requested, with the item that is now in that slot and was previously on the hotbar slot
 +
* [[Protocol#Held_Item_Change_.28clientbound.29|Held Item Change]], with the slot set to the newly chosen slot.
 +
 
 +
==== Craft Recipe Request ====
 +
 
 +
This packet is sent when a player clicks a recipe in the crafting book that is craftable (white border).
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="3"| 0x18
 +
|rowspan="3"| Play
 +
|rowspan="3"| Server
 +
| Window ID
 +
| Byte
 +
|
 +
|-
 +
| Recipe
 +
| Identifier
 +
| A recipe ID
 +
|-
 +
| Make all
 +
| Boolean
 +
| Affects the amount of items processed; true if shift is down when clicked
 +
|}
 +
 
 +
==== Player Abilities (serverbound) ====
 +
 
 +
The latter 2 fields are used to indicate the walking and flying speeds respectively, while the first field is used to determine the value of 4 booleans.
 +
 
 +
The vanilla client sends this packet when the player starts/stops flying with the Flags parameter changed accordingly. All other parameters are ignored by the vanilla server.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="3"| 0x19
 +
|rowspan="3"| Play
 +
|rowspan="3"| Server
 +
| Flags
 +
| Byte
 +
| Bit mask. 0x08: damage disabled (god mode), 0x04: can fly, 0x02: is flying, 0x01: is Creative
 +
|-
 +
| Flying Speed
 +
| Float
 +
|
 +
|-
 +
| Walking Speed
 +
| Float
 +
|
 +
|}
 +
 
 +
==== Player Digging ====
 +
 
 +
Sent when the player mines a block. A Notchian server only accepts digging packets with coordinates within a 6-unit radius between the center of the block and 1.5 units from the player's feet (''not'' their eyes).
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="3"| 0x1A
 +
|rowspan="3"| Play
 +
|rowspan="3"| Server
 +
| Status
 +
| VarInt Enum
 +
| The action the player is taking against the block (see below)
 +
|-
 +
| Location
 +
| Position
 +
| Block position
 +
|-
 +
| Face
 +
| Byte Enum
 +
| The face being hit (see below)
 +
|}
 +
 
 +
Status can be one of seven values:
 +
 
 +
{| class="wikitable"
 +
! Value
 +
! Meaning
 +
! Notes
 +
|-
 +
| 0
 +
| Started digging
 +
|
 +
|-
 +
| 1
 +
| Cancelled digging
 +
| Sent when the player lets go of the Mine Block key (default: left click)
 +
|-
 +
| 2
 +
| Finished digging
 +
| Sent when the client thinks it is finished
 +
|-
 +
| 3
 +
| Drop item stack
 +
| Triggered by using the Drop Item key (default: Q) with the modifier to drop the entire selected stack (default: depends on OS). Location is always set to 0/0/0, Face is always set to -Y.
 +
|-
 +
| 4
 +
| Drop item
 +
| Triggered by using the Drop Item key (default: Q). Location is always set to 0/0/0, Face is always set to -Y.
 +
|-
 +
| 5
 +
| Shoot arrow / finish eating
 +
| Indicates that the currently held item should have its state updated such as eating food, pulling back bows, using buckets, etc. Location is always set to 0/0/0, Face is always set to -Y.
 +
|-
 +
| 6
 +
| Swap item in hand
 +
| Used to swap or assign an item to the second hand. Location is always set to 0/0/0, Face is always set to -Y.
 +
|}
 +
 
 +
The Face field can be one of the following values, representing the face being hit:
 +
 
 +
{| class="wikitable"
 +
|-
 +
! Value
 +
! Offset
 +
! Face
 +
|-
 +
| 0
 +
| -Y
 +
| Bottom
 +
|-
 +
| 1
 +
| +Y
 +
| Top
 +
|-
 +
| 2
 +
| -Z
 +
| North
 +
|-
 +
| 3
 +
| +Z
 +
| South
 +
|-
 +
| 4
 +
| -X
 +
| West
 +
|-
 +
| 5
 +
| +X
 +
| East
 +
|}
 +
 
 +
==== Entity Action ====
 +
 
 +
Sent by the client to indicate that it has performed certain actions: sneaking (crouching), sprinting, exiting a bed, jumping with a horse, and opening a horse's inventory while riding it.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="3"| 0x1B
 +
|rowspan="3"| Play
 +
|rowspan="3"| Server
 +
| Entity ID
 +
| VarInt
 +
| Player ID
 +
|-
 +
| Action ID
 +
| VarInt Enum
 +
| The ID of the action, see below
 +
|-
 +
| Jump Boost
 +
| VarInt
 +
| Only used by the “start jump with horse” action, in which case it ranges from 0 to 100. In all other cases it is 0.
 +
|}
 +
 
 +
Action ID can be one of the following values:
 +
 
 +
{| class="wikitable"
 +
! ID
 +
! Action
 +
|-
 +
| 0
 +
| Start sneaking
 +
|-
 +
| 1
 +
| Stop sneaking
 +
|-
 +
| 2
 +
| Leave bed
 +
|-
 +
| 3
 +
| Start sprinting
 +
|-
 +
| 4
 +
| Stop sprinting
 +
|-
 +
| 5
 +
| Start jump with horse
 +
|-
 +
| 6
 +
| Stop jump with horse
 +
|-
 +
| 7
 +
| Open horse inventory
 +
|-
 +
| 8
 +
| Start flying with elytra
 +
|}
 +
 
 +
Leave bed is only sent when the “Leave Bed” button is clicked on the sleep GUI, not when waking up due today time.
 +
 
 +
Open horse inventory is only sent when pressing the inventory key (default: E) while on a horse — all other methods of opening a horse's inventory (involving right-clicking or shift-right-clicking it) do not use this packet.
 +
 
 +
==== Steer Vehicle ====
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="3"| 0x1C
 +
|rowspan="3"| Play
 +
|rowspan="3"| Server
 +
| Sideways
 +
| Float
 +
| Positive to the left of the player
 +
|-
 +
| Forward
 +
| Float
 +
| Positive forward
 +
|-
 +
| Flags
 +
| Unsigned Byte
 +
| Bit mask. 0x1: jump, 0x2: unmount
 +
|}
 +
 
 +
Also known as 'Input' packet.
 +
 
 +
==== Recipe Book Data ====
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
!colspan="2"| Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="11"| 0x1D
 +
|rowspan="11"| Play
 +
|rowspan="11"| Server
 +
|colspan="2"| Type
 +
| VarInt
 +
| Determines the format of the rest of the packet
 +
|-
 +
! Type
 +
! Field Name
 +
!
 +
!
 +
|-
 +
| 0: Displayed Recipe
 +
| Recipe ID
 +
| Identifier
 +
| A recipe ID
 +
|-
 +
|rowspan="4"| 1: Recipe Book States
 +
| Crafting Recipe Book Open
 +
| Boolean
 +
| Whether the player has the crafting recipe book currently opened/active.
 +
|-
 +
| Crafting Recipe Filter Active
 +
| Boolean
 +
| Whether the player has the crafting recipe book filter option currently active.
 +
|-
 +
| Smelting Recipe Book Open
 +
| Boolean
 +
| Whether the player has the smelting recipe book currently opened/active.
 +
|-
 +
| Smelting Recipe Filter Active
 +
| Boolean
 +
| Whether the player has the smelting recipe book filter option currently active.
 +
|-
 +
| Blasting Recipe Book Open
 +
| Boolean
 +
| May be swapped with smoking recipe book.  Also, the notchian client appears to use the same value for both of those books currently.
 +
|-
 +
| Blasting Recipe Filter Active
 +
| Boolean
 +
| May be swapped with smoking recipe book.  Also, the notchian client appears to use the same value for both of those books currently.
 +
|-
 +
| Smoking Recipe Book Open
 +
| Boolean
 +
|
 +
|-
 +
| Smoking Recipe Filter Active
 +
| Boolean
 +
|
 +
|}
 +
 
 +
The Recipe Book Status type is sent when one of the states changes.
 +
 
 +
==== Name Item ====
 +
 
 +
Sent as a player is renaming an item in an anvil (each keypress in the anvil UI sends a new Name Item packet).  If the new name is empty, then the item loses its custom name (this is different from setting the custom name to the normal name of the item).  The item name may be no longer than 35 characters long, and if it is longer than that, then the rename is silently ignored.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="1"| 0x1E
 +
|rowspan="1"| Play
 +
|rowspan="1"| Server
 +
| Item name
 +
| String (32767)
 +
| The new name of the item
 +
|}
 +
 
 +
==== Resource Pack Status ====
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="1"| 0x1F
 +
|rowspan="1"| Play
 +
|rowspan="1"| Server
 +
| Result
 +
| VarInt Enum
 +
| 0: successfully loaded, 1: declined, 2: failed download, 3: accepted
 +
|}
 +
 
 +
==== Advancement Tab ====
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="2"| 0x20
 +
|rowspan="2"| Play
 +
|rowspan="2"| Server
 +
| Action
 +
| VarInt enum
 +
| 0: Opened tab, 1: Closed screen
 +
|-
 +
| Tab ID
 +
| Optional identifier
 +
| Only present if action is Opened tab
 +
|}
 +
 
 +
==== Select Trade ====
 +
 
 +
When a player selects a specific trade offered by a villager NPC.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="1"| 0x21
 +
|rowspan="1"| Play
 +
|rowspan="1"| Server
 +
| Selected slot
 +
| VarInt
 +
| The selected slot int the players current (trading) inventory. (Was a full Integer for the plugin message)
 +
|}
 +
 
 +
==== Set Beacon Effect ====
 +
 
 +
Changes the effect of the current beacon.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="2"| 0x22
 +
|rowspan="2"| Play
 +
|rowspan="2"| Server
 +
| Primary Effect
 +
| VarInt
 +
| A [http://minecraft.gamepedia.com/Data_values#Potions Potion ID]. (Was a full Integer for the plugin message)
 +
|-
 +
| Secondary Effect
 +
| VarInt
 +
| A [http://minecraft.gamepedia.com/Data_values#Potions Potion ID]. (Was a full Integer for the plugin message)
 +
|}
 +
 
 +
==== Held Item Change (serverbound) ====
 +
 
 +
Sent when the player changes the slot selection
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="1"| 0x23
 +
|rowspan="1"| Play
 +
|rowspan="1"| Server
 +
| Slot
 +
| Short
 +
| The slot which the player has selected (0–8)
 +
|}
 +
 
 +
==== Update Command Block ====
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="5"| 0x24
 +
|rowspan="5"| Play
 +
|rowspan="5"| Server
 +
|-
 +
| Location
 +
| Position
 +
|
 +
|-
 +
| Command
 +
| String (32767)
 +
|
 +
|-
 +
| Mode || VarInt enum || One of SEQUENCE (0), AUTO (1), or REDSTONE (2)
 +
|-
 +
| Flags
 +
| Byte
 +
| 0x01: Track Output (if false, the output of the previous command will not be stored within the command block); 0x02: Is conditional; 0x04: Automatic
 +
|}
 +
 
 +
==== Update Command Block Minecart ====
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="3"| 0x25
 +
|rowspan="3"| Play
 +
|rowspan="3"| Server
 +
| Entity ID
 +
| VarInt
 +
|
 +
|-
 +
| Command
 +
| String
 +
|
 +
|-
 +
| Track Output
 +
| Boolean
 +
| If false, the output of the previous command will not be stored within the command block.
 +
|}
 +
 
 +
==== Creative Inventory Action ====
 +
 
 +
While the user is in the standard inventory (i.e., not a crafting bench) in Creative mode, the player will send this packet.
 +
 
 +
Clicking in the creative inventory menu is quite different from non-creative inventory management. Picking up an item with the mouse actually deletes the item from the server, and placing an item into a slot or dropping it out of the inventory actually tells the server to create the item from scratch. (This can be verified by clicking an item that you don't mind deleting, then severing the connection to the server; the item will be nowhere to be found when you log back in.) As a result of this implementation strategy, the "Destroy Item" slot is just a client-side implementation detail that means "I don't intend to recreate this item.". Additionally, the long listings of items (by category, etc.) are a client-side interface for choosing which item to create. Picking up an item from such listings sends no packets to the server; only when you put it somewhere does it tell the server to create the item in that location.
 +
 
 +
This action can be described as "set inventory slot". Picking up an item sets the slot to item ID -1. Placing an item into an inventory slot sets the slot to the specified item. Dropping an item (by clicking outside the window) effectively sets slot -1 to the specified item, which causes the server to spawn the item entity, etc.. All other inventory slots are numbered the same as the non-creative inventory (including slots for the 2x2 crafting menu, even though they aren't visible in the vanilla client).
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="2"| 0x26
 +
|rowspan="2"| Play
 +
|rowspan="2"| Server
 +
| Slot
 +
| Short
 +
| Inventory slot
 +
|-
 +
| Clicked Item
 +
| [[Slot Data|Slot]]
 +
|
 +
|}
 +
 
 +
==== Update Jigsaw Block ====
 +
 
 +
Sent when Done is pressed on the {{Minecraft Wiki|Jigsaw Block}} interface.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="4"| 0x27
 +
|rowspan="4"| Play
 +
|rowspan="4"| Server
 +
| Location
 +
| Position
 +
| Block entity location
 +
|-
 +
| Attachment type
 +
| Identifier
 +
|
 +
|-
 +
| Target pool
 +
| Identifier
 +
|
 +
|-
 +
| Final state
 +
| String
 +
| "Turns into" on the GUI, <code>final_state</code> in NBT
 +
|}
 +
 
 +
==== Update Structure Block ====
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="17"| 0x28
 +
|rowspan="17"| Play
 +
|rowspan="17"| Server
 +
|-
 +
| Location
 +
| Position
 +
| Block entity location
 +
|-
 +
| Action
 +
| VarInt enum
 +
| An additional action to perform beyond simply saving the given data; see below
 +
|-
 +
| Mode
 +
| VarInt enum
 +
| One of SAVE (0), LOAD (1), CORNER (2), DATA (3).
 +
|-
 +
| Name
 +
| String
 +
|
 +
|-
 +
| Offset X || Byte
 +
| Between -32 and 32
 +
|-
 +
| Offset Y || Byte
 +
| Between -32 and 32
 +
|-
 +
| Offset Z || Byte
 +
| Between -32 and 32
 +
|-
 +
| Size X || Byte
 +
| Between 0 and 32
 +
|-
 +
| Size Y || Byte
 +
| Between 0 and 32
 +
|-
 +
| Size Z || Byte
 +
| Between 0 and 32
 +
|-
 +
| Mirror
 +
| VarInt enum
 +
| One of NONE (0), LEFT_RIGHT (1), FRONT_BACK (2).
 +
|-
 +
| Rotation
 +
| VarInt enum
 +
| One of NONE (0), CLOCKWISE_90 (1), CLOCKWISE_180 (2), COUNTERCLOCKWISE_90 (3).
 +
|-
 +
| Metadata
 +
| String
 +
|
 +
|-
 +
| Integrity
 +
| Float
 +
| Between 0 and 1
 +
|-
 +
|Seed
 +
|VarLong
 +
|
 +
|-
 +
| Flags
 +
| Byte
 +
| 0x01: Ignore entities; 0x02: Show air; 0x04: Show bounding box
 +
|}
 +
 
 +
Possible actions:
 +
 
 +
* 0 - Update data
 +
* 1 - Save the structure
 +
* 2 - Load the structure
 +
* 3 - Detect size
 +
 
 +
The Notchian client uses update data to indicate no special action should be taken (i.e. the done button).
 +
 
 +
==== Update Sign ====
 +
 
 +
{{anchor|Update Sign (serverbound)}}This message is sent from the client to the server when the “Done” button is pushed after placing a sign.
 +
 
 +
The server only accepts this packet after [[#Open Sign Editor|Open Sign Editor]], otherwise this packet is silently ignored.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="5"| 0x29
 +
|rowspan="5"| Play
 +
|rowspan="5"| Server
 +
| Location
 +
| Position
 +
| Block Coordinates
 +
|-
 +
| Line 1
 +
| String (384)
 +
| First line of text in the sign
 +
|-
 +
| Line 2
 +
| String (384)
 +
| Second line of text in the sign
 +
|-
 +
| Line 3
 +
| String (384)
 +
| Third line of text in the sign
 +
|-
 +
| Line 4
 +
| String (384)
 +
| Fourth line of text in the sign
 +
|}
 +
 
 +
==== Animation (serverbound) ====
 +
 
 +
Sent when the player's arm swings.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
| 0x2A
 +
| Play
 +
| Server
 +
| Hand
 +
| VarInt Enum
 +
| Hand used for the animation. 0: main hand, 1: off hand.
 +
|}
 +
 
 +
==== Spectate ====
 +
 
 +
Teleports the player to the given entity.  The player must be in spectator mode.
 +
 
 +
The Notchian client only uses this to teleport to players, but it appears to accept any type of entity.  The entity does not need to be in the same dimension as the player; if necessary, the player will be respawned in the right world.  If the given entity cannot be found (or isn't loaded), this packet will be ignored.  It will also be ignored if the player attempts to teleport to themselves.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="1"| 0x2B
 +
|rowspan="1"| Play
 +
|rowspan="1"| Server
 +
| Target Player
 +
| UUID
 +
| UUID of the player to teleport to (can also be an entity UUID)
 +
|}
 +
 
 +
==== Player Block Placement ====
 +
 
 +
{| class="wikitable"
 +
|-
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="7"| 0x2C
 +
|rowspan="7"| Play
 +
|rowspan="7"| Server
 +
| Hand
 +
| VarInt Enum
 +
| The hand from which the block is placed; 0: main hand, 1: off hand
 +
|-
 +
| Location
 +
| Position
 +
| Block position
 +
|-
 +
| Face
 +
| VarInt Enum
 +
| The face on which the block is placed (as documented at [[#Player Digging|Player Digging]])
 +
|-
 +
| Cursor Position X
 +
| Float
 +
| The position of the crosshair on the block, from 0 to 1 increasing from west to east
 +
|-
 +
| Cursor Position Y
 +
| Float
 +
| The position of the crosshair on the block, from 0 to 1 increasing from bottom to top
 +
|-
 +
| Cursor Position Z
 +
| Float
 +
| The position of the crosshair on the block, from 0 to 1 increasing from north to south
 +
|-
 +
| Inside block
 +
| Boolean
 +
| True when the player's head is inside of a block.
 +
|}
 +
 
 +
Upon placing a block, this packet is sent once.
 +
 
 +
The Cursor Position X/Y/Z fields (also known as in-block coordinates) are calculated using raytracing. The unit corresponds to sixteen pixels in the default resource pack. For example, let's say a slab is being placed against the south face of a full block. The Cursor Position X will be higher if the player was pointing near the right (east) edge of the face, lower if pointing near the left. The Cursor Position Y will be used to determine whether it will appear as a bottom slab (values 0.0–0.5) or as a top slab (values 0.5-1.0). The Cursor Position Z should be 1.0 since the player was looking at the southernmost part of the block.
 +
 
 +
Inside block is true when a player's head (specifically eyes) are inside of a block's collision. In 1.13 and later versions, collision is rather complicated and individual blocks can have multiple collision boxes. For instance, a ring of vines has a non-colliding hole in the middle. This value is only true when the player is directly in the box. In practice, though, this value is only used by scaffolding to place in front of the player when sneaking inside of it (other blocks will place behind when you intersect with them -- try with glass for instance).
 +
 
 +
==== Use Item ====
 +
 
 +
Sent when pressing the Use Item key (default: right click) with an item in hand.
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
| 0x2D
 +
| Play
 +
| Server
 +
| Hand
 +
| VarInt Enum
 +
| Hand used for the animation. 0: main hand, 1: off hand.
 +
|}
 +
 
 +
== Status ==
 +
{{Main|Server List Ping}}
 +
 
 +
=== Clientbound ===
 +
 
 +
==== Response ====
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="1"| 0x00
 +
|rowspan="1"| Status
 +
|rowspan="1"| Client
 +
| JSON Response
 +
| String (32767)
 +
| See [[Server List Ping#Response]]
 +
|}
 +
 
 +
==== Pong ====
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="1"| 0x01
 +
|rowspan="1"| Status
 +
|rowspan="1"| Client
 +
| Payload
 +
| Long
 +
| Should be the same as sent by the client
 +
|}
 +
 
 +
=== Serverbound ===
 +
 
 +
==== Request ====
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 +
|-
 +
|rowspan="1"| 0x00
 +
| Status
 +
| Server
 +
|colspan="3"| ''no fields''
 +
|}
 +
 
 +
==== Ping ====
 +
 
 +
{| class="wikitable"
 
  ! Packet ID
 
  ! Packet ID
 
  ! State
 
  ! State
Line 5,514: Line 7,166:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  | 0x20
+
  |rowspan="1"| 0x01
  | Play
+
  |rowspan="1"| Status
  | Server
+
  |rowspan="1"| Server
  | Hand
+
  | Payload
  | VarInt Enum
+
  | Long
  | Hand used for the animation. 0: main hand, 1: off hand.
+
  | May be any number. Notchian clients use a system-dependent time value which is counted in milliseconds.
 
  |}
 
  |}
  
== Status ==
+
== Login ==
{{Main|Server List Ping}}
+
 
 +
The login process is as follows:
 +
 
 +
# C→S: [[#Handshake|Handshake]] with Next State set to 2 (login)
 +
# C→S: [[#Login Start|Login Start]]
 +
# S→C: [[#Encryption Request|Encryption Request]]
 +
# Client auth
 +
# C→S: [[#Encryption Response|Encryption Response]]
 +
# Server auth, both enable encryption
 +
# S→C: [[#Set Compression|Set Compression]] (optional)
 +
# S→C: [[#Login Success|Login Success]]
 +
 
 +
Set Compression, if present, must be sent before Login Success. Note that anything sent after Set Compression must use the [[#With_compression|Post Compression packet format]].
 +
 
 +
For unauthenticated and localhost connections (either of the two conditions is enough for an unencrypted connection) there is no encryption. In that case [[#Login Start|Login Start]] is directly followed by [[#Login Success|Login Success]].
 +
 
 +
See [[Protocol Encryption]] for details.
  
 
=== Clientbound ===
 
=== Clientbound ===
  
==== Response ====
+
==== Disconnect (login) ====
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,538: Line 7,206:
 
  |-
 
  |-
 
  |rowspan="1"| 0x00
 
  |rowspan="1"| 0x00
  |rowspan="1"| Status
+
  |rowspan="1"| Login
 
  |rowspan="1"| Client
 
  |rowspan="1"| Client
  | JSON Response
+
  | Reason
  | String (32767)
+
  | [[Chat]]
| See [[Server List Ping#Response]]
+
|
 
  |}
 
  |}
  
==== Pong ====
+
==== Encryption Request ====
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,555: Line 7,223:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="1"| 0x01
+
  |rowspan="5"| 0x01
  |rowspan="1"| Status
+
  |rowspan="5"| Login
  |rowspan="1"| Client
+
  |rowspan="5"| Client
  | Payload
+
  | Server ID
  | Long
+
  | String (20)
  | Should be the same as sent by the client
+
  | Appears to be empty
 +
|-
 +
| Public Key Length
 +
| VarInt
 +
| Length of Public Key
 +
|-
 +
| Public Key
 +
| Byte Array
 +
|
 +
|-
 +
| Verify Token Length
 +
| VarInt
 +
| Length of Verify Token. Always 4 for Notchian servers.
 +
|-
 +
| Verify Token
 +
| Byte Array
 +
| A sequence of random bytes generated by the server
 
  |}
 
  |}
  
=== Serverbound ===
+
See [[Protocol Encryption]] for details.
  
==== Request ====
+
==== Login Success ====
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,575: Line 7,259:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="1"| 0x00
+
  |rowspan="2"| 0x02
  | Status
+
  |rowspan="2"| Login
| Server
+
  |rowspan="2"| Client
  |colspan="3"| ''no fields''
+
| UUID
  |}
+
| String (36)
 +
| Unlike in other packets, this field contains the UUID as a string with hyphens.
 +
|-
 +
| Username
 +
| String (16)
 +
|
 +
  |}
  
==== Ping ====
+
This packet switches the connection state to [[#Play|play]].
 +
 
 +
==== Set Compression ====
 +
 
 +
Enables compression.  If compression is enabled, all following packets are encoded in the [[#With compression|compressed packet format]].  Negative values will disable compression, meaning the packet format should remain in the [[#Without compression|uncompressed packet format]].  However, this packet is entirely optional, and if not sent, compression will also not be enabled (the notchian server does not send the packet when compression is disabled).
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,591: Line 7,285:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="1"| 0x01
+
  |rowspan="1"| 0x03
  |rowspan="1"| Status
+
  |rowspan="1"| Login
  |rowspan="1"| Server
+
  |rowspan="1"| Client
  | Payload
+
  | Threshold
  | Long
+
  | VarInt
  | May be any number. Notchian clients use a system-dependent time value which is counted in milliseconds.
+
  | Maximum size of a packet before it is compressed
 
  |}
 
  |}
  
== Login ==
+
==== Login Plugin Request ====
  
The login process is as follows:
+
Used to implement a custom handshaking flow together with [[#Login_Plugin_Response | Login Plugin Response]].
  
# C→S: [[#Handshake|Handshake]] with Next State set to 2 (login)
+
Unlike plugin messages in "play" mode, these messages follow a lock-step request/response scheme, where the client is expected to respond to a request indicating whether it understood. The notchian client always responds that it hasn't understood, and sends an empty payload.
# C→S: [[#Login Start|Login Start]]
 
# S→C: [[#Encryption Request|Encryption Request]]
 
# Client auth
 
# C→S: [[#Encryption Response|Encryption Response]]
 
# Server auth, both enable encryption
 
# S→C: [[#Set Compression|Set Compression]] (optional)
 
# S→C: [[#Login Success|Login Success]]
 
 
 
Set Compression, if present, must be sent before Login Success. Note that anything sent after Set Compression must use the [[#With_compression|Post Compression packet format]].
 
 
 
For unauthenticated and localhost connections (either of the two conditions is enough for an unencrypted connection) there is no encryption. In that case [[#Login Start|Login Start]] is directly followed by [[#Login Success|Login Success]].
 
 
 
See [[Protocol Encryption]] for details.
 
 
 
=== Clientbound ===
 
 
 
==== Disconnect (login) ====
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,630: Line 7,307:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="1"| 0x00
+
  |rowspan="3"| 0x04
  |rowspan="1"| Login
+
  |rowspan="3"| Login
  |rowspan="1"| Client
+
  |rowspan="3"| Client
  | Reason
+
  | Message ID
  | [[Chat]]
+
  | VarInt
  |  
+
| Generated by the server - should be unique to the connection.
 +
|-
 +
| Channel
 +
| Identifier
 +
| Name of the [[plugin channel]] used to send the data
 +
|-
 +
| Data
 +
| Byte Array
 +
  | Any data, depending on the channel. The length of this array must be inferred from the packet length.
 
  |}
 
  |}
  
==== Encryption Request ====
+
=== Serverbound ===
 +
 
 +
==== Login Start  ====
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,648: Line 7,335:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="5"| 0x01
+
  |rowspan="1"| 0x00
  |rowspan="5"| Login
+
  |rowspan="1"| Login
  |rowspan="5"| Client
+
  |rowspan="1"| Server
  | Server ID
+
  | Name
  | String (20)
+
  | String (16)
  | Appears to be empty
+
  | Player's Username
 +
|}
 +
 
 +
==== Encryption Response ====
 +
 
 +
{| class="wikitable"
 +
! Packet ID
 +
! State
 +
! Bound To
 +
! Field Name
 +
! Field Type
 +
! Notes
 
  |-
 
  |-
  | Public Key Length
+
  |rowspan="4"| 0x01
 +
|rowspan="4"| Login
 +
|rowspan="4"| Server
 +
| Shared Secret Length
 
  | VarInt
 
  | VarInt
  | Length of Public Key
+
  | Length of Shared Secret
 
  |-
 
  |-
  | Public Key
+
  | Shared Secret
 
  | Byte Array
 
  | Byte Array
 
  |  
 
  |  
Line 5,665: Line 7,366:
 
  | Verify Token Length
 
  | Verify Token Length
 
  | VarInt
 
  | VarInt
  | Length of Verify Token. Always 4 for Notchian servers.
+
  | Length of Verify Token
 
  |-
 
  |-
 
  | Verify Token
 
  | Verify Token
 
  | Byte Array
 
  | Byte Array
  | A sequence of random bytes generated by the server
+
  |  
 
  |}
 
  |}
  
 
See [[Protocol Encryption]] for details.
 
See [[Protocol Encryption]] for details.
  
==== Login Success ====
+
==== Login Plugin Response ====
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 5,684: Line 7,385:
 
  ! Notes
 
  ! Notes
 
  |-
 
  |-
  |rowspan="2"| 0x02
+
  |rowspan="3"| 0x02
  |rowspan="2"| Login
+
  |rowspan="3"| Login
  |rowspan="2"| Client
+
  |rowspan="3"| Server
  | UUID
+
  | Message ID
| String (36)
 
| Unlike in other packets, this field contains the UUID as a string with hyphens.
 
|-
 
| Username
 
| String (16)
 
|
 
|}
 
 
 
This packet switches the connection state to [[#Play|play]].
 
 
 
==== Set Compression ====
 
 
 
Enables compression.  If compression is enabled, all following packets are encoded in the [[#With compression|compressed packet format]].  Negative values will disable compression, meaning the packet format should remain in the [[#Without compression|uncompressed packet format]].  However, this packet is entirely optional, and if not sent, compression will also not be enabled (the notchian server does not send the packet when compression is disabled).
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
|-
 
|rowspan="1"| 0x03
 
|rowspan="1"| Login
 
|rowspan="1"| Client
 
| Threshold
 
 
  | VarInt
 
  | VarInt
  | Maximum size of a packet before it is compressed
+
  | Should match ID from server.
|}
 
 
 
=== Serverbound ===
 
 
 
==== Login Start  ====
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="1"| 0x00
+
  | Successful
|rowspan="1"| Login
+
  | Boolean
|rowspan="1"| Server
+
  | <code>true</code> if the client understands the request, <code>false</code> otherwise. When <code>false</code>, no payload follows.
| Name
 
| String (16)
 
  | Player's Username
 
  |}
 
 
 
==== Encryption Response ====
 
 
 
{| class="wikitable"
 
! Packet ID
 
! State
 
! Bound To
 
! Field Name
 
! Field Type
 
! Notes
 
 
  |-
 
  |-
  |rowspan="4"| 0x01
+
  | Data
|rowspan="4"| Login
+
  | Optional Byte Array
|rowspan="4"| Server
+
  | Any data, depending on the channel. The length of this array must be inferred from the packet length.
| Shared Secret Length
 
| VarInt
 
| Length of Shared Secret
 
|-
 
| Shared Secret
 
  | Byte Array
 
  |  
 
|-
 
| Verify Token Length
 
| VarInt
 
| Length of Verify Token
 
|-
 
| Verify Token
 
| Byte Array
 
|
 
 
  |}
 
  |}
 
See [[Protocol Encryption]] for details.
 
  
 
[[Category:Protocol Details]]
 
[[Category:Protocol Details]]
 
[[Category:Minecraft Modern]]
 
[[Category:Minecraft Modern]]

Revision as of 03:07, 14 February 2020

Heads up!

This article is about the protocol for the latest stable release of Minecraft computer edition (1.15.2, protocol 578). For the computer edition pre-releases, see Pre-release protocol. For Pocket Edition, see Pocket Edition Protocol Documentation.

This page presents a dissection of the current Minecraft protocol.

If you're having trouble, check out the FAQ or ask for help in the IRC channel #mcdevs on chat.freenode.net (More Information).

Note: While you may use the contents of this page without restriction to create servers, clients, bots, etc… you still need to provide attribution to #mcdevs if you copy any of the contents of this page for publication elsewhere.

The changes between versions may be viewed at Protocol History.

Contents

Definitions

The Minecraft server accepts connections from TCP clients and communicates with them using packets. A packet is a sequence of bytes sent over the TCP connection. The meaning of a packet depends both on its packet ID and the current state of the connection. The initial state of each connection is Handshaking, and state is switched using the packets Handshake and Login Success.

Data types

All data sent over the network (except for VarInt and VarLong) is big-endian, that is the bytes are sent from most significant byte to least significant byte. The majority of everyday computers are little-endian, therefore it may be necessary to change the endianness before sending data over the network.


Name Size (bytes) Encodes Notes
Boolean 1 Either false or true True is encoded as 0x01, false as 0x00.
Byte 1 An integer between -128 and 127 Signed 8-bit integer, two's complement
Unsigned Byte 1 An integer between 0 and 255 Unsigned 8-bit integer
Short 2 An integer between -32768 and 32767 Signed 16-bit integer, two's complement
Unsigned Short 2 An integer between 0 and 65535 Unsigned 16-bit integer
Int 4 An integer between -2147483648 and 2147483647 Signed 32-bit integer, two's complement
Long 8 An integer between -9223372036854775808 and 9223372036854775807 Signed 64-bit integer, two's complement
Float 4 A single-precision 32-bit IEEE 754 floating point number
Double 8 A double-precision 64-bit IEEE 754 floating point number
String (n) ≥ 1
≤ (n×3) + 3
A sequence of Unicode scalar values UTF-8 string prefixed with its size in bytes as a VarInt. Maximum length of n characters, which varies by context. The encoding used on the wire is regular UTF-8, not Java's "slight modification". However, the length of the string for purposes of the length limit is its number of UTF-16 code units, that is, scalar values > U+FFFF are counted as two. Up to n × 3 bytes can be used to encode a UTF-8 string comprising n code units when converted to UTF-16, and both of those limits are checked. Maximum n value is 32767. The + 3 is due to the max size of a valid length VarInt.
Text Component Varies See Text formatting#Text components Encoded as a NBT Tag, with the type of tag used depending on the case:
  • As a String Tag: For components only containing text (no styling, no events etc.).
  • As a Compound Tag: Every other case.
JSON Text Component ≥ 1
≤ (262144×3) + 3
See Text formatting#Text components Encoded as a String with max length of 262144.
Identifier ≥ 1
≤ (32767×3) + 3
See Identifier below Encoded as a String with max length of 32767.
VarInt ≥ 1
≤ 5
An integer between -2147483648 and 2147483647 Variable-length data encoding a two's complement signed 32-bit integer; more info in their section
VarLong ≥ 1
≤ 10
An integer between -9223372036854775808 and 9223372036854775807 Variable-length data encoding a two's complement signed 64-bit integer; more info in their section
Entity Metadata Varies Miscellaneous information about an entity See Entity_metadata#Entity Metadata Format
Slot Varies An item stack in an inventory or container See Slot Data
NBT Varies Depends on context See NBT
Position 8 An integer/block position: x (-33554432 to 33554431), z (-33554432 to 33554431), y (-2048 to 2047) x as a 26-bit integer, followed by z as a 26-bit integer, followed by y as a 12-bit integer (all signed, two's complement). See also the section below.
Angle 1 A rotation angle in steps of 1/256 of a full turn Whether or not this is signed does not matter, since the resulting angles are the same.
UUID 16 A UUID Encoded as an unsigned 128-bit integer (or two unsigned 64-bit integers: the most significant 64 bits and then the least significant 64 bits)
BitSet Varies See #BitSet below A length-prefixed bit set.
Fixed BitSet (n) n See #Fixed BitSet below A bit set with a fixed length of n bits.
Optional X 0 or size of X A field of type X, or nothing Whether or not the field is present must be known from the context.
Array of X count times size of X Zero or more fields of type X The count must be known from the context.
X Enum size of X A specific value from a given list The list of possible values and how each is encoded as an X must be known from the context. An invalid value sent by either side will usually result in the client being disconnected with an error or even crashing.
Byte Array Varies Depends on context This is just a sequence of zero or more bytes, its meaning should be explained somewhere else, e.g. in the packet description. The length must also be known from the context.

Identifier

Identifiers are a namespaced location, in the form of minecraft:thing. If the namespace is not provided, it defaults to minecraft (i.e. thing is minecraft:thing). Custom content should always be in its own namespace, not the default one. Both the namespace and value can use all lowercase alphanumeric characters (a-z and 0-9), dot (.), dash (-), and underscore (_). In addition, values can use slash (/). The naming convention is lower_case_with_underscores. More information. For ease of determining whether a namespace or value is valid, here are regular expressions for each:

  • Namespace: [a-z0-9.-_]
  • Value: [a-z0-9.-_/]

VarInt and VarLong

Variable-length format such that smaller numbers use fewer bytes. These are very similar to Protocol Buffer Varints: the 7 least significant bits are used to encode the value and the most significant bit indicates whether there's another byte after it for the next part of the number. The least significant group is written first, followed by each of the more significant groups; thus, VarInts are effectively little endian (however, groups are 7 bits, not 8).

VarInts are never longer than 5 bytes, and VarLongs are never longer than 10 bytes. Within these limits, unnecessarily long encodings (e.g. 81 00 to encode 1) are allowed.

Pseudocode to read and write VarInts and VarLongs:

private static final int SEGMENT_BITS = 0x7F;
private static final int CONTINUE_BIT = 0x80;
public int readVarInt() {
    int value = 0;
    int position = 0;
    byte currentByte;

    while (true) {
        currentByte = readByte();
        value |= (currentByte & SEGMENT_BITS) << position;

        if ((currentByte & CONTINUE_BIT) == 0) break;

        position += 7;

        if (position >= 32) throw new RuntimeException("VarInt is too big");
    }

    return value;
}
public long readVarLong() {
    long value = 0;
    int position = 0;
    byte currentByte;

    while (true) {
        currentByte = readByte();
        value |= (long) (currentByte & SEGMENT_BITS) << position;

        if ((currentByte & CONTINUE_BIT) == 0) break;

        position += 7;

        if (position >= 64) throw new RuntimeException("VarLong is too big");
    }

    return value;
}
public void writeVarInt(int value) {
    while (true) {
        if ((value & ~SEGMENT_BITS) == 0) {
            writeByte(value);
            return;
        }

        writeByte((value & SEGMENT_BITS) | CONTINUE_BIT);

        // Note: >>> means that the sign bit is shifted with the rest of the number rather than being left alone
        value >>>= 7;
    }
}
public void writeVarLong(long value) {
    while (true) {
        if ((value & ~((long) SEGMENT_BITS)) == 0) {
            writeByte(value);
            return;
        }

        writeByte((value & SEGMENT_BITS) | CONTINUE_BIT);

        // Note: >>> means that the sign bit is shifted with the rest of the number rather than being left alone
        value >>>= 7;
    }
}

Warning.png Note Minecraft's VarInts are identical to LEB128 with the slight change of throwing a exception if it goes over a set amount of bytes.

Warning.png Note that Minecraft's VarInts are not encoded using Protocol Buffers; it's just similar. If you try to use Protocol Buffers Varints with Minecraft's VarInts, you'll get incorrect results in some cases. The major differences:

  • Minecraft's VarInts are all signed, but do not use the ZigZag encoding. Protocol buffers have 3 types of Varints: uint32 (normal encoding, unsigned), sint32 (ZigZag encoding, signed), and int32 (normal encoding, signed). Minecraft's are the int32 variety. Because Minecraft uses the normal encoding instead of ZigZag encoding, negative values always use the maximum number of bytes.
  • Minecraft's VarInts are never longer than 5 bytes and its VarLongs will never be longer than 10 bytes, while Protocol Buffer Varints will always use 10 bytes when encoding negative numbers, even if it's an int32.

Sample VarInts:

Value Hex bytes Decimal bytes
0 0x00 0
1 0x01 1
2 0x02 2
127 0x7f 127
128 0x80 0x01 128 1
255 0xff 0x01 255 1
25565 0xdd 0xc7 0x01 221 199 1
2097151 0xff 0xff 0x7f 255 255 127
2147483647 0xff 0xff 0xff 0xff 0x07 255 255 255 255 7
-1 0xff 0xff 0xff 0xff 0x0f 255 255 255 255 15
-2147483648 0x80 0x80 0x80 0x80 0x08 128 128 128 128 8

Sample VarLongs:

Value Hex bytes Decimal bytes
0 0x00 0
1 0x01 1
2 0x02 2
127 0x7f 127
128 0x80 0x01 128 1
255 0xff 0x01 255 1
2147483647 0xff 0xff 0xff 0xff 0x07 255 255 255 255 7
9223372036854775807 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x7f 255 255 255 255 255 255 255 255 127
-1 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0x01 255 255 255 255 255 255 255 255 255 1
-2147483648 0x80 0x80 0x80 0x80 0xf8 0xff 0xff 0xff 0xff 0x01 128 128 128 128 248 255 255 255 255 1
-9223372036854775808 0x80 0x80 0x80 0x80 0x80 0x80 0x80 0x80 0x80 0x01 128 128 128 128 128 128 128 128 128 1

Position

Note: What you are seeing here is the latest version of the Data types article, but the position type was different before 1.14.

64-bit value split into three signed integer parts:

  • x: 26 MSBs
  • z: 26 middle bits
  • y: 12 LSBs

For example, a 64-bit position can be broken down as follows:

Example value (big endian): 01000110000001110110001100 10110000010101101101001000 001100111111

  • The red value is the X coordinate, which is 18357644 in this example.
  • The blue value is the Z coordinate, which is -20882616 in this example.
  • The green value is the Y coordinate, which is 831 in this example.

Encoded as follows:

((x & 0x3FFFFFF) << 38) | ((z & 0x3FFFFFF) << 12) | (y & 0xFFF)

And decoded as:

val = read_long();
x = val >> 38;
y = val << 52 >> 52;
z = val << 26 >> 38;

Note: The above assumes that the right shift operator sign extends the value (this is called an arithmetic shift), so that the signedness of the coordinates is preserved. In many languages, this requires the integer type of val to be signed. In the absence of such an operator, the following may be useful:

if x >= 1 << 25 { x -= 1 << 26 }
if y >= 1 << 11 { y -= 1 << 12 }
if z >= 1 << 25 { z -= 1 << 26 }

Fixed-point numbers

Some fields may be stored as fixed-point numbers, where a certain number of bits represents the signed integer part (number to the left of the decimal point) and the rest represents the fractional part (to the right). Floating points (float and double), in contrast, keep the number itself (mantissa) in one chunk, while the location of the decimal point (exponent) is stored beside it.

Essentially, while fixed-point numbers have lower range than floating points, their fractional precision is greater for higher values. This makes them ideal for representing global coordinates of an entity in Minecraft, as it's more important to store the integer part accurately than position them more precisely within a single block (or meter).

Coordinates are often represented as a 32-bit integer, where 5 of the least-significant bits are dedicated to the fractional part, and the rest store the integer part.

Java lacks support for fractional integers directly, but you can represent them as integers. To convert from a double to this integer representation, use the following formulas:

 abs_int = (int) (double * 32.0D);

And back again:

 double = (double) (abs_int / 32.0D);

Bit sets

The types BitSet and Fixed BitSet represent packed lists of bits. The Notchian implementation uses Java's BitSet class.

BitSet

Bit sets of type BitSet are prefixed by their length in longs.

Field Name Field Type Meaning
Length VarInt Number of longs in the following array. May be 0 (if no bits are set).
Data Array of Long A packed representation of the bit set as created by BitSet.toLongArray.

The ith bit is set when (Data[i / 64] & (1 << (i % 64))) != 0, where i starts at 0.

Fixed BitSet

Bit sets of type Fixed BitSet (n) have a fixed length of n bits, encoded as ceil(n / 8) bytes. Note that this is different from BitSet, which uses longs.

Field Name Field Type Meaning
Data Byte Array (n) A packed representation of the bit set as created by BitSet.toByteArray.

The ith bit is set when (Data[i / 8] & (1 << (i % 8))) != 0, where i starts at 0. This encoding is not equivalent to the long array in BitSet.


Other definitions

Term Definition
Player When used in the singular, Player always refers to the client connected to the server.
Entity Entity refers to any item, player, mob, minecart or boat etc. See the Minecraft Wiki article for a full list.
EID An EID — or Entity ID — is a 4-byte sequence used to identify a specific entity. An entity's EID is unique on the entire server.
XYZ In this document, the axis names are the same as those shown in the debug screen (F3). Y points upwards, X points east, and Z points south.
Meter The meter is Minecraft's base unit of length, equal to the length of a vertex of a solid block. The term “block” may be used to mean “meter” or “cubic meter”.
Global palette A table/dictionary/palette mapping nonnegative integers to block states. Block state IDs are created in a linear fashion based off of order of assignment. One block state ID allocated for each unique block state for a block; if a block has multiple properties then the number of allocated states is the product of the number of values for each property. A current list of properties and state ID ranges is found on burger.

Alternatively, the vanilla server now includes an option to export the current block state ID mapping, by running java -cp minecraft_server.jar net.minecraft.data.Main --reports. See Data Generators for more information.

Notchian The official implementation of vanilla Minecraft as developed and released by Mojang.

Packet format

Without compression

Field Name Field Type Notes
Length VarInt Length of packet data + length of the packet ID
Packet ID VarInt
Data Byte Array Depends on the connection state and packet ID, see the sections below

With compression

Once a Set Compression packet (with a non-negative threshold) is sent, zlib compression is enabled for all following packets. The format of a packet changes slighty to include the size of the uncompressed packet.

Compressed? Field Name Field Type Notes
No Packet Length VarInt Length of Data Length + compressed length of (Packet ID + Data)
No Data Length VarInt Length of uncompressed (Packet ID + Data) or 0
Yes Packet ID VarInt zlib compressed packet ID (see the sections below)
Data Byte Array zlib compressed packet data (see the sections below)

The length given by the Packet Length field is the number of bytes that remain in that packet, including the Data Length field.

If Data Length is set to zero, then the packet is uncompressed; otherwise it is the size of the uncompressed packet.

If compressed, the uncompressed length of (Packet ID + Data) must be equal to or over the threshold set in the packet Set Compression, otherwise the receiving party will disconnect.

Compression can be disabled by sending the packet Set Compression with a negative Threshold, or not sending the Set Compression packet at all.

Handshaking

Clientbound

There are no clientbound packets in the Handshaking state, since the protocol immediately switches to a different state after the client sends the first packet.

Serverbound

Handshake

This causes the server to switch into the target state.

Packet ID State Bound To Field Name Field Type Notes
0x00 Handshaking Server Protocol Version VarInt See protocol version numbers (currently 578 in Minecraft 1.15.2)
Server Address String (255) Hostname or IP, e.g. localhost or 127.0.0.1, that was used to connect. The Notchian server does not use this information. Note that SRV records are a complete redirect, e.g. if _minecraft._tcp.example.com points to mc.example.org, users connecting to example.com will provide mc.example.org as server address in addition to connecting to it.
Server Port Unsigned Short Default is 25565. The Notchian server does not use this information.
Next State VarInt Enum 1 for status, 2 for login

Legacy Server List Ping

Warning.png This packet uses a nonstandard format. It is never length-prefixed, and the packet ID is an Unsigned Byte instead of a VarInt.

While not technically part of the current protocol, legacy clients may send this packet to initiate Server List Ping, and modern servers should handle it correctly.

Packet ID State Bound To Field Name Field Type Notes
0xFE Handshaking Server Payload Unsigned Byte always 1 (0x01)

See Server List Ping#1.6 for the details of the protocol that follows this packet.

Play

Clientbound

Spawn Object

Sent by the server when a vehicle or other object is created.

Packet ID State Bound To Field Name Field Type Notes
0x00 Play Client Entity ID VarInt EID of the object
Object UUID UUID
Type VarInt The type of object (same as in Spawn Mob)
X Double
Y Double
Z Double
Pitch Angle
Yaw Angle
Data Int Meaning dependent on the value of the Type field, see Object Data for details.
Velocity X Short Same units as Entity Velocity. Always sent, but only used when Data is greater than 0 (except for some entities which always ignore it; see Object Data for details).
Velocity Y Short
Velocity Z Short

Spawn Experience Orb

Spawns one or more experience orbs.

Packet ID State Bound To Field Name Field Type Notes
0x01 Play Client Entity ID VarInt
X Double
Y Double
Z Double
Count Short The amount of experience this orb will reward once collected

Spawn Global Entity

With this packet, the server notifies the client of thunderbolts striking within a 512 block radius around the player. The coordinates specify where exactly the thunderbolt strikes.

Packet ID State Bound To Field Name Field Type Notes
0x02 Play Client Entity ID VarInt The EID of the thunderbolt
Type Byte Enum The global entity type, currently always 1 for thunderbolt
X Double
Y Double
Z Double

Spawn Mob

Sent by the server when a mob entity is spawned.

Packet ID State Bound To Field Name Field Type Notes
0x03 Play Client Entity ID VarInt
Entity UUID UUID
Type VarInt The type of mob. See Entities#Mobs
X Double
Y Double
Z Double
Yaw Angle
Pitch Angle
Head Pitch Angle
Velocity X Short Same units as Entity Velocity
Velocity Y Short Same units as Entity Velocity
Velocity Z Short Same units as Entity Velocity

Spawn Painting

This packet shows location, name, and type of painting.

Packet ID State Bound To Field Name Field Type Notes
0x04 Play Client Entity ID VarInt
Entity UUID UUID
Motive VarInt Panting's ID, see below
Location Position Center coordinates (see below)
Direction Byte Enum Direction the painting faces (North = 2, South = 0, West = 1, East = 3)

Calculating the center of an image: given a (width × height) grid of cells, with (0, 0) being the top left corner, the center is (max(0, width / 2 - 1), height / 2). E.g. (1, 0) for a 2×1 painting, or (1, 2) for a 4×4 painting.

List of paintings by coordinates in paintings_kristoffer_zetterstrand.png (where x and y are in pixels from the top left and width and height are in pixels or 16ths of a block):

Name ID x y width height
minecraft:kebab 0 0 0 16 16
minecraft:aztec 1 16 0 16 16
minecraft:alban 2 32 0 16 16
minecraft:aztec2 3 48 0 16 16
minecraft:bomb 4 64 0 16 16
minecraft:plant 5 80 0 16 16
minecraft:wasteland 6 96 0 16 16
minecraft:pool 7 0 32 32 16
minecraft:courbet 8 32 32 32 16
minecraft:sea 9 64 32 32 16
minecraft:sunset 10 96 32 32 16
minecraft:creebet 11 128 32 32 16
minecraft:wanderer 12 0 64 16 32
minecraft:graham 13 16 64 16 32
minecraft:match 14 0 128 32 32
minecraft:bust 15 32 128 32 32
minecraft:stage 16 64 128 32 32
minecraft:void 17 96 128 32 32
skull_and_roses 18 128 128 32 32
minecraft:wither 19 160 128 32 32
minecraft:fighters 20 0 96 64 32
minecraft:pointer 21 0 192 64 64
minecraft:pigscene 22 64 192 64 64
minecraft:burning_skull 23 128 192 64 64
minecraft:skeleton 24 192 64 64 48
minecraft:donkey_kong 25 192 112 64 48

The Minecraft Wiki article on paintings also provides a list of painting names to the actual images.

Spawn Player

This packet is sent by the server when a player comes into visible range, not when a player joins.

This packet must be sent after the Player Info packet that adds the player data for the client to use when spawning a player. If the Player Info for the player spawned by this packet is not present when this packet arrives, Notchian clients will not spawn the player entity. The Player Info packet includes skin/cape data.

Servers can, however, safely spawn player entities for players not in visible range. The client appears to handle it correctly.

Packet ID State Bound To Field Name Field Type Notes
0x05 Play Client Entity ID VarInt Player's EID
Player UUID UUID See below for notes on offline mode and NPCs
X Double
Y Double
Z Double
Yaw Angle
Pitch Angle

When in online mode, the UUIDs must be valid and have valid skin blobs.

In offline mode, UUID v3 is used with the String OfflinePlayer:<player name>, encoded in UTF-8 (and case-sensitive).

For NPCs UUID v2 should be used. Note:

<+Grum> i will never confirm this as a feature you know that :)

In an example UUID, xxxxxxxx-xxxx-Yxxx-xxxx-xxxxxxxxxxxx, the UUID version is specified by Y. So, for UUID v3, Y will always be 3, and for UUID v2, Y will always be 2.

Entity Animation (clientbound)

Sent whenever an entity should change animation.

Packet ID State Bound To Field Name Field Type Notes
0x06 Play Client Entity ID VarInt Player ID
Animation Unsigned Byte Animation ID (see below)

Animation can be one of the following values:

ID Animation
0 Swing main arm
1 Take damage
2 Leave bed
3 Swing offhand
4 Critical effect
5 Magic critical effect

Statistics

Sent as a response to Client Status 0x04 (id 1).

Packet ID State Bound To Field Name Field Type Notes
0x07 Play Client Count VarInt Number of elements in the following array
Statistic Category ID Array VarInt See below
Statistic ID VarInt See below
Value VarInt The amount to set it to

Categories (these are namespaced, but with : replaced with .):

Name ID Registry
minecraft.mined 0 Blocks
minecraft.crafted 1 Items
minecraft.used 2 Items
minecraft.broken 3 Items
minecraft.picked_up 4 Items
minecraft.dropped 5 Items
minecraft.killed 6 Entities
minecraft.killed_by 7 Entities
minecraft.custom 8 Custom

Blocks, Items, and Entities use block (not block state), item, and entity ids.

Custom has the following (unit only matters for clients):

Name ID Unit
minecraft.leave_game 0 None
minecraft.play_one_minute 1 Time
minecraft.time_since_death 2 Time
minecraft.sneak_Time 3 Time
minecraft.walk_one_cm 4 Distance
minecraft.crouch_one_cm 5 Distance
minecraft.sprint_one_cm 6 Distance
minecraft.swim_one_cm 7 Distance
minecraft.fall_one_cm 8 Distance
minecraft.climb_one_cm 9 Distance
minecraft.fly_one_cm 10 Distance
minecraft.dive_one_cm 11 Distance
minecraft.minecart_one_cm 12 Distance
minecraft.boat_one_cm 13 Distance
minecraft.pig_one_cm 14 Distance
minecraft.horse_one_cm 15 Distance
minecraft.aviate_one_cm 16 Distance
minecraft.jump 17 None
minecraft.drop 18 None
minecraft.damage_dealt 19 Damage
minecraft.damage_taken 20 Damage
minecraft.deaths 21 None
minecraft.mob_kills 22 None
minecraft.animals_bred 23 None
minecraft.player_kills 24 None
minecraft.fish_caught 25 None
minecraft.talked_to_villager 26 None
minecraft.traded_with_villager 27 None
minecraft.eat_cake_slice 28 None
minecraft.fill_cauldron 29 None
minecraft.use_cauldron 30 None
minecraft.clean_armor 31 None
minecraft.clean_banner 32 None
minecraft.interact_with_brewingstand 33 None
minecraft.interact_with_beacon 34 None
minecraft.inspect_dropper 35 None
minecraft.inspect_hopper 36 None
minecraft.inspect_dispenser 37 None
minecraft.play_noteblock 38 None
minecraft.tune_noteblock 39 None
minecraft.pot_flower 40 None
minecraft.trigger_trapped_chest 41 None
minecraft.open_enderchest 42 None
minecraft.enchant_item 43 None
minecraft.play_record 44 None
minecraft.interact_with_furnace 45 None
minecraft.interact_with_crafting_table 46 None
minecraft.open_chest 47 None
minecraft.sleep_in_bed 48 None
minecraft.open_shulker_box 49 None

Units:

  • None: just a normal number (formatted with 0 decimal places)
  • Damage: value is 10 times the normal amount
  • Distance: a distance in centimeters (hundredths of blocks)
  • Time: a time span in ticks

Acknowledge Player Digging

Packet ID State Bound To Field Name Field Type Notes
0x08 Play Client Location Position Position where the digging was happening
Block VarInt Block state ID of the block that should be at that position now.
Status VarInt enum Same as Player Digging. Only Started digging (0), Cancelled digging (1), and Finished digging (2) are used.
Successful Boolean True if the digging succeeded; false if the client should undo any changes it made locally. (How does this work?)

Block Break Animation

0–9 are the displayable destroy stages and each other number means that there is no animation on this coordinate.

Block break animations can still be applied on air; the animation will remain visible although there is no block being broken. However, if this is applied to a transparent block, odd graphical effects may happen, including water losing its transparency. (An effect similar to this can be seen in normal gameplay when breaking ice blocks)

If you need to display several break animations at the same time you have to give each of them a unique Entity ID. The entity ID does not need to correspond to an actual entity on the client. It is valid to use a randomly generated number.

Packet ID State Bound To Field Name Field Type Notes
0x09 Play Client Entity ID VarInt Entity ID of the entity breaking the block
Location Position Block Position
Destroy Stage Byte 0–9 to set it, any other value to remove it

Update Block Entity

Sets the block entity associated with the block at the given location.

Packet ID State Bound To Field Name Field Type Notes
0x0A Play Client Location Position
Action Unsigned Byte The type of update to perform, see below
NBT Data NBT Tag Data to set. May be a TAG_END (0), in which case the block entity at the given location is removed (though this is not required since the client will remove the block entity automatically on chunk unload or block removal)

Action field:

  • 1: Set data of a mob spawner (everything except for SpawnPotentials: current delay, min/max delay, mob to be spawned, spawn count, spawn range, etc.)
  • 2: Set command block text (command and last execution status)
  • 3: Set the level, primary, and secondary powers of a beacon
  • 4: Set rotation and skin of mob head
  • 5: Declare a conduit
  • 6: Set base color and patterns on a banner
  • 7: Set the data for a Structure tile entity
  • 8: Set the destination for a end gateway
  • 9: Set the text on a sign
  • 10: Unused
  • 11: Declare a bed
  • 12: Set data of a jigsaw block
  • 13: Set items in a campfire
  • 14: Behive information

Block Action

This packet is used for a number of actions and animations performed by blocks, usually non-persistent.

See Block Actions for a list of values.

Warning.png This packet uses a block ID, not a block state. Unfortunately, block IDs are not directly included in the output from Data Generators, but can manually be calculated.

Packet ID State Bound To Field Name Field Type Notes
0x0B Play Client Location Position Block coordinates
Action ID (Byte 1) Unsigned Byte Varies depending on block — see Block Actions
Action Param (Byte 2) Unsigned Byte Varies depending on block — see Block Actions
Block Type VarInt The block type ID for the block. This must match the block at the given coordinates.

Block Change

Fired whenever a block is changed within the render distance.

Warning.png Changing a block in a chunk that is not loaded is not a stable action. The Notchian client currently uses a shared empty chunk which is modified for all block changes in unloaded chunks; while in 1.9 this chunk never renders in older versions the changed block will appear in all copies of the empty chunk. Servers should avoid sending block changes in unloaded chunks and clients should ignore such packets.

Packet ID State Bound To Field Name Field Type Notes
0x0C Play Client Location Position Block Coordinates
Block ID VarInt The new block state ID for the block as given in the global palette. See that section for more information.

Boss Bar

Packet ID State Bound To Field Name Field Type Notes
0x0D Play Client UUID UUID Unique ID for this bar
Action VarInt Enum Determines the layout of the remaining packet
Action Field Name
0: add Title Chat
Health Float From 0 to 1. Values greater than 1 do not crash a Notchian client, and start rendering part of a second health bar at around 1.5.
Color VarInt Enum Color ID (see below)
Division VarInt Enum Type of division (see below)
Flags Unsigned Byte Bit mask. 0x1: should darken sky, 0x2: is dragon bar (used to play end music), 0x04: create fog (previously was also controlled by 0x02)
1: remove no fields no fields Removes this boss bar
2: update health Health Float as above
3: update title Title Chat
4: update style Color VarInt Enum Color ID (see below)
Dividers VarInt Enum as above
5: update flags Flags Unsigned Byte as above
ID Color
0 Pink
1 Blue
2 Red
3 Green
4 Yellow
5 Purple
6 White
ID Type of division
0 No division
1 6 notches
2 10 notches
3 12 notches
4 20 notches

Server Difficulty

Changes the difficulty setting in the client's option menu

Packet ID State Bound To Field Name Field Type Notes
0x0E Play Client Difficulty Unsigned Byte 0: peaceful, 1: easy, 2: normal, 3: hard
Difficulty locked? Boolean

Chat Message (clientbound)

Identifying the difference between Chat/System Message is important as it helps respect the user's chat visibility options. See processing chat for more info about these positions.

Warning.png Game info accepts json formatting but does not display it, although the deprecated §-based formatting works. This is not an issue when using the Title packet, so prefer that packet for displaying information in that slot. See MC-119145 for more information.

Packet ID State Bound To Field Name Field Type Notes
0x0F Play Client JSON Data Chat Limited to 32767 bytes
Position Byte 0: chat (chat box), 1: system message (chat box), 2: game info (above hotbar).

Multi Block Change

Fired whenever 2 or more blocks are changed within the same chunk on the same tick.

Warning.png Changing blocks in chunks not loaded by the client is unsafe (see note on Block Change).

Packet ID State Bound To Field Name Field Type Notes
0x10 Play Client Chunk X Int Chunk X coordinate
Chunk Z Int Chunk Z coordinate
Record Count VarInt Number of elements in the following array, i.e. the number of blocks affected
Record Horizontal Position Array Unsigned Byte The 4 most significant bits (0xF0) encode the X coordinate, relative to the chunk. The 4 least significant bits (0x0F) encode the Z coordinate, relative to the chunk.
Y Coordinate Unsigned Byte Y coordinate of the block
Block ID VarInt The new block state ID for the block as given in the global palette. See that section for more information.

To decode the position into a world position:

worldX = (horizPos >> 4 & 15) + (chunkX * 16);
worldY = vertPos;
worldZ = (horizPos & 15) + (chunkZ * 16);

Tab-Complete (clientbound)

The server responds with a list of auto-completions of the last word sent to it. In the case of regular chat, this is a player username. Command names and parameters are also supported. The client sorts these alphabetically before listing them.

Packet ID State Bound To Field Name Field Type Notes
0x11 Play Client
ID VarInt Transaction ID
Start VarInt Start of the text to replace
Length VarInt Length of the text to replace
Count VarInt Number of elements in the following array
Matches Match Array String (32767) One eligible value to insert, note that each command is sent separately instead of in a single string, hence the need for Count. Note that for instance this doesn't include a leading / on commands.
Has tooltip Boolean True if the following is present
Tooltip Optional Chat Tooltip to display; only present if previous boolean is true

Declare Commands

Lists all of the commands on the server, and how they are parsed.

This is a directed graph, with one root node. Each redirect or child node must refer only to nodes that have already been declared.

Packet ID State Bound To Field Name Field Type Notes
0x12 Play Client Count VarInt Number of elements in the following array
Nodes Array of Node An array of nodes
Root index VarInt Index of the root node in the previous array

For more information on this packet, see the Command Data article.

Window Confirmation (clientbound)

A packet from the server indicating whether a request from the client was accepted, or whether there was a conflict (due to lag). If the packet was not accepted, the client must respond with a serverbound window confirmation packet.

Packet ID State Bound To Field Name Field Type Notes
0x13 Play Client Window ID Byte The ID of the window that the action occurred in
Action Number Short Every action that is to be accepted has a unique number. This number is an incrementing integer (starting at 0) with separate counts for each window ID.
Accepted Boolean Whether the action was accepted

Close Window (clientbound)

This packet is sent from the server to the client when a window is forcibly closed, such as when a chest is destroyed while it's open.

Packet ID State Bound To Field Name Field Type Notes
0x14 Play Client Window ID Unsigned Byte This is the ID of the window that was closed. 0 for inventory.

Window Items

The inventory slots

Sent by the server when items in multiple slots (in a window) are added/removed. This includes the main inventory, equipped armour and crafting slots.

Packet ID State Bound To Field Name Field Type Notes
0x15 Play Client Window ID Unsigned Byte The ID of window which items are being sent for. 0 for player inventory.
Count Short Number of elements in the following array
Slot Data Array of Slot

See inventory windows for further information about how slots are indexed.

Window Property

This packet is used to inform the client that part of a GUI window should be updated.

Packet ID State Bound To Field Name Field Type Notes
0x16 Play Client Window ID Unsigned Byte
Property Short The property to be updated, see below
Value Short The new value for the property, see below

The meaning of the Property field depends on the type of the window. The following table shows the known combinations of window type and property, and how the value is to be interpreted.

Window type Property Value
Furnace 0: Fire icon (fuel left) counting from fuel burn time down to 0 (in-game ticks)
1: Maximum fuel burn time fuel burn time or 0 (in-game ticks)
2: Progress arrow counting from 0 to maximum progress (in-game ticks)
3: Maximum progress always 200 on the notchian server
Enchantment Table 0: Level requirement for top enchantment slot The enchantment's xp level requirement
1: Level requirement for middle enchantment slot
2: Level requirement for bottom enchantment slot
3: The enchantment seed Used for drawing the enchantment names (in SGA) clientside. The same seed is used to calculate enchantments, but some of the data isn't sent to the client to prevent easily guessing the entire list (the seed value here is the regular seed bitwise and 0xFFFFFFF0).
4: Enchantment ID shown on mouse hover over top enchantment slot The enchantment id (set to -1 to hide it), see below for values
5: Enchantment ID shown on mouse hover over middle enchantment slot
6: Enchantment ID shown on mouse hover over bottom enchantment slot
7: Enchantment level shown on mouse hover over the top slot The enchantment level (1 = I, 2 = II, 6 = VI, etc.), or -1 if no enchant
8: Enchantment level shown on mouse hover over the middle slot
9: Enchantment level shown on mouse hover over the bottom slot
Beacon 0: Power level 0-4, controls what effect buttons are enabled
1: First potion effect Potion effect ID for the first effect, or -1 if no effect
2: Second potion effect Potion effect ID for the second effect, or -1 if no effect
Anvil 0: Repair cost The repair's cost in xp levels
Brewing Stand 0: Brew time 0 – 400, with 400 making the arrow empty, and 0 making the arrow full
1: Fuel time 0 - 20, with 0 making the arrow empty, and 20 making the arrow full

For an enchanting table, the following numerical IDs are used:

Numerical ID Enchantment ID Enchantment Name
0 minecraft:protection Protection
1 minecraft:fire_protection Fire Protection
2 minecraft:feather_falling Feather Falling
3 minecraft:blast_protection Blast Protection
4 minecraft:projectile_protection Projectile Protection
5 minecraft:respiration Respiration
6 minecraft:aqua_affinity Aqua Affinity
7 minecraft:thorns Thorns
8 minecraft:depth_strider Depth Strider
9 minecraft:frost_walker Frost Walker
10 minecraft:binding_curse Curse of Binding
11 minecraft:sharpness Sharpness
12 minecraft:smite Smite
13 minecraft:bane_of_arthropods Bane of Arthropods
14 minecraft:knockback Knockback
15 minecraft:fire_aspect Fire Aspect
16 minecraft:looting Looting
17 minecraft:sweeping Sweeping Edge
18 minecraft:efficiency Efficiency
19 minecraft:silk_touch Silk Touch
20 minecraft:unbreaking Unbreaking
21 minecraft:fortune Fortune
22 minecraft:power Power
23 minecraft:punch Punch
24 minecraft:flame Flame
25 minecraft:infinity Infinity
26 minecraft:luck_of_the_sea Luck of the Sea
27 minecraft:lure Lure
28 minecraft:loyalty Loyalty
29 minecraft:impaling Impaling
30 minecraft:riptide Riptide
31 minecraft:channeling Channeling
32 minecraft:mending Mending
33 minecraft:vanishing_curse Curse of Vanishing

Set Slot

Sent by the server when an item in a slot (in a window) is added/removed.

Packet ID State Bound To Field Name Field Type Notes
0x17 Play Client Window ID Byte The window which is being updated. 0 for player inventory. Note that all known window types include the player inventory. This packet will only be sent for the currently opened window while the player is performing actions, even if it affects the player inventory. After the window is closed, a number of these packets are sent to update the player's inventory window (0).
Slot Short The slot that should be updated
Slot Data Slot

To set the cursor (the item currently dragged with the mouse), use -1 as Window ID and as Slot.

This packet can only be used to edit the hotbar of the player's inventory if window ID is set to 0 (slots 36 through 44). If the window ID is set to -2, then any slot in the inventory can be used but no add item animation will be played.

Set Cooldown

Applies a cooldown period to all items with the given type. Used by the Notchian server with enderpearls. This packet should be sent when the cooldown starts and also when the cooldown ends (to compensate for lag), although the client will end the cooldown automatically. Can be applied to any item, note that interactions still get sent to the server with the item but the client does not play the animation nor attempt to predict results (i.e block placing).

Packet ID State Bound To Field Name Field Type Notes
0x18 Play Client Item ID VarInt Numeric ID of the item to apply a cooldown to.
Cooldown Ticks VarInt Number of ticks to apply a cooldown for, or 0 to clear the cooldown.

Plugin Message (clientbound)

Main article: Plugin channels

Mods and plugins can use this to send their data. Minecraft itself uses several plugin channels. These internal channels are in the minecraft namespace.

More documentation on this: http://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/

Packet ID State Bound To Field Name Field Type Notes
0x19 Play Client Channel Identifier Name of the plugin channel used to send the data
Data Byte Array Any data, depending on the channel. minecraft: channels are documented here. The length of this array must be inferred from the packet length.

Named Sound Effect

See also: #Sound Effect

Used to play a sound effect on the client. Custom sounds may be added by resource packs.

Packet ID State Bound To Field Name Field Type Notes
0x1A Play Client Sound Name Identifier All sound effect names as of 1.15.2 can be seen here.
Sound Category VarInt Enum The category that this sound will be played from (current categories)
Effect Position X Int Effect X multiplied by 8 (fixed-point number with only 3 bits dedicated to the fractional part)
Effect Position Y Int Effect Y multiplied by 8 (fixed-point number with only 3 bits dedicated to the fractional part)
Effect Position Z Int Effect Z multiplied by 8 (fixed-point number with only 3 bits dedicated to the fractional part)
Volume Float 1 is 100%, can be more
Pitch Float Float between 0.5 and 2.0 by Notchian clients

Disconnect (play)

Sent by the server before it disconnects a client. The client assumes that the server has already closed the connection by the time the packet arrives.

Packet ID State Bound To Field Name Field Type Notes
0x1B Play Client Reason Chat Displayed to the client when the connection terminates.

Entity Status

Entity statuses generally trigger an animation for an entity. The available statuses vary by the entity's type (and are available to subclasses of that type as well).

Packet ID State Bound To Field Name Field Type Notes
0x1C Play Client Entity ID Int
Entity Status Byte Enum See below

See Entity statuses for a list of which statuses are valid for each type of entity.

Explosion

Sent when an explosion occurs (creepers, TNT, and ghast fireballs).

Each block in Records is set to air. Coordinates for each axis in record is int(X) + record.x

Packet ID State Bound To Field Name Field Type Notes
0x1D Play Client X Float
Y Float
Z Float
Strength Float A strength greater than or equal to 2.0 spawns a minecraft:explosion_emitter particle, while a lesser strength spawns a minecraft:explosion particle.
Record Count Int Number of elements in the following array
Records Array of (Byte, Byte, Byte) Each record is 3 signed bytes long; the 3 bytes are the XYZ (respectively) signed offsets of affected blocks.
Player Motion X Float X velocity of the player being pushed by the explosion
Player Motion Y Float Y velocity of the player being pushed by the explosion
Player Motion Z Float Z velocity of the player being pushed by the explosion

Unload Chunk

Tells the client to unload a chunk column.

Packet ID State Bound To Field Name Field Type Notes
0x1E Play Client Chunk X Int Block coordinate divided by 16, rounded down
Chunk Z Int Block coordinate divided by 16, rounded down

It is legal to send this packet even if the given chunk is not currently loaded.

Change Game State

Used for a wide variety of game state things, from whether to bed use to gamemode to demo messages.

Packet ID State Bound To Field Name Field Type Notes
0x1F Play Client Reason Unsigned Byte See below
Value Float Depends on Reason

Reason codes:

Reason Effect Value
0 Invalid Bed Would be used to switch between messages, but the only used message is 0 for invalid bed
1 Begin raining
2 End raining
3 Change gamemode 0: Survival, 1: Creative, 2: Adventure, 3: Spectator
4 Exit end 0: Immediately send Client Status of respawn without showing end credits; 1: Show end credits and respawn at the end (or when esc is pressed). 1 is sent if the player has not yet received the "The end?" advancement, while if they do have it 0 is used.
5 Demo message 0: Show welcome to demo screen, 101: Tell movement controls, 102: Tell jump control, 103: Tell inventory control, 104: Tell that the demo is over and print a message about how to take a screenshot
6 Arrow hitting player Appears to be played when an arrow strikes another player in Multiplayer
7 Fade value The current darkness value. 1 = Dark, 0 = Bright, Setting the value higher causes the game to change color and freeze
8 Fade time Time in ticks for the sky to fade
9 Play pufferfish sting sound
10 Play elder guardian mob appearance (effect and sound)
11 Enable respawn screen 0: Enable respawn screen, 1: Immediately respawn (sent when the doImmediateRespawn gamerule changes)

Open Horse Window

This packet is used exclusively for opening the horse GUI. Open Window is used for all other GUIs.

Packet ID State Bound To Field Name Field Type Notes
0x20 Play Client Window ID? Byte
Number of slots? VarInt
Entity ID? Integer

Keep Alive (clientbound)

The server will frequently send out a keep-alive, each containing a random ID. The client must respond with the same packet. If the client does not respond to them for over 30 seconds, the server kicks the client. Vice versa, if the server does not send any keep-alives for 20 seconds, the client will disconnect and yields a "Timed out" exception.

The Notchian server uses a system-dependent time in milliseconds to generate the keep alive ID value.

Packet ID State Bound To Field Name Field Type Notes
0x21 Play Client Keep Alive ID Long

Chunk Data

Main article: Chunk Format
See also: #Unload Chunk
Huh.png The following information needs to be added to this page:
How do biomes work now? The biome change happened at the same time as the seed change, but it's not clear how/if biomes could be computed given that it's not the actual seed... (/r/mojira discussion which notes that it seems to be some kind of interpolation, and 3D biomes are only used in the nether)

The server only sends skylight information for chunk pillars in the Overworld, it's up to the client to know in which dimenison the player is currently located. You can also infer this information from the primary bitmask and the amount of uncompressed bytes sent. This packet also sends all block entities in the chunk (though sending them is not required; it is still legal to send them with Update Block Entity later).

Packet ID State Bound To Field Name Field Type Notes
0x22 Play Client Chunk X Int Chunk coordinate (block coordinate divided by 16, rounded down)
Chunk Z Int Chunk coordinate (block coordinate divided by 16, rounded down)
Full chunk Boolean See Chunk Format
Primary Bit Mask VarInt Bitmask with bits set to 1 for every 16×16×16 chunk section whose data is included in Data. The least significant bit represents the chunk section at the bottom of the chunk column (from y=0 to y=15).
Heightmaps NBT Compound containing one long array named MOTION_BLOCKING, which is a heightmap for the highest solid block at each position in the chunk (as a compacted long array with 256 entries at 9 bits per entry totaling 36 longs). The Notchian server also adds a WORLD_SURFACE long array, the purpose of which is unknown, but it's not required for the chunk to be accepted.
Biomes Optional array of Integer 1024 biome IDs, ordered by x then z then y, in 4×4×4 blocks. Not present if full chunk is false.
Size VarInt Size of Data in bytes
Data Byte array See data structure in Chunk Format
Number of block entities VarInt Number of elements in the following array
Block entities Array of NBT Tag All block entities in the chunk. Use the x, y, and z tags in the NBT to determine their positions.

Note that the Notchian client requires an Update View Position packet when it crosses a chunk border, otherwise it'll only display render distance + 2 chunks around the chunk it spawned in.

Effect

Sent when a client is to play a sound or particle effect.

By default, the Minecraft client adjusts the volume of sound effects based on distance. The final boolean field is used to disable this, and instead the effect is played from 2 blocks away in the correct direction. Currently this is only used for effect 1023 (wither spawn) and effect 1028 (enderdragon death); it is ignored on other effects.

Packet ID State Bound To Field Name Field Type Notes
0x23 Play Client Effect ID Int The ID of the effect, see below
Location Position The location of the effect
Data Int Extra data for certain effects, see below
Disable Relative Volume Boolean See above

Effect IDs:

ID Name Data
Sound
1000 Dispenser dispenses
1001 Dispenser fails to dispense
1002 Dispenser shoots
1003 Ender eye launched
1004 Firework shot
1005 Iron door opened
1006 Wooden door opened
1007 Wooden trapdoor opened
1008 Fence gate opened
1009 Fire extinguished
1010 Play record Special case, see below for more info
1011 Iron door closed
1012 Wooden door closed
1013 Wooden trapdoor closed
1014 Fence gate closed
1015 Ghast warns
1016 Ghast shoots
1017 Enderdragon shoots
1018 Blaze shoots
1019 Zombie attacks wood door
1020 Zombie attacks iron door
1021 Zombie breaks wood door
1022 Wither breaks block
1023 Wither spawned
1024 Wither shoots
1025 Bat takes off
1026 Zombie infects
1027 Zombie villager converted
1028 Ender dragon death
1029 Anvil destroyed
1030 Anvil used
1031 Anvil landed
1032 Portal travel
1033 Chorus flower grown
1034 Chorus flower died
1035 Brewing stand brewed
1036 Iron trapdoor opened
1037 Iron trapdoor closed
Particle
2000 Spawns 10 smoke particles, e.g. from a fire Direction, see below
2001 Block break + block break sound Block state, as an index into the global palette
2002 Splash potion. Particle effect + glass break sound. Potion ID
2003 Eye of Ender entity break animation — particles and sound
2004 Mob spawn particle effect: smoke + flames
2005 Bonemeal particles How many particles to spawn (if set to 0, 15 are spawned)
2006 Dragon breath
2007 Instant splash potion Potion ID
3000 End gateway spawn
3001 Enderdragon growl

Smoke directions:

ID Direction
0 South-East
1 South
2 South-West
3 East
4 (Up or middle ?)
5 West
6 North-East
7 North
8 North-West

Play record: This is actually a special case within this packet. You can start/stop a record at a specific location. Use a valid Record ID to start a record (or overwrite a currently playing one), any other value will stop the record. See Data Generators for information on item IDs.

Particle

Displays the named particle

Packet ID State Bound To Field Name Field Type Notes
0x24 Play Client Particle ID Int The particle ID listed in the particle data type.
Long Distance Boolean If true, particle distance increases from 256 to 65536
X Double X position of the particle
Y Double Y position of the particle
Z Double Z position of the particle
Offset X Float This is added to the X position after being multiplied by random.nextGaussian()
Offset Y Float This is added to the Y position after being multiplied by random.nextGaussian()
Offset Z Float This is added to the Z position after being multiplied by random.nextGaussian()
Particle Data Float The data of each particle
Particle Count Int The number of particles to create
Data Varies The variable data listed in the particle data type.

Update Light

Updates light levels for a chunk.

Packet ID State Bound To Field Name Field Type Notes
0x25 Play Client Chunk X VarInt Chunk coordinate (block coordinate divided by 16, rounded down)
Chunk Z VarInt Chunk coordinate (block coordinate divided by 16, rounded down)
Sky Light Mask VarInt Mask containing 18 bits, with the lowest bit corresponding to chunk section -1 (in the void, y=-16 to y=-1) and the highest bit for chunk section 16 (above the world, y=256 to y=271)
Block Light Mask VarInt Mask containing 18 bits, with the same order as sky light
Empty Sky Light Mask VarInt Mask containing 18 bits, which indicates sections that have 0 for all their sky light values. If a section is set in both this mask and the main sky light mask, it is ignored for this mask and it is included in the sky light arrays (the notchian server does not create such masks). If it is only set in this mask, it is not included in the sky light arrays.
Empty Block Light Mask VarInt Mask containing 18 bits, which indicates sections that have 0 for all their block light values. If a section is set in both this mask and the main block light mask, it is ignored for this mask and it is included in the block light arrays (the notchian server does not create such masks). If it is only set in this mask, it is not included in the block light arrays.
Sky Light arrays Length Array VarInt Length of the following array in bytes (always 2048)
Sky Light array Array of 2048 bytes There is 1 array for each bit set to true in the sky light mask, starting with the lowest value. Half a byte per light value.
Block Light arrays Length Array VarInt Length of the following array in bytes (always 2048)
Block Light array Array of 2048 bytes There is 1 array for each bit set to true in the block light mask, starting with the lowest value. Half a byte per light value.

Individual block or sky light arrays are is given for each block with increasing x coordinates, within rows of increasing z coordinates, within layers of increasing y coordinates. Even-indexed items (those with an even x coordinate, starting at 0) are packed into the low bits, odd-indexed into the high bits.

Join Game

See Protocol Encryption for information on logging in.

Packet ID State Bound To Field Name Field Type Notes
0x26 Play Client Entity ID Int The player's Entity ID (EID)
Gamemode Unsigned Byte 0: Survival, 1: Creative, 2: Adventure, 3: Spectator. Bit 3 (0x8) is the hardcore flag.
Dimension Int Enum -1: Nether, 0: Overworld, 1: End; also, note that this is not a VarInt but instead a regular int.
Hashed seed Long First 8 bytes of the SHA-256 hash of the world's seed.
Max Players Unsigned Byte Was once used by the client to draw the player list, but now is ignored
Level Type String Enum (16) default, flat, largeBiomes, amplified, customized, buffet, default_1_1
View Distance VarInt Render distance (2-32)
Reduced Debug Info Boolean If true, a Notchian client shows reduced information on the debug screen. For servers in development, this should almost always be false.
Enable respawn screen Boolean Set to false when the doImmediateRespawn gamerule is true

Map Data

Updates a rectangular area on a map item.

Packet ID State Bound To Field Name Field Type Notes
0x27 Play Client Map ID VarInt Map ID of the map being modified
Scale Byte From 0 for a fully zoomed-in map (1 block per pixel) to 4 for a fully zoomed-out map (16 blocks per pixel)
Tracking Position Boolean Specifies whether player and item frame icons are shown
Locked Boolean True if the map has been locked in a cartography table
Icon Count VarInt Number of elements in the following array
Icon Type Array VarInt enum See below
X Byte Map coordinates: -128 for furthest left, +127 for furthest right
Z Byte Map coordinates: -128 for highest, +127 for lowest
Direction Byte 0-15
Has Display Name Boolean
Display Name Optional Chat Only present if previous Boolean is true
Columns Unsigned Byte Number of columns updated
Rows Optional Byte Only if Columns is more than 0; number of rows updated
X Optional Byte Only if Columns is more than 0; x offset of the westernmost column
Z Optional Byte Only if Columns is more than 0; z offset of the northernmost row
Length Optional VarInt Only if Columns is more than 0; length of the following array
Data Optional Array of Unsigned Byte Only if Columns is more than 0; see Map item format

For icons, a direction of 0 is a vertical icon and increments by 22.5° (360/16).

Types are based off of rows and columns in map_icons.png:

Icon type Result
0 White arrow (players)
1 Green arrow (item frames)
2 Red arrow
3 Blue arrow
4 White cross
5 Red pointer
6 White circle (off-map players)
7 Small white circle (far-off-map players)
8 Mansion
9 Temple
10 White Banner
11 Orange Banner
12 Magenta Banner
13 Light Blue Banner
14 Yellow Banner
15 Lime Banner
16 Pink Banner
17 Gray Banner
18 Light Gray Banner
19 Cyan Banner
20 Purple Banner
21 Blue Banner
22 Brown Banner
23 Green Banner
24 Red Banner
25 Black Banner
26 Treasure marker

Trade List

The list of trades a villager NPC is offering.

Packet ID State Bound To Field Name Field Type Notes
0x28 Play Client
Window ID VarInt The ID of the window that is open; this is an int rather than a byte.
Size Byte The number of trades in the following array
Trades Input item 1 Array Slot The first item the villager is buying
Output item Slot The item the villager is selling
Has second item Boolean Whether there is a second item
Input item 2 Optional Slot The second item the villager is buying; only present if they have a second item.
Trade disabled Boolean True if the trade is disabled; false if the trade is enabled.
Number of trade uses Integer Number of times the trade has been used so far
Maximum number of trade uses Integer Number of times this trade can be used
XP Integer
Special Price Integer
Price Multiplier Float
Demand Integer
Villager level VarInt Appears on the trade GUI; meaning comes from the translation key merchant.level. + level.

1: Novice, 2: Apprentice, 3: Journeyman, 4: Expert, 5: Master

Experience VarInt Total experience for this villager (always 0 for the wandering trader)
Is regular villager Boolean True if this is a regular villager; false for the wandering trader. When false, hides the villager level and some other GUI elements.
Can restock Boolean True for regular villagers and false for the wandering trader. If true, the "Villagers restock up to two times per day." message is displayed when hovering over disabled trades.
The merchant UI, for reference

Entity Position

This packet is sent by the server when an entity moves less then 8 blocks; if an entity moves more than 8 blocks Entity Teleport should be sent instead.

This packet allows at most 8 blocks movement in any direction, because short range is from -32768 to 32767. And 32768 / (128 * 32) = 8.

Packet ID State Bound To Field Name Field Type Notes
0x29 Play Client Entity ID VarInt
Delta X Short Change in X position as (currentX * 32 - prevX * 32) * 128
Delta Y Short Change in Y position as (currentY * 32 - prevY * 32) * 128
Delta Z Short Change in Z position as (currentZ * 32 - prevZ * 32) * 128
On Ground Boolean

Entity Position and Rotation

This packet is sent by the server when an entity rotates and moves. Since a short range is limited from -32768 to 32767, and movement is offset of fixed-point numbers, this packet allows at most 8 blocks movement in any direction. (-32768 / (32 * 128) == -8)

Packet ID State Bound To Field Name Field Type Notes
0x2A Play Client Entity ID VarInt
Delta X Short Change in X position as (currentX * 32 - prevX * 32) * 128
Delta Y Short Change in Y position as (currentY * 32 - prevY * 32) * 128
Delta Z Short Change in Z position as (currentZ * 32 - prevZ * 32) * 128
Yaw Angle New angle, not a delta
Pitch Angle New angle, not a delta
On Ground Boolean

Entity Rotation

This packet is sent by the server when an entity rotates.

Packet ID State Bound To Field Name Field Type Notes
0x2B Play Client Entity ID VarInt
Yaw Angle New angle, not a delta
Pitch Angle New angle, not a delta
On Ground Boolean

Entity Movement

This packet may be used to initialize an entity.

For player entities, either this packet or any move/look packet is sent every game tick. So the meaning of this packet is basically that the entity did not move/look since the last such packet.

Packet ID State Bound To Field Name Field Type Notes
0x2C Play Client Entity ID VarInt

Vehicle Move (clientbound)

Note that all fields use absolute positioning and do not allow for relative positioning.

Packet ID State Bound To Field Name Field Type Notes
0x2D Play Client X Double Absolute position (X coordinate)
Y Double Absolute position (Y coordinate)
Z Double Absolute position (Z coordinate)
Yaw Float Absolute rotation on the vertical axis, in degrees
Pitch Float Absolute rotation on the horizontal axis, in degrees

Open Book

Sent when a player right clicks with a signed book. This tells the client to open the book GUI.

Packet ID State Bound To Field Name Field Type Notes
0x2E Play Client Hand VarInt enum 0: Main hand, 1: Off hand

Open Window

This is sent to the client when it should open an inventory, such as a chest, workbench, or furnace. This message is not sent anywhere for clients opening their own inventory. For horses, use Open Horse Window.

Packet ID State Bound To Field Name Field Type Notes
0x2F Play Client Window ID VarInt A unique id number for the window to be displayed. Notchian server implementation is a counter, starting at 1.
Window Type VarInt The window type to use for display. Contained in the minecraft:menu regisry; see Inventory for the different values.
Window Title Chat The title of the window

Open Sign Editor

Sent when the client has placed a sign and is allowed to send Update Sign. There must already be a sign at the given location (which the client does not do automatically) - send a Block Change first.

Packet ID State Bound To Field Name Field Type Notes
0x30 Play Client Location Position

Craft Recipe Response

Response to the serverbound packet (Craft Recipe Request), with the same recipe ID. Appears to be used to notify the UI.

Packet ID State Bound To Field Name Field Type Notes
0x31 Play Client Window ID Byte
Recipe Identifier A recipe ID

Player Abilities (clientbound)

The latter 2 floats are used to indicate the field of view and flying speed respectively, while the first byte is used to determine the value of 4 booleans.

Packet ID State Bound To Field Name Field Type Notes
0x32 Play Client Flags Byte Bit field, see below
Flying Speed Float 0.05 by default
Field of View Modifier Float Modifies the field of view, like a speed potion. A Notchian server will use the same value as the movement speed sent in the Entity Properties packet, which defaults to 0.1 for players.

About the flags:

Field Bit
Invulnerable 0x01
Flying 0x02
Allow Flying 0x04
Creative Mode (Instant Break) 0x08

Combat Event

Packet ID State Bound To Field Name Field Type Notes
0x33 Play Client Event VarInt Enum Determines the layout of the remaining packet
Event Field Name
0: enter combat no fields no fields
1: end combat Duration VarInt
Entity ID Int
2: entity dead Player ID VarInt
Entity ID Int
Message Chat

Player Info

Sent by the server to update the user list (<tab> in the client).

Packet ID State Bound To Field Name Field Type Notes
0x34 Play Client Action VarInt Determines the rest of the Player format after the UUID
Number Of Players VarInt Number of elements in the following array
Player UUID Array UUID
Action Field Name
0: add player Name String (16)
Number Of Properties VarInt Number of elements in the following array
Property Name Array String (32767)
Value String (32767)
Is Signed Boolean
Signature Optional String (32767) Only if Is Signed is true
Gamemode VarInt
Ping VarInt Measured in milliseconds
Has Display Name Boolean
Display Name Optional Chat Only if Has Display Name is true
1: update gamemode Gamemode VarInt
2: update latency Ping VarInt Measured in milliseconds
3: update display name Has Display Name Boolean
Display Name Optional Chat Only send if Has Display Name is true
4: remove player no fields no fields

The Property field looks as in the response of Mojang API#UUID -> Profile + Skin/Cape, except of course using the protocol format instead of JSON. That is, each player will usually have one property with Name “textures” and Value being a base64-encoded JSON string as documented at Mojang API#UUID -> Profile + Skin/Cape. An empty properties array is also acceptable, and will cause clients to display the player with one of the two default skins depending on UUID.

Ping values correspond with icons in the following way:

  • A ping that negative (i.e. not known to the server yet) will result in the no connection icon.
  • A ping under 150 milliseconds will result in 5 bars
  • A ping under 300 milliseconds will result in 4 bars
  • A ping under 600 milliseconds will result in 3 bars
  • A ping under 1000 milliseconds (1 second) will result in 2 bars
  • A ping greater than or equal to 1 second will result in 1 bar.

Face Player

Used to rotate the client player to face the given location or entity (for /teleport [<targets>] <x> <y> <z> facing).

Packet ID State Bound To Field Name Field Type Notes
0x35 Play Client
Feet/eyes VarInt enum Values are feet=0, eyes=1. If set to eyes, aims using the head position; otherwise aims using the feet position.
Target x Double x coordinate of the point to face towards
Target y Double y coordinate of the point to face towards
Target z Double z coordinate of the point to face towards
Is entity Boolean If true, additional information about an entity is provided.
Entity ID Optional VarInt Only if is entity is true — the entity to face towards
Entity feet/eyes Optional VarInt enum Whether to look at the entity's eyes or feet. Same values and meanings as before, just for the entity's head/feet.

If the entity given by entity ID cannot be found, this packet should be treated as if is entity was false.

Player Position And Look (clientbound)

Updates the player's position on the server. This packet will also close the “Downloading Terrain” screen when joining/respawning.

If the distance between the last known position of the player on the server and the new position set by this packet is greater than 100 meters, the client will be kicked for “You moved too quickly :( (Hacking?)”.

Also if the fixed-point number of X or Z is set greater than 3.2E7D the client will be kicked for “Illegal position”.

Yaw is measured in degrees, and does not follow classical trigonometry rules. The unit circle of yaw on the XZ-plane starts at (0, 1) and turns counterclockwise, with 90 at (-1, 0), 180 at (0, -1) and 270 at (1, 0). Additionally, yaw is not clamped to between 0 and 360 degrees; any number is valid, including negative numbers and numbers greater than 360.

Pitch is measured in degrees, where 0 is looking straight ahead, -90 is looking straight up, and 90 is looking straight down.

Packet ID State Bound To Field Name Field Type Notes
0x36 Play Client X Double Absolute or relative position, depending on Flags
Y Double Absolute or relative position, depending on Flags
Z Double Absolute or relative position, depending on Flags
Yaw Float Absolute or relative rotation on the X axis, in degrees
Pitch Float Absolute or relative rotation on the Y axis, in degrees
Flags Byte Bit field, see below
Teleport ID VarInt Client should confirm this packet with Teleport Confirm containing the same Teleport ID

About the Flags field:

<Dinnerbone> It's a bitfield, X/Y/Z/Y_ROT/X_ROT. If X is set, the x value is relative and not absolute.
Field Bit
X 0x01
Y 0x02
Z 0x04
Y_ROT 0x08
X_ROT 0x10

Unlock Recipes

Packet ID State Bound To Field Name Field Type Notes
0x37 Play Client
Action VarInt 0: init, 1: add, 2: remove
Crafting Recipe Book Open Boolean If true, then the crafting recipe book will be open when the player opens its inventory.
Crafting Recipe Book Filter Active Boolean If true, then the filtering option is active when the players opens its inventory.
Smelting Recipe Book Open Boolean If true, then the smelting recipe book will be open when the player opens its inventory.
Smelting Recipe Book Filter Active Boolean If true, then the filtering option is active when the players opens its inventory.
Array size 1 VarInt Number of elements in the following array
Recipe IDs Array of Identifier
Array size 2 Optional VarInt Number of elements in the following array, only present if mode is 0 (init)
Recipe IDs Optional Array of Identifier, only present if mode is 0 (init)

Action:

  • 0 (init) = All the recipes in the list 2 will added to the recipe book. All the recipes in list 1 will be tagged as displayed, recipes that aren't tagged will be shown in the notification. VERIFY LIST ORDER?
  • 1 (add) = All the recipes in the list are added and their icon will be shown in the notification.
  • 2 (remove) = Remove all the recipes in the list. This allows them to re-displayed when they are readded.

Destroy Entities

Sent by the server when a list of entities is to be destroyed on the client.

Packet ID State Bound To Field Name Field Type Notes
0x38 Play Client Count VarInt Number of elements in the following array
Entity IDs Array of VarInt The list of entities of destroy

Remove Entity Effect

Packet ID State Bound To Field Name Field Type Notes
0x39 Play Client Entity ID VarInt
Effect ID Byte See this table

Resource Pack Send

Packet ID State Bound To Field Name Field Type Notes
0x3A Play Client URL String (32767) The URL to the resource pack.
Hash String (40) A 40 character hexadecimal and lowercase SHA-1 hash of the resource pack file. (must be lower case in order to work)
If it's not a 40 character hexadecimal string, the client will not use it for hash verification and likely waste bandwidth — but it will still treat it as a unique id

Respawn

To change the player's dimension (overworld/nether/end), send them a respawn packet with the appropriate dimension, followed by prechunks/chunks for the new dimension, and finally a position and look packet. You do not need to unload chunks, the client will do it automatically.

Packet ID State Bound To Field Name Field Type Notes
0x3B Play Client Dimension Int Enum -1: The Nether, 0: The Overworld, 1: The End
Hashed seed Long First 8 bytes of the SHA-256 hash of the world's seed.
Gamemode Unsigned Byte 0: survival, 1: creative, 2: adventure, 3: spectator. The hardcore flag is not included
Level Type String (16) Same as Join Game

Warning.png Avoid changing player's dimension to same dimension they were already in unless they are dead. If you change the dimension to one they are already in, weird bugs can occur, such as the player being unable to attack other players in new world (until they die and respawn).

If you must respawn a player in the same dimension without killing them, send two respawn packets, one to a different world and then another to the world you want. You do not need to complete the first respawn; it only matters that you send two packets.

Entity Head Look

Changes the direction an entity's head is facing.

While sending the Entity Look packet changes the vertical rotation of the head, sending this packet appears to be necessary to rotate the head horizontally.

Packet ID State Bound To Field Name Field Type Notes
0x3C Play Client Entity ID VarInt
Head Yaw Angle New angle, not a delta

Select Advancement Tab

Sent by the server to indicate that the client should switch advancement tab. Sent either when the client switches tab in the GUI or when an advancement in another tab is made.

Packet ID State Bound To Field Name Field Type Notes
0x3D Play Client Has id Boolean Indicates if the next field is present
Optional Identifier String (32767) See below

The Identifier can be one of the following:

Optional Identifier
minecraft:story/root
minecraft:nether/root
minecraft:end/root
minecraft:adventure/root
minecraft:husbandry/root

If no or an invalid identifier is sent, the client will switch to the first tab in the GUI.

World Border

Packet ID State Bound To Field Name Field Type Notes
0x3E Play Client Action VarInt Enum Determines the format of the rest of the packet
Action Field Name
0: set size Diameter Double Length of a single side of the world border, in meters
1: lerp size Old Diameter Double Current length of a single side of the world border, in meters
New Diameter Double Target length of a single side of the world border, in meters
Speed VarLong Number of real-time milliseconds until New Diameter is reached. It appears that Notchian server does not sync world border speed to game ticks, so it gets out of sync with server lag. If the world border is not moving, this is set to 0.
2: set center X Double
Z Double
3: initialize X Double
Z Double
Old Diameter Double Current length of a single side of the world border, in meters
New Diameter Double Target length of a single side of the world border, in meters
Speed VarLong Number of real-time milliseconds until New Diameter is reached. It appears that Notchian server does not sync world border speed to game ticks, so it gets out of sync with server lag. If the world border is not moving, this is set to 0.
Portal Teleport Boundary VarInt Resulting coordinates from a portal teleport are limited to ±value. Usually 29999984.
Warning Time VarInt In seconds as set by /worldborder warning time
Warning Blocks VarInt In meters
4: set warning time Warning Time VarInt In seconds as set by /worldborder warning time
5: set warning blocks Warning Blocks VarInt In meters

The Notchian client determines how solid to display the warning by comparing to whichever is higher, the warning distance or whichever is lower, the distance from the current diameter to the target diameter or the place the border will be after warningTime seconds. In pseudocode:

distance = max(min(resizeSpeed * 1000 * warningTime, abs(targetDiameter - currentDiameter)), warningDistance);
if (playerDistance < distance) {
    warning = 1.0 - playerDistance / distance;
} else {
    warning = 0.0;
}

Camera

Sets the entity that the player renders from. This is normally used when the player left-clicks an entity while in spectator mode.

The player's camera will move with the entity and look where it is looking. The entity is often another player, but can be any type of entity. The player is unable to move this entity (move packets will act as if they are coming from the other entity).

If the given entity is not loaded by the player, this packet is ignored. To return control to the player, send this packet with their entity ID.

The Notchian server resets this (sends it back to the default entity) whenever the spectated entity is killed or the player sneaks, but only if they were spectating an entity. It also sends this packet whenever the player switches out of spectator mode (even if they weren't spectating an entity).

Packet ID State Bound To Field Name Field Type Notes
0x3F Play Client Camera ID VarInt ID of the entity to set the client's camera to

The notchian also loads certain shaders for given entities:

  • Creeper → shaders/post/creeper.json
  • Spider (and cave spider) → shaders/post/spider.json
  • Enderman → shaders/post/invert.json
  • Anything else → the current shader is unloaded

Held Item Change (clientbound)

Sent to change the player's slot selection.

Packet ID State Bound To Field Name Field Type Notes
0x40 Play Client Slot Byte The slot which the player has selected (0–8)

Update View Position

Huh.png The following information needs to be added to this page:
Why is this even needed? Is there a better name for it? My guess is that it's something to do with logical behavior with latency, but it still seems weird.

Updates the client's location. This is used to determine what chunks should remain loaded and if a chunk load should be ignored; chunks outside of the view distance may be unloaded.

Sent whenever the player moves across a chunk border horizontally, and also (according to testing) for any integer change in the vertical axis, even if it doesn't go across a chunk section border.

Packet ID State Bound To Field Name Field Type Notes
0x41 Play Client Chunk X VarInt Chunk X coordinate of the player's position
Chunk Z VarInt Chunk Z coordinate of the player's position

Update View Distance

Sent by the integrated singleplayer server when changing render distance. Does not appear to be used by the dedicated server, as view-distance in server.properties cannot be changed at runtime.

Packet ID State Bound To Field Name Field Type Notes
0x42 Play Client View Distance VarInt Render distance (2-32)

Display Scoreboard

This is sent to the client when it should display a scoreboard.

Packet ID State Bound To Field Name Field Type Notes
0x43 Play Client Position Byte The position of the scoreboard. 0: list, 1: sidebar, 2: below name, 3 - 18: team specific sidebar, indexed as 3 + team color.
Score Name String (16) The unique name for the scoreboard to be displayed.

Entity Metadata

Updates one or more metadata properties for an existing entity. Any properties not included in the Metadata field are left unchanged.

Packet ID State Bound To Field Name Field Type Notes
0x44 Play Client Entity ID VarInt
Metadata Entity Metadata

Attach Entity

This packet is sent when an entity has been leashed to another entity.

Packet ID State Bound To Field Name Field Type Notes
0x45 Play Client Attached Entity ID Int Attached entity's EID
Holding Entity ID Int ID of the entity holding the lead. Set to -1 to detach.

Entity Velocity

Velocity is believed to be in units of 1/8000 of a block per server tick (50ms); for example, -1343 would move (-1343 / 8000) = −0.167875 blocks per tick (or −3,3575 blocks per second).

Packet ID State Bound To Field Name Field Type Notes
0x46 Play Client Entity ID VarInt
Velocity X Short Velocity on the X axis
Velocity Y Short Velocity on the Y axis
Velocity Z Short Velocity on the Z axis

Entity Equipment

Packet ID State Bound To Field Name Field Type Notes
0x47 Play Client Entity ID VarInt Entity's EID
Slot VarInt Enum Equipment slot. 0: main hand, 1: off hand, 2–5: armor slot (2: boots, 3: leggings, 4: chestplate, 5: helmet)
Item Slot

Set Experience

Sent by the server when the client should change experience levels.

Packet ID State Bound To Field Name Field Type Notes
0x48 Play Client Experience bar Float Between 0 and 1
Level VarInt
Total Experience VarInt See Experience#Leveling up on the Minecraft Wiki for Total Experience to Level conversion

Update Health

Sent by the server to update/set the health of the player it is sent to.

Food saturation acts as a food “overcharge”. Food values will not decrease while the saturation is over zero. Players logging in automatically get a saturation of 5.0. Eating food increases the saturation as well as the food bar.

Packet ID State Bound To Field Name Field Type Notes
0x49 Play Client Health Float 0 or less = dead, 20 = full HP
Food VarInt 0–20
Food Saturation Float Seems to vary from 0.0 to 5.0 in integer increments

Scoreboard Objective

This is sent to the client when it should create a new scoreboard objective or remove one.

Packet ID State Bound To Field Name Field Type Notes
0x4A Play Client Objective Name String (16) An unique name for the objective
Mode Byte 0 to create the scoreboard. 1 to remove the scoreboard. 2 to update the display text.
Objective Value Optional Chat Only if mode is 0 or 2. The text to be displayed for the score
Type Optional VarInt enum Only if mode is 0 or 2. 0 = "integer", 1 = "hearts".

Set Passengers

Packet ID State Bound To Field Name Field Type Notes
0x4B Play Client Entity ID VarInt Vehicle's EID
Passenger Count VarInt Number of elements in the following array
Passengers Array of VarInt EIDs of entity's passengers

Teams

Creates and updates teams.

Packet ID State Bound To Field Name Field Type Notes
0x4C Play Client Team Name String (16) A unique name for the team. (Shared with scoreboard).
Mode Byte Determines the layout of the remaining packet
0: create team Team Display Name Chat
Friendly Flags Byte Bit mask. 0x01: Allow friendly fire, 0x02: can see invisible players on same team
Name Tag Visibility String Enum (32) always, hideForOtherTeams, hideForOwnTeam, never
Collision Rule String Enum (32) always, pushOtherTeams, pushOwnTeam, never
Team Color VarInt enum Used to color the name of players on the team; see below
Team Prefix Chat Displayed before the names of players that are part of this team
Team Suffix Chat Displayed after the names of players that are part of this team
Entity Count VarInt Number of elements in the following array
Entities Array of String (40) Identifiers for the entities in this team. For players, this is their username; for other entities, it is their UUID.
1: remove team no fields no fields
2: update team info Team Display Name Chat
Friendly Flags Byte Bit mask. 0x01: Allow friendly fire, 0x02: can see invisible entities on same team
Name Tag Visibility String Enum (32) always, hideForOtherTeams, hideForOwnTeam, never
Collision Rule String Enum (32) always, pushOtherTeams, pushOwnTeam, never
Team Color VarInt enum Used to color the name of players on the team; see below
Team Prefix Chat Displayed before the names of players that are part of this team
Team Suffix Chat Displayed after the names of players that are part of this team
3: add players to team Entity Count VarInt Number of elements in the following array
Entities Array of String (40) Identifiers for the entities added. For players, this is their username; for other entities, it is their UUID.
4: remove players from team Entity Count VarInt Number of elements in the following array
Entities Array of String (40) Identifiers for the entities removed. For players, this is their username; for other entities, it is their UUID.

Team Color: The color of a team defines how the names of the team members are visualized; any formatting code can be used. The following table lists all the possible values.

ID Formatting
0-15 Color formatting, same values as Chat colors.
16 Obfuscated
17 Bold
18 Strikethrough
19 Underlined
20 Italic
21 Reset

Update Score

This is sent to the client when it should update a scoreboard item.

Packet ID State Bound To Field Name Field Type Notes
0x4D Play Client Entity Name String (40) The entity whose score this is. For players, this is their username; for other entities, it is their UUID.
Action Byte 0 to create/update an item. 1 to remove an item.
Objective Name String (16) The name of the objective the score belongs to
Value Optional VarInt The score to be displayed next to the entry. Only sent when Action does not equal 1.

Spawn Position

Sent by the server after login to specify the coordinates of the spawn point (the point at which players spawn at, and which the compass points to). It can be sent at any time to update the point compasses point at.

Packet ID State Bound To Field Name Field Type Notes
0x4E Play Client Location Position Spawn location

Time Update

Time is based on ticks, where 20 ticks happen every second. There are 24000 ticks in a day, making Minecraft days exactly 20 minutes long.

The time of day is based on the timestamp modulo 24000. 0 is sunrise, 6000 is noon, 12000 is sunset, and 18000 is midnight.

The default SMP server increments the time by 20 every second.

Packet ID State Bound To Field Name Field Type Notes
0x4F Play Client World Age Long In ticks; not changed by server commands
Time of day Long The world (or region) time, in ticks. If negative the sun will stop moving at the Math.abs of the time

Title

Packet ID State Bound To Field Name Field Type Notes
0x50 Play Client Action VarInt Enum
Action Field Name
0: set title Title Text Chat
1: set subtitle Subtitle Text Chat
2: set action bar Action bar text Chat Displays a message above the hotbar (the same as position 2 in Chat Message (clientbound), except that it correctly renders formatted chat. See MC-119145 for more information.)
3: set times and display Fade In Int Ticks to spend fading in
Stay Int Ticks to keep the title displayed
Fade Out Int Ticks to spend out, not when to start fading out
4: hide no fields no fields
5: reset no fields no fields

“Hide” makes the title disappear, but if you run times again the same title will appear. “Reset” erases the text.

The title is visible on screen for Fade In + Stay + Fade Out ticks.

Entity Sound Effect

Plays a sound effect from an entity.

Packet ID State Bound To Field Name Field Type Notes
0x51 Play Client Sound ID VarInt ID of hardcoded sound event (events as of 1.15.2)
Sound Category VarInt Enum The category that this sound will be played from (current categories)
Entity ID VarInt
Volume Float 1.0 is 100%, capped between 0.0 and 1.0 by Notchian clients
Pitch Float Float between 0.5 and 2.0 by Notchian clients

Sound Effect

This packet is used to play a number of hardcoded sound events. For custom sounds, use Named Sound Effect.

Warning.png Numeric sound effect IDs are liable to change between versions

Packet ID State Bound To Field Name Field Type Notes
0x52 Play Client Sound ID VarInt ID of hardcoded sound event (events as of 1.15.2)
Sound Category VarInt Enum The category that this sound will be played from (current categories)
Effect Position X Int Effect X multiplied by 8 (fixed-point number with only 3 bits dedicated to the fractional part)
Effect Position Y Int Effect Y multiplied by 8 (fixed-point number with only 3 bits dedicated to the fractional part)
Effect Position Z Int Effect Z multiplied by 8 (fixed-point number with only 3 bits dedicated to the fractional part)
Volume Float 1.0 is 100%, capped between 0.0 and 1.0 by Notchian clients
Pitch Float Float between 0.5 and 2.0 by Notchian clients

Stop Sound

Packet ID State Bound To Field Name Field Type Notes
0x53 Play Client Flags Byte Controls which fields are present.
Source Optional VarInt enum Only if flags is 3 or 1 (bit mask 0x1). See below. If not present, then sounds from all sources are cleared.
Sound Optional Identifier Only if flags is 2 or 3 (bit mask 0x2). A sound effect name, see Named Sound Effect. If not present, then all sounds are cleared.

Categories:

Name Value
master 0
music 1
record 2
weather 3
block 4
hostile 5
neutral 6
player 7
ambient 8
voice 9

Player List Header And Footer

This packet may be used by custom servers to display additional information above/below the player list. It is never sent by the Notchian server.

Packet ID State Bound To Field Name Field Type Notes
0x54 Play Client Header Chat To remove the header, send a empty translatable component: {"translate":""}
Footer Chat To remove the footer, send a empty translatable component: {"translate":""}

NBT Query Response

Sent in response to Query Block NBT or Query Entity NBT.

Packet ID State Bound To Field Name Field Type Notes
0x55 Play Client Transaction ID VarInt Can be compared to the one sent in the original query packet.
NBT NBT Tag The NBT of the block or entity. May be a TAG_END (0) in which case no NBT is present.

Collect Item

Sent by the server when someone picks up an item lying on the ground — its sole purpose appears to be the animation of the item flying towards you. It doesn't destroy the entity in the client memory, and it doesn't add it to your inventory. The server only checks for items to be picked up after each Player Position (and Player Position And Look) packet sent by the client. The collector entity can be any entity; it does not have to be a player. The collected entity also can be any entity, but the Notchian server only uses this for items, experience orbs, and the different varieties of arrows.

Packet ID State Bound To Field Name Field Type Notes
0x56 Play Client Collected Entity ID VarInt
Collector Entity ID VarInt
Pickup Item Count VarInt Seems to be 1 for XP orbs, otherwise the number of items in the stack.

Entity Teleport

This packet is sent by the server when an entity moves more than 8 blocks.

Packet ID State Bound To Field Name Field Type Notes
0x57 Play Client Entity ID VarInt
X Double
Y Double
Z Double
Yaw Angle New angle, not a delta
Pitch Angle New angle, not a delta
On Ground Boolean

Advancements

Packet ID State Bound To Field Name Field Type Notes
0x58 Play Client Reset/Clear Boolean Whether to reset/clear the current advancements
Mapping size VarInt Size of the following array
Advancement mapping Key Array Identifier The identifier of the advancement
Value Advancement See below
List size VarInt Size of the following array
Identifiers Array of Identifier The identifiers of the advancements that should be removed
Progress size VarInt Size of the following array
Progress mapping Key Array Identifier The identifier of the advancement
Value Advancement progress See below

Advancement structure:

Field Name Field Type Notes
Has parent Boolean Indicates whether the next field exists.
Parent id Optional Identifier The identifier of the parent advancement.
Has display Boolean Indicates whether the next field exists
Display data Optional advancement display See below.
Number of criteria VarInt Size of the following array
Criteria Key Array Identifier The identifier of the criterion
Value Void There is no content written here. Perhaps this will be expanded in the future?
Array length VarInt Number of arrays in the following array
Requirements Array length 2 Array VarInt Number of elements in the following array
Requirement Array of String Array of required criteria

Advancement display:

Field Name Field Type Notes
Title Chat
Description Chat
Icon Slot
Frame type VarInt enum 0 = task, 1 = challenge, 2 = goal
Flags Integer 0x1: has background texture; 0x2: show_toast; 0x4: hidden
Background texture Optional Identifier Background texture location. Only if flags indicates it.
X coord Float
Y coord Float

Advancement progress:

Field Name Field Type Notes
Size VarInt Size of the following array
Criteria Criterion identifier Array Identifier The identifier of the criterion.
Criterion progress Criterion progress

Criterion progress:

Field Name Field Type Notes
Achieved Boolean If true, next field is present
Date of achieving Optional Long As returned by Date.getTime

Entity Properties

Sets attributes on the given entity.

Packet ID State Bound To Field Name Field Type Notes
0x59 Play Client Entity ID VarInt
Number Of Properties Int Number of elements in the following array
Property Key Array String (64) See below
Value Double See below
Number Of Modifiers VarInt Number of elements in the following array
Modifiers Array of Modifier Data See Attribute#Modifiers. Modifier Data defined below.

Known Key values (see also Attribute#Modifiers):

Key Default Min Max Label
generic.maxHealth 20.0 0.0 1024.0 Max Health
generic.followRange 32.0 0.0 2048.0 Follow Range
generic.knockbackResistance 0.0 0.0 1.0 Knockback Resistance
generic.movementSpeed 0.699999988079071 0.0 1024.0 Movement Speed
generic.attackDamage 2.0 0.0 2048.0 Attack Damage
generic.attackSpeed 4.0 0.0 1024.0 Attack Speed
generic.flyingSpeed 0.4000000059604645 0.0 1024.0 Flying Speed
horse.jumpStrength 0.7 0.0 2.0 Jump Strength
zombie.spawnReinforcements 0.0 0.0 1.0 Spawn Reinforcements Chance
generic.reachDistance 5.0 0.0 1024.0 Player Reach Distance (Forge only)
forge.swimSpeed 1.0 0.0 1024.0 Swimming Speed (Forge only)

Modifier Data structure:

Field Name Field Type Notes
UUID UUID
Amount Double May be positive or negative
Operation Byte See below

The operation controls how the base value of the modifier is changed.

  • 0: Add/subtract amount
  • 1: Add/subtract amount percent of the current value
  • 2: Multiply by amount percent

All of the 0's are applied first, and then the 1's, and then the 2's.

Entity Effect

Packet ID State Bound To Field Name Field Type Notes
0x5A Play Client Entity ID VarInt
Effect ID Byte See this table
Amplifier Byte Notchian client displays effect level as Amplifier + 1
Duration VarInt Seconds
Flags Byte Bit field, see below.

Within flags:

  • 0x01: Is ambient - was the effect spawned from a beacon? All beacon-generated effects are ambient. Ambient effects use a different icon in the HUD (blue border rather than gray). If all effects on an entity are ambient, the "Is potion effect ambient" living metadata field should be set to true. Usually should not be enabled.
  • 0x02: Show particles - should all particles from this effect be hidden? Effects with particles hidden are not included in the calculation of the effect color, and are not rendered on the HUD (but are still rendered within the inventory). Usually should be enabled.
  • 0x04: Show icon - should the icon be displayed on the client? Usually should be enabled.

Declare Recipes

Packet ID State Bound To Field Name Field Type Notes
0x5B Play Client Num Recipes VarInt Number of elements in the following array
Recipe Recipe ID Array Identifier
Type String The recipe type, see below
Data Optional, varies Additional data for the recipe. For some types, there will be no data.

Recipe types:

Type Description Data
crafting_shapeless Shapeless crafting recipe. All items in the ingredient list must be present, but in any order/slot. As follows:
Name Type Description
Group String Used to group similar recipes together in the recipe book. Tag is present in recipe JSON.
Ingredient count VarInt Number of elements in the following array
Ingredients Array of Ingredient
Result Slot
crafting_shaped Shaped crafting recipe. All items must be present in the same pattern (which may be flipped horizontally or translated) As follows:
Name Type Description
Width VarInt
Height VarInt
Group String Used to group similar recipes together in the recipe book. Tag is present in recipe JSON.
Ingredients Array of Ingredient Length is width * height. Indexed by x + (y * width).
Result Slot
crafting_special_armordye Recipe for dying leather armor None
crafting_special_bookcloning Recipe for copying contents of written books None
crafting_special_mapcloning Recipe for copying maps None
crafting_special_mapextending Recipe for adding paper to maps None
crafting_special_firework_rocket Recipe for making firework rockets None
crafting_special_firework_star Recipe for making firework stars None
crafting_special_firework_star_fade Recipe for making firework stars fade between multiple colors None
crafting_special_repairitem Recipe for repairing items via crafting None
crafting_special_tippedarrow Recipe for crafting tipped arrows None
crafting_special_bannerduplicate Recipe for copying banner patterns None
crafting_special_banneraddpattern Recipe for adding patterns to banners None
crafting_special_shielddecoration Recipe for applying a banner's pattern to a shield None
crafting_special_shulkerboxcoloring Recipe for recoloring a shulker box None
smelting Smelting recipe As follows:
Name Type Description
Group String Used to group similar recipes together in the recipe book.
Ingredient Ingredient
Result Slot
Experience Float
Cooking time VarInt

Ingredient is defined as:

Name Type Description
Count VarInt Number of elements in the following array
Items Array of Slot Any item in this array may be used for the recipe. The count of each item should be 1.

Tags

Packet ID State Bound To Field Name Field Type Notes
0x5C Play Client Block Tags (See below) IDs are block IDs
Item Tags (See below) IDs are item IDs
Fluid Tags (See below) IDs are fluid IDs
Entity Tags (See below) IDs are entity IDs

Tags look like:

Field Name Field Type Notes
Length VarInt Number of elements in the following array
Tags Tag name Array Identifier
Count VarInt Number of elements in the following array
Entries Array of VarInt Numeric ID of the block/item.

Serverbound

Teleport Confirm

Sent by client as confirmation of Player Position And Look.

Packet ID State Bound To Field Name Field Type Notes
0x00 Play Server Teleport ID VarInt The ID given by the Player Position And Look packet

Query Block NBT

Used when Shift+F3+I is pressed while looking at a block.

Packet ID State Bound To Field Name Field Type Notes
0x01 Play Server Transaction ID VarInt An incremental ID so that the client can verify that the response matches.
Location Position The location of the block to check.

Set Difficulty

Must have at least op level 2 to use. Appears to only be used on singleplayer; the difficulty buttons are still disabled in multiplayer.

Packet ID State Bound To Field Name Field Type Notes
0x02 Play Server New difficulty Byte 0: peaceful, 1: easy, 2: normal, 3: hard

Chat Message (serverbound)

Used to send a chat message to the server. The message may not be longer than 256 characters or else the server will kick the client.

If the message starts with a /, the server will attempt to interpret it as a command. Otherwise, the server will broadcast the same chat message to all players on the server (including the player that sent the message), prepended with player's name. Specifically, it will respond with a translate chat component, "chat.type.text" with the first parameter set to the display name of the player (including some chat component logic to support clicking the name to send a PM) and the second parameter set to the message. See processing chat for more information.

Packet ID State Bound To Field Name Field Type Notes
0x03 Play Server Message String (256) The client sends the raw input, not a Chat component

Client Status

Packet ID State Bound To Field Name Field Type Notes
0x04 Play Server Action ID VarInt Enum See below

Action ID values:

Action ID Action Notes
0 Perform respawn Sent when the client is ready to complete login and when the client is ready to respawn after death.
1 Request stats Sent when the client opens the Statistics menu

Client Settings

Sent when the player connects, or when settings are changed.

Packet ID State Bound To Field Name Field Type Notes
0x05 Play Server Locale String (16) e.g. en_GB
View Distance Byte Client-side render distance, in chunks
Chat Mode VarInt Enum 0: enabled, 1: commands only, 2: hidden. See processing chat for more information.
Chat Colors Boolean “Colors” multiplayer setting
Displayed Skin Parts Unsigned Byte Bit mask, see below
Main Hand VarInt Enum 0: Left, 1: Right

Displayed Skin Parts flags:

  • Bit 0 (0x01): Cape enabled
  • Bit 1 (0x02): Jacket enabled
  • Bit 2 (0x04): Left Sleeve enabled
  • Bit 3 (0x08): Right Sleeve enabled
  • Bit 4 (0x10): Left Pants Leg enabled
  • Bit 5 (0x20): Right Pants Leg enabled
  • Bit 6 (0x40): Hat enabled

The most significant bit (bit 7, 0x80) appears to be unused.

Tab-Complete (serverbound)

Sent when the client needs to tab-complete a minecraft:ask_server suggestion type.

Packet ID State Bound To Field Name Field Type Notes
0x06 Play Server Transaction Id VarInt The id received in the tab completion request packet, must match or the client will ignore this packet. Client generates this and increments it each time it sends another tab completion that doesn't get a response.
Text String (32500) All text behind the cursor without the / (e.g. to the left of the cursor in left-to-right languages like English)

Window Confirmation (serverbound)

If a confirmation sent by the client was not accepted, the server will reply with a Window Confirmation (clientbound) packet with the Accepted field set to false. When this happens, the client must send this packet to apologize (as with movement), otherwise the server ignores any successive confirmations.

Packet ID State Bound To Field Name Field Type Notes
0x07 Play Server Window ID Byte The ID of the window that the action occurred in
Action Number Short Every action that is to be accepted has a unique number. This number is an incrementing integer (starting at 1) with separate counts for each window ID.
Accepted Boolean Whether the action was accepted

Click Window Button

Used when clicking on window buttons. Until 1.14, this was only used by enchantment tables.

Packet ID State Bound To Field Name Field Type Notes
0x07 Play Server Window ID Byte The ID of the window sent by Open Window
Button ID Byte Meaning depends on window type; see below
Window type ID Meaning
Enchantment Table 0 Topmost enchantment
1 Middle enchantment
2 Bottom enchantment
Lectern 1 Previous page (which does give a redstone output)
2 Next page
3 Take Book
100+page Opened page number - 100 + number
Stonecutter Recipe button number - 4*row + col. Depends on the item.
Loom Recipe button number - 4*row + col. Depends on the item.

Click Window

This packet is sent by the player when it clicks on a slot in a window.

Packet ID State Bound To Field Name Field Type Notes
0x09 Play Server Window ID Unsigned Byte The ID of the window which was clicked. 0 for player inventory.
Slot Short The clicked slot number, see below
Button Byte The button used in the click, see below
Action Number Short A unique number for the action, implemented by Notchian as a counter, starting at 1 (different counter for every window ID). Used by the server to send back a Confirm Transaction (clientbound).
Mode VarInt Enum Inventory operation mode, see below
Clicked item Slot The clicked slot. Has to be empty (item ID = -1) for drop mode.

See Inventory for further information about how slots are indexed.

When right-clicking on a stack of items, half the stack will be picked up and half left in the slot. If the stack is an odd number, the half left in the slot will be smaller of the amounts.

The distinct type of click performed by the client is determined by the combination of the Mode and Button fields.

Mode Button Slot Trigger
0 0 Normal Left mouse click
1 Normal Right mouse click
1 0 Normal Shift + left mouse click
1 Normal Shift + right mouse click (identical behavior)
2 0 Normal Number key 1
1 Normal Number key 2
2 Normal Number key 3
8 Normal Number key 9
3 2 Normal Middle click, only defined for creative players in non-player inventories.
4 0 Normal* Drop key (Q) (* Clicked item is different, see above)
1 Normal* Ctrl + Drop key (Ctrl-Q) (drops full stack)
0 -999 Left click outside inventory holding nothing (no-op)
1 -999 Right click outside inventory holding nothing (no-op)
5 0 -999 Starting left mouse drag
4 -999 Starting right mouse drag
8 -999 Starting middle mouse drag, only defined for creative players in non-player inventories. (Note: the vanilla client will still incorrectly send this for non-creative players - see MC-46584)
1 Normal Add slot for left-mouse drag
5 Normal Add slot for right-mouse drag
9 Normal Add slot for middle-mouse drag, only defined for creative players in non-player inventories. (Note: the vanilla client will still incorrectly send this for non-creative players - see MC-46584)
2 -999 Ending left mouse drag
6 -999 Ending right mouse drag
10 -999 Ending middle mouse drag, only defined for creative players in non-player inventories. (Note: the vanilla client will still incorrectly send this for non-creative players - see MC-46584)
6 0 Normal Double click

Starting from version 1.5, “painting mode” is available for use in inventory windows. It is done by picking up stack of something (more than 1 item), then holding mouse button (left, right or middle) and dragging held stack over empty (or same type in case of right button) slots. In that case client sends the following to server after mouse button release (omitting first pickup packet which is sent as usual):

  1. packet with mode 5, slot -999, button (0 for left | 4 for right);
  2. packet for every slot painted on, mode is still 5, button (1 | 5);
  3. packet with mode 5, slot -999, button (2 | 6);

If any of the painting packets other than the “progress” ones are sent out of order (for example, a start, some slots, then another start; or a left-click in the middle) the painting status will be reset.

The server will send back a Confirm Transaction packet. If the click was not accepted, the client must send a matching serverbound confirm transaction packet before sending more Click Window packets, otherwise the server will reject them silently. The Notchian server also sends a Window Items packet for the open window and Set Slot packets for the clicked and cursor slot, but only when the click was not accepted, probably to resynchronize client and server.

Close Window (serverbound)

This packet is sent by the client when closing a window.

Notchian clients send a Close Window packet with Window ID 0 to close their inventory even though there is never an Open Window packet for the inventory.

Packet ID State Bound To Field Name Field Type Notes
0x0A Play Server Window ID Unsigned Byte This is the ID of the window that was closed. 0 for player inventory.

Plugin Message (serverbound)

Main article: Plugin channels

Mods and plugins can use this to send their data. Minecraft itself uses some plugin channels. These internal channels are in the minecraft namespace.

More documentation on this: http://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/

Note that the length of Data is known only from the packet length, since the packet has no length field of any kind.

Packet ID State Bound To Field Name Field Type Notes
0x0B Play Server Channel Identifier Name of the plugin channel used to send the data
Data Byte Array Any data, depending on the channel. minecraft: channels are documented here. The length of this array must be inferred from the packet length.

Edit Book

Packet ID State Bound To Field Name Field Type Notes
0x0C Play Server New book Slot
Is signing Boolean True if the player is signing the book; false if the player is saving a draft.
Hand VarInt enum 0: Main hand, 1: Off hand

When editing a draft, the NBT section of the Slot contains this:

TAG_Compound(''): 1 entry
{
  TAG_List('pages'): 2 entries
  {
    TAG_String(0): 'Something on Page 1'
    TAG_String(1): 'Something on Page 2'
  }
}

When signing the book, it instead looks like this:

TAG_Compound(''): 3 entires
{
  TAG_String('author'): 'Steve'
  TAG_String('title'): 'A Wonderful Book'
  TAG_List('pages'): 2 entries
  {
    TAG_String(0): 'Something on Page 1'
    TAG_String(1): 'Something on Page 2'
  }
}

Entity NBT Request

Used when Shift+F3+I is pressed while looking at an entity.

Packet ID State Bound To Field Name Field Type Notes
0x0D Play Server Transaction ID VarInt An incremental ID so that the client can verify that the response matches.
Entity ID VarInt The ID of the entity to query.

Interact Entity

This packet is sent from the client to the server when the client attacks or right-clicks another entity (a player, minecart, etc).

A Notchian server only accepts this packet if the entity being attacked/used is visible without obstruction and within a 4-unit radius of the player's position.

Note that middle-click in creative mode is interpreted by the client and sent as a Creative Inventory Action packet instead.

Packet ID State Bound To Field Name Field Type Notes
0x0E Play Server Entity ID VarInt The ID of the entity to interact
Type VarInt Enum 0: interact, 1: attack, 2: interact at
Target X Optional Float Only if Type is interact at
Target Y Optional Float Only if Type is interact at
Target Z Optional Float Only if Type is interact at
Hand Optional VarInt Enum Only if Type is interact or interact at; 0: main hand, 1: off hand

Keep Alive (serverbound)

The server will frequently send out a keep-alive, each containing a random ID. The client must respond with the same packet.

Packet ID State Bound To Field Name Field Type Notes
0x0F Play Server Keep Alive ID Long

Lock Difficulty

Must have at least op level 2 to use. Appears to only be used on singleplayer; the difficulty buttons are still disabled in multiplayer.

Packet ID State Bound To Field Name Field Type Notes
0x10 Play Server Locked Boolean

Player Position

Updates the player's XYZ position on the server.

Checking for moving too fast is achieved like this:

  • Each server tick, the player's current position is stored
  • When a player moves, the changes in x, y, and z coordinates are compared with the positions from the previous tick (Δx, Δy, Δz)
  • Total movement distance squared is computed as Δx² + Δy² + Δz²
  • The expected movement distance squared is computed as velocityX² + veloctyY² + velocityZ²
  • If the total movement distance squared value minus the expected movement distance squared value is more than 100 (300 if the player is using an elytra), they are moving too fast.

If the player is moving too fast, it will be logged that "<player> moved too quickly! " followed by the change in x, y, and z, and the player will be teleported back to their current (before this packet) serverside position.

Also, if the absolute value of X or the absolute value of Z is a value greater than 3.2×107, or X, Y, or Z are not finite (either positive infinity, negative infinity, or NaN), the client will be kicked for “Invalid move player packet received”.

Packet ID State Bound To Field Name Field Type Notes
0x11 Play Server X Double Absolute position
Feet Y Double Absolute feet position, normally Head Y - 1.62
Z Double Absolute position
On Ground Boolean True if the client is on the ground, false otherwise

Player Position And Rotation (serverbound)

A combination of Player Rotation and Player Position.

Packet ID State Bound To Field Name Field Type Notes
0x12 Play Server X Double Absolute position
Feet Y Double Absolute feet position, normally Head Y - 1.62
Z Double Absolute position
Yaw Float Absolute rotation on the X Axis, in degrees
Pitch Float Absolute rotation on the Y Axis, in degrees
On Ground Boolean True if the client is on the ground, false otherwise

Player Rotation

The unit circle for yaw
The unit circle of yaw, redrawn

Updates the direction the player is looking in.

Yaw is measured in degrees, and does not follow classical trigonometry rules. The unit circle of yaw on the XZ-plane starts at (0, 1) and turns counterclockwise, with 90 at (-1, 0), 180 at (0,-1) and 270 at (1, 0). Additionally, yaw is not clamped to between 0 and 360 degrees; any number is valid, including negative numbers and numbers greater than 360.

Pitch is measured in degrees, where 0 is looking straight ahead, -90 is looking straight up, and 90 is looking straight down.

The yaw and pitch of player (in degrees), standing at point (x0, y0, z0) and looking towards point (x, y, z) can be calculated with:

dx = x-x0
dy = y-y0
dz = z-z0
r = sqrt( dx*dx + dy*dy + dz*dz )
yaw = -atan2(dx,dz)/PI*180
if yaw < 0 then
    yaw = 360 + yaw
pitch = -arcsin(dy/r)/PI*180

You can get a unit vector from a given yaw/pitch via:

x = -cos(pitch) * sin(yaw)
y = -sin(pitch)
z =  cos(pitch) * cos(yaw)
Packet ID State Bound To Field Name Field Type Notes
0x13 Play Server Yaw Float Absolute rotation on the X Axis, in degrees
Pitch Float Absolute rotation on the Y Axis, in degrees
On Ground Boolean True if the client is on the ground, False otherwise

Player Movement

This packet as well as Player Position, Player Look, and Player Position And Look are called the “serverbound movement packets”. Vanilla clients will send Player Position once every 20 ticks even for a stationary player.

This packet is used to indicate whether the player is on ground (walking/swimming), or airborne (jumping/falling).

When dropping from sufficient height, fall damage is applied when this state goes from false to true. The amount of damage applied is based on the point where it last changed from true to false. Note that there are several movement related packets containing this state.

Packet ID State Bound To Field Name Field Type Notes
0x14 Play Server On Ground Boolean True if the client is on the ground, false otherwise

Vehicle Move (serverbound)

Sent when a player moves in a vehicle. Fields are the same as in Player Position And Look. Note that all fields use absolute positioning and do not allow for relative positioning.

Packet ID State Bound To Field Name Field Type Notes
0x15 Play Server X Double Absolute position (X coordinate)
Y Double Absolute position (Y coordinate)
Z Double Absolute position (Z coordinate)
Yaw Float Absolute rotation on the vertical axis, in degrees
Pitch Float Absolute rotation on the horizontal axis, in degrees

Steer Boat

Used to visually update whether boat paddles are turning. The server will update the Boat entity metadata to match the values here.

Packet ID State Bound To Field Name Field Type Notes
0x16 Play Server Left paddle turning Boolean
Right paddle turning Boolean

Right paddle turning is set to true when the left button or forward button is held; left paddle turning is set to true when the right button or forward button is set to true.

Pick Item

Used to swap out an empty space on the hotbar with the item in the given inventory slot. The Notchain client uses this for pick block functionality (middle click) to retrieve items from the inventory.


Packet ID State Bound To Field Name Field Type Notes
0x17 Play Server Slot to use VarInt See Inventory

The server will first search the player's hotbar for an empty slot, starting from the current slot and looping around to the slot before it. If there are no empty slots, it will start a second search from the current slot and find the first slot that does not contain an enchanted item. If there still are no slots that meet that criteria, then the server will use the currently selected slot.

After finding the appropriate slot, the server swaps the items and then send 3 packets:

  • Set Slot, with window ID set to -2 and slot set to the newly chosen slot and the item set to the item that is now in that slot (which was previously at the slot the client requested)
  • Set Slot, with window ID set to -2 and slot set to the slot the player requested, with the item that is now in that slot and was previously on the hotbar slot
  • Held Item Change, with the slot set to the newly chosen slot.

Craft Recipe Request

This packet is sent when a player clicks a recipe in the crafting book that is craftable (white border).

Packet ID State Bound To Field Name Field Type Notes
0x18 Play Server Window ID Byte
Recipe Identifier A recipe ID
Make all Boolean Affects the amount of items processed; true if shift is down when clicked

Player Abilities (serverbound)

The latter 2 fields are used to indicate the walking and flying speeds respectively, while the first field is used to determine the value of 4 booleans.

The vanilla client sends this packet when the player starts/stops flying with the Flags parameter changed accordingly. All other parameters are ignored by the vanilla server.

Packet ID State Bound To Field Name Field Type Notes
0x19 Play Server Flags Byte Bit mask. 0x08: damage disabled (god mode), 0x04: can fly, 0x02: is flying, 0x01: is Creative
Flying Speed Float
Walking Speed Float

Player Digging

Sent when the player mines a block. A Notchian server only accepts digging packets with coordinates within a 6-unit radius between the center of the block and 1.5 units from the player's feet (not their eyes).

Packet ID State Bound To Field Name Field Type Notes
0x1A Play Server Status VarInt Enum The action the player is taking against the block (see below)
Location Position Block position
Face Byte Enum The face being hit (see below)

Status can be one of seven values:

Value Meaning Notes
0 Started digging
1 Cancelled digging Sent when the player lets go of the Mine Block key (default: left click)
2 Finished digging Sent when the client thinks it is finished
3 Drop item stack Triggered by using the Drop Item key (default: Q) with the modifier to drop the entire selected stack (default: depends on OS). Location is always set to 0/0/0, Face is always set to -Y.
4 Drop item Triggered by using the Drop Item key (default: Q). Location is always set to 0/0/0, Face is always set to -Y.
5 Shoot arrow / finish eating Indicates that the currently held item should have its state updated such as eating food, pulling back bows, using buckets, etc. Location is always set to 0/0/0, Face is always set to -Y.
6 Swap item in hand Used to swap or assign an item to the second hand. Location is always set to 0/0/0, Face is always set to -Y.

The Face field can be one of the following values, representing the face being hit:

Value Offset Face
0 -Y Bottom
1 +Y Top
2 -Z North
3 +Z South
4 -X West
5 +X East

Entity Action

Sent by the client to indicate that it has performed certain actions: sneaking (crouching), sprinting, exiting a bed, jumping with a horse, and opening a horse's inventory while riding it.

Packet ID State Bound To Field Name Field Type Notes
0x1B Play Server Entity ID VarInt Player ID
Action ID VarInt Enum The ID of the action, see below
Jump Boost VarInt Only used by the “start jump with horse” action, in which case it ranges from 0 to 100. In all other cases it is 0.

Action ID can be one of the following values:

ID Action
0 Start sneaking
1 Stop sneaking
2 Leave bed
3 Start sprinting
4 Stop sprinting
5 Start jump with horse
6 Stop jump with horse
7 Open horse inventory
8 Start flying with elytra

Leave bed is only sent when the “Leave Bed” button is clicked on the sleep GUI, not when waking up due today time.

Open horse inventory is only sent when pressing the inventory key (default: E) while on a horse — all other methods of opening a horse's inventory (involving right-clicking or shift-right-clicking it) do not use this packet.

Steer Vehicle

Packet ID State Bound To Field Name Field Type Notes
0x1C Play Server Sideways Float Positive to the left of the player
Forward Float Positive forward
Flags Unsigned Byte Bit mask. 0x1: jump, 0x2: unmount

Also known as 'Input' packet.

Recipe Book Data

Packet ID State Bound To Field Name Field Type Notes
0x1D Play Server Type VarInt Determines the format of the rest of the packet
Type Field Name
0: Displayed Recipe Recipe ID Identifier A recipe ID
1: Recipe Book States Crafting Recipe Book Open Boolean Whether the player has the crafting recipe book currently opened/active.
Crafting Recipe Filter Active Boolean Whether the player has the crafting recipe book filter option currently active.
Smelting Recipe Book Open Boolean Whether the player has the smelting recipe book currently opened/active.
Smelting Recipe Filter Active Boolean Whether the player has the smelting recipe book filter option currently active.
Blasting Recipe Book Open Boolean May be swapped with smoking recipe book. Also, the notchian client appears to use the same value for both of those books currently.
Blasting Recipe Filter Active Boolean May be swapped with smoking recipe book. Also, the notchian client appears to use the same value for both of those books currently.
Smoking Recipe Book Open Boolean
Smoking Recipe Filter Active Boolean

The Recipe Book Status type is sent when one of the states changes.

Name Item

Sent as a player is renaming an item in an anvil (each keypress in the anvil UI sends a new Name Item packet). If the new name is empty, then the item loses its custom name (this is different from setting the custom name to the normal name of the item). The item name may be no longer than 35 characters long, and if it is longer than that, then the rename is silently ignored.

Packet ID State Bound To Field Name Field Type Notes
0x1E Play Server Item name String (32767) The new name of the item

Resource Pack Status

Packet ID State Bound To Field Name Field Type Notes
0x1F Play Server Result VarInt Enum 0: successfully loaded, 1: declined, 2: failed download, 3: accepted

Advancement Tab

Packet ID State Bound To Field Name Field Type Notes
0x20 Play Server Action VarInt enum 0: Opened tab, 1: Closed screen
Tab ID Optional identifier Only present if action is Opened tab

Select Trade

When a player selects a specific trade offered by a villager NPC.

Packet ID State Bound To Field Name Field Type Notes
0x21 Play Server Selected slot VarInt The selected slot int the players current (trading) inventory. (Was a full Integer for the plugin message)

Set Beacon Effect

Changes the effect of the current beacon.

Packet ID State Bound To Field Name Field Type Notes
0x22 Play Server Primary Effect VarInt A Potion ID. (Was a full Integer for the plugin message)
Secondary Effect VarInt A Potion ID. (Was a full Integer for the plugin message)

Held Item Change (serverbound)

Sent when the player changes the slot selection

Packet ID State Bound To Field Name Field Type Notes
0x23 Play Server Slot Short The slot which the player has selected (0–8)

Update Command Block

Packet ID State Bound To Field Name Field Type Notes
0x24 Play Server
Location Position
Command String (32767)
Mode VarInt enum One of SEQUENCE (0), AUTO (1), or REDSTONE (2)
Flags Byte 0x01: Track Output (if false, the output of the previous command will not be stored within the command block); 0x02: Is conditional; 0x04: Automatic

Update Command Block Minecart

Packet ID State Bound To Field Name Field Type Notes
0x25 Play Server Entity ID VarInt
Command String
Track Output Boolean If false, the output of the previous command will not be stored within the command block.

Creative Inventory Action

While the user is in the standard inventory (i.e., not a crafting bench) in Creative mode, the player will send this packet.

Clicking in the creative inventory menu is quite different from non-creative inventory management. Picking up an item with the mouse actually deletes the item from the server, and placing an item into a slot or dropping it out of the inventory actually tells the server to create the item from scratch. (This can be verified by clicking an item that you don't mind deleting, then severing the connection to the server; the item will be nowhere to be found when you log back in.) As a result of this implementation strategy, the "Destroy Item" slot is just a client-side implementation detail that means "I don't intend to recreate this item.". Additionally, the long listings of items (by category, etc.) are a client-side interface for choosing which item to create. Picking up an item from such listings sends no packets to the server; only when you put it somewhere does it tell the server to create the item in that location.

This action can be described as "set inventory slot". Picking up an item sets the slot to item ID -1. Placing an item into an inventory slot sets the slot to the specified item. Dropping an item (by clicking outside the window) effectively sets slot -1 to the specified item, which causes the server to spawn the item entity, etc.. All other inventory slots are numbered the same as the non-creative inventory (including slots for the 2x2 crafting menu, even though they aren't visible in the vanilla client).

Packet ID State Bound To Field Name Field Type Notes
0x26 Play Server Slot Short Inventory slot
Clicked Item Slot

Update Jigsaw Block

Sent when Done is pressed on the Jigsaw Block interface.

Packet ID State Bound To Field Name Field Type Notes
0x27 Play Server Location Position Block entity location
Attachment type Identifier
Target pool Identifier
Final state String "Turns into" on the GUI, final_state in NBT

Update Structure Block

Packet ID State Bound To Field Name Field Type Notes
0x28 Play Server
Location Position Block entity location
Action VarInt enum An additional action to perform beyond simply saving the given data; see below
Mode VarInt enum One of SAVE (0), LOAD (1), CORNER (2), DATA (3).
Name String
Offset X Byte Between -32 and 32
Offset Y Byte Between -32 and 32
Offset Z Byte Between -32 and 32
Size X Byte Between 0 and 32
Size Y Byte Between 0 and 32
Size Z Byte Between 0 and 32
Mirror VarInt enum One of NONE (0), LEFT_RIGHT (1), FRONT_BACK (2).
Rotation VarInt enum One of NONE (0), CLOCKWISE_90 (1), CLOCKWISE_180 (2), COUNTERCLOCKWISE_90 (3).
Metadata String
Integrity Float Between 0 and 1
Seed VarLong
Flags Byte 0x01: Ignore entities; 0x02: Show air; 0x04: Show bounding box

Possible actions:

  • 0 - Update data
  • 1 - Save the structure
  • 2 - Load the structure
  • 3 - Detect size

The Notchian client uses update data to indicate no special action should be taken (i.e. the done button).

Update Sign

This message is sent from the client to the server when the “Done” button is pushed after placing a sign.

The server only accepts this packet after Open Sign Editor, otherwise this packet is silently ignored.

Packet ID State Bound To Field Name Field Type Notes
0x29 Play Server Location Position Block Coordinates
Line 1 String (384) First line of text in the sign
Line 2 String (384) Second line of text in the sign
Line 3 String (384) Third line of text in the sign
Line 4 String (384) Fourth line of text in the sign

Animation (serverbound)

Sent when the player's arm swings.

Packet ID State Bound To Field Name Field Type Notes
0x2A Play Server Hand VarInt Enum Hand used for the animation. 0: main hand, 1: off hand.

Spectate

Teleports the player to the given entity. The player must be in spectator mode.

The Notchian client only uses this to teleport to players, but it appears to accept any type of entity. The entity does not need to be in the same dimension as the player; if necessary, the player will be respawned in the right world. If the given entity cannot be found (or isn't loaded), this packet will be ignored. It will also be ignored if the player attempts to teleport to themselves.

Packet ID State Bound To Field Name Field Type Notes
0x2B Play Server Target Player UUID UUID of the player to teleport to (can also be an entity UUID)

Player Block Placement

Packet ID State Bound To Field Name Field Type Notes
0x2C Play Server Hand VarInt Enum The hand from which the block is placed; 0: main hand, 1: off hand
Location Position Block position
Face VarInt Enum The face on which the block is placed (as documented at Player Digging)
Cursor Position X Float The position of the crosshair on the block, from 0 to 1 increasing from west to east
Cursor Position Y Float The position of the crosshair on the block, from 0 to 1 increasing from bottom to top
Cursor Position Z Float The position of the crosshair on the block, from 0 to 1 increasing from north to south
Inside block Boolean True when the player's head is inside of a block.

Upon placing a block, this packet is sent once.

The Cursor Position X/Y/Z fields (also known as in-block coordinates) are calculated using raytracing. The unit corresponds to sixteen pixels in the default resource pack. For example, let's say a slab is being placed against the south face of a full block. The Cursor Position X will be higher if the player was pointing near the right (east) edge of the face, lower if pointing near the left. The Cursor Position Y will be used to determine whether it will appear as a bottom slab (values 0.0–0.5) or as a top slab (values 0.5-1.0). The Cursor Position Z should be 1.0 since the player was looking at the southernmost part of the block.

Inside block is true when a player's head (specifically eyes) are inside of a block's collision. In 1.13 and later versions, collision is rather complicated and individual blocks can have multiple collision boxes. For instance, a ring of vines has a non-colliding hole in the middle. This value is only true when the player is directly in the box. In practice, though, this value is only used by scaffolding to place in front of the player when sneaking inside of it (other blocks will place behind when you intersect with them -- try with glass for instance).

Use Item

Sent when pressing the Use Item key (default: right click) with an item in hand.

Packet ID State Bound To Field Name Field Type Notes
0x2D Play Server Hand VarInt Enum Hand used for the animation. 0: main hand, 1: off hand.

Status

Main article: Server List Ping

Clientbound

Response

Packet ID State Bound To Field Name Field Type Notes
0x00 Status Client JSON Response String (32767) See Server List Ping#Response

Pong

Packet ID State Bound To Field Name Field Type Notes
0x01 Status Client Payload Long Should be the same as sent by the client

Serverbound

Request

Packet ID State Bound To Field Name Field Type Notes
0x00 Status Server no fields

Ping

Packet ID State Bound To Field Name Field Type Notes
0x01 Status Server Payload Long May be any number. Notchian clients use a system-dependent time value which is counted in milliseconds.

Login

The login process is as follows:

  1. C→S: Handshake with Next State set to 2 (login)
  2. C→S: Login Start
  3. S→C: Encryption Request
  4. Client auth
  5. C→S: Encryption Response
  6. Server auth, both enable encryption
  7. S→C: Set Compression (optional)
  8. S→C: Login Success

Set Compression, if present, must be sent before Login Success. Note that anything sent after Set Compression must use the Post Compression packet format.

For unauthenticated and localhost connections (either of the two conditions is enough for an unencrypted connection) there is no encryption. In that case Login Start is directly followed by Login Success.

See Protocol Encryption for details.

Clientbound

Disconnect (login)

Packet ID State Bound To Field Name Field Type Notes
0x00 Login Client Reason Chat

Encryption Request

Packet ID State Bound To Field Name Field Type Notes
0x01 Login Client Server ID String (20) Appears to be empty
Public Key Length VarInt Length of Public Key
Public Key Byte Array
Verify Token Length VarInt Length of Verify Token. Always 4 for Notchian servers.
Verify Token Byte Array A sequence of random bytes generated by the server

See Protocol Encryption for details.

Login Success

Packet ID State Bound To Field Name Field Type Notes
0x02 Login Client UUID String (36) Unlike in other packets, this field contains the UUID as a string with hyphens.
Username String (16)

This packet switches the connection state to play.

Set Compression

Enables compression. If compression is enabled, all following packets are encoded in the compressed packet format. Negative values will disable compression, meaning the packet format should remain in the uncompressed packet format. However, this packet is entirely optional, and if not sent, compression will also not be enabled (the notchian server does not send the packet when compression is disabled).

Packet ID State Bound To Field Name Field Type Notes
0x03 Login Client Threshold VarInt Maximum size of a packet before it is compressed

Login Plugin Request

Used to implement a custom handshaking flow together with Login Plugin Response.

Unlike plugin messages in "play" mode, these messages follow a lock-step request/response scheme, where the client is expected to respond to a request indicating whether it understood. The notchian client always responds that it hasn't understood, and sends an empty payload.

Packet ID State Bound To Field Name Field Type Notes
0x04 Login Client Message ID VarInt Generated by the server - should be unique to the connection.
Channel Identifier Name of the plugin channel used to send the data
Data Byte Array Any data, depending on the channel. The length of this array must be inferred from the packet length.

Serverbound

Login Start

Packet ID State Bound To Field Name Field Type Notes
0x00 Login Server Name String (16) Player's Username

Encryption Response

Packet ID State Bound To Field Name Field Type Notes
0x01 Login Server Shared Secret Length VarInt Length of Shared Secret
Shared Secret Byte Array
Verify Token Length VarInt Length of Verify Token
Verify Token Byte Array

See Protocol Encryption for details.

Login Plugin Response

Packet ID State Bound To Field Name Field Type Notes
0x02 Login Server Message ID VarInt Should match ID from server.
Successful Boolean true if the client understands the request, false otherwise. When false, no payload follows.
Data Optional Byte Array Any data, depending on the channel. The length of this array must be inferred from the packet length.