This article is licensed under a Creative Commons Attribution-ShareAlike 3.0 license. Derivative works must be licensed using the same or a compatible license.

Java Edition protocol: Difference between revisions

Jump to navigation Jump to search
Content added Content deleted
wiki.vg>Tehme
m (Fix incorrectly formatted table entry)
 
Line 1: Line 1:
{{DISPLAYTITLE:''Java Edition'' protocol}}
This page presents a dissection of the current stable [http://minecraft.net/game/ Minecraft] protocol. The current pre-release protocol is documented [[Pre-release_protocol|elsewhere]]. The protocol for Pocket Minecraft is substantially different, and is documented at [[Pocket Minecraft Protocol]].
{{about|the protocol for a stable release of {{JE}}|the protocol used in development versions of {{JE}}|Minecraft Wiki:Projects/wiki.vg merge/Pre-release protocol|the protocol used in {{BE}}|Bedrock Edition protocol|the protocol used in old ''[[Pocket Edition]]'' versions|Pocket Edition protocol}}
{{See also|Java Edition protocol/FAQ|title1=Protocol FAQ}}
{{exclusive|java}}
{{Info|While you may use the contents of this page without restriction to create servers, clients, bots, etc; keep in mind that the contents of this page are distributed under the terms of [https://creativecommons.org/licenses/by-sa/3.0/ CC BY-SA 3.0 Unported]. Reproductions and derivative works must be distributed accordingly.}}


This article presents a dissection of the current {{JE}} '''protocol''' for [[Minecraft Wiki:Projects/wiki.vg merge/Protocol version numbers|1.21.4, protocol 769]].
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 irc.freenode.net]).


The changes between versions may be viewed at [[Minecraft Wiki:Projects/wiki.vg merge/Protocol History|Protocol History]].
'''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.

== 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]] and [[#Login Success|Login Success]].

=== Data types ===

{{:Protocol data types}} <!-- Transcluded contents of Data types article in here — go to that page if you want to edit it -->

=== Other definitions ===


{| class="wikitable"
{| class="wikitable"
|-
|-
! Term
! Term
! Definition
! Definition
|-
|-
| Player
| Player
| When used in the singular, Player always refers to the client connected to the server
| When used in the singular, Player always refers to the client connected to the server.
|-
|-
| Entity
| Entity
| Entity refers to any item, player, mob, minecart or boat in the world. This definition is subject to change as Notch extends the protocol
| Entity refers to any item, player, mob, minecart or boat etc. See [[Entity|the Minecraft Wiki article]] for a full list.
|-
|-
| EID
| EID
| An EID - or Entity ID - is a unique 4-byte integer used to identify a specific entity
| 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
| XYZ
| In this document, the axis names are the same as those used by Notch. Y points upwards, X points South, and Z points West.
| 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
!colspan="2"|See also: [[Data types]], [[Units of Measurement]]
| 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”.
|}
|-
| Registry
| A table describing static, gameplay-related objects of some kind, such as the types of entities, block states or biomes. The entries of a registry are typically associated with textual or numeric identifiers, or both.


Minecraft has a unified registry system used to implement most of the registries, including blocks, items, entities, biomes and dimensions. These "ordinary" registries associate entries with both namespaced textual identifiers (see [[#Identifier]]), and signed (positive) 32-bit numeric identifiers. There is also a registry of registries listing all of the registries in the registry system. Some other registries, most notably the [[Minecraft Wiki:Projects/wiki.vg merge/Chunk Format#Block state registry|block state registry]], are however implemented in a more ad-hoc fashion.
== Packets ==
All packets begin with a single "Packet ID" byte. Listed packet size includes this byte. Packets are either "server to client", "client to server", or "Two-Way" (both). Packets are not prefixed with their length. For variable length packets, you must parse it completely to determine its length.
=== Protocol Version ===
1.6.2 - 74


Some registries, such as biomes and dimensions, can be customized at runtime by the server (see [[Minecraft Wiki:Projects/wiki.vg merge/Registry Data|Registry Data]]), while others, such as blocks, items and entities, are hardcoded. The contents of the hardcoded registries can be extracted via the built-in [[Minecraft Wiki:Projects/wiki.vg merge/Data Generators|Data Generators]] system.
{{anchor|0x00}}
|-
=== Keep Alive (0x00) ===
| Block state
''Two-Way''
| Each block in Minecraft has 0 or more properties, which in turn may have any number of possible values. These represent, for example, the orientations of blocks, poweredness states of redstone components, and so on. Each of the possible permutations of property values for a block is a distinct block state. The block state registry assigns a numeric identifier to every block state of every block.


A current list of properties and state ID ranges is found on [https://pokechu22.github.io/Burger/1.21.html burger].
The server will frequently send out a keep-alive, each containing a random ID. The client must respond with the same packet.

The Beta server will disconnect a client if it doesn't receive at least one packet before 1200 in-game ticks, and the Beta client will time out the connection under the same conditions. The client may send packets with Keep-alive ID=0.
Alternatively, the vanilla server now includes an option to export the current block state ID mapping, by running <code>java -DbundlerMainClass=net.minecraft.data.Main -jar minecraft_server.jar --reports</code>. See [[Minecraft Wiki:Projects/wiki.vg merge/Data Generators|Data Generators]] for more information.
|-
| Vanilla
| The official implementation of Minecraft as developed and released by Mojang.
|-
| Sequence
| The action number counter for local block changes, incremented by one when clicking a block with a hand, right clicking an item, or starting or finishing digging a block. Counter handles latency to avoid applying outdated block changes to the local world. Also is used to revert ghost blocks created when placing blocks, using buckets, or breaking blocks.
|}

== Packet format ==

Packets cannot be larger than 2<sup>21</sup> &minus; 1 or 2097151 bytes (the maximum that can be sent in a 3-byte {{Type|VarInt}}). Moreover, the length field must not be longer than 3 bytes, even if the encoded value is within the limit. Unnecessarily long encodings at 3 bytes or below are still allowed. For compressed packets, this applies to the Packet Length field, i.e. the compressed length.

=== Without compression ===


{| class="wikitable"
{| class="wikitable"
! Field Name
|-
! Field Type
| Packet ID
! Notes
| Field Name
|-
| Field Type
| Length
| Example
| {{Type|VarInt}}
| Notes
| Length of Packet ID + Data
|-
|-
| 0x00
| Keep-alive ID
| Packet ID
| {{Type|VarInt}}
| int
| Corresponds to <code>protocol_id</code> from [[Minecraft Wiki:Projects/wiki.vg merge/Data Generators#Packets report|the server's packet report]]
| <code>957759560</code>
|-
| Server-generated random id
| Data
|-
| {{Type|Byte Array}}
| Total Size:
| Depends on the connection state and packet ID, see the sections below
| colspan="4" | 5 bytes
|}
|}


=== With compression ===
{{anchor|0x01}}
=== Login Request (0x01) ===
''Server to Client'' ''(and Client to Server in some mods, see below)''


Once a [[#Set Compression|Set Compression]] packet (with a non-negative threshold) is sent, [[wikipedia:Zlib|zlib]] compression is enabled for all following packets. The format of a packet changes slightly to include the size of the uncompressed packet.
See [[Protocol Encryption]] for information on logging in.

{| class=wikitable
! Present?
! Compressed?
! Field Name
! Field Type
! Notes
|-
| always
| No
| Packet Length
| {{Type|VarInt}}
| Length of (Data Length) + length of compressed (Packet ID + Data)
|-
| rowspan="3"| if size >= threshold
| No
| Data Length
| {{Type|VarInt}}
| Length of uncompressed (Packet ID + Data)
|-
| rowspan="2"| Yes
| Packet ID
| {{Type|VarInt}}
| zlib compressed packet ID (see the sections below)
|-
| Data
| {{Type|Byte Array}}
| zlib compressed packet data (see the sections below)
|-
| rowspan="3"| if size < threshold
| rowspan="3"| No
| Data Length
| {{Type|VarInt}}
| 0 to indicate uncompressed
|-
| Packet ID
| {{Type|VarInt}}
| packet ID (see the sections below)
|-
| Data
| {{Type|Byte Array}}
| packet data (see the sections below)
|}

For serverbound packets, the uncompressed length of (Packet ID + Data) must not be greater than 2<sup>23</sup> or 8388608 bytes. Note that a length equal to 2<sup>23</sup> is permitted, which differs from the compressed length limit. The vanilla client, on the other hand, has no limit for the uncompressed length of incoming compressed packets.

If the size of the buffer containing the packet data and ID (as a {{Type|VarInt}}) is smaller than the threshold specified in the packet [[#Set Compression|Set Compression]]. It will be sent as uncompressed. This is done by setting the data length as 0. (Comparable to sending a non-compressed format with an extra 0 between the length, and packet data).

If it's larger than or equal to the threshold, then it follows the regular compressed protocol format.

The vanilla server (but not client) rejects compressed packets smaller than the threshold. Uncompressed packets exceeding the threshold, however, are accepted.

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 ==

=== 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 packet causes the server to switch into the target state. It should be sent right after opening the TCP connection to prevent the server from disconnecting.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="4"| ''protocol:''<br/><code>0x00</code><br/><br/>''resource:''<br/><code>intention</code>
| rowspan="7" | 0x01
| rowspan="4"| Handshaking
| Entity ID
| rowspan="4"| Server
| int
| Protocol Version
| <code>1298</code>
| {{Type|VarInt}}
| The Player's Entity ID
| See [[Minecraft Wiki:Projects/wiki.vg merge/Protocol version numbers|protocol version numbers]] (currently 769 in Minecraft 1.21.4).
|-
|-
| Level type
| Server Address
| string
| {{Type|String}} (255)
| default
| Hostname or IP, e.g. localhost or 127.0.0.1, that was used to connect. The vanilla server does not use this information. Note that SRV records are a simple redirect, e.g. if _minecraft._tcp.example.com points to mc.example.org, users connecting to example.com will provide example.org as server address in addition to connecting to it.
| <code>default</code>, <code>flat</code>, or <code>largeBiomes</code>. level-type in server.properties
|-
|-
| Game mode
| Server Port
| {{Type|Unsigned Short}}
| byte
| Default is 25565. The vanilla server does not use this information.
| <code>0</code>
|-
| <code>0</code>: survival, <code>1</code>: creative, <code>2</code>: adventure. Bit 3 (<code>0x8</code>) is the hardcore flag
| Next State
|-
| {{Type|VarInt}} {{Type|Enum}}
| Dimension
| 1 for [[#Status|Status]], 2 for [[#Login|Login]], 3 for [[#Login|Transfer]].
| byte
|}
| <code>0</code>
| <code>-1</code>: nether, <code>0</code>: overworld, <code>1</code>: end
|-
| Difficulty
| byte
| <code>1</code>
| <code>0</code> thru <code>3</code> for Peaceful, Easy, Normal, Hard
|-
| Not used
| byte
| <code>0</code>
| Only 0 observed from vanilla server, was previously world height
|-
| Max players
| byte
| <code>8</code>
| Used by the client to draw the player list
|-
| Total Size:
| colspan="4" | 12 bytes + length of strings
|}


==== Legacy Server List Ping ====
* MinecraftForge sends packet with type 0x01 and 25 bytes(may depend on mods installed with it) following it after completing handshake and enabling encryption. In our tests it sent the following payload:
0x53 0xC8 0xE6 0x1B 0x00 0x07 0x00 0x64 0x00 0x65 0x00 0x66 0x00 0x61 0x00 0x75 0x00 0x6C 0x00 0x74 0xFF 0x02 0x00 0x00 0x00


{{Warning|This packet uses a nonstandard format. It is never length-prefixed, and the packet ID is an {{Type|Unsigned Byte}} instead of a {{Type|VarInt}}.}}
It is probably safe for server to ignore them unless you know what to do. More insights are needed on MinecraftForge protocol specifics.


While not technically part of the current protocol, (legacy) clients may send this packet to initiate [[Minecraft Wiki:Projects/wiki.vg merge/Server List Ping|Server List Ping]], and modern servers should handle it correctly.
{{anchor|0x02}}
The format of this packet is a remnant of the pre-Netty age, before the switch to Netty in 1.7 brought the standard format that is recognized now. This packet merely exists to inform legacy clients that they can't join our modern server.


Modern clients (tested with 1.21.5 + 1.21.4) also send this packet when the server does not send any response within a 30 seconds time window or when the connection is immediately closed.
=== Handshake (0x02) ===
{{Warning|The client does not close the connection with the legacy packet on its own!
''Client to server''
It only gets closed when the Minecraft client is closed.}}
{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| 0xFE
| Handshaking
| Server
| Payload
| {{Type|Unsigned Byte}}
| always 1 (<code>0x01</code>).
|}


See [[Minecraft Wiki:Projects/wiki.vg merge/Server List Ping#1.6|Server List Ping#1.6]] for the details of the protocol that follows this packet.
See [[Protocol Encryption]] for information on logging in.

== Status ==
{{Main|Minecraft Wiki:Projects/wiki.vg merge/Server List Ping}}

=== Clientbound ===

==== Status Response ====


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| ''protocol:''<br/><code>0x00</code><br/><br/>''resource:''<br/><code>status_response</code>
| rowspan="4" | 0x02
| Status
| Protocol Version
| byte
| Client
| JSON Response
| <code>51</code>
| {{Type|String}} (32767)
| As of 1.6.1 the protocol version is 73. See [[Protocol version numbers]] for list.
| See [[Minecraft Wiki:Projects/wiki.vg merge/Server List Ping#Status Response|Server List Ping#Status Response]]; as with all strings this is prefixed by its length as a {{Type|VarInt}}.
|-
|}
| Username
| string
| <code>Notch</code>
| The username of the player attempting to connect
|-
| Server Host
| string
| <code>localhost</code>
|
|-
| Server Port
| int
| <code>25565</code>
|
|-
| Total Size:
| colspan="4" | 10 bytes + length of strings
|}
{{anchor|0x03}}


=== Chat Message (0x03) ===
==== Pong Response (status) ====


{| class="wikitable"
''Client to Server''
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x01</code><br/><br/>''resource:''<br/><code>pong_response</code>
| Status
| Client
| Timestamp
| {{Type|Long}}
| Should match the one sent by the client.
|}


=== Serverbound ===
The default server will check the message to see if it begins with a '/'. If it doesn't, the username of the sender is prepended and sent to all other clients (including the original sender). If it does, the server assumes it to be a command and attempts to process it. A message longer than 100 characters will cause the server to kick the client. (As of 1.3.2, the vanilla client appears to limit the text a user can enter to 100 charaters.) This limits the chat message packet length to 203 bytes (as characters are encoded on 2 bytes). Note that this limit does not apply to chat messages sent by the server, which are limited to 32767 characters since 1.2.5. This change was initially done by allowing the client to not slice the message up to 119 (the previous limit), without changes to the server. For this reason, the vanilla server kept the code to cut messages at 119, but this isn't a protocol limitation and can be ignored.


==== Status Request ====
For more information, see [[Chat]].


The status can only be requested once immediately after the handshake, before any ping. The server won't respond otherwise.
''Server to Client''


{| class="wikitable"
The chat string must now be a valid JSON object:
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x00</code><br/><br/>''resource:''<br/><code>status_request</code>
| Status
| Server
| colspan="3"| ''no fields''
|}


==== Ping Request (status) ====
{"translate":"chat.type.announcement","using":["Server","hi"]}
{"color":"gray","italic":true,"translate":"chat.type.admin","using":["Server",{"translate":"commands.save.success"}]}
{"text":"§aOld style chat"}
[https://gist.github.com/Dinnerbone/5631634 Original Gist from Dinnerbone]


{| class="wikitable"
Where translate is one of the following:
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x01</code><br/><br/>''resource:''<br/><code>ping_request</code>
| Status
| Server
| Timestamp
| {{Type|Long}}
| May be any number, but vanilla clients use will always use the timestamp in milliseconds.
|}


== Login ==
chat.type.admin: [%s: %s]
chat.type.announcement: [%s] %s
chat.type.emote: * %s %s
chat.type.text: <%s> %s


The login process is as follows:


# C→S: [[#Handshake|Handshake]] with Next State set to 2 (login)
{{anchor|0x04}}
# C→S: [[#Login Start|Login Start]]
=== Time Update (0x04) ===
# S→C: [[#Encryption Request|Encryption Request]]
''Server to Client''
# Client auth (if enabled)
# C→S: [[#Encryption Response|Encryption Response]]
# Server auth (if enabled)
# Both enable encryption
# S→C: [[#Set Compression|Set Compression]] (optional)
# S→C: [[#Login Success|Login Success]]
# C→S: [[#Login Acknowledged|Login Acknowledged]]


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]].
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.


Three modes of operation are possible depending on how the packets are sent:
The time of day is based on the timestamp modulo 24000. 0 is sunrise, 6000 is noon, 12000 is sunset, and 18000 is midnight.
* Online-mode with encryption
* Offline-mode with encryption
* Offline-mode without encryption


For online-mode servers (the ones with authentication enabled), encryption is always mandatory, and the entire process described above needs to be followed.
The default SMP server increments the time by <code>20</code> every second.

For offline-mode servers (the ones with authentication disabled), encryption is optional, and part of the process can be skipped. In that case [[#Login Start|Login Start]] is directly followed by [[#Login Success|Login Success]]. The vanilla server only uses UUID v3 for offline player UUIDs, deriving it from the string <code>OfflinePlayer:<player's name></code> For example, Notch’s offline UUID would be chosen from the string <code>OfflinePlayer:Notch</code>. This is not a requirement however, the UUID can be set to anything.

As of 1.21, the vanilla server never uses encryption in offline mode.

See [[protocol encryption]] for details.

=== Clientbound ===

==== Disconnect (login) ====


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
! | Packet ID
! Bound To
! | Field Name
! | Field Type
! Field Name
! Field Type
! | Example
! | Notes
! Notes
|-
|-
| ''protocol:''<br/><code>0x00</code><br/><br/>''resource:''<br/><code>login_disconnect</code>
| rowspan="2" | 0x04
| Login
| Age of the world
| long
| Client
| Reason
| 45464654
| {{Type|JSON Text Component}}
| In ticks; not changed by server commands
| The reason why the player was disconnected.
|-
|}
| Time of Day
| long
| 21321
| The world (or region) time, in ticks. '''If negative the sun will stop moving at the Math.abs of the time.'''
|-
! | Total Size:
| colspan="4" | 17 Bytes
|}


==== Encryption Request ====
{{anchor|0x05}}
=== Entity Equipment (0x05) ===
''Server to Client''


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="4"| ''protocol:''<br/><code>0x01</code><br/><br/>''resource:''<br/><code>hello</code>
| rowspan="3" | 0x05
| rowspan="4"| Login
| Entity ID
| rowspan="4"| Client
| int
| Server ID
| 0x00010643
| {{Type|String}} (20)
| Named Entity ID
| Always empty when sent by the vanilla server.
|-
|-
| Slot
| Public Key
| short
| {{Type|Prefixed Array}} of {{Type|Byte}}
| 4
| The server's public key, in bytes.
| Equipment slot: 0=held, 1-4=armor slot (1 - boots, 2 - leggings, 3 - chestplate, 4 - helmet)
|-
|-
| Verify Token
| Item
| {{Type|Prefixed Array}} of {{Type|Byte}}
| [[Slot_Data|slot]]
| A sequence of random bytes generated by the server.
|
|-
| Item in slot format
| Should authenticate
|-
| {{Type|Boolean}}
| Total Size:
| Whether the client should attempt to [[Minecraft Wiki:Projects/wiki.vg merge/Protocol_Encryption#Authentication|authenticate through mojang servers]].
| colspan="4" | 7 bytes + slot data
|}
|}


See [[protocol encryption]] for details.
{{anchor|0x06}}
=== Spawn Position (0x06) ===
''Server to Client''


==== Login Success ====
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"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! colspan="2"| Field Name
! colspan="2"| Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="5"| ''protocol:''<br/><code>0x02</code><br/><br/>''resource:''<br/><code>login_finished</code>
| rowspan="3" | 0x06
| rowspan="5"| Login
| X
| rowspan="5"| Client
| int
| colspan="2"| UUID
| <code>117</code>
| colspan="2"| {{Type|UUID}}
| Spawn X in block coordinates
| colspan="2"|
|-
| Y
|-
| colspan="2"| Username
| int
| colspan="2"| {{Type|String}} (16)
| <code>70</code>
| colspan="2"|
| Spawn Y in block coordinates
|-
|-
| rowspan="3"| Property
| Z
| int
| Name
| rowspan="3"| {{Type|Prefixed Array}} (16)
| <code>-46</code>
| {{Type|String}} (64)
| Spawn Z in block coordinates
| colspan="2"|
|-
|-
| Total Size:
| Value
| colspan="4" | 13 bytes
| {{Type|String}} (32767)
|}
| colspan="1"|
|-
| Signature
| {{Type|Prefixed Optional}} {{Type|String}} (1024)
|
|}


The Property field looks like response of [[Minecraft Wiki:Projects/wiki.vg merge/Mojang API#UUID to Profile and Skin/Cape|Mojang API#UUID to Profile and Skin/Cape]], except using the protocol format instead of JSON. That is, each player will usually have one property with Name being “textures” and Value being a base64-encoded JSON string, as documented at [[Minecraft Wiki:Projects/wiki.vg merge/Mojang API#UUID to Profile and Skin/Cape|Mojang API#UUID to Profile and 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 their UUID (again, see the Mojang API page).
{{anchor|0x07}}
=== Use Entity (0x07) ===
''Client to Server''


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


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 vanilla server does not send the packet when compression is disabled).
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.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| ''protocol:''<br/><code>0x03</code><br/><br/>''resource:''<br/><code>login_compression</code>
| rowspan="3" | 0x07
| User
| Login
| int
| Client
| Threshold
| <code>1298</code>
| {{Type|VarInt}}
| The entity of the player (ignored by the server)
| Maximum size of a packet before it is compressed.
|-
|}
| Target
| int
| <code>1805</code>
| The entity the player is interacting with
|-
| Mouse button
| boolean
| <code>true</code>
| <code>true</code> when the player is left-clicking and <code>false</code> when right-clicking.
|-
| Total Size:
| colspan="4" | 10 bytes
|}


==== Login Plugin Request ====


Used to implement a custom handshaking flow together with [[#Login Plugin Response|Login Plugin Response]].
{{anchor|0x08}}

=== Update Health (0x08) ===
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 vanilla client always responds that it hasn't understood, and sends an empty payload.
''Server to Client''

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x04</code><br/><br/>''resource:''<br/><code>custom_query</code>
| rowspan="3"| Login
| rowspan="3"| Client
| Message ID
| {{Type|VarInt}}
| Generated by the server - should be unique to the connection.
|-
| Channel
| {{Type|Identifier}}
| Name of the [[Minecraft Wiki:Projects/wiki.vg merge/Plugin channels|plugin channel]] used to send the data.
|-
| Data
| {{Type|Byte Array}} (1048576)
| Any data, depending on the channel. The length of this array must be inferred from the packet length.
|}


==== Cookie Request (login) ====
Sent by the server to update/set the health of the player it is sent to. Added in protocol version 5.


Requests a cookie that was previously stored.
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.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! colspan="2"| Field Name
! colspan="2"| Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x05</code><br/><br/>''resource:''<br/><code>cookie_request</code>
| rowspan="3" | 0x08
| rowspan="1"| Login
| Health
| rowspan="1"| Client
| '''float'''
| colspan="2"| Key
| '''20.0'''
| colspan="2"| {{Type|Identifier}}
| 0 or less = dead, 20 = full HP
| The identifier of the cookie.
|-
|}
| Food
| short
| 20
| 0 - 20
|-
| Food Saturation
| float
| 5.0
| Seems to vary from 0.0 to 5.0 in integer increments
|-
| Total Size:
| colspan="4" | 11 bytes
|}


=== Serverbound ===
{{anchor|0x09}}
=== Respawn (0x09) ===
''Server to Client''


==== Login Start ====
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"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x00</code><br/><br/>''resource:''<br/><code>hello</code>
| rowspan="5" | 0x09
| rowspan="2"| Login
| Dimension
| rowspan="2"| Server
| int
| Name
| <code>1</code>
| {{Type|String}} (16)
| <code>-1</code>: The Nether, <code>0</code>: The Overworld, <code>1</code>: The End
| Player's Username.
|-
|-
| Difficulty
| Player UUID
| byte
| {{Type|UUID}}
| <code>1</code>
| The {{Type|UUID}} of the player logging in. Unused by the vanilla server.
| <code>0</code> thru <code>3</code> for Peaceful, Easy, Normal, Hard. <code>1</code> is always sent c->s
|-
|}
| Game mode
| byte
| <code>1</code>
| <code>0</code>: survival, <code>1</code>: creative, <code>2</code>: adventure. The hardcore flag is not included
|-
| World height
| short
| <code>256</code>
| Defaults to <code>256</code>
|-
| Level type
| string
| default
| See [[#0x01|0x01 login]]
|-
| Total Size:
| colspan="4" | 11 bytes + length of string
|}
* Please avoid changing player's dimension to same dimension as he was in (i.e. from Nether to Nether, from Overworld to Overworld). While at first glance everything seems to work, weird bugs can occur, i.e. such player will be unable to attack other players in new world (minecraft client just won't send "Use Entity (0x07)" packet on hitting, only "Animation (0x12)" packet), even though he can see them and they can attack him (fixes after his death and respawn though).
If you actually have multiple worlds of same dimension on server and need to teleport player between them, use intermediate world (with different dimension) between them.


==== Encryption Response ====
{{anchor|0x0A}}
=== Player (0x0A) ===
''Client to Server''


{| class="wikitable"
This packet is used to indicate whether the player is on ground (walking/swimming), or airborne (jumping/falling).
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x01</code><br/><br/>''resource:''<br/><code>key</code>
| rowspan="2"| Login
| rowspan="2"| Server
| Shared Secret
| {{Type|Prefixed Array}} of {{Type|Byte}}
| Shared Secret value, encrypted with the server's public key.
|-
| Verify Token
| {{Type|Prefixed Array}} of {{Type|Byte}}
| Verify Token value, encrypted with the same public key as the shared secret.
|}


See [[protocol encryption]] for details.
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.


==== Login Plugin Response ====
This packet was previously referred to as Flying


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x02</code><br/><br/>''resource:''<br/><code>custom_query_answer</code>
| 0x0A
| rowspan="2"| Login
| On Ground
| rowspan="2"| Server
| boolean
| Message ID
| <code>1</code>
| {{Type|VarInt}}
| <code>True</code> if the client is on the ground, <code>False</code> otherwise
| Should match ID from server.
|-
|-
| Total Size:
| Data
| colspan="4" | 2 bytes
| {{Type|Prefixed Optional}} {{Type|Byte Array}} (1048576)
|}
| Any data, depending on the channel. The length of this array must be inferred from the packet length. Only present if the client understood the request.
|}


==== Login Acknowledged ====
{{anchor|0x0B}}
=== Player Position (0x0B) ===
''Client to Server''


Acknowledgement to the [[Java Edition protocol#Login_Success|Login Success]] packet sent by the server.
Updates the players XYZ position on the server.
If <code>Stance - Y</code> is less than <code>0.1</code> or greater than <code>1.65</code>, the stance is illegal and the client will be kicked with the message “Illegal Stance”.
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 units will result in the client being kicked for "You moved too quickly :( (Hacking?)"
Also if the absolute number of X or Z is set greater than <code>3.2E7D</code> the client will be kicked for "Illegal position"


{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x03</code><br/><br/>''resource:''<br/><code>login_acknowledged</code>
| Login
| Server
| colspan="3"| ''no fields''
|}

This packet switches the connection state to [[#Configuration|configuration]].

==== Cookie Response (login) ====

Response to a [[#Cookie_Request_(login)|Cookie Request (login)]] from the server. The vanilla server only accepts responses of up to 5 kiB in size.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x04</code><br/><br/>''resource:''<br/><code>cookie_response</code>
| rowspan="5" | 0x0B
| rowspan="2"| Login
| X
| rowspan="2"| Server
| double
| Key
| <code>102.809</code>
| {{Type|Identifier}}
| Absolute position
| The identifier of the cookie.
|-
| Y
|-
| Payload
| double
| {{Type|Prefixed Optional}} {{Type|Prefixed Array}} (5120) of {{Type|Byte}}
| <code>70.00</code>
| The data of the cookie.
| Absolute position
|-
|}
| Stance
| double
| <code>71.62</code>
| Used to modify the players bounding box when going up stairs, crouching, etc…
|-
| Z
| double
| <code>68.30</code>
| Absolute position
|-
| On Ground
| boolean
| <code>1</code>
|
Derived from packet [[#0x0A|0x0A]]
|-
| Total Size:
| colspan="4" | 34 bytes
|}


== Configuration ==


=== Clientbound ===
{{anchor|0x0C}}
=== Player Look (0x0C) ===
''Client to Server''


==== Cookie Request (configuration) ====
[[File:Minecraft-trig-yaw.png|thumb|The unit circle for yaw]]


Requests a cookie that was previously stored.
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 backwards towards (-1, 0), or in other words, it turns clockwise instead of counterclockwise. Additionally, yaw is not clamped to between 0 and 360 degrees; any number is valid, including negative numbers and numbers greater than 360.
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x00</code><br/><br/>''resource:''<br/><code>cookie_request</code>
| rowspan="1"| Configuration
| rowspan="1"| Client
| colspan="2"| Key
| colspan="2"| {{Type|Identifier}}
| The identifier of the cookie.
|}


==== Clientbound Plugin Message (configuration) ====
Pitch is measured in degrees, where 0 is looking straight ahead, -90 is looking straight up, and 90 is looking straight down.


{{Main|Minecraft Wiki:Projects/wiki.vg merge/Plugin channels}}
You can get a unit vector from a given yaw/pitch via:

x = -cos(pitch) * sin(yaw)
Mods and plugins can use this to send their data. Minecraft itself uses several [[Minecraft Wiki:Projects/wiki.vg merge/Plugin channels|plugin channels]]. These internal channels are in the <code>minecraft</code> namespace.
y = -sin(pitch)

z = cos(pitch) * cos(yaw)
More information on how it works on [https://web.archive.org/web/20220831140929/https://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/ Dinnerbone's blog]. More documentation about internal and popular registered channels are [[Minecraft Wiki:Projects/wiki.vg merge/Plugin channels|here]].


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x01</code><br/><br/>''resource:''<br/><code>custom_payload</code>
| rowspan="3" | 0x0C
| rowspan="2"| Configuration
| Yaw
| rowspan="2"| Client
| float
| Channel
| <code>0.00</code>
| {{Type|Identifier}}
| Absolute rotation on the X Axis, in degrees
| Name of the [[Minecraft Wiki:Projects/wiki.vg merge/Plugin channels|plugin channel]] used to send the data.
|-
|-
| Pitch
| float
| Data
| {{Type|Byte Array}} (1048576)
| <code>0.00</code>
| Any data. The length of this array must be inferred from the packet length.
| Absolute rotation on the Y Axis, in degrees
|-
|}
| On Ground
| boolean
| <code>1</code>
|
Derived from packet [[#0x0A|0x0A]]
|-
| Total Size:
| colspan="4" | 10 bytes
|}


In vanilla clients, the maximum data length is 1048576 bytes.
{{anchor|0x0D}}
=== Player Position and Look (0x0D) ===
''Two-Way''


==== Disconnect (configuration) ====
A combination of [[#0x0C|Player Look]] and [[#0x0B|Player position]].


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| ''protocol:''<br/><code>0x02</code><br/><br/>''resource:''<br/><code>disconnect</code>
| rowspan="7" | 0x0D
| Configuration
| X
| double
| Client
| Reason
| <code>6.5</code>
| {{Type|Text Component}}
| Absolute position
| The reason why the player was disconnected.
|-
| Y
|}
| double
| <code>65.620000004768372</code>
| Absolute position
|-
| Stance
| double
| <code>67.240000009536743</code>
| Used to modify the players bounding box when going up stairs, crouching, etc…
|-
| Z
| double
| <code>7.5</code>
| Absolute position
|-
| Yaw
| float
| <code>0.0</code>
| Absolute rotation on the X Axis
|-
| Pitch
| float
| <code>0.0</code>
| Absolute rotation on the Y Axis
|-
| On Ground
| boolean
| <code>0</code>
|
Derived from packet [[#0x0A|0x0A]]
|-
| Total Size:
| colspan="4" | 42 bytes
|}


==== Finish Configuration ====
{{anchor|0x0E}}


Sent by the server to notify the client that the configuration process has finished. The client answers with [[#Acknowledge_Finish_Configuration|Acknowledge Finish Configuration]] whenever it is ready to continue.
=== Player Digging (0x0E) ===
''Client to Server''


{| class="wikitable"
Sent when the player mines a block. A Notchian server only accepts digging packets with coordinates within a 6-unit radius of the player's position.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x03</code><br/><br/>''resource:''<br/><code>finish_configuration</code>
| rowspan="1"| Configuration
| rowspan="1"| Client
| colspan="3"| ''no fields''
|}

This packet switches the connection state to [[#Play|play]].

==== Clientbound Keep Alive (configuration) ====

The server will frequently send out a keep-alive, each containing a random ID. The client must respond with the same payload (see [[#Serverbound Keep Alive (configuration)|Serverbound Keep Alive]]). If the client does not respond to a Keep Alive packet within 15 seconds after it was sent, 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 vanilla server uses a system-dependent time in milliseconds to generate the keep alive ID value.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| ''protocol:''<br/><code>0x04</code><br/><br/>''resource:''<br/><code>keep_alive</code>
| rowspan="5" | 0x0E
| Configuration
| Status
| byte
| Client
| Keep Alive ID
| <code>1</code>
| {{Type|Long}}
| The action the player is taking against the block (see below)
|-
|
| X
|}

| int
==== Ping (configuration) ====
| <code>32</code>
| Block position
|-
| Y
| byte
| <code>64</code>
| Block position
|-
| Z
| int
| <code>32</code>
| Block position
|-
| Face
| byte
| <code>3</code>
| The face being hit (see below)
|-
| Total Size:
| colspan="4" | 12 bytes
|}


Packet is not used by the vanilla server. When sent to the client, client responds with a [[#Pong (configuration)|Pong]] packet with the same id.
Status can (currently) be one of six values:


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Meaning
! Bound To
| Value
! Field Name
|-
! Field Type
| Started digging
! Notes
| <code>0</code>
|-
|-
| ''protocol:''<br/><code>0x05</code><br/><br/>''resource:''<br/><code>ping</code>
| Cancelled digging
| Configuration
| <code>1</code>
| Client
|-
| ID
| Finished digging
| {{Type|Int}}
| <code>2</code>
|-
|
|}
| Drop item stack
| <code>3</code>
|-
| Drop item
| <code>4</code>
|-
| Shoot arrow / finish eating
| <code>5</code>
|}


==== Reset Chat ====
Notchian clients send a 0 (started digging) when they start digging and a 2 (finished digging) once they think they are finished. If digging is aborted, the client simply send a 1 (Cancel digging).


{| class="wikitable"
Status code 4 (drop item) is a special case. In-game, when you use the Drop Item command (keypress 'q'), a dig packet with a status of 4, and all other values set to 0, is sent from client to server. Status code 3 is similar, but drops the entire stack.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x06</code><br/><br/>''resource:''<br/><code>reset_chat</code>
| Configuration
| Client
| colspan="3"| ''no fields''
|}

==== Registry Data ====

Represents certain registries that are sent from the server and are applied on the client.

See [[Minecraft Wiki:Projects/wiki.vg merge/Registry_Data|Registry Data]] for details.

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x07</code><br/><br/>''resource:''<br/><code>registry_data</code>
| rowspan="3"| Configuration
| rowspan="3"| Client
| colspan="2"| Registry ID
| colspan="2"| {{Type|Identifier}}
|
|-
| rowspan="2"| Entries
| Entry ID
| rowspan="2"| {{Type|Prefixed Array}}
| {{Type|Identifier}}
|
|-
| Data
| {{Type|Prefixed Optional}} {{Type|NBT}}
| Entry data.
|}

==== Remove Resource Pack (configuration) ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x08</code><br/><br/>''resource:''<br/><code>resource_pack_pop</code>
| rowspan="1"| Configuration
| rowspan="1"| Client
| UUID
| {{Type|Prefixed Optional}} {{Type|UUID}}
| The {{Type|UUID}} of the resource pack to be removed. If not present every resource pack will be removed.
|}

==== Add Resource Pack (configuration) ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="5"| ''protocol:''<br/><code>0x09</code><br/><br/>''resource:''<br/><code>resource_pack_push</code>
| rowspan="5"| Configuration
| rowspan="5"| Client
| UUID
| {{Type|UUID}}
| The unique identifier of the resource pack.
|-
| URL
| {{Type|String}} (32767)
| The URL to the resource pack.
|-
| Hash
| {{Type|String}} (40)
| A 40 character hexadecimal, case-insensitive [[wikipedia:SHA-1|SHA-1]] hash of the resource pack file.<br />If it's not a 40 character hexadecimal string, the client will not use it for hash verification and likely waste bandwidth.
|-
| Forced
| {{Type|Boolean}}
| The vanilla client will be forced to use the resource pack from the server. If they decline they will be kicked from the server.
|-
| Prompt Message
| {{Type|Prefixed Optional}} {{Type|Text Component}}
| This is shown in the prompt making the client accept or decline the resource pack (only if present).
|}

==== Store Cookie (configuration) ====

Stores some arbitrary data on the client, which persists between server transfers. The vanilla client only accepts cookies of up to 5 kiB in size.

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x0A</code><br/><br/>''resource:''<br/><code>store_cookie</code>
| rowspan="2"| Configuration
| rowspan="2"| Client
| colspan="2"| Key
| colspan="2"| {{Type|Identifier}}
| The identifier of the cookie.
|-
| colspan="2"| Payload
| colspan="2"| {{Type|Prefixed Array}} (5120) of {{Type|Byte}}
| The data of the cookie.
|}

==== Transfer (configuration) ====

Notifies the client that it should transfer to the given server. Cookies previously stored are preserved between server transfers.

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x0B</code><br/><br/>''resource:''<br/><code>transfer</code>
| rowspan="2"| Configuration
| rowspan="2"| Client
| colspan="2"| Host
| colspan="2"| {{Type|String}} (32767)
| The hostname or IP of the server.
|-
| colspan="2"| Port
| colspan="2"| {{Type|VarInt}}
| The port of the server.
|}

==== Feature Flags ====

Used to enable and disable features, generally experimental ones, on the client.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x0C</code><br/><br/>''resource:''<br/><code>update_enabled_features</code>
| rowspan="1"| Configuration
| rowspan="1"| Client
| Feature Flags
| {{Type|Prefixed Array}} of {{Type|Identifier}}
|
|}

There is one special feature flag, which is in most versions:
* minecraft:vanilla - enables vanilla features

For the other feature flags, which may change between versions, see [[Experiments#Java_Edition]].

==== Update Tags (configuration) ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x0D</code><br/><br/>''resource:''<br/><code>update_tags</code>
| rowspan="2"| Configuration
| rowspan="2"| Client
| rowspan="2"| Array of tags
| Registry
| rowspan="2"| {{Type|Prefixed Array}}
| {{Type|Identifier}}
| Registry identifier (Vanilla expects tags for the registries <code>minecraft:block</code>, <code>minecraft:item</code>, <code>minecraft:fluid</code>, <code>minecraft:entity_type</code>, and <code>minecraft:game_event</code>)
|-
| Array of Tag
| (See below)
|
|}

Tag arrays look like:

{| class="wikitable"
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="2"| Tags
| Tag name
| rowspan="2"| {{Type|Prefixed Array}}
| {{Type|Identifier}}
|
|-
| Entries
| {{Type|Prefixed Array}} of {{Type|VarInt}}
| Numeric IDs of the given type (block, item, etc.). This list replaces the previous list of IDs for the given tag. If some preexisting tags are left unmentioned, a warning is printed.
|}

See [[Tag]] on the Minecraft Wiki for more information, including a list of vanilla tags.

==== Clientbound Known Packs ====

Informs the client of which data packs are present on the server.
The client is expected to respond with its own [[#Serverbound_Known_Packs|Serverbound Known Packs]] packet.
The vanilla server does not continue with Configuration until it receives a response.

The vanilla client requires the <code>minecraft:core</code> pack with version <code>1.21.4</code> for a normal login sequence. This packet must be sent before the Registry Data packets.

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x0E</code><br/><br/>''resource:''<br/><code>select_known_packs</code>
| rowspan="3"| Configuration
| rowspan="3"| Client
| rowspan="3"| Known Packs
| Namespace
| rowspan="3"| {{Type|Prefixed Array}}
| {{Type|String}}
|
|-
| ID
| {{Type|String}}
|
|-
| Version
| {{Type|String}}
|
|}


==== Custom Report Details (configuration) ====
Status code 5 (shoot arrow / finish eating) is also a special case. The x, y and z fields are all set to 0 like above, with the exception of the face field, which is set to 255.


Contains a list of key-value text entries that are included in any crash or disconnection report generated during connection to the server.
The face can be one of six values, representing the face being hit:


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Value
! Bound To
| 0
! colspan="2"| Field Name
| 1
! colspan="2"| Field Type
| 2
! Notes
| 3
| 4
|-
| rowspan="2"| ''protocol:''<br/><code>0x0F</code><br/><br/>''resource:''<br/><code>custom_report_details</code>
| 5
| rowspan="2"| Configuration
|-
| rowspan="2"| Client
| Offset
| rowspan="2"| Details
| -Y
| +Y
| Title
| rowspan="2"| {{Type|Prefixed Array}} (32)
| -Z
| {{Type|String}} (128)
| +Z
|
| -X
|-
| +X
| Description
| {{Type|String}} (4096)
|
|}
|}


==== Server Links (configuration) ====
In 1.7.3, when a player opens a door with left click the server receives Packet 0xE+start digging and opens the door.


This packet contains a list of links that the vanilla client will display in the menu available from the pause menu. Link labels can be built-in or custom (i.e., any text).
{{anchor|0x0F}}
=== Player Block Placement (0x0F) ===
''Client to Server''


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! colspan="2"| Field Name
! colspan="2"| Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="3"| ''protocol:''<br/><code>0x10</code><br/><br/>''resource:''<br/><code>server_links</code>
| rowspan="8" | 0x0F
| rowspan="3"| Configuration
| X
| rowspan="3"| Client
| int
| rowspan="3"| Links
| <code>32</code>
| Is built-in
| Block position
| rowspan="3"| {{Type|Prefixed Array}}
|-
| {{Type|Boolean}}
| Y
| True if Label is an enum (built-in label), false if it's a text component (custom label).
| unsigned byte
|-
| <code>64</code>
| Label
| Block position
| {{Type|VarInt}} {{Type|Enum}} / {{Type|Text Component}}
|-
| See below.
| Z
|-
| int
| URL
| <code>32</code>
| {{Type|String}}
| Block position
| Valid URL.
|-
| Direction
| byte
| <code>3</code>
| The offset to use for block/item placement (see below)
|-
| Held item
| [[Slot_Data|slot]]
|
|
|-
| Cursor position X
| byte
| 0 - 16
| The position of the crosshair on the block
|-
| Cursor position Y
| byte
| 0 - 16
|
|-
| Cursor position Z
| byte
| 0 - 16
|
|-
| Total Size:
| colspan="4" | 14 bytes + slot data
|}
|}
In normal operation (ie placing a block), this packet is sent once, with the values set normally.


This packet has a special case where X, Y, Z, and Direction 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, shooting bows, using buckets, etc.


{| class="wikitable"
In a Notchian Beta client, the block or item ID corresponds to whatever the client is currently holding, and the client sends one of these packets any time a right-click is issued on a surface, so no assumptions can be made about the safety of the ID. However, with the implementation of server-side inventory, a Notchian server seems to ignore the item ID, instead operating on server-side inventory information and holding selection. The client has been observed (1.2.5 and 1.3.2) to send both real item IDs and -1 in a single session.
! ID
! Name
! Notes
|-
| 0
| Bug Report
| Displayed on connection error screen; included as a comment in the disconnection report.
|-
| 1
| Community Guidelines
|
|-
| 2
| Support
|
|-
| 3
| Status
|
|-
| 4
| Feedback
|
|-
| 5
| Community
|
|-
| 6
| Website
|
|-
| 7
| Forums
|
|-
| 8
| News
|
|-
| 9
| Announcements
|
|-
|}


=== Serverbound ===
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.


==== Client Information (configuration) ====
{{anchor|0x10}}
=== Held Item Change (0x10) ===
''Two-Way''


Sent when the player changes the slot selection
Sent when the player connects, or when settings are changed.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="9"| ''protocol:''<br/><code>0x00</code><br/><br/>''resource:''<br/><code>client_information</code>
| 0x10
| rowspan="9"| Configuration
| Slot ID
| rowspan="9"| Server
| short
| Locale
| <code>1</code>
| {{Type|String}} (16)
| The slot which the player has selected (0-8)
| e.g. <code>en_GB</code>.
|-
|-
| Total Size:
| View Distance
| colspan="4" | 3 bytes
| {{Type|Byte}}
|}
| Client-side render distance, in chunks.
|-
| Chat Mode
| {{Type|VarInt}} {{Type|Enum}}
| 0: enabled, 1: commands only, 2: hidden. See [[Minecraft Wiki:Projects/wiki.vg merge/Chat#Client chat mode|Chat#Client chat mode]] for more information.
|-
| Chat Colors
| {{Type|Boolean}}
| “Colors” multiplayer setting. The vanilla server stores this value but does nothing with it (see [https://bugs.mojang.com/browse/MC-64867 MC-64867]). Third-party servers such as Hypixel disable all coloring in chat and system messages when it is false.
|-
| Displayed Skin Parts
| {{Type|Unsigned Byte}}
| Bit mask, see below.
|-
| Main Hand
| {{Type|VarInt}} {{Type|Enum}}
| 0: Left, 1: Right.
|-
| Enable text filtering
| {{Type|Boolean}}
| Enables filtering of text on signs and written book titles. The vanilla client sets this according to the <code>profanityFilterPreferences.profanityFilterOn</code> account attribute indicated by the [[Minecraft Wiki:Projects/wiki.vg merge/Mojang API#Player Attributes|<code>/player/attributes</code> Mojang API endpoint]]. In offline mode it is always false.
|-
| Allow server listings
| {{Type|Boolean}}
| Servers usually list online players, this option should let you not show up in that list.
|-
| Particle Status
| {{Type|VarInt}} {{Type|Enum}}
| 0: all, 1: decreased, 2: minimal
|}

''Displayed Skin Parts'' flags:


* Bit 0 (0x01): Cape enabled
{{anchor|0x11}}
* Bit 1 (0x02): Jacket enabled
=== Use Bed (0x11) ===
* Bit 2 (0x04): Left Sleeve enabled
''Server to Client''
* 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 tells that a player goes to bed.


==== Cookie Response (configuration) ====
The client with the matching Entity ID will go into bed mode.


Response to a [[#Cookie_Request_(configuration)|Cookie Request (configuration)]] from the server. The vanilla server only accepts responses of up to 5 kiB in size.
This Packet is sent to all nearby players including the one sent to bed.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x01</code><br/><br/>''resource:''<br/><code>cookie_response</code>
| rowspan="5" | 0x11
| rowspan="2"| Configuration
| Entity ID
| rowspan="2"| Server
| int
| 89
| Key
| {{Type|Identifier}}
| Player ID
| The identifier of the cookie.
|-
|-
| Unknown
| Payload
| byte
| {{Type|Prefixed Optional}} {{Type|Prefixed Array}} (5120) of {{Type|Byte}}
| 0
| The data of the cookie.
| Only 0 has been observed
|-
|}
| Bed X
| int
| -247
| Bed headboard X as block coordinate
|-
| Bed Y
| byte
| 78
| Bed headboard Y as block coordinate
|-
| Bed Z
| int
| 128
| Bed headboard Z as block coordinate
|-
| Total Size:
| colspan="4" | 15 bytes
|}


==== Serverbound Plugin Message (configuration) ====
{{anchor|0x12}}


{{Main|Minecraft Wiki:Projects/wiki.vg merge/Plugin channels}}
=== Animation (0x12) ===

''Two-Way''
Mods and plugins can use this to send their data. Minecraft itself uses some [[Minecraft Wiki:Projects/wiki.vg merge/Plugin channels|plugin channels]]. These internal channels are in the <code>minecraft</code> namespace.

More documentation on this: [https://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/ https://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"| ''protocol:''<br/><code>0x02</code><br/><br/>''resource:''<br/><code>custom_payload</code>
| rowspan="2"| Configuration
| rowspan="2"| Server
| Channel
| {{Type|Identifier}}
| Name of the [[Minecraft Wiki:Projects/wiki.vg merge/Plugin channels|plugin channel]] used to send the data.
|-
| Data
| {{Type|Byte Array}} (32767)
| Any data, depending on the channel. <code>minecraft:</code> channels are documented [[Minecraft Wiki:Projects/wiki.vg merge/Plugin channels|here]]. The length of this array must be inferred from the packet length.
|}

In vanilla server, the maximum data length is 32767 bytes.

==== Acknowledge Finish Configuration ====

Sent by the client to notify the server that the configuration process has finished. It is sent in response to the server's [[#Finish_Configuration|Finish Configuration]].

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x03</code><br/><br/>''resource:''<br/><code>finish_configuration</code>
| rowspan="1"| Configuration
| rowspan="1"| Server
| colspan="3"| ''no fields''
|}

This packet switches the connection state to [[#Play|play]].

==== Serverbound Keep Alive (configuration) ====

The server will frequently send out a keep-alive (see [[#Clientbound Keep Alive (configuration)|Clientbound 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
|-
| ''protocol:''<br/><code>0x04</code><br/><br/>''resource:''<br/><code>keep_alive</code>
| Configuration
| Server
| Keep Alive ID
| {{Type|Long}}
|
|}

==== Pong (configuration) ====

Response to the clientbound packet ([[#Ping (configuration)|Ping]]) with the same id.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x05</code><br/><br/>''resource:''<br/><code>pong</code>
| Configuration
| Server
| ID
| {{Type|Int}}
|
|}

==== Resource Pack Response (configuration) ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2" | ''protocol:''<br/><code>0x06</code><br/><br/>''resource:''<br/><code>resource_pack</code>
| rowspan="2" | Configuration
| rowspan="2" | Server
| UUID
| {{Type|UUID}}
| The unique identifier of the resource pack received in the [[#Add_Resource_Pack_(configuration)|Add Resource Pack (configuration)]] request.
|-
| Result
| {{Type|VarInt}} {{Type|Enum}}
| Result ID (see below).
|}

Result can be one of the following values:

{| class="wikitable"
! ID
! Result
|-
| 0
| Successfully downloaded
|-
| 1
| Declined
|-
| 2
| Failed to download
|-
| 3
| Accepted
|-
| 4
| Downloaded
|-
| 5
| Invalid URL
|-
| 6
| Failed to reload
|-
| 7
| Discarded
|}

==== Serverbound Known Packs ====

Informs the server of which data packs are present on the client. The client sends this in response to [[#Clientbound_Known_Packs|Clientbound Known Packs]].

If the client specifies a pack in this packet, the server should omit its contained data from the [[#Registry_Data|Registry Data]] packet.

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x07</code><br/><br/>''resource:''<br/><code>select_known_packs</code>
| rowspan="3"| Configuration
| rowspan="3"| Server
| rowspan="3"| Known Packs
| Namespace
| rowspan="3"| {{Type|Prefixed Array}}
| {{Type|String}}
|
|-
| ID
| {{Type|String}}
|
|-
| Version
| {{Type|String}}
|
|}

== Play ==

=== Clientbound ===

==== Bundle Delimiter ====

The delimiter for a bundle of packets. When received, the client should store every subsequent packet it receives, and wait until another delimiter is received. Once that happens, the client is guaranteed to process every packet in the bundle on the same tick, and the client should stop storing packets.

As of 1.20.6, the vanilla server only uses this to ensure [[#Spawn_Entity|Spawn Entity]] and associated packets used to configure the entity happen on the same tick. Each entity gets a separate bundle.

The vanilla client doesn't allow more than 4096 packets in the same bundle.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x00</code><br/><br/>''resource:''<br/><code>bundle_delimiter</code>
| Play
| Client
| colspan="3"| ''no fields''
|}

==== Spawn Entity ====

Sent by the server when an entity (aside from [[#Spawn_Experience_Orb|Experience Orb]]) is created.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="13"| ''protocol:''<br/><code>0x01</code><br/><br/>''resource:''<br/><code>add_entity</code>
| rowspan="13"| Play
| rowspan="13"| Client
| Entity ID
| {{Type|VarInt}}
| A unique integer ID mostly used in the protocol to identify the entity.
|-
| Entity UUID
| {{Type|UUID}}
| A unique identifier that is mostly used in persistence and places where the uniqueness matters more.
|-
| Type
| {{Type|VarInt}}
| ID in the <code>minecraft:entity_type</code> registry (see "type" field in [[Minecraft Wiki:Projects/wiki.vg merge/Entity metadata#Entities|Entity metadata#Entities]]).
|-
| X
| {{Type|Double}}
|
|-
| Y
| {{Type|Double}}
|
|-
| Z
| {{Type|Double}}
|
|-
| Pitch
| {{Type|Angle}}
| To get the real pitch, you must divide this by (256.0F / 360.0F)
|-
| Yaw
| {{Type|Angle}}
| To get the real yaw, you must divide this by (256.0F / 360.0F)
|-
| Head Yaw
| {{Type|Angle}}
| Only used by living entities, where the head of the entity may differ from the general body rotation.
|-
| Data
| {{Type|VarInt}}
| Meaning dependent on the value of the Type field, see [[Minecraft Wiki:Projects/wiki.vg merge/Object Data|Object Data]] for details.
|-
| Velocity X
| {{Type|Short}}
| rowspan="3"| Same units as [[#Set Entity Velocity|Set Entity Velocity]].
|-
| Velocity Y
| {{Type|Short}}
|-
| Velocity Z
| {{Type|Short}}
|}

{{warning|The points listed below should be considered when this packet is used to spawn a player entity.}}
When in [[Server.properties#online-mode|online mode]], the UUIDs must be valid and have valid skin blobs.
In offline mode, the vanilla server uses [[Wikipedia:Universally unique identifier#Versions 3 and 5 (namespace name-based)|UUID v3]] and chooses the player's UUID by using the String <code>OfflinePlayer:&lt;player name&gt;</code>, encoding it in UTF-8 (and case-sensitive), then processes it with <code>[https://github.com/AdoptOpenJDK/openjdk-jdk8u/blob/9a91972c76ddda5c1ce28b50ca38cbd8a30b7a72/jdk/src/share/classes/java/util/UUID.java#L153-L175 UUID.nameUUIDFromBytes]</code>.

For NPCs UUID v2 should be used. Note:

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

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>.

==== Spawn Experience Orb ====

Spawns one or more experience orbs.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="5"| ''protocol:''<br/><code>0x02</code><br/><br/>''resource:''<br/><code>add_experience_orb</code>
| rowspan="5"| Play
| rowspan="5"| Client
| Entity ID
| {{Type|VarInt}}
|
|-
| X
| {{Type|Double}}
|
|-
| Y
| {{Type|Double}}
|
|-
| Z
| {{Type|Double}}
|
|-
| Count
| {{Type|Short}}
| The amount of experience this orb will reward once collected.
|}

==== Entity Animation ====


Sent whenever an entity should change animation.
Sent whenever an entity should change animation.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x03</code><br/><br/>''resource:''<br/><code>animate</code>
| rowspan="2" | 0x12
| rowspan="2"| Play
| EID
| rowspan="2"| Client
| int
| Entity ID
| <code>55534</code>
| {{Type|VarInt}}
| Player ID
| Player ID.
|-
|-
| Animation
| Animation
| byte
| {{Type|Unsigned Byte}}
| <code>1</code>
| Animation ID
| Animation ID (see below).
|-
|}
| Total Size:
| colspan="4" | 6 bytes
|}


Animation can be one of the following values:
Animation can be one of the following values:


{| class="wikitable"
{| class="wikitable"
! ID
|-
! Animation
! ID
|-
! Animation
|-
| 0
| Swing main arm
| 0
|-
| No animation
|-
| 2
| Leave bed
| 1
|-
| Swing arm
|-
| 3
| Swing offhand
| 2
|-
| Damage animation
|-
| 4
| Critical effect
| 3
|-
| Leave bed
|-
| 5
| Magic critical effect
| 5
|}
| Eat food
|-
| 6
| Critical effect
|-
| 7
| Magic critical effect
|-
| 102
| (unknown)
|-
| 104
| Crouch
|-
| 105
| Uncrouch
|}


==== Award Statistics ====
Only <code>1</code> (swing arm) is sent by notchian clients. Crouching is sent via 0x13. Damage is server-side, and so is not sent by notchian clients. See also [[#0x26|Entity Status]]. As of client 1.5.2, crouching / uncrouching is sent through [[#0x28|Entity Metadata]].


Sent as a response to [[#Client Status|Client Status]] (id 1). Will only send the changed values if previously requested.
{{anchor|0x13}}


{| class="wikitable"
=== Entity Action (0x13) ===
! Packet ID
''Client to Server''
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x04</code><br/><br/>''resource:''<br/><code>award_stats</code>
| rowspan="3"| Play
| rowspan="3"| Client
| rowspan="3"| Statistic
| Category ID
| rowspan="3"| {{Type|Prefixed Array}}
| {{Type|VarInt}}
| See below.
|-
| Statistic ID
| {{Type|VarInt}}
| See below.
|-
| Value
| {{Type|VarInt}}
| The amount to set it to.
|}


Categories (these are namespaced, but with <code>:</code> replaced with <code>.</code>):
Sent at least when crouching, leaving a bed, or sprinting.
To send action animation to client use 0x28.
The client will send this with Action ID = 3 when "Leave Bed" is clicked.


{| class="wikitable"
{| class="wikitable"
! Name
|-
| Packet ID
! ID
! Registry
| Field Name
|-
| Field Type
| <code>minecraft.mined</code>
| Example
| Notes
| 0
| Blocks
|-
|-
| rowspan="3" | 0x13
| <code>minecraft.crafted</code>
| EID
| int
| 1
| Items
| <code>55534</code>
|-
| Player ID
| <code>minecraft.used</code>
|-
| 2
| Action ID
| byte
| Items
|-
| <code>1</code>
| <code>minecraft.broken</code>
| The ID of the action, see below.
|-
| 3
| Items
| '''jumpBoost'''
|-
| int
| <code>0</code>
| <code>minecraft.picked_up</code>
| 4
| Horse jump boost. Ranged from 0 -> 100.
| Items
|-
|-
| Total Size:
| <code>minecraft.dropped</code>
| colspan="4" | 10 bytes
|}
| 5
| Items
|-
| <code>minecraft.killed</code>
| 6
| Entities
|-
| <code>minecraft.killed_by</code>
| 7
| Entities
|-
| <code>minecraft.custom</code>
| 8
| Custom
|}


Blocks, Items, and Entities use block (not block state), item, and entity ids.
Action ID can be one of the following values:

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


{| class="wikitable"
{| class="wikitable"
! Name
|-
! ID
! ID
! Action
! Unit
|-
|-
| <code>minecraft.leave_game</code>
| 1
| Crouch
| 0
| None
|-
| 2
|-
| <code>minecraft.play_time</code>
| Uncrouch
|-
| 1
| 3
| Time
|-
| Leave bed
| <code>minecraft.total_world_time</code>
|-
| 4
| 2
| Time
| Start sprinting
|-
|-
| <code>minecraft.time_since_death</code>
| 5
| 3
| Stop sprinting
| Time
|}
|-
| <code>minecraft.time_since_rest</code>
| 4
| Time
|-
| <code>minecraft.sneak_time</code>
| 5
| Time
|-
| <code>minecraft.walk_one_cm</code>
| 6
| Distance
|-
| <code>minecraft.crouch_one_cm</code>
| 7
| Distance
|-
| <code>minecraft.sprint_one_cm</code>
| 8
| Distance
|-
| <code>minecraft.walk_on_water_one_cm</code>
| 9
| Distance
|-
| <code>minecraft.fall_one_cm</code>
| 10
| Distance
|-
| <code>minecraft.climb_one_cm</code>
| 11
| Distance
|-
| <code>minecraft.fly_one_cm</code>
| 12
| Distance
|-
| <code>minecraft.walk_under_water_one_cm</code>
| 13
| Distance
|-
| <code>minecraft.minecart_one_cm</code>
| 14
| Distance
|-
| <code>minecraft.boat_one_cm</code>
| 15
| Distance
|-
| <code>minecraft.pig_one_cm</code>
| 16
| Distance
|-
| <code>minecraft.horse_one_cm</code>
| 17
| Distance
|-
| <code>minecraft.aviate_one_cm</code>
| 18
| Distance
|-
| <code>minecraft.swim_one_cm</code>
| 19
| Distance
|-
| <code>minecraft.strider_one_cm</code>
| 20
| Distance
|-
| <code>minecraft.jump</code>
| 21
| None
|-
| <code>minecraft.drop</code>
| 22
| None
|-
| <code>minecraft.damage_dealt</code>
| 23
| Damage
|-
| <code>minecraft.damage_dealt_absorbed</code>
| 24
| Damage
|-
| <code>minecraft.damage_dealt_resisted</code>
| 25
| Damage
|-
| <code>minecraft.damage_taken</code>
| 26
| Damage
|-
| <code>minecraft.damage_blocked_by_shield</code>
| 27
| Damage
|-
| <code>minecraft.damage_absorbed</code>
| 28
| Damage
|-
| <code>minecraft.damage_resisted</code>
| 29
| Damage
|-
| <code>minecraft.deaths</code>
| 30
| None
|-
| <code>minecraft.mob_kills</code>
| 31
| None
|-
| <code>minecraft.animals_bred</code>
| 32
| None
|-
| <code>minecraft.player_kills</code>
| 33
| None
|-
| <code>minecraft.fish_caught</code>
| 34
| None
|-
| <code>minecraft.talked_to_villager</code>
| 35
| None
|-
| <code>minecraft.traded_with_villager</code>
| 36
| None
|-
| <code>minecraft.eat_cake_slice</code>
| 37
| None
|-
| <code>minecraft.fill_cauldron</code>
| 38
| None
|-
| <code>minecraft.use_cauldron</code>
| 39
| None
|-
| <code>minecraft.clean_armor</code>
| 40
| None
|-
| <code>minecraft.clean_banner</code>
| 41
| None
|-
| <code>minecraft.clean_shulker_box</code>
| 42
| None
|-
| <code>minecraft.interact_with_brewingstand</code>
| 43
| None
|-
| <code>minecraft.interact_with_beacon</code>
| 44
| None
|-
| <code>minecraft.inspect_dropper</code>
| 45
| None
|-
| <code>minecraft.inspect_hopper</code>
| 46
| None
|-
| <code>minecraft.inspect_dispenser</code>
| 47
| None
|-
| <code>minecraft.play_noteblock</code>
| 48
| None
|-
| <code>minecraft.tune_noteblock</code>
| 49
| None
|-
| <code>minecraft.pot_flower</code>
| 50
| None
|-
| <code>minecraft.trigger_trapped_chest</code>
| 51
| None
|-
| <code>minecraft.open_enderchest</code>
| 52
| None
|-
| <code>minecraft.enchant_item</code>
| 53
| None
|-
| <code>minecraft.play_record</code>
| 54
| None
|-
| <code>minecraft.interact_with_furnace</code>
| 55
| None
|-
| <code>minecraft.interact_with_crafting_table</code>
| 56
| None
|-
| <code>minecraft.open_chest</code>
| 57
| None
|-
| <code>minecraft.sleep_in_bed</code>
| 58
| None
|-
| <code>minecraft.open_shulker_box</code>
| 59
| None
|-
| <code>minecraft.open_barrel</code>
| 60
| None
|-
| <code>minecraft.interact_with_blast_furnace</code>
| 61
| None
|-
| <code>minecraft.interact_with_smoker</code>
| 62
| None
|-
| <code>minecraft.interact_with_lectern</code>
| 63
| None
|-
| <code>minecraft.interact_with_campfire</code>
| 64
| None
|-
| <code>minecraft.interact_with_cartography_table</code>
| 65
| None
|-
| <code>minecraft.interact_with_loom</code>
| 66
| None
|-
| <code>minecraft.interact_with_stonecutter</code>
| 67
| None
|-
| <code>minecraft.bell_ring</code>
| 68
| None
|-
| <code>minecraft.raid_trigger</code>
| 69
| None
|-
| <code>minecraft.raid_win</code>
| 70
| None
|-
| <code>minecraft.interact_with_anvil</code>
| 71
| None
|-
| <code>minecraft.interact_with_grindstone</code>
| 72
| None
|-
| <code>minecraft.target_hit</code>
| 73
| None
|-
| <code>minecraft.interact_with_smithing_table</code>
| 74
| 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 Block Change ====
{{anchor|0x14}}


Acknowledges a user-initiated block change. After receiving this packet, the client will display the block state sent by the server instead of the one predicted by the client.
=== Spawn Named Entity (0x14) ===
''Server to Client''


{| class="wikitable"
The only named entities (at the moment) are players (either real or NPC/Bot). This packet is sent by the server when a player comes into visible range, '''not''' when a player joins.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x05</code><br/><br/>''resource:''<br/><code>block_changed_ack</code>
| rowspan="1"| Play
| rowspan="1"| Client
| Sequence ID
| {{Type|VarInt}}
| Represents the sequence to acknowledge, this is used for properly syncing block changes to the client after interactions.
|}


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


0–9 are the displayable destroy stages and each other number means that there is no animation on this coordinate.
At one point, the Notchian client was not okay with receiving player entity packets, including 0x14, that refer to its own username or EID; and would teleport to the absolute origin of the map and fall through the Void any time it received them. However, in more recent versions, it appears to handle them correctly, by spawning a new entity as directed (though future packets referring to the entity ID may be handled incorrectly).

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.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="3"| ''protocol:''<br/><code>0x06</code><br/><br/>''resource:''<br/><code>block_destruction</code>
| rowspan="9" | 0x14
| rowspan="3"| Play
| EID
| rowspan="3"| Client
| int
| Entity ID
| <code>94453</code>
| {{Type|VarInt}}
| Player ID
| The ID of the entity breaking the block.
|-
|-
| Player Name
| Location
| string
| {{Type|Position}}
| <code>Twdtwd</code>
| Block Position.
| Max length of 16
|-
|-
| Destroy Stage
| X
| {{Type|Unsigned Byte}}
| int
| 0–9 to set it, any other value to remove it.
| <code>784</code>
|}
| Player X as Absolute Integer
|-
| Y
| int
| <code>2131</code>
| Player Y as Absolute Integer
|-
| Z
| int
| <code>-752</code>
| Player Z as Absolute Integer
|-
| Yaw
| byte
| <code>0</code>
| Player rotation as a packed byte
|-
| Pitch
| byte
| <code>0</code>
| Player rotation as a packed byte
|-
| Current Item
| short
| <code>0</code>
| The item the player is currently holding. Note that this should be 0 for "no item", unlike -1 used in other packets. A negative value crashes clients.
|-
| Metadata
| [[Entities#Entity_Metadata_Format|Metadata]]
| <code></code>
| The 1.3 client crashes on packets with no metadata, but the server can send any metadata key of 0, 1 or 8 and the client is fine.
|-
| Total Size:
| colspan="4" | 22 bytes + length of strings + metadata (at least 1)
|}


==== Block Entity Data ====
{{anchor|0x15}}
=== Collect Item (0x16) ===
''Server to Client''


Sets the block entity associated with the block at the given location.
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 ([[#0x1D|0x1D]] does that), and it doesn't add it to your inventory ([[#0x67|0x67]] does that). The server only checks for items to be picked up after each [[#0x0B|Player Position]] and [[#0x0D|Player Position & Look]] packet sent by the client.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="3"| ''protocol:''<br/><code>0x07</code><br/><br/>''resource:''<br/><code>block_entity_data</code>
| rowspan="2" | 0x16
| rowspan="3"| Play
| Collected EID
| rowspan="3"| Client
| int
| Location
| <code>38</code>
| {{Type|Position}}
|
|-
|
|-
| Collector EID
| int
| Type
| {{Type|VarInt}}
| <code>20</code>
| The type of the block entity
|
|-
|-
| Total Size:
| NBT Data
| {{Type|NBT}}
| colspan="4" | 9 bytes
| 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).
|}
|}


==== Block Action ====
{{anchor|0x17}}
=== Spawn Object/Vehicle (0x17) ===
''Server to Client''


This packet is used for a number of actions and animations performed by blocks, usually non-persistent. The client ignores the provided block type and instead uses the block state in their world.
Sent by the server when an Object/Vehicle is created. The throwers entity id is now used for fishing floats too.

See [[Minecraft Wiki:Projects/wiki.vg merge/Block Actions|Block Actions]] for a list of values.

{{warning|This packet uses a block ID from the <code>minecraft:block</code> registry, not a block state.}}


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="4"| ''protocol:''<br/><code>0x08</code><br/><br/>''resource:''<br/><code>block_event</code>
| rowspan="8" | 0x17
| rowspan="4"| Play
| EID
| rowspan="4"| Client
| int
| Location
| <code>62</code>
| {{Type|Position}}
| Entity ID of the Object
| Block coordinates.
|-
|-
| Type
| Action ID (Byte 1)
| byte
| {{Type|Unsigned Byte}}
| <code>11</code>
| Varies depending on block — see [[Minecraft Wiki:Projects/wiki.vg merge/Block Actions|Block Actions]].
| The type of object (see [[Entities#Objects]])
|-
|-
| Action Parameter (Byte 2)
| X
| {{Type|Unsigned Byte}}
| int
| Varies depending on block — see [[Minecraft Wiki:Projects/wiki.vg merge/Block Actions|Block Actions]].
| <code>16080</code>
|-
| The Absolute Integer X Position of the object
| Block Type
|-
| {{Type|VarInt}}
| Y
| The block type ID for the block. This value is unused by the vanilla client, as it will infer the type of block based on the given position.
| int
|}
| <code>2299</code>
| The Absolute Integer Y Position of the object
|-
| Z
| int
| <code>592</code>
| The Absolute Integer Z Position of the object
|-
| Pitch
| byte
| <code>67</code>
| The pitch in steps of 2p/256
|-
| Yaw
| byte
| <code>0</code>
| The yaw in steps of 2p/256
|-
| [[Object Data]]
| [[Object Data]]
|
|
|-
| Total Size:
| colspan="4" | 23 or 29 bytes
|}


==== Block Update ====
{{anchor|0x18}}
=== Spawn Mob (0x18) ===
''Server to Client''


Fired whenever a block is changed within the render distance.
Sent by the server when a Mob Entity is Spawned

{{warning|Changing a block in a chunk that is not loaded is not a stable action. The vanilla 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"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x09</code><br/><br/>''resource:''<br/><code>block_update</code>
| rowspan="12" | 0x18
| rowspan="2"| Play
| EID
| rowspan="2"| Client
| int
| Location
| <code>446</code>
| {{Type|Position}}
| Entity ID
| Block Coordinates.
|-
|-
| Type
| Block ID
| byte
| {{Type|VarInt}}
| <code>91</code>
| The new block state ID for the block as given in the [[Minecraft Wiki:Projects/wiki.vg merge/Chunk Format#Block state registry|block state registry]].
| The type of mob. See [[Entities#Mobs]]
|-
|}
| X
| int
| <code>13366</code>
| The Absolute Integer X Position of the object
|-
| Y
| int
| <code>2176</code>
| The Absolute Integer Y Position of the object
|-
| Z
| int
| <code>1680</code>
| The Absolute Integer Z Position of the object
|-
| Pitch
| byte
| <code>0</code>
| The pitch in steps of 2p/256
|-
| Head Pitch
| byte
| <code>10</code>
| The head pitch in steps of 2p/256
|-
| Yaw
| byte
| <code>-27</code>
| Yaw in steps of 2p/256
|-
| Velocity X
| short
| <code>0</code>
|
|-
| Velocity Y
| short
| <code>0</code>
|
|-
| Velocity Z
| short
| <code>0</code>
|
|-
| Metadata
| [[Entities#Entity_Metadata_Format|Metadata]]
| <code>0 0 127</code>
| Varies by mob, see [[Entities]]
|-
| Total Size:
| colspan="4" | 27 bytes + Metadata (at least 3 as you must send at least 1 item of metadata)
|}


==== Boss Bar ====
{{anchor|0x19}}
=== Spawn Painting (0x19) ===
''Server to Client''


{| class="wikitable"
This packet shows location, name, and type of painting.
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! Field Type
! Notes
|-
| rowspan="14"| ''protocol:''<br/><code>0x0A</code><br/><br/>''resource:''<br/><code>boss_event</code>
| rowspan="14"| Play
| rowspan="14"| Client
| colspan="2"| UUID
| {{Type|UUID}}
| Unique ID for this bar.
|-
| colspan="2"| Action
| {{Type|VarInt}} {{Type|Enum}}
| Determines the layout of the remaining packet.
|-
! Action
! Field Name
!
!
|-
| rowspan="5"| 0: add
| Title
| {{Type|Text Component}}
|
|-
| Health
| {{Type|Float}}
| From 0 to 1. Values greater than 1 do not crash a vanilla client, and start [https://i.johni0702.de/nA.png rendering part of a second health bar] at around 1.5.
|-
| Color
| {{Type|VarInt}} {{Type|Enum}}
| Color ID (see below).
|-
| Division
| {{Type|VarInt}} {{Type|Enum}}
| Type of division (see below).
|-
| Flags
| {{Type|Unsigned Byte}}
| Bit mask. 0x01: should darken sky, 0x02: 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
| {{Type|Float}}
| ''as above''
|-
| 3: update title
| Title
| {{Type|Text Component}}
|
|-
| rowspan="2"| 4: update style
| Color
| {{Type|VarInt}} {{Type|Enum}}
| Color ID (see below).
|-
| Dividers
| {{Type|VarInt}} {{Type|Enum}}
| ''as above''
|-
| 5: update flags
| Flags
| {{Type|Unsigned Byte}}
| ''as above''
|}


{| class="wikitable"
{| class="wikitable"
! ID
|-
! Color
| Packet ID
|-
| Field Name
| 0
| Field Type
| Pink
| Example
|-
| Notes
|-
| 1
| Blue
| rowspan="6" | 0x19
|-
| Entity ID
| int
| 2
| Red
| <code>0x00000326</code>
|-
| Unique entity ID
|-
| 3
| Title
| Green
|-
| string
| 4
| <code>Creepers</code>
| Yellow
| Name of the painting; max length 13 (length of "SkullAndRoses")
|-
|-
| X
| 5
| int
| Purple
|-
| <code>50</code>
| 6
| Center X coordinate
| White
|-
| Y
|}
| int
| <code>66</code>
| Center Y coordinate
|-
| Z
| int
| <code>-50</code>
| Center Z coordinate
|-
| Direction
| int
| <code>0</code>
| Direction the painting faces (0 -z, 1 -x, 2 +z, 3 +x)
|-
| Total Size:
| colspan="4" | 23 bytes + length of string
|}


{| class="wikitable"
Calculating the center of an image: given a (width x height) grid of cells, with (0, 0) being the top left corner, the center is (max(0, width / 2 - 1), height / 2). E.g.
! ID
! Type of division
|-
| 0
| No division
|-
| 1
| 6 notches
|-
| 2
| 10 notches
|-
| 3
| 12 notches
|-
| 4
| 20 notches
|}


==== Change Difficulty ====
2x1 (1, 0)
4x4 (1, 2)


Changes the difficulty setting in the client's option menu
{{anchor|0x1A}}
=== Spawn Experience Orb (0x1A) ===
''Server to Client''


{| class="wikitable"
Spawns one or more experience orbs. Coordinates are in absolute units.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x0B</code><br/><br/>''resource:''<br/><code>change_difficulty</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Difficulty
| {{Type|Unsigned Byte}} {{Type|Enum}}
| 0: peaceful, 1: easy, 2: normal, 3: hard.
|-
| Difficulty locked?
| {{Type|Boolean}}
|
|}

==== Chunk Batch Finished ====

Marks the end of a chunk batch. The vanilla client marks the time it receives this packet and calculates the elapsed duration since the [[#Chunk Batch Start|beginning of the chunk batch]]. The server uses this duration and the batch size received in this packet to estimate the number of milliseconds elapsed per chunk received. This value is then used to calculate the desired number of chunks per tick through the formula <code>25 / millisPerChunk</code>, which is reported to the server through [[#Chunk Batch Received|Chunk Batch Received]]. This likely uses <code>25</code> instead of the normal tick duration of <code>50</code> so chunk processing will only use half of the client's and network's bandwidth.

The vanilla client uses the samples from the latest 15 batches to estimate the milliseconds per chunk number.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x0C</code><br/><br/>''resource:''<br/><code>chunk_batch_finished</code>
| rowspan="5" | 0x1A
| rowspan="1"| Play
| Entity ID
| rowspan="1"| Client
| int
| Batch size
| 105668
| {{Type|VarInt}}
|
| Number of chunks.
|-
| x
|}
| int
| -1143
|
|-
| y
| int
| 1952
|
|-
| z
| int
| 1166
|
|-
| count
| short
| 7
|
|-
| Total Size:
| colspan="4" | 19 bytes
|}


==== Chunk Batch Start ====
{{anchor|0x1B}}
=== Steer Vehicle (0x1B) ===
''Client to Server''


Marks the start of a chunk batch. The vanilla client marks and stores the time it receives this packet.
Sent by client to steer the horse, minecart and boats.
Horses listen to all directions, boats and minecarts only listen to the positive forward value in combination with the direction the player is looking in.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| ''protocol:''<br/><code>0x0D</code><br/><br/>''resource:''<br/><code>chunk_batch_start</code>
| rowspan="4" | 0x1B
| Play
| Sideways
| float
| Client
| colspan="3"| ''no fields''
| 0.98
|}
| Positive to the left of the player
|-
| Forward
| float
| -0.98
| Positive forward
|-
| Jump
| bool
| true
|
|-
| Unmount
| bool
| false
| True when leaving the vehicle
|-
| Total Size:
| colspan="4" | 11 bytes
|}


==== Chunk Biomes ====
{{anchor|0x1C}}
=== Entity Velocity (0x1C) ===
''Server to Client''


{| class="wikitable"
This packet is new to version 4 of the protocol, and is believed to be Entity Velocity/Motion.
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x0E</code><br/><br/>''resource:''<br/><code>chunks_biomes</code>
| rowspan="3"| Play
| rowspan="3"| Client
| rowspan="3"| Chunk biome data
| Chunk Z
| rowspan="3"| {{Type|Prefixed Array}}
| {{Type|Int}}
| Chunk coordinate (block coordinate divided by 16, rounded down)
|-
| Chunk X
| {{Type|Int}}
| Chunk coordinate (block coordinate divided by 16, rounded down)
|-
| Data
| {{Type|Prefixed Array}} of {{Type|Byte}}
| Chunk [[Minecraft Wiki:Projects/wiki.vg merge/Chunk Format#Data structure|data structure]], with [[Minecraft Wiki:Projects/wiki.vg merge/Chunk Format#Chunk_Section|sections]] containing only the <code>Biomes</code> field
|}


Note: The order of X and Z is inverted, because the client reads them as one big-endian {{Type|Long}}, with Z being the upper 32 bits.
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).


==== Clear Titles ====
(This packet data values are not fully verified)

Clear the client's current title information, with the option to also reset it.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x0F</code><br/><br/>''resource:''<br/><code>clear_titles</code>
| rowspan="4" | 0x1C
| rowspan="1"| Play
| Entity ID
| rowspan="1"| Client
| int
| Reset
| <code>1805</code>
| {{Type|Boolean}}
| The entity ID
|-
|
|}
| Velocity X
| short
| <code>-1343</code>
| Velocity on the X axis
|-
| Velocity Y
| short
| <code>0</code>
| Velocity on the Y axis
|-
| Velocity Z
| short
| <code>0</code>
| Velocity on the Z axis
|-
| Total Size:
| colspan="4" | 11 bytes
|}


==== Command Suggestions Response ====
{{anchor|0x1D}}


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.
=== Destroy Entity (0x1D) ===
''Server to Client''


{| class="wikitable"
Sent by the server when an list of Entities is to be destroyed on the client.
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="5"| ''protocol:''<br/><code>0x10</code><br/><br/>''resource:''<br/><code>command_suggestions</code>
| rowspan="5"| Play
| rowspan="5"| Client
| colspan="2"| ID
| colspan="2"| {{Type|VarInt}}
| Transaction ID.
|-
| colspan="2"| Start
| colspan="2"| {{Type|VarInt}}
| Start of the text to replace.
|-
| colspan="2"| Length
| colspan="2"| {{Type|VarInt}}
| Length of the text to replace.
|-
| rowspan="2"| Matches
| Match
| rowspan="2"| {{Type|Prefixed Array}}
| {{Type|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.
|-
| Tooltip
| {{Type|Prefixed Optional}} {{Type|Text Component}}
| Tooltip to display.
|}

==== 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.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x11</code><br/><br/>''resource:''<br/><code>commands</code>
| rowspan="2" | 0x1D
| rowspan="2"| Play
| Entity Count
| rowspan="2"| Client
| byte
| Nodes
| <code>3</code>
| {{Type|Prefixed Array}} of [[Minecraft Wiki:Projects/wiki.vg merge/Command Data#Node Format|Node]]
| The amount of entities which should be destroyed
| An array of nodes.
|-
|-
| Entity IDs
| Root index
| array of int
| {{Type|VarInt}}
| <code>452, 546, 123</code>
| Index of the <code>root</code> node in the previous array.
| The list of entity ids which should be destroyed
|-
|}
| Total Size:
| colspan="4" | 2 + (entity count * 4) bytes
|}


For more information on this packet, see the [[Minecraft Wiki:Projects/wiki.vg merge/Command Data|Command Data]] article.
{{anchor|0x1E}}
=== Entity (0x1E) ===
''Server to Client''


==== Close Container ====
Most entity-related packets are subclasses of this packet. When sent from the server to the client, it may initialize the entry.


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. The vanilla client disregards the provided window ID and closes any active window.
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
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| ''protocol:''<br/><code>0x12</code><br/><br/>''resource:''<br/><code>container_close</code>
| 0x1E
| EID
| Play
| int
| Client
| Window ID
| <code>446</code>
| {{Type|VarInt}}
| Entity ID
| This is the ID of the window that was closed. 0 for inventory.
|-
|}
| Total Size:
| colspan="4" | 5 bytes
|}


==== Set Container Content ====
{{anchor|0x1F}}
[[File:Inventory-slots.png|thumb|The inventory slots]]
=== Entity Relative Move (0x1F) ===
''Server to Client''


Replaces the contents of a container window. Sent by the server upon initialization of a container window or the player's inventory, and in response to state ID mismatches (see [[#Click Container]]).
This packet is sent by the server when an entity moves less then 4 blocks; if an entity moves more than 4 blocks [[#0x22|Entity Teleport]] should be sent instead.


{| class="wikitable"
This packet allows at most four blocks movement in any direction, because byte range is from -128 to 127. Movement is an offset of Absolute Int; to convert relative move to block coordinate offset, divide by 32.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="4"| ''protocol:''<br/><code>0x13</code><br/><br/>''resource:''<br/><code>container_set_content</code>
| rowspan="4"| Play
| rowspan="4"| Client
| Window ID
| {{Type|VarInt}}
| The ID of window which items are being sent for. 0 for player inventory. The client ignores any packets targeting a Window ID other than the current one. However, an exception is made for the player inventory, which may be targeted at any time. (The vanilla server does not appear to utilize this special case.)
|-
| State ID
| {{Type|VarInt}}
| A server-managed sequence number used to avoid desynchronization; see [[#Click Container]].
|-
| Slot Data
| {{Type|Prefixed Array}} of {{Type|Slot}}
|-
| Carried Item
| {{Type|Slot}}
| Item being dragged with the mouse.
|}

See [[Minecraft Wiki:Projects/wiki.vg merge/Inventory#Windows|inventory windows]] for further information about how slots are indexed.
Use [[#Open Screen|Open Screen]] to open the container on the client.

==== Set Container Property ====

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


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="3"| ''protocol:''<br/><code>0x14</code><br/><br/>''resource:''<br/><code>container_set_data</code>
| rowspan="4" | 0x1F
| rowspan="3"| Play
| EID
| rowspan="3"| Client
| int
| Window ID
| <code>459</code>
| {{Type|VarInt}}
| Entity ID
|-
|
|-
| dX
| Property
| byte
| {{Type|Short}}
| <code>1</code>
| The property to be updated, see below.
| X axis Relative movement as an Absolute Integer
|-
|-
| dY
| Value
| {{Type|Short}}
| byte
| The new value for the property, see below.
| <code>-7</code>
|}
| Y axis Relative movement as an Absolute Integer
|-
| dZ
| byte
| <code>5</code>
| Z axis Relative movement as an Absolute Integer
|-
| Total Size:
| colspan="4" | 8 bytes
|}


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.
{{anchor|0x20}}
=== Entity Look (0x20) ===
''Server to Client''


{| class="wikitable"
This packet is sent by the server when an entity rotates. Example: "Yaw" field 64 means a 90 degree turn.
|-
! Window type
! Property
! Value
|-
| rowspan="4"| 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 vanilla server
|-
| rowspan="10"| Enchantment Table
| 0: Level requirement for top enchantment slot
| rowspan="3"| 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 [[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>).
|-
| 4: Enchantment ID shown on mouse hover over top enchantment slot
| rowspan="3"| 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
| 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
|-
| 9: Enchantment level shown on mouse hover over the bottom slot
|-
| rowspan="3"| Beacon
| 0: Power level
| 0-4, controls what effect buttons are enabled
|-
| 1: First potion effect
| [[Data values#Status effects|Potion effect ID]] for the first effect, or -1 if no effect
|-
| 2: Second potion effect
| [[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
|-
| 1: Fuel time
| 0 - 20, with 0 making the arrow empty, and 20 making the arrow full
|-
| Stonecutter
| 0: Selected recipe
| The index of the selected recipe. -1 means none is selected.
|-
| Loom
| 0: Selected pattern
| The index of the selected pattern. 0 means none is selected, 0 is also the internal id of the "base" pattern.
|-
| Lectern
| 0: Page number
| The current page number, starting from 0.
|}

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


{| class="wikitable"
{| class="wikitable"
! Numerical ID
|-
| Packet ID
! Enchantment ID
| Field Name
! Enchantment Name
|-
| Field Type
| 0
| Example
| minecraft:protection
| Notes
| Protection
|-
|-
| rowspan="3" | 0x20
| EID
| 1
| minecraft:fire_protection
| int
| Fire Protection
| <code>459</code>
|-
| Entity ID
|-
| 2
| minecraft:feather_falling
| Yaw
| Feather Falling
| byte
|-
| <code>126</code>
| 3
| The X Axis rotation as a fraction of 360
| minecraft:blast_protection
|-
| Blast Protection
| Pitch
|-
| byte
| 4
| <code>0</code>
| minecraft:projectile_protection
| The Y Axis rotation as a fraction of 360
| Projectile Protection
|-
|-
| Total Size:
| 5
| colspan="4" | 7 bytes
| 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:soul_speed
| Soul Speed
|-
| 12
| minecraft:swift_sneak
| Swift Sneak
|-
| 13
| minecraft:sharpness
| Sharpness
|-
| 14
| minecraft:smite
| Smite
|-
| 15
| minecraft:bane_of_arthropods
| Bane of Arthropods
|-
| 16
| minecraft:knockback
| Knockback
|-
| 17
| minecraft:fire_aspect
| Fire Aspect
|-
| 18
| minecraft:looting
| Looting
|-
| 19
| minecraft:sweeping_edge
| Sweeping Edge
|-
| 20
| minecraft:efficiency
| Efficiency
|-
| 21
| minecraft:silk_touch
| Silk Touch
|-
| 22
| minecraft:unbreaking
| Unbreaking
|-
| 23
| minecraft:fortune
| Fortune
|-
| 24
| minecraft:power
| Power
|-
| 25
| minecraft:punch
| Punch
|-
| 26
| minecraft:flame
| Flame
|-
| 27
| minecraft:infinity
| Infinity
|-
| 28
| minecraft:luck_of_the_sea
| Luck of the Sea
|-
| 29
| minecraft:lure
| Lure
|-
| 30
| minecraft:loyalty
| Loyalty
|-
| 31
| minecraft:impaling
| Impaling
|-
| 32
| minecraft:riptide
| Riptide
|-
| 33
| minecraft:channeling
| Channeling
|-
| 34
| minecraft:multishot
| Multishot
|-
| 35
| minecraft:quick_charge
| Quick Charge
|-
| 36
| minecraft:piercing
| Piercing
|-
| 37
| minecraft:density
| Density
|-
| 38
| minecraft:breach
| Breach
|-
| 39
| minecraft:wind_burst
| Wind Burst
|-
| 40
| minecraft:mending
| Mending
|-
| 41
| minecraft:vanishing_curse
| Curse of Vanishing
|}

==== Set Container 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
|-
| rowspan="4"| ''protocol:''<br/><code>0x15</code><br/><br/>''resource:''<br/><code>container_set_slot</code>
| rowspan="4"| Play
| rowspan="4"| Client
| Window ID
| {{Type|VarInt}}
| The window which is being updated. 0 for player inventory. The client ignores any packets targeting a Window ID other than the current one; see below for exceptions.
|-
| State ID
| {{Type|VarInt}}
| A server-managed sequence number used to avoid desynchronization; see [[#Click Container]].
|-
| Slot
| {{Type|Short}}
| The slot that should be updated.
|-
| Slot Data
| {{Type|Slot}}
|
|}

If Window ID is 0, the hotbar and offhand slots (slots 36 through 45) may be updated even when a different container window is open. (The vanilla server does not appear to utilize this special case.) Updates are also restricted to those slots when the player is looking at a creative inventory tab other than the survival inventory. (The vanilla server does ''not'' handle this restriction in any way, leading to [https://bugs.mojang.com/browse/MC-242392 MC-242392].)

If Window ID is -1, the item being dragged with the mouse is set. In this case, State ID and Slot are ignored.

If Window ID is -2, any slot in the player's inventory can be updated irrespective of the current container window. In this case, State ID is ignored, and the vanilla server uses a bogus value of 0. Used by the vanilla server to implement the [[#Pick Item]] functionality.

When a container window is open, the server never sends updates targeting Window ID 0&mdash;all of the [[Minecraft Wiki:Projects/wiki.vg merge/Inventory|window types]] include slots for the player inventory. The client must automatically apply changes targeting the inventory portion of a container window to the main inventory; the server does not resend them for ID 0 when the window is closed. However, since the armor and offhand slots are only present on ID 0, updates to those slots occurring while a window is open must be deferred by the server until the window's closure.

==== Cookie Request (play) ====

Requests a cookie that was previously stored.

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x16</code><br/><br/>''resource:''<br/><code>cookie_request</code>
| rowspan="1"| Play
| rowspan="1"| Client
| colspan="2"| Key
| colspan="2"| {{Type|Identifier}}
| The identifier of the cookie.
|}

==== Set Cooldown ====

Applies a cooldown period to all items with the given type. Used by the vanilla 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
|-
| rowspan="2"| ''protocol:''<br/><code>0x17</code><br/><br/>''resource:''<br/><code>cooldown</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Item ID
| {{Type|VarInt}}
| Numeric ID of the item to apply a cooldown to.
|-
| Cooldown Ticks
| {{Type|VarInt}}
| Number of ticks to apply a cooldown for, or 0 to clear the cooldown.
|}

==== Chat Suggestions ====

Unused by the vanilla server. Likely provided for custom servers to send chat message completions to clients.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x18</code><br/><br/>''resource:''<br/><code>custom_chat_completions</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Action
| {{Type|VarInt}} {{Type|Enum}}
| 0: Add, 1: Remove, 2: Set
|-
| Entries
| {{Type|Prefixed Array}} of {{Type|String}} (32767)
|
|}

==== Clientbound Plugin Message (play) ====

{{Main|Minecraft Wiki:Projects/wiki.vg merge/Plugin channels}}

Mods and plugins can use this to send their data. Minecraft itself uses several [[Minecraft Wiki:Projects/wiki.vg merge/Plugin channels|plugin channels]]. These internal channels are in the <code>minecraft</code> namespace.

More information on how it works on [https://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/ Dinnerbone's blog]. More documentation about internal and popular registered channels are [[Minecraft Wiki:Projects/wiki.vg merge/Plugin channels|here]].

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x19</code><br/><br/>''resource:''<br/><code>custom_payload</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Channel
| {{Type|Identifier}}
| Name of the [[Minecraft Wiki:Projects/wiki.vg merge/Plugin channels|plugin channel]] used to send the data.
|-
| Data
| {{Type|Byte Array}} (1048576)
| Any data. The length of this array must be inferred from the packet length.
|}

In vanilla clients, the maximum data length is 1048576 bytes.

==== Damage Event ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="9"| ''protocol:''<br/><code>0x1A</code><br/><br/>''resource:''<br/><code>damage_event</code>
| rowspan="9"| Play
| rowspan="9"| Client
|-
| colspan="2"| Entity ID
| colspan="2"| {{Type|VarInt}}
| The ID of the entity taking damage
|-
| colspan="2"| Source Type ID
| colspan="2"| {{Type|VarInt}}
| The type of damage in the <code>minecraft:damage_type</code> registry, defined by the [[Java Edition protocol#Registry_Data|Registry Data]] packet.
|-
| colspan="2"| Source Cause ID
| colspan="2"| {{Type|VarInt}}
| The ID + 1 of the entity responsible for the damage, if present. If not present, the value is 0
|-
| colspan="2"| Source Direct ID
| colspan="2"| {{Type|VarInt}}
| The ID + 1 of the entity that directly dealt the damage, if present. If not present, the value is 0. If this field is present:
* and damage was dealt indirectly, such as by the use of a projectile, this field will contain the ID of such projectile;
* and damage was dealt dirctly, such as by manually attacking, this field will contain the same value as Source Cause ID.
|-
| colspan="2"| Has Source Position
| colspan="2"| {{Type|Boolean}}
| Indicates the presence of the three following fields.
The vanilla server sends the Source Position when the damage was dealt by the /damage command and a position was specified
|-
| colspan="2"| Source Position X
| colspan="2"| {{Type|Optional}} {{Type|Double}}
| Only present if Has Source Position is true
|-
| colspan="2"| Source Position Y
| colspan="2"| {{Type|Optional}} {{Type|Double}}
| Only present if Has Source Position is true
|-
| colspan="2"| Source Position Z
| colspan="2"| {{Type|Optional}} {{Type|Double}}
| Only present if Has Source Position is true
|}

==== Debug Sample ====

Sample data that is sent periodically after the client has subscribed with [[#Debug_Sample_Subscription|Debug Sample Subscription]].

The vanilla server only sends debug samples to players that are server operators.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x1B</code><br/><br/>''resource:''<br/><code>debug_sample</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Sample
| {{Type|Prefixed Array}} of {{Type|Long}}
| Array of type-dependent samples.
|-
| Sample Type
| {{Type|VarInt}} {{Type|Enum}}
| See below.
|}

Types:

{| class="wikitable"
! Id !! Name !! Description
|-
| 0 || Tick time || Four different tick-related metrics, each one represented by one long on the array.
They are measured in nano-seconds, and are as follows:
* 0: Full tick time: Aggregate of the three times below;
* 1: Server tick time: Main server tick logic;
* 2: Tasks time: Tasks scheduled to execute after the main logic;
* 3: Idle time: Time idling to complete the full 50ms tick cycle.
Note that the vanilla client calculates the timings used for min/max/average display by subtracting the idle time from the full tick time. This can cause the displayed values to go negative if the idle time is (nonsensically) greater than the full tick time.
|}

==== Delete Message ====

Removes a message from the client's chat. This only works for messages with signatures, system messages cannot be deleted with this packet.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x1C</code><br/><br/>''resource:''<br/><code>delete_chat</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Message ID
| {{Type|VarInt}}
| The message Id + 1, used for validating message signature. The next field is present only when value of this field is equal to 0.
|-
| Signature
| {{Type|Optional}} {{Type|Byte Array}} (256)
| The previous message's signature. Always 256 bytes and not length-prefixed.
|}

==== 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
|-
| ''protocol:''<br/><code>0x1D</code><br/><br/>''resource:''<br/><code>disconnect</code>
| Play
| Client
| Reason
| {{Type|Text Component}}
| Displayed to the client when the connection terminates.
|}

==== Disguised Chat Message ====

{{Main|Chat}}

Sends the client a chat message, but without any message signing information.

The vanilla server uses this packet when the console is communicating with players through commands, such as <code>/say</code>, <code>/tell</code>, <code>/me</code>, among others.

{| class="wikitable
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="4"| ''protocol:''<br/><code>0x1E</code><br/><br/>''resource:''<br/><code>disguised_chat</code>
| rowspan="4"| Play
| rowspan="4"| Client
| Message
| {{Type|Text Component}}
| This is used as the <code>content</code> parameter when formatting the message on the client.
|-
| Chat Type
| {{Type|VarInt}}
| The type of chat in the <code>minecraft:chat_type</code> registry, defined by the [[Java Edition protocol#Registry_Data|Registry Data]] packet.
|-
| Sender Name
| {{Type|Text Component}}
| The name of the one sending the message, usually the sender's display name.
This is used as the <code>sender</code> parameter when formatting the message on the client.
|-
| Target Name
| {{Type|Prefixed Optional}} {{Type|Text Component}}
| The name of the one receiving the message, usually the receiver's display name.
This is used as the <code>target</code> parameter when formatting the message on the client.
|}

==== Entity Event ====

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
|-
| rowspan="2"| ''protocol:''<br/><code>0x1F</code><br/><br/>''resource:''<br/><code>entity_event</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Entity ID
| {{Type|Int}}
|
|-
| Entity Status
| {{Type|Byte}} {{Type|Enum}}
| See [[Minecraft Wiki:Projects/wiki.vg merge/Entity statuses|Entity statuses]] for a list of which statuses are valid for each type of entity.
|}

==== Teleport Entity ====


{{warning|The Mojang-specified name of this packet was changed in 1.21.2 from <code>teleport_entity</code> to <code>entity_position_sync</code>. There is a new <code>teleport_entity</code>, which this document more appropriately calls [[#Synchronize Vehicle Position|Synchronize Vehicle Position]]. That packet has a different function and will lead to confusing results if used in place of this one.}}
{{anchor|0x21}}
=== Entity Look and Relative Move (0x21) ===
''Server to Client''


This packet is sent by the server when an entity rotates and moves.
This packet is sent by the server when an entity moves more than 8 blocks.
Since a byte range is limited from -128 to 127, and movement is offset of Absolute Int,
this packet allows at most four blocks movement in any direction. (-128/32 == -4)


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="10"| ''protocol:''<br/><code>0x20</code><br/><br/>''resource:''<br/><code>entity_position_sync</code>
| rowspan="6" | 0x21
| rowspan="10"| Play
| EID
| rowspan="10"| Client
| int
| Entity ID
| <code>459</code>
| {{Type|VarInt}}
| Entity ID
|-
|
|-
| dX
| byte
| X
| {{Type|Double}}
| <code>1</code>
|
| X axis Relative movement as an Absolute Integer
|-
|-
| dY
| Y
| {{Type|Double}}
| byte
|
| <code>-7</code>
|-
| Y axis Relative movement as an Absolute Integer
|-
| Z
| {{Type|Double}}
| dZ
|
| byte
|-
| <code>5</code>
| Velocity X
| Z axis Relative movement as an Absolute Integer
| {{Type|Double}}
|-
|
| Yaw
|-
| byte
| Velocity Y
| <code>126</code>
| {{Type|Double}}
| The X Axis rotation as a fraction of 360
|-
|
|-
| Pitch
| Velocity Z
| byte
| {{Type|Double}}
| <code>0</code>
|
| The Y Axis rotation as a fraction of 360
|-
|-
| Yaw
| Total Size:
| {{Type|Float}}
| colspan="4" | 10 bytes
| Rotation on the X axis, in degrees.
|-
| Pitch
| {{Type|Float}}
| Rotation on the Y axis, in degrees.
|-
| On Ground
| {{Type|Boolean}}
|
|}
|}


==== Explosion ====
{{anchor|0x22}}
=== Entity Teleport (0x22) ===
''Server to Client''


Sent when an explosion occurs (creepers, TNT, and ghast fireballs).
This packet is sent by the server when an entity moves more than 4 blocks.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="10"| ''protocol:''<br/><code>0x21</code><br/><br/>''resource:''<br/><code>explode</code>
| rowspan="6" | 0x22
| rowspan="10"| Play
| EID
| rowspan="10"| Client
| int
| X
| <code>459</code>
| {{Type|Double}}
| Entity ID
|-
|
| X
|-
| int
| Y
| {{Type|Double}}
| <code>14162</code>
|
| X axis position as an Absolute Integer
|-
|-
| Y
| Z
| {{Type|Double}}
| int
|
| <code>2176</code>
|-
| Y axis position as an Absolute Integer
| Has Player Velocity
|-
| {{Type|Boolean}}
| Z
|
| int
|-
| <code>1111</code>
| Player Velocity X
| Z axis position as an Absolute Integer
| {{Type|Optional}} {{Type|Double}}
|-
| X velocity of the player being pushed by the explosion. Only present if Has Player Velocity is true.
| Yaw
|-
| byte
| Player Velocity Y
| <code>126</code>
| {{Type|Optional}} {{Type|Float}}
| The X Axis rotation as a fraction of 360
| Y velocity of the player being pushed by the explosion. Only present if Has Player Velocity is true.
|-
|-
| Pitch
| Player Velocity Z
| byte
| {{Type|Optional}} {{Type|Float}}
| <code>0</code>
| Z velocity of the player being pushed by the explosion. Only present if Has Player Velocity is true.
| The Y Axis rotation as a fraction of 360
|-
|-
| Explosion Particle ID
| Total Size:
| {{Type|VarInt}}
| colspan="4" | 19 bytes
| The particle ID listed in [[Minecraft Wiki:Projects/wiki.vg merge/Particles|Particles]].
|-
| Explosion Particle Data
| Varies
| Particle data as specified in [[Minecraft Wiki:Projects/wiki.vg merge/Particles|Particles]].
|-
| Explosion Sound
| {{Type|ID or}} {{Type|Sound Event}}
| ID in the <code>minecraft:sound_event</code> registry, or an inline definition.
|}

==== Unload Chunk ====

Tells the client to unload a chunk column.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x22</code><br/><br/>''resource:''<br/><code>forget_level_chunk</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Chunk Z
| {{Type|Int}}
| Block coordinate divided by 16, rounded down.
|-
| Chunk X
| {{Type|Int}}
| Block coordinate divided by 16, rounded down.
|}

Note: The order is inverted, because the client reads this packet as one big-endian {{Type|Long}}, with Z being the upper 32 bits.

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

==== Game Event ====

Used for a wide variety of game events, from weather to bed use to game mode to demo messages.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x23</code><br/><br/>''resource:''<br/><code>game_event</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Event
| {{Type|Unsigned Byte}}
| See below.
|-
| Value
| {{Type|Float}}
| Depends on Event.
|}

''Events'':

{| class="wikitable"
! Event
! Effect
! Value
|-
| 0
| No respawn block available
| Note: Displays message 'block.minecraft.spawn.not_valid' (You have no home bed or charged respawn anchor, or it was obstructed) to the player.
|-
| 1
| Begin raining
|
|-
| 2
| End raining
|
|-
| 3
| Change game mode
| 0: Survival, 1: Creative, 2: Adventure, 3: Spectator.
|-
| 4
| Win game
| 0: Just respawn player.<br>1: Roll the credits and respawn player.<br>Note that 1 is only sent by vanilla server when player has not yet achieved advancement "The end?", else 0 is sent.
|-
| 5
| Demo event
| 0: Show welcome to demo screen.<br>101: Tell movement controls.<br>102: Tell jump control.<br>103: Tell inventory control.<br>104: Tell that the demo is over and print a message about how to take a screenshot.
|-
| 6
| Arrow hit player
| Note: Sent when any player is struck by an arrow.
|-
| 7
| Rain level change
| Note: Seems to change both sky color and lighting.<br>Rain level ranging from 0 to 1.
|-
| 8
| Thunder level change
| Note: Seems to change both sky color and lighting (same as Rain level change, but doesn't start rain). It also requires rain to render by vanilla client.<br>Thunder level ranging from 0 to 1.
|-
| 9
| Play pufferfish sting sound
|-
| 10
| Play elder guardian mob appearance (effect and sound)
|
|-
| 11
| Enable respawn screen
| 0: Enable respawn screen.<br>1: Immediately respawn (sent when the <code>doImmediateRespawn</code> gamerule changes).
|-
| 12
| Limited crafting
| 0: Disable limited crafting.<br>1: Enable limited crafting (sent when the <code>doLimitedCrafting</code> gamerule changes).
|-
| 13
| Start waiting for level chunks
| Instructs the client to begin the waiting process for the level chunks.<br>Sent by the server after the level is cleared on the client and is being re-sent (either during the first, or subsequent reconfigurations).
|}

==== Open Horse Screen ====

This packet is used exclusively for opening the horse GUI. [[#Open Screen|Open Screen]] is used for all other GUIs. The client will not open the inventory if the Entity ID does not point to an horse-like animal.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x24</code><br/><br/>''resource:''<br/><code>horse_screen_open</code>
| rowspan="3"| Play
| rowspan="3"| Client
| Window ID
| {{Type|VarInt}}
| Same as the field of [[#Open Screen|Open Screen]].
|-
| Inventory columns count
| {{Type|VarInt}}
| How many columns of horse inventory slots exist in the GUI, 3 slots per column.
|-
| Entity ID
| {{Type|Int}}
| The "owner" entity of the GUI. The client should close the GUI if the owner entity dies or is cleared.
|}

==== Hurt Animation ====

Plays a bobbing animation for the entity receiving damage.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x25</code><br/><br/>''resource:''<br/><code>hurt_animation</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Entity ID
| {{Type|VarInt}}
| The ID of the entity taking damage
|-
| Yaw
| {{Type|Float}}
| The direction the damage is coming from in relation to the entity
|}

==== Initialize World Border ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="8"| ''protocol:''<br/><code>0x26</code><br/><br/>''resource:''<br/><code>initialize_border</code>
| rowspan="8"| Play
| rowspan="8"| Client
| X
| {{Type|Double}}
|
|-
| Z
| {{Type|Double}}
|
|-
| Old Diameter
| {{Type|Double}}
| Current length of a single side of the world border, in meters.
|-
| New Diameter
| {{Type|Double}}
| Target length of a single side of the world border, in meters.
|-
| Speed
| {{Type|VarLong}}
| Number of real-time ''milli''seconds until New Diameter is reached. It appears that vanilla 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
| {{Type|VarInt}}
| Resulting coordinates from a portal teleport are limited to ±value. Usually 29999984.
|-
| Warning Blocks
| {{Type|VarInt}}
| In meters.
|-
| Warning Time
| {{Type|VarInt}}
| In seconds as set by <code>/worldborder warning time</code>.
|}

The vanilla 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>

==== Clientbound Keep Alive (play) ====

The server will frequently send out a keep-alive, each containing a random ID. The client must respond with the same payload (see [[#Serverbound Keep Alive (play)|Serverbound Keep Alive]]). If the client does not respond to a Keep Alive packet within 15 seconds after it was sent, 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 vanilla 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
|-
| ''protocol:''<br/><code>0x27</code><br/><br/>''resource:''<br/><code>keep_alive</code>
| Play
| Client
| Keep Alive ID
| {{Type|Long}}
|
|}

==== Chunk Data and Update Light ====
{{Main|Minecraft Wiki:Projects/wiki.vg merge/Chunk Format}}
{{See also|#Unload Chunk}}

Sent when a chunk comes into the client's view distance, specifying its terrain, lighting and block entities.

The chunk must be within the view area previously specified with [[#Set Center Chunk|Set Center Chunk]]; see that packet for details.

It is not strictly necessary to send all block entities in this packet; it is still legal to send them with [[#Block Entity Data|Block Entity Data]] later.
{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="4"| ''protocol:''<br/><code>0x28</code><br/><br/>''resource:''<br/><code>level_chunk_with_light</code>
| rowspan="4"| Play
| rowspan="4"| Client
| Chunk X
| {{Type|Int}}
| Chunk coordinate (block coordinate divided by 16, rounded down)
|-
| Chunk Z
| {{Type|Int}}
| Chunk coordinate (block coordinate divided by 16, rounded down)
|-
| Data
| {{Type|Chunk Data}}
|
|-
| Light
| {{Type|Light Data}}
|
|}

Unlike the [[#Update Light|Update Light]] packet which uses the same format, setting the bit corresponding to a section to 0 in both of the block light or sky light masks does not appear to be useful, and the results in testing have been highly inconsistent.

==== World Event ====

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), effect 1028 (enderdragon death), and effect 1038 (end portal opening); it is ignored on other effects.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="4"| ''protocol:''<br/><code>0x29</code><br/><br/>''resource:''<br/><code>level_event</code>
| rowspan="4"| Play
| rowspan="4"| Client
| Event
| {{Type|Int}}
| The event, see below.
|-
| Location
| {{Type|Position}}
| The location of the event.
|-
| Data
| {{Type|Int}}
| Extra data for certain events, see below.
|-
| Disable Relative Volume
| {{Type|Boolean}}
| See above.
|}

Events:

{| class="wikitable"
! ID
! Name
! Data
|-
! colspan="3"| Sound
|-
| 1000
| Dispenser dispenses
|
|-
| 1001
| Dispenser fails to dispense
|
|-
| 1002
| Dispenser shoots
|
|-
| 1004
| Firework shot
|
|-
| 1009
| Fire extinguished
|
|-
| 1010
| Play record
| An ID in the <code>minecraft:item</code> registry, corresponding to a [[Music Disc|record item]]. If the ID doesn't correspond to a record, the packet is ignored. Any record already being played at the given location is overwritten. See [[Minecraft Wiki:Projects/wiki.vg merge/Data Generators|Data Generators]] for information on item IDs.
|-
| 1011
| Stop record
|
|-
| 1015
| Ghast warns
|
|-
| 1016
| Ghast shoots
|
|-
| 1017
| Ender dragon shoots
|
|-
| 1018
| Blaze shoots
|
|-
| 1019
| Zombie attacks wooden door
|
|-
| 1020
| Zombie attacks iron door
|
|-
| 1021
| Zombie breaks wooden 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 dies
|
|-
| 1029
| Anvil destroyed
|
|-
| 1030
| Anvil used
|
|-
| 1031
| Anvil lands
|
|-
| 1032
| Portal travel
|
|-
| 1033
| Chorus flower grows
|
|-
| 1034
| Chorus flower dies
|
|-
| 1035
| Brewing stand brews
|
|-
| 1038
| End portal created
|
|-
| 1039
| Phantom bites
|
|-
| 1040
| Zombie converts to drowned
|
|-
| 1041
| Husk converts to zombie by drowning
|
|-
| 1042
| Grindstone used
|
|-
| 1043
| Book page turned
|
|-
| 1044
| Smithing table used
|
|-
| 1045
| Pointed dripstone landing
|
|-
| 1046
| Lava dripping on cauldron from dripstone
|
|-
| 1047
| Water dripping on cauldron from dripstone
|
|-
| 1048
| Skeleton converts to stray
|
|-
| 1049
| Crafter successfully crafts item
|
|-
| 1050
| Crafter fails to craft item
|
|-
! colspan="3"| Particle
|-
| 1500
| Composter composts
|
|-
| 1501
| Lava converts block (either water to stone, or removes existing blocks such as torches)
|
|-
| 1502
| Redstone torch burns out
|
|-
| 1503
| Ender eye placed in end portal frame
|
|-
| 1504
| Fluid drips from dripstone
|
|-
| 1505
| Bone meal particles and sound
| How many particles to spawn.
|-
| 2000
| Dispenser activation smoke
| Direction, see below.
|-
| 2001
| Block break + block break sound
| Block state ID (see [[Minecraft Wiki:Projects/wiki.vg merge/Chunk Format#Block state registry|Chunk Format#Block state registry]]).
|-
| 2002
| Splash potion. Particle effect + glass break sound.
| RGB color as an integer (e.g. 8364543 for #7FA1FF).
|-
| 2003
| Eye of ender entity break animation — particles and sound
|
|-
| 2004
| Spawner spawns mob: smoke + flames
|
|-
| 2006
| Dragon breath
|
|-
| 2007
| Instant splash potion. Particle effect + glass break sound.
| RGB color as an integer (e.g. 8364543 for #7FA1FF).
|-
| 2008
| Ender dragon destroys block
|
|-
| 2009
| Wet sponge vaporizes
|
|-
| 2010
| Crafter activation smoke
| Direction, see below.
|-
| 2011
| Bee fertilizes plant
| How many particles to spawn.
|-
| 2012
| Turtle egg placed
| How many particles to spawn.
|-
| 2013
| Smash attack (mace)
| How many particles to spawn.
|-
| 3000
| End gateway spawns
|
|-
| 3001
| Ender dragon resurrected
|
|-
| 3002
| Electric spark
|
|-
| 3003
| Copper apply wax
|
|-
| 3004
| Copper remove wax
|
|-
| 3005
| Copper scrape oxidation
|
|-
| 3006
| Sculk charge
|
|-
| 3007
| Sculk shrieker shriek
|
|-
| 3008
| Block finished brushing
| Block state ID (see [[Minecraft Wiki:Projects/wiki.vg merge/Chunk Format#Block state registry|Chunk Format#Block state registry]])
|-
| 3009
| Sniffer egg cracks
| If 1, 3-6, if any other number, 1-3 particles will be spawned.
|-
| 3011
| Trial spawner spawns mob (at spawner)
|
|-
| 3012
| Trial spawner spawns mob (at spawn location)
|
|-
| 3013
| Trial spawner detects player
| Number of players nearby
|-
| 3014
| Trial spawner ejects item
|
|-
| 3015
| Vault activates
|
|-
| 3016
| Vault deactivates
|
|-
| 3017
| Vault ejects item
|
|-
| 3018
| Cobweb weaved
|
|-
| 3019
| Ominous trial spawner detects player
| Number of players nearby
|-
| 3020
| Trial spawner turns ominous
| If 0, the sound will be played at 0.3 volume. Otherwise, it is played at full volume.
|-
| 3021
| Ominous item spawner spawns item
|
|}

Smoke directions:

{| class="wikitable"
! ID
! Direction
|-
| 0
| Down
|-
| 1
| Up
|-
| 2
| North
|-
| 3
| South
|-
| 4
| West
|-
| 5
| East
|}

==== Particle ====

Displays the named particle

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="12"| ''protocol:''<br/><code>0x2A</code><br/><br/>''resource:''<br/><code>level_particles</code>
| rowspan="12"| Play
| rowspan="12"| Client
| Long Distance
| {{Type|Boolean}}
| If true, particle distance increases from 256 to 65536.
|-
| Always Visible
| {{Type|Boolean}}
| Whether this particle should always be visible.
|-
| X
| {{Type|Double}}
| X position of the particle.
|-
| Y
| {{Type|Double}}
| Y position of the particle.
|-
| Z
| {{Type|Double}}
| Z position of the particle.
|-
| Offset X
| {{Type|Float}}
| This is added to the X position after being multiplied by <code>random.nextGaussian()</code>.
|-
| Offset Y
| {{Type|Float}}
| This is added to the Y position after being multiplied by <code>random.nextGaussian()</code>.
|-
| Offset Z
| {{Type|Float}}
| This is added to the Z position after being multiplied by <code>random.nextGaussian()</code>.
|-
| Max Speed
| {{Type|Float}}
|
|-
| Particle Count
| {{Type|Int}}
| The number of particles to create.
|-
| Particle ID
| {{Type|VarInt}}
| The particle ID listed in [[Minecraft Wiki:Projects/wiki.vg merge/Particles|Particles]].
|-
| Data
| Varies
| Particle data as specified in [[Minecraft Wiki:Projects/wiki.vg merge/Particles|Particles]].
|}

==== Update Light ====

Updates light levels for a chunk. See [[Light]] for information on how lighting works in Minecraft.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x2B</code><br/><br/>''resource:''<br/><code>light_update</code>
| rowspan="3"| Play
| rowspan="3"| Client
| Chunk X
| {{Type|VarInt}}
| Chunk coordinate (block coordinate divided by 16, rounded down)
|-
| Chunk Z
| {{Type|VarInt}}
| Chunk coordinate (block coordinate divided by 16, rounded down)
|-
| Data
| {{Type|Light Data}}
|
|}

A bit will never be set in both the block light mask and the empty block light mask, though it may be present in neither of them (if the block light does not need to be updated for the corresponding chunk section). The same applies to the sky light mask and the empty sky light mask.

==== Login (play) ====

{{missing info|section|Although the number of portal cooldown ticks is included in this packet, the whole portal usage process is still dictated entirely by the server. What kind of effect does this value have on the client, if any?}}

See [[protocol encryption]] for information on logging in.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="22"| ''protocol:''<br/><code>0x2C</code><br/><br/>''resource:''<br/><code>login</code>
| rowspan="22"| Play
| rowspan="22"| Client
| Entity ID
| {{Type|Int}}
| The player's Entity ID (EID).
|-
| Is hardcore
| {{Type|Boolean}}
|
|-
| Dimension Names
| {{Type|Prefixed Array}} of {{Type|Identifier}}
| Identifiers for all dimensions on the server.
|-
| Max Players
| {{Type|VarInt}}
| Was once used by the client to draw the player list, but now is ignored.
|-
| View Distance
| {{Type|VarInt}}
| Render distance (2-32).
|-
| Simulation Distance
| {{Type|VarInt}}
| The distance that the client will process specific things, such as entities.
|-
| Reduced Debug Info
| {{Type|Boolean}}
| If true, a vanilla client shows reduced information on the [[debug screen]]. For servers in development, this should almost always be false.
|-
| Enable respawn screen
| {{Type|Boolean}}
| Set to false when the doImmediateRespawn gamerule is true.
|-
| Do limited crafting
| {{Type|Boolean}}
| Whether players can only craft recipes they have already unlocked. Currently unused by the client.
|-
| Dimension Type
| {{Type|VarInt}}
| The ID of the type of dimension in the <code>minecraft:dimension_type</code> registry, defined by the Registry Data packet.
|-
| Dimension Name
| {{Type|Identifier}}
| Name of the dimension being spawned into.
|-
| Hashed seed
| {{Type|Long}}
| First 8 bytes of the SHA-256 hash of the world's seed. Used client side for biome noise
|-
| Game mode
| {{Type|Unsigned Byte}}
| 0: Survival, 1: Creative, 2: Adventure, 3: Spectator.
|-
| Previous Game mode
| {{Type|Byte}}
| -1: Undefined (null), 0: Survival, 1: Creative, 2: Adventure, 3: Spectator. The previous game mode. Vanilla client uses this for the debug (F3 + N & F3 + F4) game mode switch. (More information needed)
|-
| Is Debug
| {{Type|Boolean}}
| True if the world is a [[debug mode]] world; debug mode worlds cannot be modified and have predefined blocks.
|-
| Is Flat
| {{Type|Boolean}}
| True if the world is a [[superflat]] world; flat worlds have different void fog and a horizon at y=0 instead of y=63.
|-
| Has death location
| {{Type|Boolean}}
| If true, then the next two fields are present.
|-
| Death dimension name
| {{Type|Optional}} {{Type|Identifier}}
| Name of the dimension the player died in.
|-
| Death location
| {{Type|Optional}} {{Type|Position}}
| The location that the player died at.
|-
| Portal cooldown
| {{Type|VarInt}}
| The number of ticks until the player can use the portal again.
|-
| Sea level
| {{Type|VarInt}}
|
|-
| Enforces Secure Chat
| {{Type|Boolean}}
|
|}

==== Map Data ====

Updates a rectangular area on a [[map]] item.

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="13"| ''protocol:''<br/><code>0x2D</code><br/><br/>''resource:''<br/><code>map_item_data</code>
| rowspan="13"| Play
| rowspan="13"| Client
| colspan="2"| Map ID
| colspan="2"| {{Type|VarInt}}
| Map ID of the map being modified
|-
| colspan="2"| Scale
| colspan="2"| {{Type|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"| Locked
| colspan="2"| {{Type|Boolean}}
| True if the map has been locked in a cartography table
|-
| rowspan="5"| Icon
| Type
| rowspan="5"| {{Type|Prefixed Optional}} {{Type|Prefixed Array}}
| {{Type|VarInt}} {{Type|Enum}}
| See below
|-
| X
| {{Type|Byte}}
| Map coordinates: -128 for furthest left, +127 for furthest right
|-
| Z
| {{Type|Byte}}
| Map coordinates: -128 for highest, +127 for lowest
|-
| Direction
| {{Type|Byte}}
| 0-15
|-
| Display Name
| {{Type|Prefixed Optional}} {{Type|Text Component}}
|
|-
| rowspan="5"| Color Patch
| Columns
| colspan="2"| {{Type|Unsigned Byte}}
| Number of columns updated
|-
| Rows
| colspan="2"| {{Type|Optional}} {{Type|Unsigned Byte}}
| Only if Columns is more than 0; number of rows updated
|-
| X
| colspan="2"| {{Type|Optional}} {{Type|Unsigned Byte}}
| Only if Columns is more than 0; x offset of the westernmost column
|-
| Z
| colspan="2"| {{Type|Optional}} {{Type|Unsigned Byte}}
| Only if Columns is more than 0; z offset of the northernmost row
|-
| Data
| colspan="2"| {{Type|Optional}} {{Type|Prefixed Array}} of {{Type|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&deg; (360/16).

Types are based off of rows and columns in <code>map_icons.png</code>:

{| class="wikitable"
|-
! 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
| Monument
|-
| 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
|-
| 27
| Desert Village
|-
| 28
| Plains Village
|-
| 29
| Savanna Village
|-
| 30
| Snowy Village
|-
| 31
| Taiga Village
|-
| 32
| Jungle Temple
|-
| 33
| Swamp Hut
|-
| 34
| Trial Chambers
|}

==== Merchant Offers ====

The list of trades a villager NPC is offering.

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="15"| ''protocol:''<br/><code>0x2E</code><br/><br/>''resource:''<br/><code>merchant_offers</code>
| rowspan="15"| Play
| rowspan="15"| Client
| colspan="2"| Window ID
| colspan="2"| {{Type|VarInt}}
| The ID of the window that is open; this is an int rather than a byte.
|-
| rowspan="10"| Trades
| Input item 1
| rowspan="10"| {{Type|Prefixed Array}}
| Trade Item
| See below. The first item the player has to supply for this villager trade. The count of the item stack is the default "price" of this trade.
|-
| Output item
| {{Type|Slot}}
| The item the player will receive from this villager trade.
|-
| Input item 2
| {{Type|Prefixed Optional}} Trade Item
| The second item the player has to supply for this villager trade.
|-
| Trade disabled
| {{Type|Boolean}}
| True if the trade is disabled; false if the trade is enabled.
|-
| Number of trade uses
| {{Type|Int}}
| Number of times the trade has been used so far. If equal to the maximum number of trades, the client will display a red X.
|-
| Maximum number of trade uses
| {{Type|Int}}
| Number of times this trade can be used before it's exhausted.
|-
| XP
| {{Type|Int}}
| Amount of XP the villager will earn each time the trade is used.
|-
| Special Price
| {{Type|Int}}
| Can be zero or negative. The number is added to the price when an item is discounted due to player reputation or other effects.
|-
| Price Multiplier
| {{Type|Float}}
| Can be low (0.05) or high (0.2). Determines how much demand, player reputation, and temporary effects will adjust the price.
|-
| Demand
| {{Type|Int}}
| If positive, causes the price to increase. Negative values seem to be treated the same as zero.
|-
| colspan="2"| Villager level
| colspan="2"| {{Type|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"| {{Type|VarInt}}
| Total experience for this villager (always 0 for the wandering trader).
|-
| colspan="2"| Is regular villager
| colspan="2"| {{Type|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"| {{Type|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.
|}

Trade Item:
{| class="wikitable"
! colspan="2"| Field Name
! colspan="2"| Field Type
! Meaning
|-
| colspan="2"| Item ID
| colspan="2"| {{Type|VarInt}}
| The [[Java Edition data values#Blocks|item ID]]. Item IDs are distinct from block IDs; see [[Minecraft Wiki:Projects/wiki.vg merge/Data Generators|Data Generators]] for more information.
|-
| colspan="2"| Item Count
| colspan="2"| {{Type|VarInt}}
| The item count.
|-
| rowspan="2"| Components
| Component type
| rowspan="2"| {{Type|Prefixed Array}}
| {{Type|VarInt}} {{Type|Enum}}
| The type of component. See [[Minecraft Wiki:Projects/wiki.vg merge/Slot_Data#Structured_components|Structured components]] for more detail.
|-
| Component data
| Varies
| The component-dependent data. See [[Minecraft Wiki:Projects/wiki.vg merge/Slot_Data#Structured_components|Structured components]] for more detail.
|-
|}

Modifiers can increase or decrease the number of items for the first input slot. The second input slot and the output slot never change the number of items. The number of items may never be less than 1, and never more than the stack size. If special price and demand are both zero, only the default price is displayed. If either is non-zero, then the adjusted price is displayed next to the crossed-out default price. The adjusted prices is calculated as follows:

Adjusted price = default price + floor(default price x multiplier x demand) + special price

[[File:1.14-merchant-slots.png|thumb|The merchant UI, for reference]]
{{-}}

==== Update Entity Position ====

This packet is sent by the server when an entity moves a small distance. The change in position is represented as a [[#Fixed-point numbers|fixed-point number]] with 12 fraction bits and 4 integer bits. As such, the maximum movement distance along each axis is 8 blocks in the negative direction, or 7.999755859375 blocks in the positive direction. If the movement exceeds these limits, [[#Teleport Entity|Teleport Entity]] should be sent instead.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="5"| ''protocol:''<br/><code>0x2F</code><br/><br/>''resource:''<br/><code>move_entity_pos</code>
| rowspan="5"| Play
| rowspan="5"| Client
| Entity ID
| {{Type|VarInt}}
|
|-
| Delta X
| {{Type|Short}}
| Change in X position as <code>currentX * 4096 - prevX * 4096</code>.
|-
| Delta Y
| {{Type|Short}}
| Change in Y position as <code>currentY * 4096 - prevY * 4096</code>.
|-
| Delta Z
| {{Type|Short}}
| Change in Z position as <code>currentZ * 4096 - prevZ * 4096</code>.
|-
| On Ground
| {{Type|Boolean}}
|
|}

==== Update Entity Position and Rotation ====

This packet is sent by the server when an entity rotates and moves. See [[#Update Entity Position]] for how the position is encoded.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="7"| ''protocol:''<br/><code>0x30</code><br/><br/>''resource:''<br/><code>move_entity_pos_rot</code>
| rowspan="7"| Play
| rowspan="7"| Client
| Entity ID
| {{Type|VarInt}}
|
|-
| Delta X
| {{Type|Short}}
| Change in X position as <code>currentX * 4096 - prevX * 4096</code>.
|-
| Delta Y
| {{Type|Short}}
| Change in Y position as <code>currentY * 4096 - prevY * 4096</code>.
|-
| Delta Z
| {{Type|Short}}
| Change in Z position as <code>currentZ * 4096 - prevZ * 4096</code>.
|-
| Yaw
| {{Type|Angle}}
| New angle, not a delta.
|-
| Pitch
| {{Type|Angle}}
| New angle, not a delta.
|-
| On Ground
| {{Type|Boolean}}
|
|}

==== Move Minecart Along Track ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! colspan="2"| Notes
|-
| rowspan="10"| ''protocol:''<br/><code>0x31</code><br/><br/>''resource:''<br/><code>move_minecart_along_track</code>
| rowspan="10"| Play
| rowspan="10"| Client
| colspan="2"| Entity ID
| colspan="2"| {{Type|VarInt}}
|
|-
| rowspan="9"| Steps
| X
| rowspan="9"| {{Type|Prefixed Array}}
| {{Type|Double}}
|
|-
| Y
| {{Type|Double}}
|
|-
| Z
| {{Type|Double}}
|
|-
| Velocity X
| {{Type|Double}}
|
|-
| Velocity Y
| {{Type|Double}}
|
|-
| Velocity Z
| {{Type|Double}}
|
|-
| Yaw
| {{Type|Angle}}
|
|-
| Pitch
| {{Type|Angle}}
|
|-
| Weight
| {{Type|Float}}
|}
|}


==== Update Entity Rotation ====
{{anchor|0x23}}

=== Entity Head Look (0x23) ===
This packet is sent by the server when an entity rotates.
''Server to Client''

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="4"| ''protocol:''<br/><code>0x32</code><br/><br/>''resource:''<br/><code>move_entity_rot</code>
| rowspan="4"| Play
| rowspan="4"| Client
| Entity ID
| {{Type|VarInt}}
|
|-
| Yaw
| {{Type|Angle}}
| New angle, not a delta.
|-
| Pitch
| {{Type|Angle}}
| New angle, not a delta.
|-
| On Ground
| {{Type|Boolean}}
|
|}

==== Move Vehicle ====

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"| ''protocol:''<br/><code>0x33</code><br/><br/>''resource:''<br/><code>move_vehicle</code>
| rowspan="5"| Play
| rowspan="5"| Client
| X
| {{Type|Double}}
| Absolute position (X coordinate).
|-
| Y
| {{Type|Double}}
| Absolute position (Y coordinate).
|-
| Z
| {{Type|Double}}
| Absolute position (Z coordinate).
|-
| Yaw
| {{Type|Float}}
| Absolute rotation on the vertical axis, in degrees.
|-
| Pitch
| {{Type|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"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x34</code><br/><br/>''resource:''<br/><code>open_book</code>
| Play
| Client
| Hand
| {{Type|VarInt}} {{Type|Enum}}
| 0: Main hand, 1: Off hand .
|}

==== Open Screen ====

This is sent to the client when it should open an inventory, such as a chest, workbench, furnace, or other container. Resending this packet with already existing window id, will update the window title and window type without closing the window.

This message is not sent to clients opening their own inventory, nor do clients inform the server in any way when doing so. From the server's perspective, the inventory is always "open" whenever no other windows are.

For horses, use [[#Open Horse Screen|Open Horse Screen]].

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x35</code><br/><br/>''resource:''<br/><code>open_screen</code>
| rowspan="3"| Play
| rowspan="3"| Client
| Window ID
| {{Type|VarInt}}
| An identifier for the window to be displayed. vanilla server implementation is a counter, starting at 1. There can only be one window at a time; this is only used to ignore outdated packets targeting already-closed windows. Note also that the Window ID field in most other packets is only a single byte, and indeed, the vanilla server wraps around after 100.
|-
| Window Type
| {{Type|VarInt}}
| The window type to use for display. Contained in the <code>minecraft:menu</code> registry; see [[Minecraft Wiki:Projects/wiki.vg merge/Inventory|Inventory]] for the different values.
|-
| Window Title
| {{Type|Text Component}}
| The title of the window.
|}

==== Open Sign Editor ====

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 Update|Block Update]] first.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2" | ''protocol:''<br/><code>0x36</code><br/><br/>''resource:''<br/><code>open_sign_editor</code>
| rowspan="2" | Play
| rowspan="2" | Client
| Location
| {{Type|Position}}
|
|-
| Is Front Text
| {{Type|Boolean}}
| Whether the opened editor is for the front or on the back of the sign
|}

==== Ping (play) ====

Packet is not used by the vanilla server. When sent to the client, client responds with a [[#Pong (play)|Pong]] packet with the same id.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x37</code><br/><br/>''resource:''<br/><code>ping</code>
| Play
| Client
| ID
| {{Type|Int}}
|
|}

==== Ping Response (play) ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x38</code><br/><br/>''resource:''<br/><code>pong_response</code>
| Play
| Client
| Payload
| {{Type|Long}}
| Should be the same as sent by the client.
|}

==== Place Ghost Recipe ====

Response to the serverbound packet ([[#Place Recipe|Place Recipe]]), with the same recipe ID. Appears to be used to notify the UI.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x39</code><br/><br/>''resource:''<br/><code>place_ghost_recipe</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Window ID
| {{Type|VarInt}}
|
|-
| Recipe Display
| {{Type|Recipe Display}}
|
|}

==== Player Abilities (clientbound) ====

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

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x3A</code><br/><br/>''resource:''<br/><code>player_abilities</code>
| rowspan="3"| Play
| rowspan="3"| Client
| Flags
| {{Type|Byte}}
| Bit field, see below.
|-
| Flying Speed
| {{Type|Float}}
| 0.05 by default.
|-
| Field of View Modifier
| {{Type|Float}}
| Modifies the field of view, like a speed potion. A vanilla server will use the same value as the movement speed sent in the [[#Update Attributes|Update Attributes]] packet, which defaults to 0.1 for players.
|}

About the flags:

{| class="wikitable"
|-
! Field
! Bit
|-
| Invulnerable
| 0x01
|-
| Flying
| 0x02
|-
| Allow Flying
| 0x04
|-
| Creative Mode (Instant Break)
| 0x08
|}

If Flying is set but Allow Flying is unset, the player is unable to stop flying.

==== Player Chat Message ====

{{Main|Chat}}

Sends the client a chat message from a player.

Currently a lot is unknown about this packet, blank descriptions are for those that are unknown

{| class="wikitable"
! Packet ID
! State
! Bound To
! Sector
! colspan="2"| Field Name
! Field Type
! Notes
|-
| rowspan="14"| ''protocol:''<br/><code>0x3B</code><br/><br/>''resource:''<br/><code>player_chat</code>
| rowspan="14"| Play
| rowspan="14"| Client
| rowspan="3"| Header
| colspan="2"| Sender
| {{Type|UUID}}
| Used by the vanilla client for the disableChat launch option. Setting both longs to 0 will always display the message regardless of the setting.
|-
| colspan="2"| Index
| {{Type|VarInt}}
|
|-
| colspan="2"| Message Signature bytes
| {{Type|Prefixed Optional}} {{Type|Byte Array}} (256)
| Cryptography, the signature consists of the Sender UUID, Session UUID from the [[#Player Session|Player Session]] packet, Index, Salt, Timestamp in epoch seconds, the length of the original chat content, the original content itself, the length of Previous Messages, and all of the Previous message signatures. These values are hashed with [https://en.wikipedia.org/wiki/SHA-2 SHA-256] and signed using the [https://en.wikipedia.org/wiki/RSA_(cryptosystem) RSA] cryptosystem. Modifying any of these values in the packet will cause this signature to fail. This buffer is always 256 bytes long and it is not length-prefixed.
|-
| rowspan="3"| Body
| colspan="2"| Message
| {{Type|String}} (256)
| Raw (optionally) signed sent message content.
This is used as the <code>content</code> parameter when formatting the message on the client.
|-
| colspan="2"| Timestamp
| {{Type|Long}}
| Represents the time the message was signed as milliseconds since the [https://en.wikipedia.org/wiki/Unix_time epoch], used to check if the message was received within 2 minutes of it being sent.
|-
| colspan="2"| Salt
| {{Type|Long}}
| Cryptography, used for validating the message signature.
|-
| rowspan="2"| {{Type|Prefixed Array}} (20)
| Message ID
| {{Type|VarInt}}
| The message Id + 1, used for validating message signature. The next field is present only when value of this field is equal to 0.
|-
| Signature
| {{Type|Optional}} {{Type|Byte Array}} (256)
| The previous message's signature. Contains the same type of data as <code>Message Signature bytes</code> (256 bytes) above. Not length-prefxied.
|-
| rowspan="3"| Other
| colspan="2"| Unsigned Content
| {{Type|Prefixed Optional}} {{Type|Text Component}}
|
|-
| colspan="2"| Filter Type
| {{Type|VarInt}} {{Type|Enum}}
| If the message has been filtered
|-
| colspan="2"| Filter Type Bits
| {{Type|Optional}} {{Type|BitSet}}
| Only present if the Filter Type is Partially Filtered. Specifies the indexes at which characters in the original message string should be replaced with the <code>#</code> symbol (i.e. filtered) by the vanilla client
|-
| rowspan="3"| Chat Formatting
| colspan="2"| Chat Type
| {{Type|VarInt}}
| The type of chat in the <code>minecraft:chat_type</code> registry, defined by the [[Java Edition protocol#Registry_Data|Registry Data]] packet. This should not be 0, meaning it is likely index+1
|-
| colspan="2"| Sender Name
| {{Type|Text Component}}
| The name of the one sending the message, usually the sender's display name.
This is used as the <code>sender</code> parameter when formatting the message on the client.
|-
| colspan="2"| Target Name
| {{Type|Prefixed Optional}} {{Type|Text Component}}
| The name of the one receiving the message, usually the receiver's display name.
This is used as the <code>target</code> parameter when formatting the message on the client.
|}
[[File:MinecraftChat.drawio4.png|thumb|Player Chat Handling Logic]]

Filter Types:

The filter type mask should NOT be specified unless partially filtered is selected

{| class="wikitable"
! ID
! Name
! Description
|-
| 0
| PASS_THROUGH
| Message is not filtered at all
|-
| 1
| FULLY_FILTERED
| Message is fully filtered
|-
| 2
| PARTIALLY_FILTERED
| Only some characters in the message are filtered
|}

==== End Combat ====

Unused by the vanilla client. This data was once used for twitch.tv metadata circa 1.8.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x3C</code><br/><br/>''resource:''<br/><code>player_combat_end</code>
| rowspan="1"| Play
| rowspan="1"| Client
| Duration
| {{Type|VarInt}}
| Length of the combat in ticks.
|}

==== Enter Combat ====

Unused by the vanilla client. This data was once used for twitch.tv metadata circa 1.8.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x3D</code><br/><br/>''resource:''<br/><code>player_combat_enter</code>
| rowspan="1"| Play
| rowspan="1"| Client
| colspan="3"| ''no fields''
|}

==== Combat Death ====

Used to send a respawn screen.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x3E</code><br/><br/>''resource:''<br/><code>player_combat_kill</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Player ID
| {{Type|VarInt}}
| Entity ID of the player that died (should match the client's entity ID).
|-
| Message
| {{Type|Text Component}}
| The death message.
|}

==== Player Info Remove ====

Used by the server to remove players from the player list.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x3F</code><br/><br/>''resource:''<br/><code>player_info_remove</code>
| Play
| Client
| UUIDs
| {{Type|Prefixed Array}} of {{Type|UUID}}
| UUIDs of players to remove.
|}

==== Player Info Update ====

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

{{Warning|The EnumSet type is only used here and it is currently undocumented}}

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x40</code><br/><br/>''resource:''<br/><code>player_info_update</code>
| rowspan="3"| Play
| rowspan="3"| Client
| colspan="2"| Actions
| colspan="2"| {{Type|EnumSet}}
| Determines what actions are present.
|-
| rowspan="2" | Players
| UUID
| rowspan="2" | {{Type|Prefixed Array}}
| {{Type|UUID}}
| The player UUID
|-
| Player Actions
| {{Type|Array}} of [[#player-info:player-actions|Player&nbsp;Actions]]
| The length of this array is determined by the number of [[#player-info:player-actions|Player Actions]] that give a non-zero value when applying its mask to the actions flag. For example given the decimal number 5, binary 00000101. The masks 0x01 and 0x04 would return a non-zero value, meaning the Player Actions array would include two actions: Add Player and Update Game Mode.
|}

{| class="wikitable"
|+ id="player-info:player-actions" | Player Actions
! Action
! Mask
! colspan="2" | Field Name
! colspan="2" | Type
! Notes
|-
| rowspan="4" | Add Player
| rowspan="4" | 0x01
| colspan="2" | Name
| colspan="2" | {{Type|String}} (16)
|-
| rowspan="3" | Property
| Name
| rowspan="3"| {{Type|Prefixed Array}} (16)
| {{Type|String}} (64)
|
|-
| Value
| {{Type|String}} (32767)
|
|-
| Signature
| {{Type|Prefixed Optional}} {{Type|String}} (1024)
|
|-
| rowspan="4" | Initialize Chat
| rowspan="4" | 0x02
| rowspan="4" | Data
| Chat session ID
| rowspan="4" | {{Type|Prefixed Optional}}
| {{Type|UUID}}
|
|-
| Public key expiry time
| {{Type|Long}}
| Key expiry time, as a UNIX timestamp in milliseconds. Only sent if Has Signature Data is true.
|-
| Encoded public key
| {{Type|Prefixed Array}} (512) of {{Type|Byte}}
| The player's public key, in bytes. Only sent if Has Signature Data is true.
|-
| Public key signature
| {{Type|Prefixed Array}} (4096) of {{Type|Byte}}
| The public key's digital signature. Only sent if Has Signature Data is true.
|-
| Update Game Mode
| 0x04
| colspan="2" | Game Mode
| colspan="2" | {{Type|VarInt}}
|-
| Update Listed
| 0x08
| colspan="2" | Listed
| colspan="2" | {{Type|Boolean}}
| Whether the player should be listed on the player list.
|-
| Update Latency
| 0x10
| colspan="2" | Ping
| colspan="2" | {{Type|VarInt}}
| Measured in milliseconds.
|-
| Update Display Name
| 0x20
| colspan="2" | Display Name
| colspan="2" | {{Type|Prefixed Optional}} {{Type|Text Component}}
| Only sent if Has Display Name is true.
|-
| Update List Priority
| 0x40
| colspan="2" | Priority
| colspan="2" | {{Type|VarInt}}
| See below.
|-
| Update Hat
| 0x80
| colspan="2" | Visible
| colspan="2" | {{Type|Boolean}}
| Whether the player's hat skin layer is shown.
|}

The properties included in this packet are the same as in [[#Login Success|Login Success]], for the current player.

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.

The order of players in the player list is determined as follows:
* Players with higher priorities are sorted before those with lower priorities.
* Among players of equal priorities, spectators are sorted after non-spectators.
* Within each of those groups, players are sorted into teams. The teams are ordered case-sensitively by team name in ascending order. Players with no team are listed first.
* The players of each team (and non-team) are sorted case-insensitively by name in ascending order.

==== Look At ====

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

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="8"| ''protocol:''<br/><code>0x41</code><br/><br/>''resource:''<br/><code>player_look_at</code>
| rowspan="8"| Play
| rowspan="8"| Client
|-
| Feet/eyes
| {{Type|VarInt}} {{Type|Enum}}
| Values are feet=0, eyes=1. If set to eyes, aims using the head position; otherwise aims using the feet position.
|-
| Target x
| {{Type|Double}}
| x coordinate of the point to face towards.
|-
| Target y
| {{Type|Double}}
| y coordinate of the point to face towards.
|-
| Target z
| {{Type|Double}}
| z coordinate of the point to face towards.
|-
| Is entity
| {{Type|Boolean}}
| If true, additional information about an entity is provided.
|-
| Entity ID
| {{Type|Optional}} {{Type|VarInt}}
| Only if is entity is true &mdash; the entity to face towards.
|-
| Entity feet/eyes
| {{Type|Optional}} {{Type|VarInt}} {{Type|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.

==== Synchronize Player Position ====

Teleports the client, e.g. during login, when using an ender pearl, in response to invalid move packets, etc.

Due to latency, the server may receive outdated movement packets sent before the client was aware of the teleport. To account for this, the server ignores all movement packets from the client until a [[#Confirm Teleportation|Confirm Teleportation]] packet with an ID matching the one sent in the teleport packet is received.

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 (see [https://bugs.mojang.com/browse/MC-90097 MC-90097]).

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

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="10"| ''protocol:''<br/><code>0x42</code><br/><br/>''resource:''<br/><code>player_position</code>
| rowspan="10"| Play
| rowspan="10"| Client
| Teleport ID
| {{Type|VarInt}}
| Client should confirm this packet with [[#Confirm Teleportation|Confirm Teleportation]] containing the same Teleport ID.
|-
| X
| {{Type|Double}}
| Absolute or relative position, depending on Flags.
|-
| Y
| {{Type|Double}}
| Absolute or relative position, depending on Flags.
|-
| Z
| {{Type|Double}}
| Absolute or relative position, depending on Flags.
|-
| Velocity X
| {{Type|Double}}
|
|-
| Velocity Y
| {{Type|Double}}
|
|-
| Velocity Z
| {{Type|Double}}
|
|-
| Yaw
| {{Type|Float}}
| Absolute or relative rotation on the X axis, in degrees.
|-
| Pitch
| {{Type|Float}}
| Absolute or relative rotation on the Y axis, in degrees.
|-
| Flags
| {{Type|Teleport Flags}}
|
|}

==== Player Rotation ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x43</code><br/><br/>''resource:''<br/><code>player_rotation</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Yaw
| {{Type|Float}}
| Rotation on the X axis, in degrees.
|-
| Pitch
| {{Type|Float}}
| Rotation on the Y axis, in degrees.
|}

==== Recipe Book Add ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! colspan="2"| Notes
|-
| rowspan="7"| ''protocol:''<br/><code>0x44</code><br/><br/>''resource:''<br/><code>recipe_book_add</code>
| rowspan="7"| Play
| rowspan="7"| Client
| rowspan="6"| Recipes
| Recipe ID
| rowspan="6"| {{Type|Prefixed Array}}
| {{Type|VarInt}}
| ID to assign to the recipe.
|-
| Display
| {{Type|Recipe Display}}
|
|-
| Group ID
| {{Type|VarInt}}
|
|-
| Category ID
| {{Type|VarInt}}
| ID in the <code>minecraft:recipe_book_category</code> registry.
|-
| Ingredients
| {{Type|Prefixed Optional}} {{Type|Prefixed Array}} of {{Type|ID Set}}
| IDs in the <code>minecraft:item</code> registry, or an inline definition.
|-
| Flags
| {{Type|Byte}}
| 0x01: show notification; 0x02: highlight as new
|-
| colspan="2"| Replace
| colspan="2"| {{Type|Boolean}}
| Replace or Add to known recipes
|}

==== Recipe Book Remove ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x45</code><br/><br/>''resource:''<br/><code>recipe_book_remove</code>
| Play
| Client
| Recipes
| {{Type|Prefixed Array}} of {{Type|VarInt}}
| IDs of recipes to remove.
|}

==== Recipe Book Settings ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="8"| ''protocol:''<br/><code>0x46</code><br/><br/>''resource:''<br/><code>recipe_book_settings</code>
| rowspan="8"| Play
| rowspan="8"| Client
| Crafting Recipe Book Open
| {{Type|Boolean}}
| If true, then the crafting recipe book will be open when the player opens its inventory.
|-
| Crafting Recipe Book Filter Active
| {{Type|Boolean}}
| If true, then the filtering option is active when the players opens its inventory.
|-
| Smelting Recipe Book Open
| {{Type|Boolean}}
| If true, then the smelting recipe book will be open when the player opens its inventory.
|-
| Smelting Recipe Book Filter Active
| {{Type|Boolean}}
| If true, then the filtering option is active when the players opens its inventory.
|-
| Blast Furnace Recipe Book Open
| {{Type|Boolean}}
| If true, then the blast furnace recipe book will be open when the player opens its inventory.
|-
| Blast Furnace Recipe Book Filter Active
| {{Type|Boolean}}
| If true, then the filtering option is active when the players opens its inventory.
|-
| Smoker Recipe Book Open
| {{Type|Boolean}}
| If true, then the smoker recipe book will be open when the player opens its inventory.
|-
| Smoker Recipe Book Filter Active
| {{Type|Boolean}}
| If true, then the filtering option is active when the players opens its inventory.
|}

==== Remove Entities ====

Sent by the server when an entity is to be destroyed on the client.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x47</code><br/><br/>''resource:''<br/><code>remove_entities</code>
| Play
| Client
| Entity IDs
| {{Type|Prefixed Array}} of {{Type|VarInt}}
| The list of entities to destroy.
|}

==== Remove Entity Effect ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x48</code><br/><br/>''resource:''<br/><code>remove_mob_effect</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Entity ID
| {{Type|VarInt}}
|
|-
| Effect ID
| {{Type|VarInt}}
| See [[Status effect#Effect list|this table]].
|}

==== Reset Score ====

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

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x49</code><br/><br/>''resource:''<br/><code>reset_score</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Entity Name
| {{Type|String}} (32767)
| The entity whose score this is. For players, this is their username; for other entities, it is their UUID.
|-
| Objective Name
| {{Type|Prefixed Optional}} {{Type|String}} (32767)
| The name of the objective the score belongs to.
|}

==== Remove Resource Pack (play) ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x4A</code><br/><br/>''resource:''<br/><code>resource_pack_pop</code>
| Play
| Client
| UUID
| {{Type|Optional}} {{Type|UUID}}
| The UUID of the resource pack to be removed.
|}

==== Add Resource Pack (play) ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="5"| ''protocol:''<br/><code>0x4B</code><br/><br/>''resource:''<br/><code>resource_pack_push</code>
| rowspan="5"| Play
| rowspan="5"| Client
| UUID
| {{Type|UUID}}
| The unique identifier of the resource pack.
|-
| URL
| {{Type|String}} (32767)
| The URL to the resource pack.
|-
| Hash
| {{Type|String}} (40)
| A 40 character hexadecimal, case-insensitive [[wikipedia:SHA-1|SHA-1]] hash of the resource pack file.<br />If it's not a 40 character hexadecimal string, the client will not use it for hash verification and likely waste bandwidth.
|-
| Forced
| {{Type|Boolean}}
| The vanilla client will be forced to use the resource pack from the server. If they decline they will be kicked from the server.
|-
| Prompt Message
| {{Type|Prefixed Optional}} {{Type|Text Component}}
| This is shown in the prompt making the client accept or decline the resource pack.
|}

==== Respawn ====

{{missing info|section|Although the number of portal cooldown ticks is included in this packet, the whole portal usage process is still dictated entirely by the server. What kind of effect does this value have on the client, if any?}}

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
|-
| rowspan="13"| ''protocol:''<br/><code>0x4C</code><br/><br/>''resource:''<br/><code>respawn</code>
| rowspan="13"| Play
| rowspan="13"| Client
| Dimension Type
| {{Type|VarInt}}
| The ID of type of dimension in the <code>minecraft:dimension_type</code> registry, defined by the [[Java Edition protocol#Registry_Data|Registry Data]] packet.
|-
| Dimension Name
| {{Type|Identifier}}
| Name of the dimension being spawned into.
|-
| Hashed seed
| {{Type|Long}}
| First 8 bytes of the SHA-256 hash of the world's seed. Used client side for biome noise
|-
| Game mode
| {{Type|Unsigned Byte}}
| 0: Survival, 1: Creative, 2: Adventure, 3: Spectator.
|-
| Previous Game mode
| {{Type|Byte}}
| -1: Undefined (null), 0: Survival, 1: Creative, 2: Adventure, 3: Spectator. The previous game mode. Vanilla client uses this for the debug (F3 + N & F3 + F4) game mode switch. (More information needed)
|-
| Is Debug
| {{Type|Boolean}}
| True if the world is a [[debug mode]] world; debug mode worlds cannot be modified and have predefined blocks.
|-
| Is Flat
| {{Type|Boolean}}
| True if the world is a [[superflat]] world; flat worlds have different void fog and a horizon at y=0 instead of y=63.
|-
| Has death location
| {{Type|Boolean}}
| If true, then the next two fields are present.
|-
| Death dimension Name
| {{Type|Optional}} {{Type|Identifier}}
| Name of the dimension the player died in.
|-
| Death location
| {{Type|Optional}} {{Type|Position}}
| The location that the player died at.
|-
| Portal cooldown
| {{Type|VarInt}}
| The number of ticks until the player can use the portal again.
|-
| Sea level
| {{Type|VarInt}}
|
|-
| Data kept
| {{Type|Byte}}
| Bit mask. 0x01: Keep attributes, 0x02: Keep metadata. Tells which data should be kept on the client side once the player has respawned.
In the vanilla implementation, this is context dependent:
* normal respawns (after death) keep no data;
* exiting the end poem/credits keeps the attributes;
* other dimension changes (portals or teleports) keep all data.
|}

{{warning|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).

Before 1.16, 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.}}

==== Set Head Rotation ====


Changes the direction an entity's head is facing.
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"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x4D</code><br/><br/>''resource:''<br/><code>rotate_head</code>
| rowspan="2" | 0x23
| rowspan="2"| Play
| Entity ID
| rowspan="2"| Client
| int
| Entity ID
|
| {{Type|VarInt}}
|
|-
|
|-
| Head Yaw
| Head Yaw
| byte
| {{Type|Angle}}
|
| New angle, not a delta.
| Head yaw in steps of 2p/256
|-
|}
| Total Size:
| colspan="4" | 6 bytes
|}


==== Update Section Blocks ====
{{anchor|0x26}}

=== Entity Status (0x26) ===
Fired whenever 2 or more blocks are changed within the same chunk on the same tick.
''Server to Client''

{{Warning|Changing blocks in chunks not loaded by the client is unsafe (see note on [[#Block Update|Block Update]]).}}


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x4E</code><br/><br/>''resource:''<br/><code>section_blocks_update</code>
| rowspan="2" | 0x26
| rowspan="2"| Play
| Entity ID
| rowspan="2"| Client
| int
| Chunk section position
| 34353
| {{Type|Long}}
|
| Chunk section coordinate (encoded chunk x and z with each 22 bits, and section y with 20 bits, from left to right).
|-
|-
| Entity Status
| byte
| Blocks
| {{Type|Prefixed Array}} of {{Type|VarLong}}
| 0x03
| Each entry is composed of the block state id, shifted left by 12, and the relative block position in the chunk section (4 bits for x, z, and y, from left to right).
| See below
|-
|}

| Total Size:
Chunk section position is encoded:
| colspan="4" | 6 bytes
<syntaxhighlight lang="java">
|}
((sectionX & 0x3FFFFF) << 42) | (sectionY & 0xFFFFF) | ((sectionZ & 0x3FFFFF) << 20);
</syntaxhighlight>
and decoded:
<syntaxhighlight lang="java">
sectionX = long >> 42;
sectionY = long << 44 >> 44;
sectionZ = long << 22 >> 42;
</syntaxhighlight>

Blocks are encoded:
<syntaxhighlight lang="java">
blockStateId << 12 | (blockLocalX << 8 | blockLocalZ << 4 | blockLocalY)
//Uses the local position of the given block position relative to its respective chunk section
</syntaxhighlight>
and decoded:
<syntaxhighlight lang="java">
blockStateId = long >> 12;
blockLocalX = (long >> 8) & 0xF;
blockLocalY = long & 0xF;
blockLocalZ = (long >> 4) & 0xF;
</syntaxhighlight>

==== Select Advancements 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"
{| class="wikitable"
! Packet ID
|-
! State
! Entity Status
! Bound To
! Meaning
! Field Name
|-
! Field Type
| 2
! Notes
| Entity hurt
|-
|-
| ''protocol:''<br/><code>0x4F</code><br/><br/>''resource:''<br/><code>select_advancements_tab</code>
| 3
| Play
| Entity dead
| Client
|-
| Identifier
| 6
| {{Type|Prefixed Optional}} {{Type|Identifier}}
| Wolf taming
| See below.
|-
| 7
|}
| Wolf tamed
|-
| 8
| Wolf shaking water off itself
|-
| 9
| (of self) Eating accepted by server
|-
| 10
| Sheep eating grass
|-
| 11
| Iron Golem handing over a rose
|-
| 12
| Spawn "heart" particles near a villager
|-
| 13
| Spawn particles indicating that a villager is angry and seeking revenge
|-
| 14
| Spawn happy particles near a villager
|-
| 15
| Spawn a "magic" particle near the Witch
|-
| 16
| Zombie converting into a villager by shaking violently
|-
| 17
| A firework exploding
|-
|}


The {{Type|Identifier}} must be one of the following if no custom data pack is loaded:
{{anchor|0x27}}


{| class="wikitable"
=== Attach Entity (0x27) ===
! Identifier
''Server to Client''
|-
| 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.
This packet is sent when a player has been attached to an entity (e.g. Minecart)

==== Server Data ====


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x50</code><br/><br/>''resource:''<br/><code>server_data</code>
| rowspan="3" | 0x27
| rowspan="2"| Play
| Entity ID
| rowspan="2"| Client
| int
| MOTD
| <code>1298</code>
| {{Type|Text Component}}
| The player entity ID being attached
|-
|
|-
| Vehicle ID
| int
| Icon
| {{Type|Prefixed Optional}} {{Type|Prefixed Array}} of {{Type|Byte}}
| <code>1805</code>
| Icon bytes in the PNG format.
| The vehicle entity ID attached to (-1 for unattaching)
|-
|}
| '''Leash'''
| unsigned byte
| <code>0</code>
| If set to 1, leashes the entity to the vehicle
|-
| Total Size:
| colspan="4" | 10 bytes
|}


==== Set Action Bar Text ====
{{anchor|0x28}}


Displays a message above the hotbar. Equivalent to [[#System Chat Message|System Chat Message]] with Overlay set to true, except that [[Minecraft Wiki:Projects/wiki.vg merge/Chat#Social Interactions (blocking)|chat message blocking]] isn't performed. Used by the vanilla server only to implement the <code>/title</code> command.
=== Entity Metadata (0x28) ===
''Server to Client''


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x51</code><br/><br/>''resource:''<br/><code>set_action_bar_text</code>
| rowspan="2" | 0x28
| rowspan="1"| Play
| Entity ID
| rowspan="1"| Client
| int
| Action bar text
| <code>0x00000326</code>
| {{Type|Text Component}}
| Unique entity ID to update.
|-
|}
| Entity Metadata
| [[Entities#Entity_Metadata_Format|Metadata]]
| <code>0x00 0x01 0x7F</code>
| Metadata varies by entity. See [[Entities]]
|-
| Total Size:
| colspan="4" | 5 bytes + Metadata
|}


==== Set Border Center ====


{| class="wikitable"
{{anchor|0x29}}
! Packet ID
=== Entity Effect (0x29) ===
! State
''Server to Client''
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x52</code><br/><br/>''resource:''<br/><code>set_border_center</code>
| rowspan="2"| Play
| rowspan="2"| Client
| X
| {{Type|Double}}
|
|-
| Z
| {{Type|Double}}
|
|}

==== Set Border Lerp Size ====


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="3"| ''protocol:''<br/><code>0x53</code><br/><br/>''resource:''<br/><code>set_border_lerp_size</code>
| rowspan="4" | 0x29
| rowspan="3"| Play
| Entity ID
| rowspan="3"| Client
| int
| Old Diameter
| <code>14</code>
| {{Type|Double}}
| Entity ID of a player
| Current length of a single side of the world border, in meters.
|-
|-
| Effect ID
| New Diameter
| byte
| {{Type|Double}}
| <code>17</code>
| Target length of a single side of the world border, in meters.
| See [http://www.minecraftwiki.net/wiki/Potion_effect#Parameters here]
|-
|-
| Speed
| Amplifier
| {{Type|VarLong}}
| byte
| Number of real-time ''milli''seconds until New Diameter is reached. It appears that vanilla 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.
| <code>0</code>
|
|}
|-
| Duration
| short
| <code>64</code>
|
|-
| Total Size:
| colspan="4" | 9 bytes
|}


==== Set Border Size ====
{{anchor|0x2A}}
=== Remove Entity Effect (0x2A) ===
''Server to Client''


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x54</code><br/><br/>''resource:''<br/><code>set_border_size</code>
| rowspan="2" | 0x2a
| rowspan="1"| Play
| Entity ID
| rowspan="1"| Client
| int
| Diameter
|
| {{Type|Double}}
| Entity ID of a player
| Length of a single side of the world border, in meters.
|-
|}
| Effect ID
| byte
| <code>17</code>
| See [http://www.minecraftwiki.net/wiki/Potion_effect#Parameters here]
|-
| Total Size:
| colspan="4" | 6 bytes
|}


==== Set Border Warning Delay ====


{| class="wikitable"
{{anchor|0x2B}}
! Packet ID
=== Set Experience (0x2B) ===
! State
''Server to Client''
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x55</code><br/><br/>''resource:''<br/><code>set_border_warning_delay</code>
| rowspan="1"| Play
| rowspan="1"| Client
| Warning Time
| {{Type|VarInt}}
| In seconds as set by <code>/worldborder warning time</code>.
|}

==== Set Border Warning Distance ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x56</code><br/><br/>''resource:''<br/><code>set_border_warning_distance</code>
| rowspan="1"| Play
| rowspan="1"| Client
| Warning Blocks
| {{Type|VarInt}}
| In meters.
|}

==== Set 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 vanilla 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
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x57</code><br/><br/>''resource:''<br/><code>set_camera</code>
| Play
| Client
| Camera ID
| {{Type|VarInt}}
| ID of the entity to set the client's camera to.
|}

The vanilla client also loads certain shaders for given entities:

* 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

==== Set Center Chunk ====

Sets the center position of the client's chunk loading area. The area is square-shaped, spanning 2 &times; server view distance + 7 chunks on both axes (width, not radius!). Since the area's width is always an odd number, there is no ambiguity as to which chunk is the center.

The vanilla client ignores attempts to send chunks located outside the loading area, and immediately unloads any existing chunks no longer inside it.

The center chunk is normally the chunk the player is in, but apart from the implications on chunk loading, the (vanilla) client takes no issue with this not being the case. Indeed, as long as chunks are sent only within the default loading area centered on the world origin, it is not necessary to send this packet at all. This may be useful for servers with small bounded worlds, such as minigames, since it ensures chunks never need to be resent after the client has joined, saving on bandwidth.

The vanilla server sends this packet 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"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x58</code><br/><br/>''resource:''<br/><code>set_chunk_cache_center</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Chunk X
| {{Type|VarInt}}
| Chunk X coordinate of the loading area center.
|-
| Chunk Z
| {{Type|VarInt}}
| Chunk Z coordinate of the loading area center.
|}

==== Set Render Distance ====

Sent by the integrated singleplayer server when changing render distance. This packet is sent by the server when the client reappears in the overworld after leaving the end.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x59</code><br/><br/>''resource:''<br/><code>set_chunk_cache_radius</code>
| Play
| Client
| View Distance
| {{Type|VarInt}}
| Render distance (2-32).
|}

==== Set Cursor Item ====

Replaces or sets the inventory item that's being dragged with the mouse.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x5A</code><br/><br/>''resource:''<br/><code>set_cursor_item</code>
| Play
| Client
| Carried item
| {{Type|Slot}}
|
|}

==== Set Default 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.

The client uses this as the default position of the player upon spawning, though it's a good idea to always override this default by sending [[#Synchronize Player Position|Synchronize Player Position]]. When converting the position to floating point, 0.5 is added to the x and z coordinates and 1.0 to the y coordinate, so as to place the player centered on top of the specified block position.

Before receiving this packet, the client uses the default position 8, 64, 8, and angle 0.0 (resulting in a default player spawn position of 8.5, 65.0, 8.5).

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x5B</code><br/><br/>''resource:''<br/><code>set_default_spawn_position</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Location
| {{Type|Position}}
| Spawn location.
|-
| Angle
| {{Type|Float}}
| The angle at which to respawn at.
|}

==== Display Objective ====

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"| ''protocol:''<br/><code>0x5C</code><br/><br/>''resource:''<br/><code>set_display_objective</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Position
| {{Type|VarInt}}
| The position of the scoreboard. 0: list, 1: sidebar, 2: below name, 3 - 18: team specific sidebar, indexed as 3 + team color.
|-
| Score Name
| {{Type|String}} (32767)
| The unique name for the scoreboard to be displayed.
|}

==== Set Entity Metadata ====

Updates one or more [[Minecraft Wiki:Projects/wiki.vg merge/Entity_metadata#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"| ''protocol:''<br/><code>0x5D</code><br/><br/>''resource:''<br/><code>set_entity_data</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Entity ID
| {{Type|VarInt}}
|
|-
| Metadata
| [[Minecraft Wiki:Projects/wiki.vg merge/Entity_metadata#Entity Metadata Format|Entity Metadata]]
|
|}

==== Link Entities ====

This packet is sent when an entity has been [[Lead|leashed]] to another entity.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x5E</code><br/><br/>''resource:''<br/><code>set_entity_link</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Attached Entity ID
| {{Type|Int}}
| Attached entity's EID.
|-
| Holding Entity ID
| {{Type|Int}}
| ID of the entity holding the lead. Set to -1 to detach.
|}

==== Set Entity Velocity ====

Velocity is 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="4"| ''protocol:''<br/><code>0x5F</code><br/><br/>''resource:''<br/><code>set_entity_motion</code>
| rowspan="4"| Play
| rowspan="4"| Client
| Entity ID
| {{Type|VarInt}}
|
|-
| Velocity X
| {{Type|Short}}
| Velocity on the X axis.
|-
| Velocity Y
| {{Type|Short}}
| Velocity on the Y axis.
|-
| Velocity Z
| {{Type|Short}}
| Velocity on the Z axis.
|}

==== Set Equipment ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! colspan="2"| Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x60</code><br/><br/>''resource:''<br/><code>set_equipment</code>
| rowspan="3"| Play
| rowspan="3"| Client
| colspan="2"| Entity ID
| colspan="2"| {{Type|VarInt}}
| colspan="2"| Entity's ID.
|-
| rowspan="2"| Equipment
| Slot
| rowspan="2"| {{Type|Array}}
| {{Type|Byte}} {{Type|Enum}}
| rowspan="2"| The length of the array is unknown, it must be read until the most significant bit is 1 ((Slot >>> 7 & 1) == 1)
| Equipment slot (see below). Also has the top bit set if another entry follows, and otherwise unset if this is the last item in the array.
|-
| Item
| {{Type|Slot}}
|
|}

Equipment slot can be one of the following:

{| class="wikitable"
! ID
! Equipment slot
|-
| 0
| Main hand
|-
| 1
| Off hand
|-
| 2
| Boots
|-
| 3
| Leggings
|-
| 4
| Chestplate
|-
| 5
| Helmet
|-
| 6
| Body
|}

==== Set Experience ====


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


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="3"| ''protocol:''<br/><code>0x61</code><br/><br/>''resource:''<br/><code>set_experience</code>
| rowspan="3" | 0x2B
| rowspan="3"| Play
| Experience bar
| rowspan="3"| Client
| float
| Experience bar
| <code>0.5960060358047485</code>
| {{Type|Float}}
| Used for drawing the experience bar - value is between 0 and 1.
| Between 0 and 1.
|-
|-
| Level
| short
| Level
| {{Type|VarInt}}
| <code>8</code>
|
|
|-
|-
| Total experience
| Total Experience
| {{Type|VarInt}}
| short
| See [[Experience#Leveling up]] on the Minecraft Wiki for Total Experience to Level conversion.
| <code>130</code>
|
|}
|-
| Total Size:
| colspan="4" | 9 bytes
|}


==== Set Health ====
{{anchor|0x2C}}
=== Entity Properties (0x2C) ===
''Server to Client''


'''Note''': The server sends this packet to inform the user of its movement speed. Users move far too fast when this packet is not sent.
Sent by the server to set the health of the player it is sent to.

Food [[Food#Hunger and saturation|saturation]] acts as a food “overcharge”. Food values will not decrease while the saturation is over zero. New players logging in or respawning automatically get a saturation of 5.0. Eating food increases the saturation as well as the food bar.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="3"| ''protocol:''<br/><code>0x62</code><br/><br/>''resource:''<br/><code>set_health</code>
| rowspan="6" | 0x2C
| rowspan="3"| Play
| EntityID
| rowspan="3"| Client
| int
| 195
| Health
| {{Type|Float}}
| ?
| 0 or less = dead, 20 = full HP.
|-
|-
| Properties Count
| int
| Food
| {{Type|VarInt}}
| 3
| 0–20.
| Number of string/data (including these lists) pairs that follow. The remaining fields here are repeated this number of times.
|-
|-
| Food Saturation
| Key
| {{Type|Float}}
| string16
| Seems to vary from 0.0 to 5.0 in integer increments.
| "generic.Maxhealth"
|
|}

|-
==== Set Held Item (clientbound) ====
| Value

| double
Sent to change the player's slot selection.
| 20.0
|
|-
| ListLength
| short
| 1
| Number of list elements that follow.
|-
| ListElement
| {long (UUID MSB), long (UUID LSB), double (amount), byte (operation)}
|
| http://www.minecraftwiki.net/wiki/Attribute#Modifiers
|-
| Total Size:
| colspan="4" | ? bytes
|}


Known values:
{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Key
! Bound To
| Default
! Field Name
| Min
! Field Type
| Max
! Notes
| Label
|-
|-
| ''protocol:''<br/><code>0x63</code><br/><br/>''resource:''<br/><code>set_held_slot</code>
| generic.maxHealth
| 20.0
| Play
| 0.0
| Client
| Slot
| Double.MaxValue
| {{Type|VarInt}}
| Max Health
| The slot which the player has selected (0–8).
|-
|}
| 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
| Double.MaxValue
| Movement Speed
|-
| generic.attackDamage
| 2.0
| 0.0
| Double.MaxValue
|
|-
| horse.jumpStrength
| 0.7
| 0.0
| 2.0
| Jump Strength
|-
| zombie.spawnReinforcements
| 0.0
| 0.0
| 1.0
| Spawn Reinforcements Chance
|}


==== Update Objectives ====
{{anchor|0x33}}


This is sent to the client when it should create a new [[scoreboard]] objective or remove one.
=== Chunk Data (0x33) ===
''Server to Client''


{| class="wikitable"
Chunks are not unloaded by the client automatically. To unload chunks, send this packet with ground-up continuous=true and no 16^3 chunks (eg. primary bit mask=0). The server does not send skylight information for nether-chunks, it's up to the client to know if the player is currently in the nether. You can also infer this information from the primary bitmask and the amount of uncompressed bytes sent.
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! Field Type
! Notes
|-
| rowspan="10"| ''protocol:''<br/><code>0x64</code><br/><br/>''resource:''<br/><code>set_objective</code>
| rowspan="10"| Play
| rowspan="10"| Client
| colspan="2"| Objective Name
| {{Type|String}} (32767)
| A unique name for the objective.
|-
| colspan="2"| Mode
| {{Type|Byte}}
| 0 to create the scoreboard. 1 to remove the scoreboard. 2 to update the display text.
|-
| colspan="2"| Objective Value
| {{Type|Optional}} {{Type|Text Component}}
| Only if mode is 0 or 2.The text to be displayed for the score.
|-
| colspan="2"| Type
| {{Type|Optional}} {{Type|VarInt}} {{Type|Enum}}
| Only if mode is 0 or 2. 0 = "integer", 1 = "hearts".
|-
| colspan="2"| Has Number Format
| {{Type|Optional}} {{Type|Boolean}}
| Only if mode is 0 or 2. Whether this objective has a set number format for the scores.
|-
| colspan="2"| Number Format
| {{Type|Optional}} {{Type|VarInt}} {{Type|Enum}}
| Only if mode is 0 or 2 and the previous boolean is true. Determines how the score number should be formatted.
|-
! Number Format
! Field Name
!
!
|-
| 0: blank
| colspan="2"| ''no fields''
| Show nothing.
|-
| 1: styled
| Styling
| [[Minecraft Wiki:Projects/wiki.vg merge/NBT#Specification:compound_tag|Compound Tag]]
| The styling to be used when formatting the score number. Contains the [[Minecraft Wiki:Projects/wiki.vg merge/Text formatting#Styling fields|text component styling fields]].
|-
| 2: fixed
| Content
| {{Type|Text Component}}
| The text to be used as placeholder.
|}


==== Set Passengers ====
See also: [[SMP Map Format]]


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x65</code><br/><br/>''resource:''<br/><code>set_passengers</code>
| rowspan="7" | 0x33
| rowspan="2"| Play
| X
| rowspan="2"| Client
| int
| Entity ID
|
| {{Type|VarInt}}
| Chunk X Coordinate (*16 to get true X)
| Vehicle's EID.
|-
| Z
|-
| Passengers
| int
| {{Type|Prefixed Array}} of {{Type|VarInt}}
|
| EIDs of entity's passengers.
| Chunk Z Coordinate (*16 to get true Z)
|-
|}
| Ground-up continuous
| boolean
|
| This is True if the packet represents all sections in this vertical column, where the primary bit map specifies exactly which sections are included, and which are air.
|-
| Primary bit map
| unsigned short
| 15
| Bitmask with 1 for every 16x16x16 section which data follows in the compressed data.
|-
| Add bit map
| unsigned short
| 0
| Same as above, but this is used exclusively for the 'add' portion of the payload
|-
| Compressed size
| int
|
| Size of compressed chunk data.
|-
| Compressed data
| unsigned byte array
| <code>…</code>
| The chunk data is compressed using ZLib Deflate function.
|-
| Total Size:
| colspan="4" | 18 bytes + Compressed chunk size
|}


==== Set Player Inventory Slot ====
{{anchor|0x34}}


{| class="wikitable"
=== Multi Block Change (0x34) ===
! Packet ID
''Server to Client''
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x66</code><br/><br/>''resource:''<br/><code>set_player_inventory</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Slot
| {{Type|VarInt}}
|
|-
| Slot Data
| {{Type|Slot}}
|
|}

==== Update Teams ====

Creates and updates teams.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! colspan="2"| Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="20"| ''protocol:''<br/><code>0x67</code><br/><br/>''resource:''<br/><code>set_player_team</code>
| rowspan="5" | 0x34
| rowspan="20"| Play
| Chunk X
| rowspan="20"| Client
| int
| colspan="2"| Team Name
| <code>-9</code>
| {{Type|String}} (32767)
| Chunk X Coordinate
| A unique name for the team. (Shared with scoreboard).
|-
|-
| Chunk Z
| colspan="2"| Method
| int
| {{Type|Byte}}
| <code>12</code>
| Determines the layout of the remaining packet.
| Chunk Z Coordinate
|-
|-
| rowspan="8"| 0: create team
| Record count
| Team Display Name
| short
| {{Type|Text Component}}
|
|
| The number of blocks affected
|-
|-
| Friendly Flags
| Data size
| {{Type|Byte}}
| int
| Bit mask. 0x01: Allow friendly fire, 0x02: can see invisible players on same team.
|
|-
| The total size of the data, in bytes. Should always be 4*record count - please confirm.
| Name Tag Visibility
|-
| {{Type|String}} {{Type|Enum}} (40)
| Data
| <code>always</code>, <code>hideForOtherTeams</code>, <code>hideForOwnTeam</code>, <code>never</code>.
| Special
|-
| <code>…</code>
| Collision Rule
| Coordinates, type, and metadata of blocks to change (see below table).
| {{Type|String}} {{Type|Enum}} (40)
|-
| <code>always</code>, <code>pushOtherTeams</code>, <code>pushOwnTeam</code>, <code>never</code>.
| Total Size:
|-
| colspan="4" | 15 bytes + Arrays
| Team Color
|}
| {{Type|VarInt}} {{Type|Enum}}
| Used to color the name of players on the team; see below.
|-
| Team Prefix
| {{Type|Text Component}}
| Displayed before the names of players that are part of this team.
|-
| Team Suffix
| {{Type|Text Component}}
| Displayed after the names of players that are part of this team.
|-
| Entities
| {{Type|Prefixed Array}} of {{Type|String}} (32767)
| 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''
|
|-
| rowspan="7"| 2: update team info
| Team Display Name
| {{Type|Text Component}}
|
|-
| Friendly Flags
| {{Type|Byte}}
| Bit mask. 0x01: Allow friendly fire, 0x02: can see invisible entities on same team.
|-
| Name Tag Visibility
| {{Type|String}} {{Type|Enum}} (40)
| <code>always</code>, <code>hideForOtherTeams</code>, <code>hideForOwnTeam</code>, <code>never</code>
|-
| Collision Rule
| {{Type|String}} {{Type|Enum}} (40)
| <code>always</code>, <code>pushOtherTeams</code>, <code>pushOwnTeam</code>, <code>never</code>
|-
| Team Color
| {{Type|VarInt}} {{Type|Enum}}
| Used to color the name of players on the team; see below.
|-
| Team Prefix
| {{Type|Text Component}}
| Displayed before the names of players that are part of this team.
|-
| Team Suffix
| {{Type|Text Component}}
| Displayed after the names of players that are part of this team.
|-
| 3: add entities to team
| Entities
| {{Type|Prefixed Array}} of {{Type|String}} (32767)
| Identifiers for the added entities. For players, this is their username; for other entities, it is their UUID.
|-
| 4: remove entities from team
| Entities
| {{Type|Prefixed Array}} of {{Type|String}} (32767)
| Identifiers for the removed entities. 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.
Each record is four bytes.


{| class="wikitable"
{| class="wikitable"
! ID
|-
! Formatting
| Bit mask
|-
| Width
| 0-15
| Meaning
| Color formatting, same values as in [[Minecraft Wiki:Projects/wiki.vg merge/Text formatting#Colors|Text formatting#Colors]].
|-
|-
| 00 00 00 0F
| 4 bits
| 16
| Obfuscated
| Block metadata
|-
|-
| 17
| 00 00 FF F0
| Bold
| 12 bits
|-
| Block ID
| 18
|-
| Strikethrough
| 00 FF 00 00
|-
| 8 bits
| 19
| Y co-ordinate
| Underlined
|-
|-
| 0F 00 00 00
| 4 bits
| 20
| Italic
| Z co-ordinate, relative to chunk
|-
|-
| 21
| F0 00 00 00
| 4 bits
| Reset
|}
| X co-ordinate, relative to chunk
|}


==== Update Score ====
{{anchor|0x35}}


This is sent to the client when it should update a scoreboard item.
=== Block Change (0x35) ===
''Server to Client''


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! colspan="2"| Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="9"| ''protocol:''<br/><code>0x68</code><br/><br/>''resource:''<br/><code>set_score</code>
| rowspan="5" | 0x35
| rowspan="9"| Play
| X
| rowspan="9"| Client
| int
| colspan="2"| Entity Name
| <code>502</code>
| {{Type|String}} (32767)
| Block X Coordinate
| The entity whose score this is. For players, this is their username; for other entities, it is their UUID.
|-
| Y
|-
| colspan="2"| Objective Name
| byte
| {{Type|String}} (32767)
| <code>71</code>
| The name of the objective the score belongs to.
| Block Y Coordinate
|-
|-
| colspan="2"| Value
| Z
| {{Type|VarInt}}
| int
| The score to be displayed next to the entry.
| <code>18</code>
|-
| Block Z Coordinate
| colspan="2"| Display Name
|-
| {{Type|Prefixed Optional}} {{Type|Text Component}}
| Block Type
| The custom display name.
| short
|-
| <code>78</code>
| colspan="2"| Number Format
| The new block type for the block
| {{Type|Prefixed Optional}} {{Type|VarInt}} {{Type|Enum}}
|-
| Determines how the score number should be formatted.
| Block Metadata
|-
| byte
! Number Format
| <code>0</code>
! Field Name
| The new Metadata for the block
!
|-
!
| Total Size:
|-
| colspan="4" | 13 bytes
| 0: blank
|}
| colspan="2"| ''no fields''
| Show nothing.
|-
| 1: styled
| Styling
| [[Minecraft Wiki:Projects/wiki.vg merge/NBT#Specification:compound_tag|Compound Tag]]
| The styling to be used when formatting the score number. Contains the [[Minecraft Wiki:Projects/wiki.vg merge/Text formatting#Styling fields|text component styling fields]].
|-
| 2: fixed
| Content
| {{Type|Text Component}}
| The text to be used as placeholder.
|}


==== Set Simulation Distance ====
{{anchor|0x36}}
=== Block Action (0x36) ===
''Server to Client''


{| class="wikitable"
This packet is used for a number of things:
! Packet ID
* <div class="li">Chests opening and closing
! State
* Pistons pushing and pulling
! Bound To
* Note blocks playing
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x69</code><br/><br/>''resource:''<br/><code>set_simulation_distance</code>
| Play
| Client
| Simulation Distance
| {{Type|VarInt}}
| The distance that the client will process specific things, such as entities.
|}

==== Set Subtitle Text ====


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x6A</code><br/><br/>''resource:''<br/><code>set_subtitle_text</code>
| rowspan="6" | 0x36
| rowspan="1"| Play
| X
| rowspan="1"| Client
| int
| Subtitle Text
| <code>502</code>
| {{Type|Text Component}}
| Block X Coordinate
|-
|
| Y
|}
| short
| <code>71</code>
| Block Y Coordinate
|-
| Z
| int
| <code>18</code>
| Block Z Coordinate
|-
| Byte 1
| byte
| <code>3</code>
| Varies depending on block - see below
|-
| Byte 2
| byte
| <code>17</code>
| Varies depending on block - see below
|-
| Block ID
| short
| <code>29</code>
| The block id this action is set for
|-
| Total Size:
| colspan="4" | 15 bytes
|}
See Also: [[Block Actions]]


==== Update Time ====
{{anchor|0x37}}

=== Block Break Animation (0x37) ===
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.
''Server to Client''

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"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="3"| ''protocol:''<br/><code>0x6B</code><br/><br/>''resource:''<br/><code>set_time</code>
| rowspan="5" | 0x37
| rowspan="3"| Play
| EID?
| rowspan="3"| Client
| int
| World Age
|
| {{Type|Long}}
| Entity breaking the block?
| In ticks; not changed by server commands.
|-
| X
|-
| Time of day
| int
| {{Type|Long}}
|
| The world (or region) time, in ticks.
| rowspan="3" | Block position
|-
|-
| Time of day increasing
| Y
| {{Type|Boolean}}
| int
| If true, the client should automatically advance the time of day according to its ticking rate.
|
|-
|}
| Z
| int
|
|-
| Destroy Stage
| byte
| 1
| How far destroyed this block is. (0-7)
|-
| Total Size:
| colspan="4" | 18 bytes
|}


==== Set Title Text ====
{{anchor|0x38}}


{| class="wikitable"
=== Map Chunk Bulk (0x38) ===
! Packet ID
''Server to Client''
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x6C</code><br/><br/>''resource:''<br/><code>set_title_text</code>
| rowspan="1"| Play
| rowspan="1"| Client
| Title Text
| {{Type|Text Component}}
|
|}


==== Set Title Animation Times ====
See also: [[SMP Map Format]]


{| class="wikitable"
To reduce the number of bytes this packet is used to send chunks together for better compression results.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x6D</code><br/><br/>''resource:''<br/><code>set_titles_animation</code>
| rowspan="3"| Play
| rowspan="3"| Client
| Fade In
| {{Type|Int}}
| Ticks to spend fading in.
|-
| Stay
| {{Type|Int}}
| Ticks to keep the title displayed.
|-
| Fade Out
| {{Type|Int}}
| Ticks to spend fading out, not when to start fading out.
|}

==== Entity Sound Effect ====

Plays a sound effect from an entity, either by hardcoded ID or Identifier. Sound IDs and names can be found [https://pokechu22.github.io/Burger/1.21.html#sounds here].


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="6"| ''protocol:''<br/><code>0x6E</code><br/><br/>''resource:''<br/><code>sound_entity</code>
| rowspan="5" | 0x38
| rowspan="6"| Play
| Chunk column count
| rowspan="6"| Client
| short
| Sound Event
|
| {{Type|ID or}} {{Type|Sound Event}}
| The number of chunks in this packet
| ID in the <code>minecraft:sound_event</code> registry, or an inline definition.
|-
|-
| Data length
| Sound Category
| int
| {{Type|VarInt}} {{Type|Enum}}
|
| The category that this sound will be played from ([https://gist.github.com/konwboj/7c0c380d3923443e9d55 current categories]).
| the size of the data field
|-
|-
| Entity ID
| Sky light sent
| {{Type|VarInt}}
| boolean
|
|
|-
| Whether or not the chunk data contains a light nibble array. This is true in the main world, false in the end + nether
| Volume
|-
| {{Type|Float}}
| Data
| 1.0 is 100%, capped between 0.0 and 1.0 by vanilla clients.
| byte array
|
|-
| Pitch
| Compressed chunk data
| {{Type|Float}}
|-
| Float between 0.5 and 2.0 by vanilla clients.
| Meta information
|-
| Special
| Seed
|
| {{Type|Long}}
| see below
| Seed used to pick sound variant.
|-
|}
| Total Size:
| colspan="4" | 8 + (Chunk data size) + 12 * (Chunk Count) bytes
|}


====Meta Information Structure====
==== Sound Effect ====


Plays a sound effect at the given location, either by hardcoded ID or Identifier. Sound IDs and names can be found [https://pokechu22.github.io/Burger/1.21.html#sounds here].
This structure is repeated for each chunk column sent


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Field Name
! Bound To
| Field Type
! Field Name
| Example
! Field Type
| Notes
! Notes
|-
|-
| Chunk X
| rowspan="8"| ''protocol:''<br/><code>0x6F</code><br/><br/>''resource:''<br/><code>sound</code>
| int
| rowspan="8"| Play
| 10
| rowspan="8"| Client
| The X coordinate of the specific chunk
| Sound Event
|-
| {{Type|ID or}} {{Type|Sound Event}}
| Chunk Z
| ID in the <code>minecraft:sound_event</code> registry, or an inline definition.
| int
|-
| 10
| Sound Category
| The Z coordinate of the specific chunk
| {{Type|VarInt}} {{Type|Enum}}
|-
| The category that this sound will be played from ([https://gist.github.com/konwboj/7c0c380d3923443e9d55 current categories]).
| Primary bitmap
|-
| unsigned short
| Effect Position X
| 15
| {{Type|Int}}
| A bitmap which specifies which sections are not empty in this chunk
| Effect X multiplied by 8 ([[Minecraft Wiki:Projects/wiki.vg merge/Data types#Fixed-point numbers|fixed-point number]] with only 3 bits dedicated to the fractional part).
|-
|-
| Add bitmap
| Effect Position Y
| unsigned short
| {{Type|Int}}
| 0
| Effect Y multiplied by 8 ([[Minecraft Wiki:Projects/wiki.vg merge/Data types#Fixed-point numbers|fixed-point number]] with only 3 bits dedicated to the fractional part).
| A bitmap which specifies which sections need add information because of very high block ids. not yet used. needs verification
|-
|-
| Effect Position Z
| Total Size:
| {{Type|Int}}
| colspan="3" | 12 bytes
| Effect Z multiplied by 8 ([[Minecraft Wiki:Projects/wiki.vg merge/Data types#Fixed-point numbers|fixed-point number]] with only 3 bits dedicated to the fractional part).
|}
|-
| Volume
| {{Type|Float}}
| 1.0 is 100%, capped between 0.0 and 1.0 by vanilla clients.
|-
| Pitch
| {{Type|Float}}
| Float between 0.5 and 2.0 by vanilla clients.
|-
| Seed
| {{Type|Long}}
| Seed used to pick sound variant.
|}


==== Start Configuration ====


Sent during gameplay in order to redo the configuration process. The client must respond with [[#Acknowledge Configuration|Acknowledge Configuration]] for the process to start.
* If you send this packet to update area surrounding player in the middle of the game, entities within the updated area may become unattackable (vanilla client just won't send "Use Entity (0x07)" packet when you try to hit them, only swing animation, also it will dig blocks through them), even though they will be visible and work correctly in other ways. This is a bug in vanilla client (still there in 1.5.2), but you can workaround it by destroying relevant entities prior to sending 0x38 (via 0x1D) and spawning them again after it.


{| class="wikitable"
{{anchor|0x3C}}
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x70</code><br/><br/>''resource:''<br/><code>start_configuration</code>
| rowspan="1"| Play
| rowspan="1"| Client
| colspan="3"| ''no fields''
|}


This packet switches the connection state to [[#Configuration|configuration]].
=== Explosion (0x3C) ===
''Server to Client''


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


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="3"| ''protocol:''<br/><code>0x71</code><br/><br/>''resource:''<br/><code>stop_sound</code>
| rowspan="9" | 0x3C
| rowspan="3"| Play
| X
| rowspan="3"| Client
| double
| Flags
|
| {{Type|Byte}}
|
| Controls which fields are present.
|-
| Y
|-
| double
| Source
| {{Type|Optional}} {{Type|VarInt}} {{Type|Enum}}
|
| Only if flags is 3 or 1 (bit mask 0x1). See below. If not present, then sounds from all sources are cleared.
|
|-
|-
| Z
| Sound
| {{Type|Optional}} {{Type|Identifier}}
| double
| Only if flags is 2 or 3 (bit mask 0x2). A sound effect name, see [[#Custom Sound Effect|Custom Sound Effect]]. If not present, then all sounds are cleared.
|
|
|}
|-
| Radius
| float
| 3.0
| Currently unused in the client
|-
| Record count
| int
|
| This is the count, not the size. The size is 3 times this value.
|-
| Records
| (byte, byte, byte) × count
|
| 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
|-
| Total Size:
| colspan="4" | 45 bytes + 3*(Record count) bytes
|}


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


{| class="wikitable"
{{anchor|0x3D}}
! Name !! Value
=== Sound Or Particle Effect (0x3D) ===
|-
''Server to Client''
| master || 0
|-
| music || 1
|-
| record || 2
|-
| weather || 3
|-
| block || 4
|-
| hostile || 5
|-
| neutral || 6
|-
| player || 7
|-
| ambient || 8
|-
| voice || 9
|}


==== Store Cookie (play) ====
Sent when a client is to play a sound or particle effect.


Stores some arbitrary data on the client, which persists between server transfers. The vanilla client only accepts cookies of up to 5 kiB in size.
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 1013 (mob.wither.spawn), and is ignored for any other value by the client.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x72</code><br/><br/>''resource:''<br/><code>store_cookie</code>
| rowspan="6" | 0x3D
| rowspan="2"| Play
| Effect ID
| rowspan="2"| Client
| int
| 1003
| Key
| {{Type|Identifier}}
| The ID of the effect, see below.
| The identifier of the cookie.
|-
| X
|-
| Payload
| int
| {{Type|Prefixed Array}} (5120) of {{Type|Byte}}
|
| The X location of the effect.
| The data of the cookie.
|-
|}
| Y
| byte
|
| The Y location of the effect.
|-
| Z
| int
|
| The Z location of the effect.
|-
| Data
| int
| 0
| Extra data for certain effects, see below.
|-
| Disable relative volume
| boolean
| false
| See above
|-
| Total Size:
| colspan="4" | 19 bytes
|}


====Effects====
==== System Chat Message ====


{{Main|Chat}}
'''Sound''':


Sends the client a raw system message.
*1000: <code>random.click</code>
*1001: <code>random.click</code>
*1002: <code>random.bow</code>
*1003: <code>random.door_open</code> or <code>random.door_close</code> (50/50 chance)
*1004: <code>random.fizz</code>
*1005: Play a music disc. '''Data''': [http://www.minecraftwiki.net/wiki/Music_Discs Record ID]
*''(1006 not assigned)''
*1007: <code>mob.ghast.charge</code>
*1008: <code>mob.ghast.fireball</code>
*1009: <code>mob.ghast.fireball</code>, but with a lower volume.
*1010: <code>mob.zombie.wood</code>
*1011: <code>mob.zombie.metal</code>
*1012: <code>mob.zombie.woodbreak</code>
*1013: <code>mob.wither.spawn</code>
*1014: <code>mob.wither.shoot</code>
*1015: <code>mob.bat.takeoff</code>
*1016: <code>mob.zombie.infect</code>
*1017: <code>mob.zombie.unfect</code>
*1018: <code>mob.enderdragon.end</code>
*1020: <code>random.anvil_break</code>
*1021: <code>random.anvil_use</code>
*1022: <code>random.anvil_land</code>


{| class="wikitable"
'''Particle''':
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x73</code><br/><br/>''resource:''<br/><code>system_chat</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Content
| {{Type|Text Component}}
| Limited to 262144 bytes.
|-
| Overlay
| {{Type|Boolean}}
| Whether the message is an actionbar or chat message. See also [[#Set Action Bar Text]].
|}


==== Set Tab List Header And Footer ====
*2000: Spawns 10 smoke particles, e.g. from a fire. '''Data''': direction, see below
*2001: Block break. '''Data''': [http://www.minecraftwiki.net/wiki/Data_values Block ID]
*2002: Splash potion. Particle effect + glass break sound. '''Data''': [http://www.lb-stuff.com/Minecraft/PotionDataValues1.9pre3.txt Potion ID]
*2003: Eye of ender. Actual client effect to be determined.
*2004: Mob spawn particle effect: smoke + flames
*2005: Spawn "happy villager" effect (hearts).


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


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| ID
! Bound To
| Direction
! Field Name
|-
! Field Type
| 0
! Notes
| South - East
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x74</code><br/><br/>''resource:''<br/><code>tab_list</code>
| 1
| rowspan="2"| Play
| South
| rowspan="2"| Client
|-
| 2
| Header
| {{Type|Text Component}}
| South - West
| To remove the header, send a empty text component: <code>{"text":""}</code>.
|-
| 3
|-
| East
| Footer
| {{Type|Text Component}}
|-
| To remove the footer, send a empty text component: <code>{"text":""}</code>.
| 4
|}
| (Up or middle ?)
|-
| 5
| West
|-
| 6
| North - East
|-
| 7
| North
|-
| 8
| North - West
|}


==== Tag Query Response ====
{{anchor|0x3E}}


Sent in response to [[#Query Block Entity Tag|Query Block Entity Tag]] or [[#Query Entity Tag|Query Entity Tag]].
=== Named Sound Effect (0x3E) ===
''Server to client''


{| class="wikitable"
Used to play a sound effect on the client.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x75</code><br/><br/>''resource:''<br/><code>tag_query</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Transaction ID
| {{Type|VarInt}}
| Can be compared to the one sent in the original query packet.
|-
| NBT
| {{Type|NBT}}
| The NBT of the block or entity. May be a TAG_END (0) in which case no NBT is present.
|}


==== Pickup Item ====
All known sound effect names can be seen [https://github.com/SirCmpwn/Craft.Net/blob/master/Craft.Net.Data/SoundEffect.cs here].

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 [[#Set Player Position|Set Player Position]] (and [[#Set Player Position And Rotation|Set Player Position And Rotation]]) 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 vanilla server only uses this for items, experience orbs, and the different varieties of arrows.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="3"| ''protocol:''<br/><code>0x76</code><br/><br/>''resource:''<br/><code>take_item_entity</code>
| rowspan="6" | 0x3E
| rowspan="3"| Play
| Sound name
| rowspan="3"| Client
| string
| Collected Entity ID
| step.grass
| {{Type|VarInt}}
| 250
|-
|
|-
| Effect position X
| Collector Entity ID
| int
| {{Type|VarInt}}
| 250
|
| effect X multiplied by 8
|-
|-
| Pickup Item Count
| Effect position Y
| {{Type|VarInt}}
| int
| Seems to be 1 for XP orbs, otherwise the number of items in the stack.
| 250
|}
| effect Y multiplied by 8
|-
| Effect position Z
| int
| 250
| effect Z multiplied by 8
|-
| Volume
| float
| 9
| 1 is 100%, can be more
|-
| Pitch
| byte
| 1
| 63 is 100%, can be more
|-
| Total Size:
| colspan="4" | 20 bytes + length of string
|}


==== Synchronize Vehicle Position ====
{{anchor|0x3F}}
=== Particle (0x3F) ===
''Server to Client''


Teleports the entity on the client without changing the reference point of movement deltas in future [[#Update Entity Position|Update Entity Position]] packets. Seems to be used to make relative adjustments to vehicle positions; more information needed.
This displays the named particle


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="11"| ''protocol:''<br/><code>0x77</code><br/><br/>''resource:''<br/><code>teleport_entity</code>
| rowspan="9" | 0x3F
| rowspan="11"| Play
| Particle name
| rowspan="11"| Client
| string
| Entity ID
| <code>hugeexplosion</code>
| {{Type|VarInt}}
| The name of the particle to create. A list can be found [https://gist.github.com/thinkofdeath/5110835 here]
|-
|
| X
|-
| float
| X
| {{Type|Double}}
| 0
|
| X position of the particle
|-
|-
| Y
| Y
| {{Type|Double}}
| float
| 0
|
|-
| Y position of the particle
|-
| Z
| {{Type|Double}}
| Z
|
| float
| 0
|-
| Velocity X
| Z position of the particle
| {{Type|Double}}
|-
|
| Offset X
|-
| float
| Velocity Y
| 0
| {{Type|Double}}
| This is added to the X position after being multiplied by random.nextGaussian()
|-
|
|-
| Offset Y
| Velocity Z
| float
| {{Type|Double}}
| 0
|
| This is added to the Y position after being multiplied by random.nextGaussian()
|-
|-
| Yaw
| Offset Z
| {{Type|Float}}
| float
| Rotation on the Y axis, in degrees.
| 0
|-
| This is added to the Z position after being multiplied by random.nextGaussian()
| Pitch
|-
| {{Type|Float}}
| Particle speed
| Rotation on the Y axis, in degrees.
| float
| 0
|-
| Flags
| The speed of each particle
| {{Type|Teleport Flags}}
|-
|
| Number of particles
|-
| int
| On Ground
| 0
| {{Type|Boolean}}
| The number of particles to create
|-
|
|}
| Total Size:
| colspan="4" | 34 bytes + length of string
|}


==== Set Ticking State ====
{{anchor|0x46}}
=== Change Game State (0x46) ===
''Server to Client''


Used to adjust the ticking rate of the client, and whether it's frozen.
This packet appeared with protocol version 10. Currently, it appears when a bed can't be used as a spawn point and when the rain state changes. it could have additional uses in the future.


{| class="wikitable"
The class has an array of strings linked to reason codes 0, 1, 2, and 3 but only the codes for 1 and 2 are null.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2" | ''protocol:''<br/><code>0x78</code><br/><br/>''resource:''<br/><code>ticking_state</code>
| rowspan="2" | Play
| rowspan="2" | Client
| Tick rate
| {{Type|Float}}
|
|-
| Is frozen
| {{Type|Boolean}}
|
|}

==== Step Tick ====

Advances the client processing by the specified number of ticks. Has no effect unless client ticking is frozen.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| ''protocol:''<br/><code>0x79</code><br/><br/>''resource:''<br/><code>ticking_step</code>
| rowspan="2" | 0x46
| Reason
| Play
| byte
| Client
| Tick steps
| 0
| {{Type|VarInt}}
|
|-
|
|}
| Game mode
| byte
| 0
| Used only when reason = 3. 0 is survival, 1 is creative.
|-
| Total Size:
| colspan="4" | 3 bytes
|}


==== Transfer (play) ====
'''Reason codes'''

Notifies the client that it should transfer to the given server. Cookies previously stored are preserved between server transfers.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! Code
! State
! Bound To
! Effect
! colspan="2"| Field Name
! Text
! colspan="2"| Field Type
|-
! Notes
| 0
|-
| Invalid Bed
| rowspan="2"| ''protocol:''<br/><code>0x7A</code><br/><br/>''resource:''<br/><code>transfer</code>
| "tile.bed.notValid"
| rowspan="2"| Play
|-
| rowspan="2"| Client
| 1
| colspan="2"| Host
| Begin raining
| colspan="2"| {{Type|String}}
| null
| The hostname or IP of the server.
|-
| 2
|-
| colspan="2"| Port
| End raining
| colspan="2"| {{Type|VarInt}}
| null
| The port of the server.
|-
| 3
|}
| Change game mode
| gameMode.changed
|-
| 4
| Enter credits
|
|}


==== Update Advancements ====
{{anchor|0x47}}
=== Spawn Global Entity (0x47) ===
''Server to Client''


{| class="wikitable"
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
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="6"| ''protocol:''<br/><code>0x7B</code><br/><br/>''resource:''<br/><code>update_advancements</code>
| rowspan="6"| Play
| rowspan="6"| Client
| colspan="2"| Reset/Clear
| colspan="2"| {{Type|Boolean}}
| Whether to reset/clear the current advancements.
|-
| rowspan="2"| Advancement mapping
| Key
| rowspan="2"| {{Type|Prefixed Array}}
| {{Type|Identifier}}
| The identifier of the advancement.
|-
| Value
| Advancement
| See below
|-
| colspan="2"| Identifiers
| colspan="2"| {{Type|Prefixed Array}} of {{Type|Identifier}}
| The identifiers of the advancements that should be removed.
|-
| rowspan="2"| Progress mapping
| Key
| rowspan="2"| {{Type|Prefixed Array}}
| {{Type|Identifier}}
| The identifier of the advancement.
|-
| Value
| Advancement progress
| See below.
|}

Advancement structure:


{| class="wikitable"
{| class="wikitable"
! colspan="2"| Field Name
|-
! colspan="2"| Field Type
| Packet ID
! Notes
| Field Name
|-
| Field Type
| colspan="2"| Parent id
| Example
| colspan="2"| {{Type|Prefixed Optional}} {{Type|Identifier}}
| Notes
| The identifier of the parent advancement.
|-
|-
| rowspan="5" | 0x47
| colspan="2"| Display data
| Entity ID
| colspan="2"| {{Type|Prefixed Optional}} Advancement display
| int
| See below.
| 4
|-
| The entity ID of the thunderbolt
| colspan="2"| Nested requirements
|-
| Type
| {{Type|Prefixed Array}}
| {{Type|Prefixed Array}} of {{Type|String}} (32767)
| byte
| Array with a sub-array of criteria. To check if the requirements are met, each sub-array must be tested and mapped with the OR operator, resulting in a boolean array.
| 1
These booleans must be mapped with the AND operator to get the result.
| The global entity type, currently always 1 for thunderbolt.
|-
|-
| colspan="2"| Sends telemetry data
| X
| colspan="2"| {{Type|Boolean}}
| int
| Whether the client should include this achievement in the telemetry data when it's completed.
| 133
The vanilla client only sends data for advancements on the <code>minecraft</code> namespace.
| Thunderbolt X as Absolute Integer
|-
|}
| Y
| int
| 913
| Thunderbolt Y as Absolute Integer
|-
| Z
| int
| 63552
| Thunderbolt Z as Absolute Integer
|-
| Total Size:
| colspan="4" | 18 bytes
|}


Advancement display:
{{anchor|0x64}}


{| class="wikitable"
=== Open Window (0x64) ===
! Field Name
''Server to Client''
! Field Type
! Notes
|-
| Title
| {{Type|Text Component}}
|
|-
| Description
| {{Type|Text Component}}
|
|-
| Icon
| {{Type|Slot}}
|
|-
| Frame type
| {{Type|VarInt}} {{Type|Enum}}
| 0 = <code>task</code>, 1 = <code>challenge</code>, 2 = <code>goal</code>.
|-
| Flags
| {{Type|Int}}
| 0x01: has background texture; 0x02: <code>show_toast</code>; 0x04: <code>hidden</code>.
|-
| Background texture
| {{Type|Optional}} {{Type|Identifier}}
| Background texture location. Only if flags indicates it.
|-
| X coord
| {{Type|Float}}
|
|-
| Y coord
| {{Type|Float}}
|
|}


Advancement progress:
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"
{| class="wikitable"
! colspan="2"| Field Name
|-
! colspan="2"| Field Type
| Packet ID
! Notes
| Field Name
|-
| Field Type
| rowspan="2"| Criteria
| Example
| Criterion identifier
| Notes
| rowspan="2"| {{Type|Prefixed Array}}
|-
| {{Type|Identifier}}
| rowspan="6" | 0x64
| The identifier of the criterion.
| Window id
|-
| byte
| Date of achieving
| 123
| {{Type|Prefixed Optional}} {{Type|Long}}
| A unique id number for the window to be displayed. Notchian server implementation is a counter, starting at 1.
| Present if achieved. As returned by [https://docs.oracle.com/javase/6/docs/api/java/util/Date.html#getTime() <code>Date.getTime</code>].
|-
|}
| Inventory Type
| byte
| 2
| The window type to use for display. Check below
|-
| Window title
| string
| <code>Chest</code>
| The title of the window.
|-
| Number of Slots
| byte
| 3
| Number of slots in the window (excluding the number of slots in the player inventory).
|-
| Use provided window title
| boolean
| 1
| If false, the client will look up a string like "window.minecart". If true, the client uses what the server provides.
|-
| entityId
| int
| 0
| EntityHorse's entityId. Only sent when window type is equal to 11 (AnimalChest).
|-
| Total Size:
| colspan="4" | 8 bytes + length of string
|}


==== Update Attributes ====
See [[Inventory#Windows|inventory windows]] for further information.


Sets [[Attribute|attributes]] on the given entity.
{{anchor|0x65}}


{| class="wikitable"
=== Close Window (0x65) ===
! Packet ID
''Two-Way''
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="4"| ''protocol:''<br/><code>0x7C</code><br/><br/>''resource:''<br/><code>update_attributes</code>
| rowspan="4"| Play
| rowspan="4"| Client
| colspan="2"| Entity ID
| colspan="2"| {{Type|VarInt}}
|
|-
| rowspan="3"| Property
| Id
| rowspan="3"| {{Type|Prefixed Array}}
| {{Type|VarInt}}
| ID in the <code>minecraft:attribute</code> registry. See also [[Attribute#Attributes]].
|-
| Value
| {{Type|Double}}
| See below.
|-
| Modifiers
| {{Type|Prefixed Array}} of Modifier Data
| See [[Attribute#Modifiers]]. Modifier Data defined below.
|}

''Modifier Data'' structure:

{| class="wikitable"
|-
! Field Name
! Field Type
! Notes
|-
| Id
| {{Type|Identifier}}
|
|-
| Amount
| {{Type|Double}}
| May be positive or negative.
|-
| Operation
| {{Type|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 ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="5"| ''protocol:''<br/><code>0x7D</code><br/><br/>''resource:''<br/><code>update_mob_effect</code>
| rowspan="5"| Play
| rowspan="5"| Client
| Entity ID
| {{Type|VarInt}}
|
|-
| Effect ID
| {{Type|VarInt}}
| See [[Status effect#Effect list|this table]].
|-
| Amplifier
| {{Type|VarInt}}
| Vanilla client displays effect level as Amplifier + 1.
|-
| Duration
| {{Type|VarInt}}
| Duration in ticks. (-1 for infinite)
|-
| Flags
| {{Type|Byte}}
| Bit field, see below.
|}

{{missing info|section|What exact effect does the blend bit flag have on the client? What happens if it is used on effects besides DARKNESS?}}

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 [[Minecraft Wiki:Projects/wiki.vg merge/Entity_metadata#Living Entity|"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.
* 0x08: Blend - should the effect's hard-coded blending be applied? Currently only used in the DARKNESS effect to apply extra void fog and adjust the gamma value for lighting.

==== Update Recipes ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="4"| ''protocol:''<br/><code>0x7E</code><br/><br/>''resource:''<br/><code>update_recipes</code>
| rowspan="4"| Play
| rowspan="4"| Client
| rowspan="2"| Property Sets
| Property Set ID
| rowspan="2"| {{Type|Prefixed Array}}
| {{Type|Identifier}}
|
|-
| Items
| {{Type|Prefixed Array}} of {{Type|VarInt}}
| IDs in the <code>minecraft:item</code> registry.
|-
| rowspan="2"| Stonecutter Recipes
| Ingredients
| rowspan="2"| {{Type|Prefixed Array}}
| {{Type|ID Set}}
|
|-
| Slot Display
| {{Type|Slot Display}}
|
|}

==== Update Tags (play) ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x7F</code><br/><br/>''resource:''<br/><code>update_tags</code>
| rowspan="2"| Play
| rowspan="2"| Client
| rowspan="2"| Registry to tags map
| Registry
| rowspan="2"| {{Type|Prefixed Array}}
| {{Type|Identifier}}
| Registry identifier (Vanilla expects tags for the registries <code>minecraft:block</code>, <code>minecraft:item</code>, <code>minecraft:fluid</code>, <code>minecraft:entity_type</code>, and <code>minecraft:game_event</code>)
|-
| Tags
| {{Type|Prefixed Array}} of Tag (See below)
|
|}

A tag looks like this:

{| class="wikitable"
! Field Name
! Field Type
! Notes
|-
| Tag name
| {{Type|Identifier}}
|
|-
| Entries
| {{Type|Prefixed Array}} of {{Type|VarInt}}
| Numeric IDs of the given type (block, item, etc.). This list replaces the previous list of IDs for the given tag. If some preexisting tags are left unmentioned, a warning is printed.
|}

See [[Tag]] on the Minecraft Wiki for more information, including a list of vanilla tags.

==== Projectile Power ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x80</code><br/><br/>''resource:''<br/><code>projectile_power</code>
| rowspan="2"| Play
| rowspan="2"| Client
| Entity ID
| {{Type|VarInt}}
|
|-
| Power
| {{Type|Double}}
|
|}


==== Custom Report Details ====
This packet is sent by the client when closing a window. 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.


Contains a list of key-value text entries that are included in any crash or disconnection report generated during connection to the server.
Note, notchian clients send a close window message with window id 0 to close their inventory even though there is never an Open Window message for inventory.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! colspan="2"| Field Name
! colspan="2"| Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x81</code><br/><br/>''resource:''<br/><code>custom_report_details</code>
| 0x65
| rowspan="2"| Play
| Window id
| rowspan="2"| Client
| byte
| rowspan="2"| Details
| 0
| Title
| This is the id of the window that was closed. 0 for inventory.
| rowspan="2"| {{Type|Prefixed Array}} (32)
|-
| {{Type|String}} (128)
| Total Size:
|
| colspan="4" | 2 bytes
|-
| Description
| {{Type|String}} (4096)
|
|}
|}


==== Server Links ====
{{anchor|0x66}}
=== Click Window (0x66) ===
''Client to Server''


This packet contains a list of links that the vanilla client will display in the menu available from the pause menu. Link labels can be built-in or custom (i.e., any text).
This packet is sent by the player when it clicks on a slot in a window.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! colspan="2"| Field Name
! colspan="2"| Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="3"| ''protocol:''<br/><code>0x82</code><br/><br/>''resource:''<br/><code>server_links</code>
| rowspan="6" | 0x66
| rowspan="3"| Play
| Window id
| rowspan="3"| Client
| byte
| rowspan="3"| Links
| <code>0</code>
| Is built-in
| The id of the window which was clicked. 0 for player inventory.
| rowspan="3"| {{Type|Prefixed Array}}
|-
| {{Type|Boolean}}
| Slot
| Determines if the following label is built-in (from enum) or custom (text component).
| short
|-
| <code>36</code>
| Label
| The clicked slot. See below.
| {{Type|VarInt}} {{Type|Enum}} / {{Type|Text Component}}
|-
| See below.
| Button
|-
| byte
| URL
| <code>1</code>
| {{Type|String}}
| The button used in the click. See below.
| Valid URL.
|-
| Action number
| short
| <code>12</code>
| A unique number for the action, used for transaction handling (See the Transaction packet).
|-
| Mode
| byte
| <code>1</code>
| Inventory operation mode. See below.
|-
| Clicked item
| [[Slot_Data|slot]]
|
|
|-
| Total Size:
| colspan="4" | 8 bytes + slot data
|}
|}


{| class="wikitable"
See [[Inventory#Windows|inventory windows]] for further information about how slots are indexed.
! ID
! Name
! Notes
|-
| 0
| Bug Report
| Displayed on connection error screen; included as a comment in the disconnection report.
|-
| 1
| Community Guidelines
|
|-
| 2
| Support
|
|-
| 3
| Status
|
|-
| 4
| Feedback
|
|-
| 5
| Community
|
|-
| 6
| Website
|
|-
| 7
| Forums
|
|-
| 8
| News
|
|-
| 9
| Announcements
|
|-
|}


=== Serverbound ===
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.


==== Confirm Teleportation ====
The Action number is actually a counter, starting at 1. This number is used by the server as a transaction ID to send back a [[#0x6A|Transaction packet]].

Sent by client as confirmation of [[#Synchronize Player Position|Synchronize Player Position]].


The distinct type of click performed by the client is determined by the combination of the "Mode" and "Button" fields.
{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! Mode
! State
! Bound To
! Button
! Field Name
! Slot
! Field Type
! Trigger
! Notes
|-
|-
! rowspan="2" | 0
| ''protocol:''<br/><code>0x00</code><br/><br/>''resource:''<br/><code>accept_teleportation</code>
| 0
| N/A
| Play
| Server
| Left mouse click
| Teleport ID
|-
| {{Type|VarInt}}
| 1
| The ID given by the [[#Synchronize Player Position|Synchronize Player Position]] packet.
| N/A
|}
| Right mouse click
|-
! rowspan="2" | 1
| 0
| N/A
| Shift + left mouse click
|-
| 1
| N/A
| Shift + right mouse click ''(Identical behavior)''
|-
! rowspan="5" | 2
| 0
| N/A
| Number key 1
|-
| 1
| N/A
| Number key 2
|-
| 2
| N/A
| Number key 3
|-
| ...
| ...
| ...
|-
| 8
| N/A
| Number key 9
|-
! rowspan="1" | 3
| 2
| N/A
| Middle click
|-
! rowspan="4" | 4
| 0
| Not -999
| Drop key (Q)
|-
| 1
| Not -999
| Ctrl + Drop key (Ctrl-Q)
|-
| 0
| -999
| Left click outside inventory holding nothing ''(No-op)''
|-
| 1
| -999
| Right click outside inventory holding nothing ''(No-op)''
|-
! rowspan="6" | 5
| 0
| -999
| Starting left mouse paint ''(Or middle mouse)''
|-
| 4
| -999
| Starting right mouse paint
|-
| 1
| Not -999
| Left mouse painting progress
|-
| 5
| Not -999
| Right mouse painting progress
|-
| 2
| -999
| Ending left mouse paint
|-
| 6
| -999
| Ending right mouse paint
|-
! 6
| 0
| N/A
| Double click
|}


==== Query Block Entity Tag ====
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 items), then holding mouse button (left, right or middle) and dragging holded 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):


Used when <kbd>F3</kbd>+<kbd>I</kbd> is pressed while looking at a block.
# packet with mode 5, slot -999 , button (0 for left | 4 for right);

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x01</code><br/><br/>''resource:''<br/><code>block_entity_tag_query</code>
| rowspan="2"| Play
| rowspan="2"| Server
| Transaction ID
| {{Type|VarInt}}
| An incremental ID so that the client can verify that the response matches.
|-
| Location
| {{Type|Position}}
| The location of the block to check.
|}

==== Bundle Item Selected ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x02</code><br/><br/>''resource:''<br/><code>bundle_item_selected</code>
| rowspan="2"| Play
| rowspan="2"| Server
| Slot of Bundle
| {{Type|VarInt}}
|
|-
| Slot in Bundle
| {{Type|VarInt}}
|
|}

==== Change 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"| ''protocol:''<br/><code>0x03</code><br/><br/>''resource:''<br/><code>change_difficulty</code>
| rowspan="1"| Play
| rowspan="1"| Server
| New difficulty
| {{Type|Unsigned Byte}} {{Type|Enum}}
| 0: peaceful, 1: easy, 2: normal, 3: hard.
|}

==== Acknowledge Message ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x04</code><br/><br/>''resource:''<br/><code>chat_ack</code>
| rowspan="1"| Play
| rowspan="1"| Server
| Message Count
| {{Type|VarInt}}
|
|}

==== Chat Command ====

{{Main|Chat}}

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x05</code><br/><br/>''resource:''<br/><code>chat_command</code>
| rowspan="1"| Play
| rowspan="1"| Server
| colspan="2"| Command
| colspan="2"| {{Type|String}} (32767)
| colspan="2"| The command typed by the client.
|}

==== Signed Chat Command ====

{{Main|Chat}}

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="7"| ''protocol:''<br/><code>0x06</code><br/><br/>''resource:''<br/><code>chat_command_signed</code>
| rowspan="7"| Play
| rowspan="7"| Server
| colspan="2"| Command
| colspan="2"| {{Type|String}} (32767)
| colspan="2"| The command typed by the client.
|-
| colspan="2"| Timestamp
| colspan="2"| {{Type|Long}}
| colspan="2"| The timestamp that the command was executed.
|-
| colspan="2"| Salt
| colspan="2"| {{Type|Long}}
| colspan="2"| The salt for the following argument signatures.
|-
| rowspan="2"| Array of argument signatures
| Argument name
| rowspan="2"| {{Type|Prefixed Array}} (8)
| {{Type|String}} (16)
| The name of the argument that is signed by the following signature.
|-
| Signature
| {{Type|Byte Array}} (256)
| The signature that verifies the argument. Always 256 bytes and is not length-prefixed.
|-
| colspan="2"| Message Count
| colspan="2"| {{Type|VarInt}}
| colspan="2"|
|-
| colspan="2"| Acknowledged
| colspan="2"| {{Type|Fixed BitSet}} (20)
| colspan="2"|
|}

==== Chat Message ====

{{Main|Chat}}

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.

The server will broadcast a [[#Player Chat Message|Player Chat Message]] packet with Chat Type <code>minecraft:chat</code> to all players that haven't disabled chat (including the player that sent the message). See [[Minecraft Wiki:Projects/wiki.vg merge/Chat#Processing chat|Chat#Processing chat]] for more information.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="6"| ''protocol:''<br/><code>0x07</code><br/><br/>''resource:''<br/><code>chat</code>
| rowspan="6"| Play
| rowspan="6"| Server
| Message
| {{Type|String}} (256)
|
|-
| Timestamp
| {{Type|Long}}
|
|-
| Salt
| {{Type|Long}}
| The salt used to verify the signature hash.
|-
| Signature
| {{Type|Prefixed Optional}} {{Type|Byte Array}} (256)
| The signature used to verify the chat message's authentication. When present, always 256 bytes and not length-prefixed.
|-
| Message Count
| {{Type|VarInt}}
|
|-
| Acknowledged
| {{Type|Fixed BitSet}} (20)
|
|}

==== Player Session ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! Field Type
! Notes
|-
| rowspan="4"| ''protocol:''<br/><code>0x08</code><br/><br/>''resource:''<br/><code>chat_session_update</code>
| rowspan="4"| Play
| rowspan="4"| Server
| colspan="2"| Session Id
| {{Type|UUID}}
|
|-
| rowspan="3"| Public Key
| Expires At
| {{Type|Long}}
| The time the play session key expires in [https://en.wikipedia.org/wiki/Unix_time epoch] milliseconds.
|-
| Public Key
| {{Type|Prefixed Array}} (512) of {{Type|Byte}}
| A byte array of an X.509-encoded public key.
|-
| Key Signature
| {{Type|Prefixed Array}} (4096) of {{Type|Byte}}
| The signature consists of the player UUID, the key expiration timestamp, and the public key data. These values are hashed using [https://en.wikipedia.org/wiki/SHA-1 SHA-1] and signed using Mojang's private [https://en.wikipedia.org/wiki/RSA_(cryptosystem) RSA] key.
|}

==== Chunk Batch Received ====

Notifies the server that the chunk batch has been received by the client. The server uses the value sent in this packet to adjust the number of chunks to be sent in a batch.

The vanilla server will stop sending further chunk data until the client acknowledges the sent chunk batch. After the first acknowledgement, the server adjusts this number to allow up to 10 unacknowledged batches.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x09</code><br/><br/>''resource:''<br/><code>chunk_batch_received</code>
| rowspan="1"| Play
| rowspan="1"| Server
| Chunks per tick
| {{Type|Float}}
| Desired chunks per tick.
|}

==== Client Status ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x0A</code><br/><br/>''resource:''<br/><code>client_command</code>
| rowspan="1"| Play
| rowspan="1"| Server
| Action ID
| {{Type|VarInt}} {{Type|Enum}}
| See below
|}

''Action ID'' values:

{| class="wikitable"
|-
! Action ID
! Action
! Notes
|-
| 0
| Perform respawn
| Sent when the client is ready to respawn after death.
|-
| 1
| Request stats
| Sent when the client opens the Statistics menu.
|}

==== Client Tick End ====

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| ''protocol:''<br/><code>0x0B</code><br/><br/>''resource:''<br/><code>client_tick_end</code>
| Play
| Server
| colspan="3"| ''no fields''
|}

==== Client Information (play) ====

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

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="9"| ''protocol:''<br/><code>0x0C</code><br/><br/>''resource:''<br/><code>client_information</code>
| rowspan="9"| Play
| rowspan="9"| Server
| Locale
| {{Type|String}} (16)
| e.g. <code>en_GB</code>.
|-
| View Distance
| {{Type|Byte}}
| Client-side render distance, in chunks.
|-
| Chat Mode
| {{Type|VarInt}} {{Type|Enum}}
| 0: enabled, 1: commands only, 2: hidden. See [[Minecraft Wiki:Projects/wiki.vg merge/Chat#Client chat mode|Chat#Client chat mode]] for more information.
|-
| Chat Colors
| {{Type|Boolean}}
| “Colors” multiplayer setting. The vanilla server stores this value but does nothing with it (see [https://bugs.mojang.com/browse/MC-64867 MC-64867]). Third-party servers such as Hypixel disable all coloring in chat and system messages when it is false.
|-
| Displayed Skin Parts
| {{Type|Unsigned Byte}}
| Bit mask, see below.
|-
| Main Hand
| {{Type|VarInt}} {{Type|Enum}}
| 0: Left, 1: Right.
|-
| Enable text filtering
| {{Type|Boolean}}
| Enables filtering of text on signs and written book titles. The vanilla client sets this according to the <code>profanityFilterPreferences.profanityFilterOn</code> account attribute indicated by the [[Minecraft Wiki:Projects/wiki.vg merge/Mojang API#Player Attributes|<code>/player/attributes</code> Mojang API endpoint]]. In offline mode it is always false.
|-
| Allow server listings
| {{Type|Boolean}}
| Servers usually list online players, this option should let you not show up in that list.
|-
| Particle Status
| {{Type|VarInt}} {{Type|Enum}}
| 0: all, 1: decreased, 2: minimal
|}

''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.

==== Command Suggestions Request ====

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

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x0D</code><br/><br/>''resource:''<br/><code>command_suggestion</code>
| rowspan="2"| Play
| rowspan="2"| Server
| Transaction Id
| {{Type|VarInt}}
| The id of the transaction that the server will send back to the client in the response of this packet. Client generates this and increments it each time it sends another tab completion that doesn't get a response.
|-
| Text
| {{Type|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).
|}

==== Acknowledge Configuration ====

Sent by the client upon receiving a [[#Start Configuration|Start Configuration]] packet from the server.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x0E</code><br/><br/>''resource:''<br/><code>configuration_acknowledged</code>
| rowspan="1"| Play
| rowspan="1"| Server
| colspan="3"| ''no fields''
|}

This packet switches the connection state to [[#Configuration|configuration]].

==== Click Container Button ====

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

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x0F</code><br/><br/>''resource:''<br/><code>container_button_click</code>
| rowspan="2"| Play
| rowspan="2"| Server
| Window ID
| {{Type|VarInt}}
| The ID of the window sent by [[#Open Screen|Open Screen]].
|-
| Button ID
| {{Type|VarInt}}
| Meaning depends on window type; see below.
|}

{| class="wikitable"
! Window type
! ID
! Meaning
|-
| rowspan="3"| Enchantment Table
| 0 || Topmost enchantment.
|-
| 1 || Middle enchantment.
|-
| 2 || Bottom enchantment.
|-
| rowspan="4"| Lectern
| 1 || Previous page (which does give a redstone output).
|-
| 2 || Next page.
|-
| 3 || Take Book.
|-
| 100+page || Opened page number - 100 + number.
|-
| Stonecutter
| colspan="2"| Recipe button number - 4*row + col. Depends on the item.
|-
| Loom
| colspan="2"| Recipe button number - 4*row + col. Depends on the item.
|}

==== Click Container ====

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

{| class="wikitable"
! Packet ID
! State
! Bound To
! colspan="2"| Field Name
! colspan="2"| Field Type
! Notes
|-
| rowspan="8"| ''protocol:''<br/><code>0x10</code><br/><br/>''resource:''<br/><code>container_click</code>
| rowspan="8"| Play
| rowspan="8"| Server
| colspan="2"| Window ID
| colspan="2"| {{Type|VarInt}}
| The ID of the window which was clicked. 0 for player inventory. The server ignores any packets targeting a Window ID other than the current one, including ignoring 0 when any other window is open.
|-
| colspan="2"| State ID
| colspan="2"| {{Type|VarInt}}
| The last received State ID from either a [[#Set Container Slot|Set Container Slot]] or a [[#Set Container Content|Set Container Content]] packet.
|-
| colspan="2"| Slot
| colspan="2"| {{Type|Short}}
| The clicked slot number, see below.
|-
| colspan="2"| Button
| colspan="2"| {{Type|Byte}}
| The button used in the click, see below.
|-
| colspan="2"| Mode
| colspan="2"| {{Type|VarInt}} {{Type|Enum}}
| Inventory operation mode, see below.
|-
| rowspan="2"| Array of changed slots
| Slot number
| rowspan="2"| {{Type|Prefixed Array}} (128)
| {{Type|Short}}
|
|-
| Slot data
| {{Type|Slot}}
| New data for this slot, in the client's opinion; see below.
|-
| colspan="2"| Carried item
| colspan="2"| [[Minecraft Wiki:Projects/wiki.vg merge/Slot Data|Slot]]
| Item carried by the cursor. Has to be empty (item ID = -1) for drop mode, otherwise nothing will happen.
|}

See [[Minecraft Wiki:Projects/wiki.vg merge/Inventory|Inventory]] for further information about how slots are indexed.

After performing the action, the server compares the results to the slot change information included in the packet, as applied on top of the server's view of the container's state prior to the action. For any slots that do not match, it sends [[#Set Container Slot|Set Container Slot]] packets containing the correct results. If State ID does not match the last ID sent by the server, it will instead send a full [[#Set Container Content|Set Container Content]] to resynchronize the client.

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="4"| 0
| 0
| Normal
| Left mouse click
|-
| 1
| Normal
| Right mouse click
|-
| 0
| -999
| Left click outside inventory (drop cursor stack)
|-
| 1
| -999
| Right click outside inventory (drop cursor single item)
|-
! rowspan="2"| 1
| 0
| Normal
| Shift + left mouse click
|-
| 1
| Normal
| Shift + right mouse click ''(identical behavior)''
|-
! rowspan="7"| 2
| 0
| Normal
| Number key 1
|-
| 1
| Normal
| Number key 2
|-
| 2
| Normal
| Number key 3
|-
| ⋮
| ⋮
| ⋮
|-
| 8
| Normal
| Number key 9
|-
| ⋮
| ⋮
| Button is used as the slot index (impossible in vanilla clients)
|-
| 40
| Normal
| Offhand swap key F
|-
! 3
| 2
| Normal
| Middle click, only defined for creative players in non-player inventories.
|-
! rowspan="2"| 4
| 0
| Normal
| Drop key (Q)
|-
| 1
| Normal
| Control + Drop key (Q)
|-
! 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.
|-
| 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.
|-
| 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.
|-
! rowspan="2"| 6
| 0
| Normal
| Double click
|-
| 1
| Normal
| Pickup all but check items in reverse order (impossible in vanilla clients)
|}

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 for every slot painted on, mode is still 5, button (1 | 5);
# packet with mode 5, slot -999, button (2 | 6);
# 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.
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.


==== Close Container ====
{{anchor|0x67}}


This packet is sent by the client when closing a window.
=== Set Slot (0x67) ===
''Server to Client''


vanilla clients send a Close Window packet with Window ID 0 to close their inventory even though there is never an [[#Open Screen|Open Screen]] packet for the inventory.
Sent by the server when an item in a slot (in a window) is added/removed.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x11</code><br/><br/>''resource:''<br/><code>container_close</code>
| rowspan="3" | 0x67
| rowspan="1"| Play
| Window id
| rowspan="1"| Server
| byte
| Window ID
| <code>0</code>
| {{Type|VarInt}}
| 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).
| This is the ID of the window that was closed. 0 for player inventory.
|-
|}
| Slot
| short
| <code>36</code>
| The slot that should be updated
|-
| Slot data
| [[Slot_Data|slot]]
|
|
|-
| Total Size:
| colspan="4" | 4 bytes + slot data
|}


==== Change Container Slot State ====
Note that if window ID and slot are both -1, it means the item currently attached to the cursor.


This packet is sent by the client when toggling the state of a Crafter.
See [[Inventory#Windows|inventory windows]] for further information about how slots are indexed.


{| class="wikitable"
Slots: [http://gyazo.com/9d52e1fd4dc14790ec66eab4a9aee00e.png]
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x12</code><br/><br/>''resource:''<br/><code>container_slot_state_changed</code>
| rowspan="3"| Play
| rowspan="3"| Server
| Slot ID
| {{Type|VarInt}}
| This is the ID of the slot that was changed.
|-
| Window ID
| {{Type|VarInt}}
| This is the ID of the window that was changed.
|-
| State
| {{Type|Boolean}}
| The new state of the slot. True for enabled, false for disabled.
|}


==== Cookie Response (play) ====
{{anchor|0x68}}
=== Set Window Items (0x68) ===
''Server to Client''


Response to a [[#Cookie_Request_(play)|Cookie Request (play)]] from the server. The vanilla server only accepts responses of up to 5 kiB in size.
[[File:Inventory-slots.png|thumb|The inventory slots]]


{| class="wikitable"
Sent by the server when an item in a slot (in a window) is added/removed. This includes the main inventory, equipped armour and crafting slots.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x13</code><br/><br/>''resource:''<br/><code>cookie_response</code>
| rowspan="2"| Play
| rowspan="2"| Server
| Key
| {{Type|Identifier}}
| The identifier of the cookie.
|-
| Payload
| {{Type|Prefixed Optional}} {{Type|Prefixed Array}} (5120) of {{Type|Byte}}
| The data of the cookie.
|}

==== Serverbound Plugin Message (play) ====

{{Main|Minecraft Wiki:Projects/wiki.vg merge/Plugin channels}}

Mods and plugins can use this to send their data. Minecraft itself uses some [[Minecraft Wiki:Projects/wiki.vg merge/Plugin channels|plugin channels]]. These internal channels are in the <code>minecraft</code> namespace.

More documentation on this: [https://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/ https://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"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x14</code><br/><br/>''resource:''<br/><code>custom_payload</code>
| rowspan="3" | 0x68
| rowspan="2"| Play
| Window id
| rowspan="2"| Server
| byte
| Channel
| <code>1</code>
| {{Type|Identifier}}
| The id of window which items are being sent for. 0 for player inventory.
| Name of the [[Minecraft Wiki:Projects/wiki.vg merge/Plugin channels|plugin channel]] used to send the data.
|-
|-
| Count
| short
| Data
| {{Type|Byte Array}} (32767)
| <code>4</code>
| Any data, depending on the channel. <code>minecraft:</code> channels are documented [[Minecraft Wiki:Projects/wiki.vg merge/Plugin channels|here]]. The length of this array must be inferred from the packet length.
| The number of slots (see below)
|-
|}
| Slot data
| array of [[Slot_Data|slot]]s
|
|
|-
| Total Size:
| colspan="4" | 4 bytes + size of slot data array
|}


In vanilla servers, the maximum data length is 32767 bytes.
See [[Inventory#Windows|inventory windows]] for further information about how slots are indexed.


==== Debug Sample Subscription ====
{{anchor|0x69}}

=== Update Window Property (0x69) ===
Subscribes to the specified type of debug sample data, which is then sent periodically to the client via [[#Debug_Sample|Debug Sample]].
''Server to Client''

The subscription is retained for 10 seconds (the vanilla server checks that both 10.001 real-time seconds and 201 ticks have elapsed), after which the client is automatically unsubscribed. The vanilla client resends this packet every 5 seconds to keep up the subscription.

The vanilla server only allows subscriptions from players that are server operators.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x15</code><br/><br/>''resource:''<br/><code>debug_sample_subscription</code>
| rowspan="3" | 0x69
| rowspan="1"| Play
| Window id
| rowspan="1"| Server
| byte
| Sample Type
| 2
| {{Type|VarInt}} {{Type|Enum}}
| The id of the window.
| The type of debug sample to subscribe to. Can be one of the following:
|-
* 0 - Tick time
| Property
|}
| short
| 1
| Which property should be updated.
|-
| Value
| short
| 650
| The new value for the property.
|-
| Total Size:
| colspan="4" | 6 bytes
|}


==== Edit Book ====
'''Furnace'''


{| class="wikitable"
Properties:
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x16</code><br/><br/>''resource:''<br/><code>edit_book</code>
| rowspan="3"| Play
| rowspan="3"| Server
| Slot
| {{Type|VarInt}}
| The hotbar slot where the written book is located
|-
| Entries
| {{Type|Prefixed Array}} (100) of {{Type|String}} (1024)
| Text from each page. Maximum string length is 1024 chars.
|-
| Title
| {{Type|Prefixed Optional}} {{Type|String}} (32)
| Title of book. Present if book is being signed, not present if book is being edited.
|}


==== Query Entity Tag ====
* 0: Progress arrow
* 1: Fire icon (fuel)


Used when <kbd>F3</kbd>+<kbd>I</kbd> is pressed while looking at an entity.
Values:


{| class="wikitable"
* 0-200 for progress arrow
! Packet ID
* 0-200 for fuel indicator
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x17</code><br/><br/>''resource:''<br/><code>entity_tag_query</code>
| rowspan="2"| Play
| rowspan="2"| Server
| Transaction ID
| {{Type|VarInt}}
| An incremental ID so that the client can verify that the response matches.
|-
| Entity ID
| {{Type|VarInt}}
| The ID of the entity to query.
|}


==== Interact ====
Ranges are presumably in in-game ticks


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


A vanilla 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.
Properties: 0, 1 or 2 depending on the "enchantment slot" being given.


The target X, Y, and Z fields represent the difference between the vector location of the cursor at the time of the packet and the entity's position.
Values: The enchantment's level.


Note that middle-click in creative mode is interpreted by the client and sent as a [[#Set Creative Mode Slot|Set Creative Mode Slot]] packet instead.
{{anchor|0x6A}}
=== Confirm Transaction (0x6A) ===
''Two-Way''


{| class="wikitable"
A packet from the server indicating whether a request from the client was accepted, or whether there was a conflict (due to lag). This packet is also sent from the client to the server in response to a server transaction rejection packet.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="7"| ''protocol:''<br/><code>0x18</code><br/><br/>''resource:''<br/><code>interact</code>
| rowspan="7"| Play
| rowspan="7"| Server
| Entity ID
| {{Type|VarInt}}
| The ID of the entity to interact. Note the special case described below.
|-
| Type
| {{Type|VarInt}} {{Type|Enum}}
| 0: interact, 1: attack, 2: interact at.
|-
| Target X
| {{Type|Optional}} {{Type|Float}}
| Only if Type is interact at.
|-
| Target Y
| {{Type|Optional}} {{Type|Float}}
| Only if Type is interact at.
|-
| Target Z
| {{Type|Optional}} {{Type|Float}}
| Only if Type is interact at.
|-
| Hand
| {{Type|Optional}} {{Type|VarInt}} {{Type|Enum}}
| Only if Type is interact or interact at; 0: main hand, 1: off hand.
|-
| Sneak Key Pressed
| {{Type|Boolean}}
| If the client is pressing the sneak key. Has the same effect as a Player Command Press/Release sneak key preceding the interaction, and the state is permanently changed.
|}

Interaction with the ender dragon is an odd special case characteristic of release deadline&ndash;driven design. 8 consecutive entity IDs following the dragon's ID (<var>id</var> + 1, <var>id</var> + 2, ..., <var>id</var> + 8) are reserved for the 8 hitboxes that make up the dragon:


{| class="wikitable"
{| class="wikitable"
! ID offset
|-
! Description
| Packet ID
|-
| Field Name
| 0
| Field Type
| The dragon itself (never used in this packet)
| Example
|-
| Notes
|-
| 1
| Head
| rowspan="3" | 0x6A
|-
| Window id
| byte
| 2
| 0
| Neck
|-
| The id of the window that the action occurred in.
|-
| 3
| Body
| Action number
|-
| short
| 12
| 4
| Tail 1
| Every action that is to be accepted has a unique number. This field corresponds to that number.
|-
|-
| 5
| Accepted?
| Tail 2
| boolean
|-
| true
| 6
| Whether the action was accepted.
| Tail 3
|-
|-
| Total Size:
| 7
| colspan="4" | 5 bytes
| Wing 1
|}
|-
| 8
| Wing 2
|}


==== Jigsaw Generate ====
{{anchor|0x6B}}

=== Creative Inventory Action (0x6B) ===
Sent when Generate is pressed on the [[Jigsaw Block]] interface.
''Two-Way''

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x19</code><br/><br/>''resource:''<br/><code>jigsaw_generate</code>
| rowspan="3"| Play
| rowspan="3"| Server
| Location
| {{Type|Position}}
| Block entity location.
|-
| Levels
| {{Type|VarInt}}
| Value of the levels slider/max depth to generate.
|-
| Keep Jigsaws
| {{Type|Boolean}}
|
|}


==== Serverbound Keep Alive (play) ====
While the user is in the standard inventory (i.e., not a crafting bench) on a creative-mode server then the server will send this packet:


The server will frequently send out a keep-alive (see [[#Clientbound Keep Alive (play)|Clientbound Keep Alive]]), each containing a random ID. The client must respond with the same packet.
* <div class="li"> If an item is dropped into the quick bar</div>
* If an item is picked up from the quick bar (item id is -1)


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x1A</code><br/><br/>''resource:''<br/><code>keep_alive</code>
| rowspan="2" | 0x6B
| rowspan="1"| Play
| Slot
| rowspan="1"| Server
| short
| Keep Alive ID
| 36
| {{Type|Long}}
| Inventory slot
|-
|
|}
| Clicked item
| [[Slot_Data|slot]]
|
|
|-
| Total Size:
| colspan="4" | 3 bytes + slot data
|}


==== Lock Difficulty ====
{{anchor|0x6C}}

=== Enchant Item (0x6C) ===
Must have at least op level 2 to use. Appears to only be used on singleplayer; the difficulty buttons are still disabled in multiplayer.
''Client to Server''


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x1B</code><br/><br/>''resource:''<br/><code>lock_difficulty</code>
| rowspan="2" | 0x6C
| rowspan="1"| Play
| Window ID
| rowspan="1"| Server
| byte
| 1
| Locked
| {{Type|Boolean}}
| The ID sent by [[#0x64|Open Window]]
|-
|
|}
| Enchantment
| byte
| 0
| The position of the enchantment on the enchantment table window, starting with 0 as the topmost one.
|-
| Total Size:
| colspan="4" | 3 bytes
|}


==== Set Player Position ====
{{anchor|0x82}}

=== Update Sign (0x82) ===
Updates the player's XYZ position on the server.
''Two-Way''

If the player is in a vehicle, the position is ignored (but in case of [[#Set Player Position and Rotation|Set Player Position and Rotation]], the rotation is still used as normal). No validation steps other than value range clamping are performed in this case.

If the player is sleeping, the position (or rotation) is not changed, and a [[#Synchronize Player Position|Synchronize Player Position]] is sent if the received position deviated from the server's view by more than a meter.

The vanilla server silently clamps the x and z coordinates between -30,000,000 and 30,000,000, and the y coordinate between -20,000,000 and 20,000,000. A similar condition has historically caused a kick for "Illegal position"; this is no longer the case. However, infinite or NaN coordinates (or angles) still result in a kick for <code>multiplayer.disconnect.invalid_player_movement</code>.

As of 1.20.6, checking for moving too fast is achieved like this (sic):

* Each server tick, the player's current position is stored.
* When the player moves, the offset from the stored position to the requested position is computed (&Delta;x, &Delta;y, &Delta;z).
* The requested movement distance squared is computed as &Delta;x&sup2; + &Delta;y&sup2; + &Delta;z&sup2;.
* The baseline expected movement distance squared is computed based on the player's server-side velocity as Vx&sup2; + Vy&sup2; + Vz&sup2;. The player's server-side velocity is a somewhat ill-defined quantity that includes among other things gravity, jump velocity and knockback, but ''not'' regular horizontal movement. A proper description would bring much of Minecraft's physics engine with it. It is accessible as the <code>Motion</code> NBT tag on the player entity.
* The maximum permitted movement distance squared is computed as 100 (300 if the player is using an elytra), multiplied by the number of movement packets received since the last tick, including this one, unless that value is greater than 5, in which case no multiplier is applied.
* If the requested movement distance squared minus the baseline distance squared is more than the maximum squared, the player is moving too fast.

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

Checking for block collisions is achieved like this:

* A temporary collision-checked move of the player is attempted from its current position to the requested one.
* The offset from the resulting position to the requested position is computed. If the absolute value of the offset on the y axis is less than 0.5, it (only the y component) is rounded down to 0.
* If the magnitude of the offset is greater than 0.25 and the player isn't in creative or spectator mode, it is logged that "<player> moved wrongly!", and the player is teleported back to their current (before this packet) server-side position.
* In addition, if the player's hitbox stationary at the requested position would intersect with a block, and they aren't in spectator mode, they are teleported back without a log message.

Checking for illegal flight is achieved like this:

* When a movement packet is received, a flag indicating whether or not the player is floating mid-air is updated. The flag is set if the move test described above detected no collision below the player ''and'' the y component of the offset from the player's current position to the requested one is greater than -0.5, unless any of various conditions permitting flight (creative mode, elytra, levitation effect, etc., but not jumping) are met.
* Each server tick, it is checked if the flag has been set for more than 80 consecutive ticks. If so, and the player isn't currently sleeping, dead or riding a vehicle, they are kicked for <code>multiplayer.disconnect.flying</code>.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="4"| ''protocol:''<br/><code>0x1C</code><br/><br/>''resource:''<br/><code>move_player_pos</code>
| rowspan="7" | 0x82
| rowspan="4"| Play
| X
| rowspan="4"| Server
| int
| 128
| X
| {{Type|Double}}
| Block X Coordinate
| Absolute position.
|-
| Y
|-
| short
| Feet Y
| {{Type|Double}}
| 0
| Absolute feet position, normally Head Y - 1.62.
| Block Y Coordinate
|-
|-
| Z
| Z
| {{Type|Double}}
| int
| Absolute position.
| -128
|-
| Block Z Coordinate
| Flags
|-
| {{Type|Byte}}
| Text1
| Bit field: 0x01: on ground, 0x02: pushing against wall.
| string
|}
| <code>First line</code>
| First line of text in the sign
|-
| Text2
| string
| <code>Second line</code>
| Second line of text in the sign
|-
| Text3
| string
| <code>Third line</code>
| Third line of text in the sign
|-
| Text4
| string
| <code>Fourth line</code>
| Fourth line of text in the sign
|-
| Total Size:
| colspan="4" | 11 bytes + 4 strings
|}


==== Set Player Position and Rotation ====
This message is sent from the server to the client whenever a sign is discovered or created. This message is sent from the client to the server when the "Done" button is pushed after placing a sign. This message is NOT sent when a sign is destroyed or unloaded.


A combination of [[#Set Player Rotation|Move Player Rotation]] and [[#Set Player Position|Move Player Position]].
{{anchor|0x83}}
=== Item Data (0x83) ===
''Server to Client''


{| class="wikitable"
Sent to specify complex data on an item; currently used only for maps.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="6"| ''protocol:''<br/><code>0x1D</code><br/><br/>''resource:''<br/><code>move_player_pos_rot</code>
| rowspan="6"| Play
| rowspan="6"| Server
| X
| {{Type|Double}}
| Absolute position.
|-
| Feet Y
| {{Type|Double}}
| Absolute feet position, normally Head Y - 1.62.
|-
| Z
| {{Type|Double}}
| Absolute position.
|-
| Yaw
| {{Type|Float}}
| Absolute rotation on the X Axis, in degrees.
|-
| Pitch
| {{Type|Float}}
| Absolute rotation on the Y Axis, in degrees.
|-
| Flags
| {{Type|Byte}}
| Bit field: 0x01: on ground, 0x02: pushing against wall.
|}

==== Set 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"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="3"| ''protocol:''<br/><code>0x1E</code><br/><br/>''resource:''<br/><code>move_player_rot</code>
| rowspan="4" | 0x83
| rowspan="3"| Play
| Item Type
| rowspan="3"| Server
| short
| Yaw
| <code>358</code>
| {{Type|Float}}
| Type of item being modified
| Absolute rotation on the X Axis, in degrees.
|-
|-
| Item ID
| short
| Pitch
| {{Type|Float}}
| <code>0</code>
| Absolute rotation on the Y Axis, in degrees.
| The ID (damage value) of the item being modified
|-
|-
| Flags
| Text length
| {{Type|Byte}}
| short
| Bit field: 0x01: on ground, 0x02: pushing against wall.
| <code>35</code>
|}
| Length of following byte array
|-
| Text
| byte array
| {0,0,0,20,20,20,20,20}
| ASCII text.
|-
| Total Size:
| colspan="4" | 7 bytes + Text length
|}


==== Set Player Movement Flags ====
'''Maps'''
If the first byte of the text is 0, the next two bytes are X start and Y start and the rest of the bytes are the colors in that column.


This packet as well as [[#Set Player Position|Set Player Position]], [[#Set Player Rotation|Set Player Rotation]], and [[#Set Player Position and Rotation|Set Player Position and Rotation]] are called the “serverbound movement packets”. Vanilla clients will send Move Player Position once every 20 ticks even for a stationary player.
If the first byte of the text is 1, the rest of the bytes are in groups of three: (data, x, y). The lower half of the data is the type (always 0 under vanilla) and the upper half is the direction.


This packet is used to indicate whether the player is on ground (walking/swimming), or airborne (jumping/falling).
{{anchor|0x84}}
=== Update Tile Entity (0x84) ===
''Server to Client''


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.
Essentially a block update on a tile entity.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x1F</code><br/><br/>''resource:''<br/><code>move_player_status_only</code>
| rowspan="6" | 0x84
| rowspan="1"| Play
| X
| rowspan="1"| Server
| int
| Flags
|
| {{Type|Byte}}
|
| Bit field: 0x01: on ground, 0x02: pushing against wall.
|-
| Y
|}
| short
|
|
|-
| Z
| int
|
|
|-
| Action
| byte
|
| The type of update to perform
|-
| Data length
| Short
|
| Varies
|-
| NBT Data
| Byte Array
|
| Present if data length > 0. Compressed with [[wikipedia:Gzip|gzip]]. Varies
|-
| Total Size:
| colspan="4" | 12 + itemstack bytes
|}


==== Move Vehicle ====
'''Actions'''


Sent when a player moves in a vehicle. Fields are the same as in [[#Set Player Position and Rotation|Set Player Position and Rotation]]. Note that all fields use absolute positioning and do not allow for relative positioning.
* '''1''': Set mob displayed inside a mob spawner. Custom 1 contains the [[Entities#Mobs|mob type]]


{| class="wikitable"
{{anchor|0x85}}
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="6"| ''protocol:''<br/><code>0x20</code><br/><br/>''resource:''<br/><code>move_vehicle</code>
| rowspan="6"| Play
| rowspan="6"| Server
| X
| {{Type|Double}}
| Absolute position (X coordinate).
|-
| Y
| {{Type|Double}}
| Absolute position (Y coordinate).
|-
| Z
| {{Type|Double}}
| Absolute position (Z coordinate).
|-
| Yaw
| {{Type|Float}}
| Absolute rotation on the vertical axis, in degrees.
|-
| Pitch
| {{Type|Float}}
| Absolute rotation on the horizontal axis, in degrees.
|-
| On Ground
| {{Type|Boolean}}
| ''(This value does not seem to exist)''
|}


=== Tile Editor Open? (0x85) ===
==== Paddle Boat ====
''Server to Client''


Used to ''visually'' update whether boat paddles are turning. The server will update the [[Minecraft Wiki:Projects/wiki.vg merge/Entity_metadata#Boat|Boat entity metadata]] to match the values here.
Sent on placement of sign.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x21</code><br/><br/>''resource:''<br/><code>paddle_boat</code>
| rowspan="4" | 0x85
| rowspan="2"| Play
| Tile Entity Id
| rowspan="2"| Server
| byte
| Left paddle turning
| <code>0</code>
| {{Type|Boolean}}
| Always seems to be 0 (TileEntitySign)
|-
|
| X
|-
| Right paddle turning
| int
| {{Type|Boolean}}
| <code>70</code>
|
| X in block coordinates
|-
|}

| Y
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 held.
| int
| <code>70</code>
| Y in block coordinates
|-
| Z
| int
| <code>-46</code>
| Z in block coordinates
|-
| Total Size:
| colspan="4" | 14 bytes
|}


==== Pick Item From Block ====
{{anchor|0xC8}}


Used for pick block functionality (middle click) on blocks to retrieve items from the inventory in survival or creative mode or create them in creative mode. See [[Controls#Pick_Block]] for more information.
=== Increment Statistic (0xC8) ===
''Server to Client''


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x22</code><br/><br/>''resource:''<br/><code>pick_item_from_block</code>
| rowspan="2" | 0xC8
| rowspan="2"| Play
| Statistic ID
| rowspan="2"| Server
| int
| Location
| 1003
| {{Type|Position}}
| The ID of the statistic. See [http://www.minecraftwiki.net/wiki/Statistics List of statistics].
| The location of the block.
|-
|-
| Amount
| Include Data
| '''int'''
| {{Type|Boolean}}
| 1
| Used to tell the server to include block data in the new stack, works only if in creative mode.
| The amount to increment the statistic.
|-
|}
| Total Size:
| colspan="4" | 9 bytes
|}


==== Pick Item From Entity ====
{{anchor|0xC9}}


Used for pick block functionality (middle click) on entities to retrieve items from the inventory in survival or creative mode or create them in creative mode. See [[Controls#Pick_Block]] for more information.
=== Player List Item (0xC9) ===
''Server to Client''


{| class="wikitable"
Sent by the notchian server to update the user list (<tab> in the client). The server sends one packet per user per tick, amounting to 20 packets/s for 1 online user, 40 for 2, and so forth.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x23</code><br/><br/>''resource:''<br/><code>pick_item_from_entity</code>
| rowspan="2"| Play
| rowspan="2"| Server
| Entity ID
| {{Type|VarInt}}
| The ID of the entity to pick.
|-
| Include Data
| {{Type|Boolean}}
| Unused by the vanilla server.
|}

==== Ping Request (play) ====


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x24</code><br/><br/>''resource:''<br/><code>ping_request</code>
| rowspan="3" | 0xC9
| rowspan="1"| Play
| Player name
| rowspan="1"| Server
| string
| Payload
| barneygale
| {{Type|Long}}
| Supports chat colouring, limited to 16 characters.
| May be any number. vanilla clients use a system-dependent time value which is counted in milliseconds.
|-
|}
| Online
| boolean
| true
| If false, the client will remove the user from the list.
|-
| Ping
| short
| 193
| Ping, presumably in ms.
|-
| Total Size:
| colspan="4" | 6 bytes + length of string
|}


==== Place Recipe ====
{{anchor|0xCA}}
=== Player Abilities (0xCA) ===
''Two-Way''


This packet is sent when a player clicks a recipe in the crafting book that is craftable (white border).
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.
The flags are whether damage is disabled (god mode, 8, bit 3), whether the player can fly (4, bit 2), whether the player is flying (2, bit 1), and whether the player is in creative mode (1, bit 0).
To get the values of these booleans, simply AND (&) the byte with 1,2,4 and 8 respectively, to get the 0 or 1 bitwise value. To set them OR (|) them with their repspective masks.
The vanilla client sends this packet when the player starts/stops flying with the second parameter changed accordingly. All other parameters are ignored by the vanilla server.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="3"| ''protocol:''<br/><code>0x25</code><br/><br/>''resource:''<br/><code>place_recipe</code>
| rowspan="3" | 0xCA
| rowspan="3"| Play
| Flags
| rowspan="3"| Server
| byte
| Window ID
| 5
| {{Type|VarInt}}
|
|-
|
|-
| Flying speed*
| Recipe ID
| '''float'''
| {{Type|VarInt}}
| '''0.05'''
| ID of recipe previously defined in [[#Recipe Book Add|Recipe Book Add]].
| previous integer value divided by 250
|-
|-
| Make all
| Walking speed*
| {{Type|Boolean}}
| '''float'''
| Affects the amount of items processed; true if shift is down when clicked.
| '''0.1'''
|}
| previous integer value divided by 250
|-
| Total Size:
| colspan="4" | 10 bytes
|}


==== Player Abilities (serverbound) ====
The client ignores the walking speed and flying speed fields. Send an 0x2C packet as well.


The vanilla client sends this packet when the player starts/stops flying with the Flags parameter changed accordingly.
{{anchor|0xCB}}
=== Tab-complete (0xCB) ===
''Two-way''


{| class="wikitable"
Sent C->S when the user presses [tab] while writing text. The payload contains all text behind the cursor.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x26</code><br/><br/>''resource:''<br/><code>player_abilities</code>
| rowspan="1"| Play
| rowspan="1"| Server
| Flags
| {{Type|Byte}}
| Bit mask. 0x02: is flying.
|}


==== Player Action ====
The server responds with an auto-completion 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.


Sent when the player mines a block. A vanilla server only accepts digging packets with coordinates within a 6-unit radius between the center of the block and the player's eyes.
In the event of more than one possible completion, the server responds with the options packed into the single string field, separated by a null character. Note that as strings are UTF-16, this is two bytes wide.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="4"| ''protocol:''<br/><code>0x27</code><br/><br/>''resource:''<br/><code>player_action</code>
| 0xCB
| rowspan="4"| Play
| Text
| rowspan="4"| Server
| string
| Status
|
| {{Type|VarInt}} {{Type|Enum}}
|
| The action the player is taking against the block (see below).
|-
|-
| Total Size:
| Location
| colspan="4" | 3 bytes + length of string
| {{Type|Position}}
|}
| Block position.
|-
| Face
| {{Type|Byte}} {{Type|Enum}}
| The face being hit (see below).
|-
| Sequence
| {{Type|VarInt}}
| Block change sequence number (see [[#Acknowledge Block Change]]).
|}


Status can be one of seven values:
{{anchor|0xCC}}
=== Client Settings (0xCC) ===
''Client to server''


{| class="wikitable"
Sent when the player connects, or when settings are changed.
! Value
! Meaning
! Notes
|-
| 0
| Started digging
| Sent when the player starts digging a block. If the block was instamined or the player is in creative mode, the client will ''not'' send Status = Finished digging, and will assume the server completed the destruction. To detect this, it is necessary to [[Breaking#Speed|calculate the block destruction speed]] server-side.
|-
| 1
| Cancelled digging
| Sent when the player lets go of the Mine Block key (default: left click). Face is always set to -Y.
|-
| 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: Control or Command, depending on OS). Location is always set to 0/0/0, Face is always set to -Y. Sequence is always set to 0.
|-
| 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. Sequence is always set to 0.
|-
| 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. Sequence is always set to 0.
|-
| 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. Sequence is always set to 0.
|}

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


{| class="wikitable"
{| class="wikitable"
|-
|-
! Value
| Packet ID
! Offset
| Field Name
! Face
| Field Type
|-
| Example
| Notes
| 0
|-
| -Y
| Bottom
| rowspan="5" | 0xCC
|-
| Locale
| string
| 1
| en_GB
| +Y
| Top
|
|-
|-
| 2
| View distance
| byte
| -Z
| 0
| North
|-
| 0-3 for 'far', 'normal', 'short', 'tiny'.
|-
| 3
| +Z
| Chat flags
| byte
| South
| 8
|-
| 4
| Chat settings. See notes below.
|-
| -X
| West
| Difficulty
|-
| byte
| 0
| 5
| +X
| Client-side difficulty from options.txt
| East
|-
|}
| Show Cape
| boolean
| true
| Client-side "show cape" option
|-
| Total Size:
| colspan="4" | 7 bytes + length of string
|}


==== Player Command ====
Chat flags has several values packed into one byte.


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.
'''Chat Enabled:''' Bits 0-1. 00: Enabled. 01: Commands only. 10: Hidden.


{| class="wikitable"
'''Colors Enabled:''' Bit 3. 0: Disabled. 1: Enabled.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x28</code><br/><br/>''resource:''<br/><code>player_command</code>
| rowspan="3"| Play
| rowspan="3"| Server
| Entity ID
| {{Type|VarInt}}
| Player ID (ignored by the vanilla server)
|-
| Action ID
| {{Type|VarInt}} {{Type|Enum}}
| The ID of the action, see below.
|-
| Jump Boost
| {{Type|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:
{{anchor|0xCD}}
=== Client Statuses (0xCD) ===
''Client to server''


{| class="wikitable"
Sent when the client is ready to complete login and when the client is ready to respawn after death.
! ID
! Action
|-
| 0
| Press sneak key
|-
| 1
| Release sneak key
|-
| 2
| Leave bed
|-
| 3
| Start sprinting
|-
| 4
| Stop sprinting
|-
| 5
| Start jump with horse
|-
| 6
| Stop jump with horse
|-
| 7
| Open vehicle 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 in the morning.

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

==== Player Input ====


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x29</code><br/><br/>''resource:''<br/><code>player_input</code>
| rowspan="1" | 0xCD
| rowspan="1"| Play
| Payload
| rowspan="1"| Server
| byte
| 0
| Flags
| {{Type|Unsigned Byte}}
| Bit field. 0: Initial spawn, 1: Respawn after death
| Bit mask; see below
|-
|}
| Total Size:
| colspan="5" | 2 bytes
|}


The flags are as follows:
{{anchor|0xCE}}
=== Scoreboard Objective (0xCE) ===
''Server to Client''


{| class="wikitable"
This is sent to the client when it should create a new scoreboard or remove one.
|-
! Hex Mask
! Field
|-
| 0x01
| Forward
|-
| 0x02
| Backward
|-
| 0x04
| Left
|-
| 0x08
| Right
|-
| 0x10
| Jump
|-
| 0x20
| Sneak
|-
| 0x40
| Sprint
|}

==== Player Loaded ====

Sent by the client after the server starts sending chunks and the player's chunk has loaded.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x2A</code><br/><br/>''resource:''<br/><code>player_loaded</code>
| rowspan="3" | 0xCE
| rowspan="1"| Play
| Objective name
| rowspan="1"| Server
| string
| colspan="3"| ''no fields''
| <code>deaths</code>
|}
| An unique name for the objective
|-
| Objective value
| string
| <code>Deaths</code>
| The text to be displayed for the score.
|-
| Create/Remove
| byte
| 0
| 0 to create the scoreboard. 1 to remove the scoreboard. 2 to update the display text. TODO: Check these values
|-
| Total Size:
| colspan="4" | 6 bytes + length of string
|}


==== Pong (play) ====
{{anchor|0xCF}}
=== Update Score (0xCF) ===
''Server to Client''


Response to the clientbound packet ([[#Ping (play)|Ping]]) with the same id.
This is sent to the client when it should update a scoreboard item.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x2B</code><br/><br/>''resource:''<br/><code>pong</code>
| rowspan="4" | 0xCF
| rowspan="1"| Play
| Item Name
| rowspan="1"| Server
| string
| ID
| <code>Bob</code>
| {{Type|Int}}
| An unique name to be displayed in the list.
| id is the same as the ping packet
|-
|}
| Update/Remove
| byte
| 0
| 0 to create/update an item. 1 to remove an item.
|-
| Score Name
| string
| <code>deaths</code>
| The unique name for the scoreboard to be updated. Only sent when Update/Remove does not equal 1.
|-
| Value
| int
| 5
| The score to be displayed next to the entry. Only sent when Update/Remove does not equal 1.
|-
| Total Size:
| colspan="4" | 9 bytes + length of strings
|}


==== Change Recipe Book Settings ====
{{anchor|0xD0}}


Replaces Recipe Book Data, type 1.
=== Display Scoreboard (0xD0) ===
''Server to Client''


{| class="wikitable"
This is sent to the client when it should display a scoreboard.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x2C</code><br/><br/>''resource:''<br/><code>recipe_book_change_settings</code>
| rowspan="3"| Play
| rowspan="3"| Server
| Book ID
| {{Type|VarInt}} {{Type|Enum}}
| 0: crafting, 1: furnace, 2: blast furnace, 3: smoker.
|-
| Book Open
| {{Type|Boolean}}
|
|-
| Filter Active
| {{Type|Boolean}}
|
|}

==== Set Seen Recipe ====

Sent when recipe is first seen in recipe book. Replaces Recipe Book Data, type 0.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x2D</code><br/><br/>''resource:''<br/><code>recipe_book_seen_recipe</code>
| rowspan="2" | 0xD0
| rowspan="1"| Play
| Position
| rowspan="1"| Server
| byte
| Recipe ID
| 1
| {{Type|VarInt}}
| The position of the scoreboard. 0 = list, 1 = sidebar, 2 = belowName.
| ID of recipe previously defined in Recipe Book Add.
|-
|}
| Score Name
| string
| <code>deaths</code>
| The unique name for the scoreboard to be displayed.
|-
| Total Size:
| colspan="4" | 4 bytes + length of string
|}


==== Rename Item ====
{{anchor|0xD1}}
=== Teams (0xD1) ===
''Server to Client''


Sent as a player is renaming an item in an anvil (each keypress in the anvil UI sends a new Rename 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 50 characters long, and if it is longer than that, then the rename is silently ignored.
Creates and updates teams.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x2E</code><br/><br/>''resource:''<br/><code>rename_item</code>
| rowspan="8" | 0xD1
| rowspan="1"| Play
| Team Name
| rowspan="1"| Server
| string
| Item name
| mcdevs
| {{Type|String}} (32767)
| A unique name for the team. (Shared with scoreboard).
| The new name of the item.
|-
|}
| Mode
| byte
| 0
| If 0 then the team is created.
If 1 then the team is removed.


==== Resource Pack Response (play) ====
If 2 the team team information is updated.


{| class="wikitable"
If 3 then new players are added to the team.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="2"| ''protocol:''<br/><code>0x2F</code><br/><br/>''resource:''<br/><code>resource_pack</code>
| rowspan="2"| Play
| rowspan="2"| Server
| UUID
| {{Type|UUID}}
| The unique identifier of the resource pack received in the [[#Add_Resource_Pack_(play)|Add Resource Pack (play)]] request.
|-
| Result
| {{Type|VarInt}} {{Type|Enum}}
| Result ID (see below).
|}


Result can be one of the following values:
If 4 then players are removed from the team.
|-
| Team Display Name
| string
| McDevs
| Only if Mode = 0 or 2.
|-
| Team Prefix
| string
|
| Only if Mode = 0 or 2. Displayed before the players' name that are part of this team.
|-
| Team Suffix
| string
|
| Only if Mode = 0 or 2. Displayed after the players' name that are part of this team.
|-
| Friendly fire
| byte
| 0
| Only if Mode = 0 or 2; 0 for off, 1 for on, 3 for seeing friendly invisibles
|-
| Player count
| short
| 0
| Only if Mode = 0 or 3 or 4. Number of players in the array
|-
| Players
| Array of strings
|
| Only if Mode = 0 or 3 or 4. Players to be added/remove from the team.
|-
| Total Size:
| colspan="4" | Variable
|}


{{anchor|0xFA}}
=== Plugin Message (0xFA) ===
''Two-Way''


{| class="wikitable"
Mods and plugins can use this to send their data. As of 1.3, Minecraft itself uses a number of [[plugin channel]]s. These internal channels are prefixed with <code>MC|</code>.
! ID
! Result
|-
| 0
| Successfully downloaded
|-
| 1
| Declined
|-
| 2
| Failed to download
|-
| 3
| Accepted
|-
| 4
| Downloaded
|-
| 5
| Invalid URL
|-
| 6
| Failed to reload
|-
| 7
| Discarded
|}

==== Seen Advancements ====


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x30</code><br/><br/>''resource:''<br/><code>seen_advancements</code>
| rowspan="3" | 0xFA
| rowspan="2"| Play
| Channel
| rowspan="2"| Server
| string
| Action
| MyMod:testchannel
| {{Type|VarInt}} {{Type|Enum}}
| Name of the "channel" used to send the data.
| 0: Opened tab, 1: Closed screen.
|-
|-
| length
| short
| Tab ID
| {{Type|Optional}} {{Type|Identifier}}
|
| Only present if action is Opened tab.
| Length of the following byte array
|-
|}
| data
| byte array
|
| Any data.
|-
| Total Size:
| colspan="4" | 5 bytes + length of string + length of byte array
|}


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


When a player selects a specific trade offered by a villager NPC.
{{anchor|0xFC}}
=== Encryption Key Response (0xFC) ===
''Two-Way''


{| class="wikitable"
See [[Protocol Encryption]] for information on this packet. Bypassing the encryption is possible, authentication for the player name is still needed if the server is in online mode, but instead of sending this packet, you send [[#0xCD|Client Statuses]] instead.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x31</code><br/><br/>''resource:''<br/><code>select_trade</code>
| rowspan="1"| Play
| rowspan="1"| Server
| Selected slot
| {{Type|VarInt}}
| The selected slot in the players current (trading) inventory.
|}

==== Set Beacon Effect ====

Changes the effect of the current beacon.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x32</code><br/><br/>''resource:''<br/><code>set_beacon</code>
| rowspan="4" | 0xFC
| rowspan="2"| Play
| Shared secret length
| rowspan="2"| Server
| short
| Primary Effect
|
| {{Type|Prefixed Optional}} {{Type|VarInt}}
|
| A [https://minecraft.wiki/w/Potion#ID Potion ID].
|-
|-
| Shared secret
| Secondary Effect
| byte array
| {{Type|Prefixed Optional}} {{Type|VarInt}}
|
| A [https://minecraft.wiki/w/Potion#ID Potion ID].
|
|-
|}
| Verify token length
| short
|
|
|-
| Verify token response
| byte array
|
|
|-
| Total Size:
| colspan="4" | 5 bytes + length of shared secret + length of token
|}


==== Set Held Item (serverbound) ====
{{anchor|0xFD}}
=== Encryption Key Request (0xFD) ===
''Server to client''


Sent when the player changes the slot selection.
See [[Protocol Encryption]] for information on this packet.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="1"| ''protocol:''<br/><code>0x33</code><br/><br/>''resource:''<br/><code>set_carried_item</code>
| rowspan="5" | 0xFD
| rowspan="1"| Play
| Server id
| rowspan="1"| Server
| string
| Slot
|
| {{Type|Short}}
|
| The slot which the player has selected (0–8).
|-
|}
| Public key length
| short
|
|
|-
| Public key
| byte array
|
|
|-
| Verify token length
| short
|
|
|-
| Verify token
| byte array
|
|
|-
| Total Size:
| colspan="4" | 7 bytes + length of string + length of key + length of token
|}


==== Program Command Block ====
{{anchor|0xFE}}


{| class="wikitable"
=== Server List Ping (0xFE) ===
! Packet ID
''Client to Server''
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="4"| ''protocol:''<br/><code>0x34</code><br/><br/>''resource:''<br/><code>set_command_block</code>
| rowspan="4"| Play
| rowspan="4"| Server
| Location
| {{Type|Position}}
|
|-
| Command
| {{Type|String}} (32767)
|
|-
| Mode || {{Type|VarInt}} {{Type|Enum}} || 0: chain, 1: repeating, 2: impulse.
|-
| Flags
| {{Type|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.
|}


==== Program Command Block Minecart ====
''Main article: [[Server List Ping]]''


{| class="wikitable"
This packet is used by the multiplayer menu to retrieve MOTD, version, and player counts.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="3"| ''protocol:''<br/><code>0x35</code><br/><br/>''resource:''<br/><code>set_command_minecart</code>
| rowspan="3"| Play
| rowspan="3"| Server
| Entity ID
| {{Type|VarInt}}
|
|-
| Command
| {{Type|String}} (32767)
|
|-
| Track Output
| {{Type|Boolean}}
| If false, the output of the previous command will not be stored within the command block.
|}

==== Set Creative Mode Slot ====

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
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="2"| ''protocol:''<br/><code>0x36</code><br/><br/>''resource:''<br/><code>set_creative_mode_slot</code>
| rowspan="1" | 0xFE
| rowspan="2"| Play
| Magic
| rowspan="2"| Server
| byte
| Slot
| <code>1</code>
| {{Type|Short}}
| always <code>1</code>
| Inventory slot.
|-
|-
| Total Size:
| Clicked Item
| colspan="4" | 2 bytes
| {{Type|Slot}}
|}
|
|}


==== Program Jigsaw Block ====
{{anchor|0xFF}}


Sent when Done is pressed on the [[Jigsaw Block]] interface.
=== Disconnect/Kick (0xFF) ===
''Two-Way''


{| class="wikitable"
Sent by the server before it disconnects a client, or by the client before it disconnects from the server. The receiver of this packet assumes that the sender has already closed the connection by the time the packet arrives.
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="8"| ''protocol:''<br/><code>0x37</code><br/><br/>''resource:''<br/><code>set_jigsaw_block</code>
| rowspan="8"| Play
| rowspan="8"| Server
| Location
| {{Type|Position}}
| Block entity location
|-
| Name
| {{Type|Identifier}}
|
|-
| Target
| {{Type|Identifier}}
|
|-
| Pool
| {{Type|Identifier}}
|
|-
| Final state
| {{Type|String}} (32767)
| "Turns into" on the GUI, <code>final_state</code> in NBT.
|-
| Joint type
| {{Type|String}} (32767)
| <code>rollable</code> if the attached piece can be rotated, else <code>aligned</code>.
|-
| Selection priority
| {{Type|VarInt}}
|
|-
| Placement priority
| {{Type|VarInt}}
|
|}


==== Program Structure Block ====
Due to race conditions in the client, a local server may need to pause for a short period after sending this packet before closing the connection. An alternative is simply not to close the connection, and wait for the client to do so on receipt of this packet.


{| class="wikitable"
{| class="wikitable"
! Packet ID
|-
! State
| Packet ID
! Bound To
| Field Name
| Field Type
! Field Name
! Field Type
| Example
| Notes
! Notes
|-
|-
| rowspan="17"| ''protocol:''<br/><code>0x38</code><br/><br/>''resource:''<br/><code>set_structure_block</code>
| 0xFF
| rowspan="17"| Play
| Reason
| rowspan="17"| Server
| string
|-
| <code>The server is full!</code>
| Location
| Displayed to the client when the connection terminates
| {{Type|Position}}
|-
| Block entity location.
| Total Size:
|-
| colspan="4" | 3 bytes + length of strings
| Action
|}
| {{Type|VarInt}} {{Type|Enum}}
| An additional action to perform beyond simply saving the given data; see below.
|-
| Mode
| {{Type|VarInt}} {{Type|Enum}}
| One of SAVE (0), LOAD (1), CORNER (2), DATA (3).
|-
| Name
| {{Type|String}} (32767)
|
|-
| Offset X || {{Type|Byte}}
| Between -48 and 48.
|-
| Offset Y || {{Type|Byte}}
| Between -48 and 48.
|-
| Offset Z || {{Type|Byte}}
| Between -48 and 48.
|-
| Size X || {{Type|Byte}}
| Between 0 and 48.
|-
| Size Y || {{Type|Byte}}
| Between 0 and 48.
|-
| Size Z || {{Type|Byte}}
| Between 0 and 48.
|-
| Mirror
| {{Type|VarInt}} {{Type|Enum}}
| One of NONE (0), LEFT_RIGHT (1), FRONT_BACK (2).
|-
| Rotation
| {{Type|VarInt}} {{Type|Enum}}
| One of NONE (0), CLOCKWISE_90 (1), CLOCKWISE_180 (2), COUNTERCLOCKWISE_90 (3).
|-
| Metadata
| {{Type|String}} (128)
|
|-
| Integrity
| {{Type|Float}}
| Between 0 and 1.
|-
|Seed
|{{Type|VarLong}}
|
|-
| Flags
| {{Type|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 vanilla 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|Open Sign Editor]], otherwise this packet is silently ignored.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="6"| ''protocol:''<br/><code>0x39</code><br/><br/>''resource:''<br/><code>sign_update</code>
| rowspan="6"| Play
| rowspan="6"| Server
| Location
| {{Type|Position}}
| Block Coordinates.
|-
| Is Front Text
| {{Type|Boolean}}
| Whether the updated text is in front or on the back of the sign
|-
| Line 1
| {{Type|String}} (384)
| First line of text in the sign.
|-
| Line 2
| {{Type|String}} (384)
| Second line of text in the sign.
|-
| Line 3
| {{Type|String}} (384)
| Third line of text in the sign.
|-
| Line 4
| {{Type|String}} (384)
| Fourth line of text in the sign.
|}

==== Swing Arm ====

Sent when the player's arm swings.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x3A</code><br/><br/>''resource:''<br/><code>swing</code>
| rowspan="1"| Play
| rowspan="1"| Server
| Hand
| {{Type|VarInt}} {{Type|Enum}}
| Hand used for the animation. 0: main hand, 1: off hand.
|}

==== Teleport To Entity ====

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

The vanilla 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.

{| class="wikitable"
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="1"| ''protocol:''<br/><code>0x3B</code><br/><br/>''resource:''<br/><code>teleport_to_entity</code>
| rowspan="1"| Play
| rowspan="1"| Server
| Target Player
| {{Type|UUID}}
| UUID of the player to teleport to (can also be an entity UUID).
|}

==== Use Item On ====

{| class="wikitable"
|-
! Packet ID
! State
! Bound To
! Field Name
! Field Type
! Notes
|-
| rowspan="9"| ''protocol:''<br/><code>0x3C</code><br/><br/>''resource:''<br/><code>use_item_on</code>
| rowspan="9"| Play
| rowspan="9"| Server
| Hand
| {{Type|VarInt}} {{Type|Enum}}
| The hand from which the block is placed; 0: main hand, 1: off hand.
|-
| Location
| {{Type|Position}}
| Block position.
|-
| Face
| {{Type|VarInt}} {{Type|Enum}}
| The face on which the block is placed (as documented at [[#Player Action|Player Action]]).
|-
| Cursor Position X
| {{Type|Float}}
| The position of the crosshair on the block, from 0 to 1 increasing from west to east.
|-
| Cursor Position Y
| {{Type|Float}}
| The position of the crosshair on the block, from 0 to 1 increasing from bottom to top.
|-
| Cursor Position Z
| {{Type|Float}}
| The position of the crosshair on the block, from 0 to 1 increasing from north to south.
|-
| Inside block
| {{Type|Boolean}}
| True when the player's head is inside of a block.
|-
| World Border Hit
| {{Type|Boolean}}
| Seems to always be false, even when interacting with blocks around or outside the world border, or while the player is outside the border.
|-
| Sequence
| {{Type|VarInt}}
| Block change sequence number (see [[#Acknowledge Block Change]]).
|}

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
|-
| rowspan="4"| ''protocol:''<br/><code>0x3D</code><br/><br/>''resource:''<br/><code>use_item</code>
| rowspan="4"| Play
| rowspan="4"| Server
| Hand
| {{Type|VarInt}} {{Type|Enum}}
| Hand used for the animation. 0: main hand, 1: off hand.
|-
| Sequence
| {{Type|VarInt}}
| Block change sequence number (see [[#Acknowledge Block Change]]).
|-
| Yaw
| {{Type|Float}}
| Player head rotation along the Y-Axis.
|-
| Pitch
| {{Type|Float}}
| Player head rotation along the X-Axis.
|}

The player's rotation is permanently updated according to the Yaw and Pitch fields before performing the action, unless there is no item in the specified hand.


== See Also ==
== Navigation ==
{{Navbox Java Edition technical|General}}
* [[Protocol History]]
* [[Data Types]]
* [[Units of Measurement]]


[[Category:Protocol Details]]
[[Category:Protocol Details]]
[[Category:Minecraft Modern]]
[[Category:Java Edition protocol]]
{{license wiki.vg}}

Latest revision as of 22:54, 27 March 2025

This article is about the protocol for a stable release of Java Edition. For the protocol used in development versions of Java Edition, see Minecraft Wiki:Projects/wiki.vg merge/Pre-release protocol. For the protocol used in Bedrock Edition, see Bedrock Edition protocol. For the protocol used in old Pocket Edition versions, see Pocket Edition protocol.
See also: Protocol FAQ
This feature is exclusive to Java Edition.
 
While you may use the contents of this page without restriction to create servers, clients, bots, etc; keep in mind that the contents of this page are distributed under the terms of CC BY-SA 3.0 Unported. Reproductions and derivative works must be distributed accordingly.

This article presents a dissection of the current Java Edition protocol for 1.21.4, protocol 769.

The changes between versions may be viewed at Protocol History.

Definitions[edit | edit source]

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[edit | edit source]

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 The maximum permitted length when decoding is 262144, but the vanilla server since 1.20.3 refuses to encode longer than 32767. This may be a bug.
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 Minecraft Wiki:Projects/wiki.vg merge/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) ceil(n / 8) 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.
Prefixed Optional X size of Boolean + (is present ? Size of X : 0) A boolean and if present, a field of type X The boolean is true if the field is present.
Array of X length times size of X Zero or more fields of type X The length must be known from the context.
Prefixed Array of X size of VarInt + size of X * length See #Prefixed Array below A length-prefixed array.
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.
ID or X size of VarInt + (size of X or 0) See #ID or X below Either a registry ID or an inline data definition of type X.
ID Set Varies See #ID Set below Set of registry IDs specified either inline or as a reference to a tag.
Sound Event Varies See #Sound Event below Parameters for a sound event.
Teleport Flags 4 See #Teleport Flags below Bit field specifying how a teleportation is to be applied on each axis.
Recipe Display Varies See Recipes#Recipe Display structure Description of a recipe for use for use by the client.
Slot Display Varies See Recipes#Slot Display structure Description of a recipe ingredient slot for use for use by the client.
Chunk Data Varies See #Chunk Data below
Light Data Varies See #Light Data below

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;
    }
}
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.
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 represent the signed integer part (number to the left of the decimal point) and the rest represent the fractional part (to the right). Floating point numbers (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 point numbers, their fractional precision is greater for higher values.

Prior to version 1.9 a fixed-point format with 5 fraction bits and 27 integer bits was used to send entity positions to the client. Some uses of fixed point remain in modern versions, but they differ from that format.

Most programming languages lack support for fractional integers directly, but you can represent them as integers. The following C or Java-like pseudocode converts a double to a fixed-point integer with n fraction bits:

 x_fixed = (int)(x_double * (1 << n));

And back again:

 x_double = (double)x_fixed / (1 << n);

Arrays

The types Array and Prefixed Array represent a collection of X in a specified order.

Array

Represents a list where the length is not encoded. The length must be known from the context. If the array is empty nothing will be encoded.

A String Array with the values ["Hello", "World!"] has the following data when encoded:

Field Name Field Type Value
First element String Hello
Second element String World!

Prefixed Array

Represents an array prefixed by its length. If the array is empty the length will still be encoded.

Field Name Field Type
Length VarInt
Data Array of X

Bit sets

The types BitSet and Fixed BitSet represent packed lists of bits. The vanilla 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, padded with zeroes at the end to fit the specified length.

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.

Registry references

ID or X

Represents a data record of type X, either inline, or by reference to a registry implied by context.

Field Name Field Type Meaning
ID VarInt 0 if value of type X is given inline; otherwise registry ID + 1.
Value Optional X Only present if ID is 0.

ID Set

Represents a set of IDs in a certain registry (implied by context), either directly (enumerated IDs) or indirectly (tag name).

Field Name Field Type Meaning
Type VarInt Value used to determine the data that follows. It can be either:
  • 0 - Represents a named set of IDs defined by a tag.
  • Anything else - Represents an ad-hoc set of IDs enumerated inline.
Tag Name Optional Identifier The registry tag defining the ID set. Only present if Type is 0.
IDs Optional Array of VarInt An array of registry IDs. Only present if Type is not 0.
The size of the array is equal to Type - 1.

Registry data

These types are commonly used in conjuction with ID or X to specify custom data inline.

Sound Event

Describes a sound that can be played.

Name Type Description
Sound Name Identifier
Has Fixed Range Boolean Whether this sound has a fixed range, as opposed to a variable volume based on distance.
Fixed Range Optional Float The maximum range of the sound. Only present if Has Fixed Range is true.

Teleport Flags

A bit field represented as an Int, specifying how a teleportation is to be applied on each axis.

In the lower 8 bits of the bit field, a set bit means the teleportation on the corresponding axis is relative, and an unset bit that it is absolute.

Hex Mask Field
0x0001 Relative X
0x0002 Relative Y
0x0004 Relative Z
0x0008 Relative Yaw
0x0010 Relative Pitch
0x0020 Relative Velocity X
0x0040 Relative Velocity Y
0x0080 Relative Velocity Z
0x0100 Rotate velocity according to the change in rotation, before applying the velocity change in this packet. Combining this with absolute rotation works as expected—the difference in rotation is still used.

Chunk Data

Field Name Field Type Notes
Heightmaps NBT See Chunk Format#Heightmaps structure
Data Prefixed Array of Byte See Chunk Format#Data structure
Block Entities Packed XZ Prefixed Array Unsigned Byte The packed section coordinates are relative to the chunk they are in. Values 0-15 are valid.
packed_xz = ((blockX & 15) << 4) | (blockZ & 15) // encode
x = packed_xz >> 4, z = packed_xz & 15 // decode
Y Short The height relative to the world
Type VarInt The type of block entity
Data NBT The block entity's data, without the X, Y, and Z values

Light Data

Field Name Field Type Notes
Sky Light Mask BitSet BitSet containing bits for each section in the world + 2. Each set bit indicates that the corresponding 16×16×16 chunk section has data in the Sky Light array below. The least significant bit is for blocks 16 blocks to 1 block below the min world height (one section below the world), while the most significant bit covers blocks 1 to 16 blocks above the max world height (one section above the world).
Block Light Mask BitSet BitSet containing bits for each section in the world + 2. Each set bit indicates that the corresponding 16×16×16 chunk section has data in the Block Light array below. The order of bits is the same as in Sky Light Mask.
Empty Sky Light Mask BitSet BitSet containing bits for each section in the world + 2. Each set bit indicates that the corresponding 16×16×16 chunk section has all zeros for its Sky Light data. The order of bits is the same as in Sky Light Mask.
Empty Block Light Mask BitSet BitSet containing bits for each section in the world + 2. Each set bit indicates that the corresponding 16×16×16 chunk section has all zeros for its Block Light data. The order of bits is the same as in Sky Light Mask.
Sky Light arrays Sky Light array Prefixed Array Prefixed Array (2048) of Byte The length of any inner array is always 2048; 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 Block Light array Prefixed Array Prefixed Array (2048) of Byte The length of any inner array is always 2048; 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.



Other definitions[edit | edit source]

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”.
Registry A table describing static, gameplay-related objects of some kind, such as the types of entities, block states or biomes. The entries of a registry are typically associated with textual or numeric identifiers, or both.

Minecraft has a unified registry system used to implement most of the registries, including blocks, items, entities, biomes and dimensions. These "ordinary" registries associate entries with both namespaced textual identifiers (see #Identifier), and signed (positive) 32-bit numeric identifiers. There is also a registry of registries listing all of the registries in the registry system. Some other registries, most notably the block state registry, are however implemented in a more ad-hoc fashion.

Some registries, such as biomes and dimensions, can be customized at runtime by the server (see Registry Data), while others, such as blocks, items and entities, are hardcoded. The contents of the hardcoded registries can be extracted via the built-in Data Generators system.

Block state Each block in Minecraft has 0 or more properties, which in turn may have any number of possible values. These represent, for example, the orientations of blocks, poweredness states of redstone components, and so on. Each of the possible permutations of property values for a block is a distinct block state. The block state registry assigns a numeric identifier to every block state of every block.

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 -DbundlerMainClass=net.minecraft.data.Main -jar minecraft_server.jar --reports. See Data Generators for more information.

Vanilla The official implementation of Minecraft as developed and released by Mojang.
Sequence The action number counter for local block changes, incremented by one when clicking a block with a hand, right clicking an item, or starting or finishing digging a block. Counter handles latency to avoid applying outdated block changes to the local world. Also is used to revert ghost blocks created when placing blocks, using buckets, or breaking blocks.

Packet format[edit | edit source]

Packets cannot be larger than 221 − 1 or 2097151 bytes (the maximum that can be sent in a 3-byte VarInt). Moreover, the length field must not be longer than 3 bytes, even if the encoded value is within the limit. Unnecessarily long encodings at 3 bytes or below are still allowed. For compressed packets, this applies to the Packet Length field, i.e. the compressed length.

Without compression[edit | edit source]

Field Name Field Type Notes
Length VarInt Length of Packet ID + Data
Packet ID VarInt Corresponds to protocol_id from the server's packet report
Data Byte Array Depends on the connection state and packet ID, see the sections below

With compression[edit | edit source]

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 slightly to include the size of the uncompressed packet.

Present? Compressed? Field Name Field Type Notes
always No Packet Length VarInt Length of (Data Length) + length of compressed (Packet ID + Data)
if size >= threshold No Data Length VarInt Length of uncompressed (Packet ID + Data)
Yes Packet ID VarInt zlib compressed packet ID (see the sections below)
Data Byte Array zlib compressed packet data (see the sections below)
if size < threshold No Data Length VarInt 0 to indicate uncompressed
Packet ID VarInt packet ID (see the sections below)
Data Byte Array packet data (see the sections below)

For serverbound packets, the uncompressed length of (Packet ID + Data) must not be greater than 223 or 8388608 bytes. Note that a length equal to 223 is permitted, which differs from the compressed length limit. The vanilla client, on the other hand, has no limit for the uncompressed length of incoming compressed packets.

If the size of the buffer containing the packet data and ID (as a VarInt) is smaller than the threshold specified in the packet Set Compression. It will be sent as uncompressed. This is done by setting the data length as 0. (Comparable to sending a non-compressed format with an extra 0 between the length, and packet data).

If it's larger than or equal to the threshold, then it follows the regular compressed protocol format.

The vanilla server (but not client) rejects compressed packets smaller than the threshold. Uncompressed packets exceeding the threshold, however, are accepted.

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

Handshaking[edit | edit source]

Clientbound[edit | edit source]

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[edit | edit source]

Handshake[edit | edit source]

This packet causes the server to switch into the target state. It should be sent right after opening the TCP connection to prevent the server from disconnecting.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x00

resource:
intention
Handshaking Server Protocol Version VarInt See protocol version numbers (currently 769 in Minecraft 1.21.4).
Server Address String (255) Hostname or IP, e.g. localhost or 127.0.0.1, that was used to connect. The vanilla server does not use this information. Note that SRV records are a simple redirect, e.g. if _minecraft._tcp.example.com points to mc.example.org, users connecting to example.com will provide example.org as server address in addition to connecting to it.
Server Port Unsigned Short Default is 25565. The vanilla server does not use this information.
Next State VarInt Enum 1 for Status, 2 for Login, 3 for Transfer.

Legacy Server List Ping[edit | edit source]

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. The format of this packet is a remnant of the pre-Netty age, before the switch to Netty in 1.7 brought the standard format that is recognized now. This packet merely exists to inform legacy clients that they can't join our modern server.

Modern clients (tested with 1.21.5 + 1.21.4) also send this packet when the server does not send any response within a 30 seconds time window or when the connection is immediately closed.

The client does not close the connection with the legacy packet on its own! It only gets closed when the Minecraft client is closed.
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.

Status[edit | edit source]

Clientbound[edit | edit source]

Status Response[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x00

resource:
status_response
Status Client JSON Response String (32767) See Server List Ping#Status Response; as with all strings this is prefixed by its length as a VarInt.

Pong Response (status)[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x01

resource:
pong_response
Status Client Timestamp Long Should match the one sent by the client.

Serverbound[edit | edit source]

Status Request[edit | edit source]

The status can only be requested once immediately after the handshake, before any ping. The server won't respond otherwise.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x00

resource:
status_request
Status Server no fields

Ping Request (status)[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x01

resource:
ping_request
Status Server Timestamp Long May be any number, but vanilla clients use will always use the timestamp in milliseconds.

Login[edit | edit source]

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 (if enabled)
  5. C→S: Encryption Response
  6. Server auth (if enabled)
  7. Both enable encryption
  8. S→C: Set Compression (optional)
  9. S→C: Login Success
  10. C→S: Login Acknowledged

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

Three modes of operation are possible depending on how the packets are sent:

  • Online-mode with encryption
  • Offline-mode with encryption
  • Offline-mode without encryption

For online-mode servers (the ones with authentication enabled), encryption is always mandatory, and the entire process described above needs to be followed.

For offline-mode servers (the ones with authentication disabled), encryption is optional, and part of the process can be skipped. In that case Login Start is directly followed by Login Success. The vanilla server only uses UUID v3 for offline player UUIDs, deriving it from the string OfflinePlayer:<player's name> For example, Notch’s offline UUID would be chosen from the string OfflinePlayer:Notch. This is not a requirement however, the UUID can be set to anything.

As of 1.21, the vanilla server never uses encryption in offline mode.

See protocol encryption for details.

Clientbound[edit | edit source]

Disconnect (login)[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x00

resource:
login_disconnect
Login Client Reason JSON Text Component The reason why the player was disconnected.

Encryption Request[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x01

resource:
hello
Login Client Server ID String (20) Always empty when sent by the vanilla server.
Public Key Prefixed Array of Byte The server's public key, in bytes.
Verify Token Prefixed Array of Byte A sequence of random bytes generated by the server.
Should authenticate Boolean Whether the client should attempt to authenticate through mojang servers.

See protocol encryption for details.

Login Success[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x02

resource:
login_finished
Login Client UUID UUID
Username String (16)
Property Name Prefixed Array (16) String (64)
Value String (32767)
Signature Prefixed Optional String (1024)

The Property field looks like response of Mojang API#UUID to Profile and Skin/Cape, except using the protocol format instead of JSON. That is, each player will usually have one property with Name being “textures” and Value being a base64-encoded JSON string, as documented at Mojang API#UUID to Profile and 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 their UUID (again, see the Mojang API page).

Set Compression[edit | edit source]

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 vanilla server does not send the packet when compression is disabled).

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x03

resource:
login_compression
Login Client Threshold VarInt Maximum size of a packet before it is compressed.

Login Plugin Request[edit | edit source]

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 vanilla client always responds that it hasn't understood, and sends an empty payload.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x04

resource:
custom_query
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 (1048576) Any data, depending on the channel. The length of this array must be inferred from the packet length.

Cookie Request (login)[edit | edit source]

Requests a cookie that was previously stored.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x05

resource:
cookie_request
Login Client Key Identifier The identifier of the cookie.

Serverbound[edit | edit source]

Login Start[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x00

resource:
hello
Login Server Name String (16) Player's Username.
Player UUID UUID The UUID of the player logging in. Unused by the vanilla server.

Encryption Response[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x01

resource:
key
Login Server Shared Secret Prefixed Array of Byte Shared Secret value, encrypted with the server's public key.
Verify Token Prefixed Array of Byte Verify Token value, encrypted with the same public key as the shared secret.

See protocol encryption for details.

Login Plugin Response[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x02

resource:
custom_query_answer
Login Server Message ID VarInt Should match ID from server.
Data Prefixed Optional Byte Array (1048576) Any data, depending on the channel. The length of this array must be inferred from the packet length. Only present if the client understood the request.

Login Acknowledged[edit | edit source]

Acknowledgement to the Login Success packet sent by the server.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x03

resource:
login_acknowledged
Login Server no fields

This packet switches the connection state to configuration.

Cookie Response (login)[edit | edit source]

Response to a Cookie Request (login) from the server. The vanilla server only accepts responses of up to 5 kiB in size.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x04

resource:
cookie_response
Login Server Key Identifier The identifier of the cookie.
Payload Prefixed Optional Prefixed Array (5120) of Byte The data of the cookie.

Configuration[edit | edit source]

Clientbound[edit | edit source]

Cookie Request (configuration)[edit | edit source]

Requests a cookie that was previously stored.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x00

resource:
cookie_request
Configuration Client Key Identifier The identifier of the cookie.

Clientbound Plugin Message (configuration)[edit | edit source]

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 information on how it works on Dinnerbone's blog. More documentation about internal and popular registered channels are here.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x01

resource:
custom_payload
Configuration Client Channel Identifier Name of the plugin channel used to send the data.
Data Byte Array (1048576) Any data. The length of this array must be inferred from the packet length.

In vanilla clients, the maximum data length is 1048576 bytes.

Disconnect (configuration)[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x02

resource:
disconnect
Configuration Client Reason Text Component The reason why the player was disconnected.

Finish Configuration[edit | edit source]

Sent by the server to notify the client that the configuration process has finished. The client answers with Acknowledge Finish Configuration whenever it is ready to continue.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x03

resource:
finish_configuration
Configuration Client no fields

This packet switches the connection state to play.

Clientbound Keep Alive (configuration)[edit | edit source]

The server will frequently send out a keep-alive, each containing a random ID. The client must respond with the same payload (see Serverbound Keep Alive). If the client does not respond to a Keep Alive packet within 15 seconds after it was sent, 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 vanilla 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
protocol:
0x04

resource:
keep_alive
Configuration Client Keep Alive ID Long

Ping (configuration)[edit | edit source]

Packet is not used by the vanilla server. When sent to the client, client responds with a Pong packet with the same id.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x05

resource:
ping
Configuration Client ID Int

Reset Chat[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x06

resource:
reset_chat
Configuration Client no fields

Registry Data[edit | edit source]

Represents certain registries that are sent from the server and are applied on the client.

See Registry Data for details.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x07

resource:
registry_data
Configuration Client Registry ID Identifier
Entries Entry ID Prefixed Array Identifier
Data Prefixed Optional NBT Entry data.

Remove Resource Pack (configuration)[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x08

resource:
resource_pack_pop
Configuration Client UUID Prefixed Optional UUID The UUID of the resource pack to be removed. If not present every resource pack will be removed.

Add Resource Pack (configuration)[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x09

resource:
resource_pack_push
Configuration Client UUID UUID The unique identifier of the resource pack.
URL String (32767) The URL to the resource pack.
Hash String (40) A 40 character hexadecimal, case-insensitive SHA-1 hash of the resource pack file.
If it's not a 40 character hexadecimal string, the client will not use it for hash verification and likely waste bandwidth.
Forced Boolean The vanilla client will be forced to use the resource pack from the server. If they decline they will be kicked from the server.
Prompt Message Prefixed Optional Text Component This is shown in the prompt making the client accept or decline the resource pack (only if present).

Store Cookie (configuration)[edit | edit source]

Stores some arbitrary data on the client, which persists between server transfers. The vanilla client only accepts cookies of up to 5 kiB in size.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0A

resource:
store_cookie
Configuration Client Key Identifier The identifier of the cookie.
Payload Prefixed Array (5120) of Byte The data of the cookie.

Transfer (configuration)[edit | edit source]

Notifies the client that it should transfer to the given server. Cookies previously stored are preserved between server transfers.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0B

resource:
transfer
Configuration Client Host String (32767) The hostname or IP of the server.
Port VarInt The port of the server.

Feature Flags[edit | edit source]

Used to enable and disable features, generally experimental ones, on the client.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0C

resource:
update_enabled_features
Configuration Client Feature Flags Prefixed Array of Identifier

There is one special feature flag, which is in most versions:

  • minecraft:vanilla - enables vanilla features

For the other feature flags, which may change between versions, see Experiments#Java_Edition.

Update Tags (configuration)[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0D

resource:
update_tags
Configuration Client Array of tags Registry Prefixed Array Identifier Registry identifier (Vanilla expects tags for the registries minecraft:block, minecraft:item, minecraft:fluid, minecraft:entity_type, and minecraft:game_event)
Array of Tag (See below)

Tag arrays look like:

Field Name Field Type Notes
Tags Tag name Prefixed Array Identifier
Entries Prefixed Array of VarInt Numeric IDs of the given type (block, item, etc.). This list replaces the previous list of IDs for the given tag. If some preexisting tags are left unmentioned, a warning is printed.

See Tag on the Minecraft Wiki for more information, including a list of vanilla tags.

Clientbound Known Packs[edit | edit source]

Informs the client of which data packs are present on the server. The client is expected to respond with its own Serverbound Known Packs packet. The vanilla server does not continue with Configuration until it receives a response.

The vanilla client requires the minecraft:core pack with version 1.21.4 for a normal login sequence. This packet must be sent before the Registry Data packets.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0E

resource:
select_known_packs
Configuration Client Known Packs Namespace Prefixed Array String
ID String
Version String

Custom Report Details (configuration)[edit | edit source]

Contains a list of key-value text entries that are included in any crash or disconnection report generated during connection to the server.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0F

resource:
custom_report_details
Configuration Client Details Title Prefixed Array (32) String (128)
Description String (4096)

Server Links (configuration)[edit | edit source]

This packet contains a list of links that the vanilla client will display in the menu available from the pause menu. Link labels can be built-in or custom (i.e., any text).

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x10

resource:
server_links
Configuration Client Links Is built-in Prefixed Array Boolean True if Label is an enum (built-in label), false if it's a text component (custom label).
Label VarInt Enum / Text Component See below.
URL String Valid URL.


ID Name Notes
0 Bug Report Displayed on connection error screen; included as a comment in the disconnection report.
1 Community Guidelines
2 Support
3 Status
4 Feedback
5 Community
6 Website
7 Forums
8 News
9 Announcements

Serverbound[edit | edit source]

Client Information (configuration)[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x00

resource:
client_information
Configuration 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 Chat#Client chat mode for more information.
Chat Colors Boolean “Colors” multiplayer setting. The vanilla server stores this value but does nothing with it (see MC-64867). Third-party servers such as Hypixel disable all coloring in chat and system messages when it is false.
Displayed Skin Parts Unsigned Byte Bit mask, see below.
Main Hand VarInt Enum 0: Left, 1: Right.
Enable text filtering Boolean Enables filtering of text on signs and written book titles. The vanilla client sets this according to the profanityFilterPreferences.profanityFilterOn account attribute indicated by the /player/attributes Mojang API endpoint. In offline mode it is always false.
Allow server listings Boolean Servers usually list online players, this option should let you not show up in that list.
Particle Status VarInt Enum 0: all, 1: decreased, 2: minimal

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.

Cookie Response (configuration)[edit | edit source]

Response to a Cookie Request (configuration) from the server. The vanilla server only accepts responses of up to 5 kiB in size.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x01

resource:
cookie_response
Configuration Server Key Identifier The identifier of the cookie.
Payload Prefixed Optional Prefixed Array (5120) of Byte The data of the cookie.

Serverbound Plugin Message (configuration)[edit | edit source]

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: https://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
protocol:
0x02

resource:
custom_payload
Configuration Server Channel Identifier Name of the plugin channel used to send the data.
Data Byte Array (32767) Any data, depending on the channel. minecraft: channels are documented here. The length of this array must be inferred from the packet length.

In vanilla server, the maximum data length is 32767 bytes.

Acknowledge Finish Configuration[edit | edit source]

Sent by the client to notify the server that the configuration process has finished. It is sent in response to the server's Finish Configuration.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x03

resource:
finish_configuration
Configuration Server no fields

This packet switches the connection state to play.

Serverbound Keep Alive (configuration)[edit | edit source]

The server will frequently send out a keep-alive (see Clientbound 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
protocol:
0x04

resource:
keep_alive
Configuration Server Keep Alive ID Long

Pong (configuration)[edit | edit source]

Response to the clientbound packet (Ping) with the same id.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x05

resource:
pong
Configuration Server ID Int

Resource Pack Response (configuration)[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x06

resource:
resource_pack
Configuration Server UUID UUID The unique identifier of the resource pack received in the Add Resource Pack (configuration) request.
Result VarInt Enum Result ID (see below).

Result can be one of the following values:

ID Result
0 Successfully downloaded
1 Declined
2 Failed to download
3 Accepted
4 Downloaded
5 Invalid URL
6 Failed to reload
7 Discarded

Serverbound Known Packs[edit | edit source]

Informs the server of which data packs are present on the client. The client sends this in response to Clientbound Known Packs.

If the client specifies a pack in this packet, the server should omit its contained data from the Registry Data packet.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x07

resource:
select_known_packs
Configuration Server Known Packs Namespace Prefixed Array String
ID String
Version String

Play[edit | edit source]

Clientbound[edit | edit source]

Bundle Delimiter[edit | edit source]

The delimiter for a bundle of packets. When received, the client should store every subsequent packet it receives, and wait until another delimiter is received. Once that happens, the client is guaranteed to process every packet in the bundle on the same tick, and the client should stop storing packets.

As of 1.20.6, the vanilla server only uses this to ensure Spawn Entity and associated packets used to configure the entity happen on the same tick. Each entity gets a separate bundle.

The vanilla client doesn't allow more than 4096 packets in the same bundle.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x00

resource:
bundle_delimiter
Play Client no fields

Spawn Entity[edit | edit source]

Sent by the server when an entity (aside from Experience Orb) is created.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x01

resource:
add_entity
Play Client Entity ID VarInt A unique integer ID mostly used in the protocol to identify the entity.
Entity UUID UUID A unique identifier that is mostly used in persistence and places where the uniqueness matters more.
Type VarInt ID in the minecraft:entity_type registry (see "type" field in Entity metadata#Entities).
X Double
Y Double
Z Double
Pitch Angle To get the real pitch, you must divide this by (256.0F / 360.0F)
Yaw Angle To get the real yaw, you must divide this by (256.0F / 360.0F)
Head Yaw Angle Only used by living entities, where the head of the entity may differ from the general body rotation.
Data VarInt Meaning dependent on the value of the Type field, see Object Data for details.
Velocity X Short Same units as Set Entity Velocity.
Velocity Y Short
Velocity Z Short
The points listed below should be considered when this packet is used to spawn a player entity.

When in online mode, the UUIDs must be valid and have valid skin blobs. In offline mode, the vanilla server uses UUID v3 and chooses the player's UUID by using the String OfflinePlayer:<player name>, encoding it in UTF-8 (and case-sensitive), then processes it with UUID.nameUUIDFromBytes.

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.

Spawn Experience Orb[edit | edit source]

Spawns one or more experience orbs.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x02

resource:
add_experience_orb
Play Client Entity ID VarInt
X Double
Y Double
Z Double
Count Short The amount of experience this orb will reward once collected.

Entity Animation[edit | edit source]

Sent whenever an entity should change animation.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x03

resource:
animate
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
2 Leave bed
3 Swing offhand
4 Critical effect
5 Magic critical effect

Award Statistics[edit | edit source]

Sent as a response to Client Status (id 1). Will only send the changed values if previously requested.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x04

resource:
award_stats
Play Client Statistic Category ID Prefixed 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_time 1 Time
minecraft.total_world_time 2 Time
minecraft.time_since_death 3 Time
minecraft.time_since_rest 4 Time
minecraft.sneak_time 5 Time
minecraft.walk_one_cm 6 Distance
minecraft.crouch_one_cm 7 Distance
minecraft.sprint_one_cm 8 Distance
minecraft.walk_on_water_one_cm 9 Distance
minecraft.fall_one_cm 10 Distance
minecraft.climb_one_cm 11 Distance
minecraft.fly_one_cm 12 Distance
minecraft.walk_under_water_one_cm 13 Distance
minecraft.minecart_one_cm 14 Distance
minecraft.boat_one_cm 15 Distance
minecraft.pig_one_cm 16 Distance
minecraft.horse_one_cm 17 Distance
minecraft.aviate_one_cm 18 Distance
minecraft.swim_one_cm 19 Distance
minecraft.strider_one_cm 20 Distance
minecraft.jump 21 None
minecraft.drop 22 None
minecraft.damage_dealt 23 Damage
minecraft.damage_dealt_absorbed 24 Damage
minecraft.damage_dealt_resisted 25 Damage
minecraft.damage_taken 26 Damage
minecraft.damage_blocked_by_shield 27 Damage
minecraft.damage_absorbed 28 Damage
minecraft.damage_resisted 29 Damage
minecraft.deaths 30 None
minecraft.mob_kills 31 None
minecraft.animals_bred 32 None
minecraft.player_kills 33 None
minecraft.fish_caught 34 None
minecraft.talked_to_villager 35 None
minecraft.traded_with_villager 36 None
minecraft.eat_cake_slice 37 None
minecraft.fill_cauldron 38 None
minecraft.use_cauldron 39 None
minecraft.clean_armor 40 None
minecraft.clean_banner 41 None
minecraft.clean_shulker_box 42 None
minecraft.interact_with_brewingstand 43 None
minecraft.interact_with_beacon 44 None
minecraft.inspect_dropper 45 None
minecraft.inspect_hopper 46 None
minecraft.inspect_dispenser 47 None
minecraft.play_noteblock 48 None
minecraft.tune_noteblock 49 None
minecraft.pot_flower 50 None
minecraft.trigger_trapped_chest 51 None
minecraft.open_enderchest 52 None
minecraft.enchant_item 53 None
minecraft.play_record 54 None
minecraft.interact_with_furnace 55 None
minecraft.interact_with_crafting_table 56 None
minecraft.open_chest 57 None
minecraft.sleep_in_bed 58 None
minecraft.open_shulker_box 59 None
minecraft.open_barrel 60 None
minecraft.interact_with_blast_furnace 61 None
minecraft.interact_with_smoker 62 None
minecraft.interact_with_lectern 63 None
minecraft.interact_with_campfire 64 None
minecraft.interact_with_cartography_table 65 None
minecraft.interact_with_loom 66 None
minecraft.interact_with_stonecutter 67 None
minecraft.bell_ring 68 None
minecraft.raid_trigger 69 None
minecraft.raid_win 70 None
minecraft.interact_with_anvil 71 None
minecraft.interact_with_grindstone 72 None
minecraft.target_hit 73 None
minecraft.interact_with_smithing_table 74 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 Block Change[edit | edit source]

Acknowledges a user-initiated block change. After receiving this packet, the client will display the block state sent by the server instead of the one predicted by the client.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x05

resource:
block_changed_ack
Play Client Sequence ID VarInt Represents the sequence to acknowledge, this is used for properly syncing block changes to the client after interactions.

Set Block Destroy Stage[edit | edit source]

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
protocol:
0x06

resource:
block_destruction
Play Client Entity ID VarInt The ID of the entity breaking the block.
Location Position Block Position.
Destroy Stage Unsigned Byte 0–9 to set it, any other value to remove it.

Block Entity Data[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x07

resource:
block_entity_data
Play Client Location Position
Type VarInt The type of the block entity
NBT Data NBT 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).

Block Action[edit | edit source]

This packet is used for a number of actions and animations performed by blocks, usually non-persistent. The client ignores the provided block type and instead uses the block state in their world.

See Block Actions for a list of values.

This packet uses a block ID from the minecraft:block registry, not a block state.
Packet ID State Bound To Field Name Field Type Notes
protocol:
0x08

resource:
block_event
Play Client Location Position Block coordinates.
Action ID (Byte 1) Unsigned Byte Varies depending on block — see Block Actions.
Action Parameter (Byte 2) Unsigned Byte Varies depending on block — see Block Actions.
Block Type VarInt The block type ID for the block. This value is unused by the vanilla client, as it will infer the type of block based on the given position.

Block Update[edit | edit source]

Fired whenever a block is changed within the render distance.

Changing a block in a chunk that is not loaded is not a stable action. The vanilla 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
protocol:
0x09

resource:
block_update
Play Client Location Position Block Coordinates.
Block ID VarInt The new block state ID for the block as given in the block state registry.

Boss Bar[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0A

resource:
boss_event
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 Text Component
Health Float From 0 to 1. Values greater than 1 do not crash a vanilla 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. 0x01: should darken sky, 0x02: 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 Text Component
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

Change Difficulty[edit | edit source]

Changes the difficulty setting in the client's option menu

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0B

resource:
change_difficulty
Play Client Difficulty Unsigned Byte Enum 0: peaceful, 1: easy, 2: normal, 3: hard.
Difficulty locked? Boolean

Chunk Batch Finished[edit | edit source]

Marks the end of a chunk batch. The vanilla client marks the time it receives this packet and calculates the elapsed duration since the beginning of the chunk batch. The server uses this duration and the batch size received in this packet to estimate the number of milliseconds elapsed per chunk received. This value is then used to calculate the desired number of chunks per tick through the formula 25 / millisPerChunk, which is reported to the server through Chunk Batch Received. This likely uses 25 instead of the normal tick duration of 50 so chunk processing will only use half of the client's and network's bandwidth.

The vanilla client uses the samples from the latest 15 batches to estimate the milliseconds per chunk number.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0C

resource:
chunk_batch_finished
Play Client Batch size VarInt Number of chunks.

Chunk Batch Start[edit | edit source]

Marks the start of a chunk batch. The vanilla client marks and stores the time it receives this packet.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0D

resource:
chunk_batch_start
Play Client no fields

Chunk Biomes[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0E

resource:
chunks_biomes
Play Client Chunk biome data Chunk Z Prefixed Array Int Chunk coordinate (block coordinate divided by 16, rounded down)
Chunk X Int Chunk coordinate (block coordinate divided by 16, rounded down)
Data Prefixed Array of Byte Chunk data structure, with sections containing only the Biomes field

Note: The order of X and Z is inverted, because the client reads them as one big-endian Long, with Z being the upper 32 bits.

Clear Titles[edit | edit source]

Clear the client's current title information, with the option to also reset it.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0F

resource:
clear_titles
Play Client Reset Boolean

Command Suggestions Response[edit | edit source]

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
protocol:
0x10

resource:
command_suggestions
Play Client ID VarInt Transaction ID.
Start VarInt Start of the text to replace.
Length VarInt Length of the text to replace.
Matches Match Prefixed 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.
Tooltip Prefixed Optional Text Component Tooltip to display.

Commands[edit | edit source]

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
protocol:
0x11

resource:
commands
Play Client Nodes Prefixed 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.

Close Container[edit | edit source]

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. The vanilla client disregards the provided window ID and closes any active window.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x12

resource:
container_close
Play Client Window ID VarInt This is the ID of the window that was closed. 0 for inventory.

Set Container Content[edit | edit source]

The inventory slots

Replaces the contents of a container window. Sent by the server upon initialization of a container window or the player's inventory, and in response to state ID mismatches (see #Click Container).

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x13

resource:
container_set_content
Play Client Window ID VarInt The ID of window which items are being sent for. 0 for player inventory. The client ignores any packets targeting a Window ID other than the current one. However, an exception is made for the player inventory, which may be targeted at any time. (The vanilla server does not appear to utilize this special case.)
State ID VarInt A server-managed sequence number used to avoid desynchronization; see #Click Container.
Slot Data Prefixed Array of Slot
Carried Item Slot Item being dragged with the mouse.

See inventory windows for further information about how slots are indexed. Use Open Screen to open the container on the client.

Set Container Property[edit | edit source]

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
protocol:
0x14

resource:
container_set_data
Play Client Window ID VarInt
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 vanilla 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
Stonecutter 0: Selected recipe The index of the selected recipe. -1 means none is selected.
Loom 0: Selected pattern The index of the selected pattern. 0 means none is selected, 0 is also the internal id of the "base" pattern.
Lectern 0: Page number The current page number, starting from 0.

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:soul_speed Soul Speed
12 minecraft:swift_sneak Swift Sneak
13 minecraft:sharpness Sharpness
14 minecraft:smite Smite
15 minecraft:bane_of_arthropods Bane of Arthropods
16 minecraft:knockback Knockback
17 minecraft:fire_aspect Fire Aspect
18 minecraft:looting Looting
19 minecraft:sweeping_edge Sweeping Edge
20 minecraft:efficiency Efficiency
21 minecraft:silk_touch Silk Touch
22 minecraft:unbreaking Unbreaking
23 minecraft:fortune Fortune
24 minecraft:power Power
25 minecraft:punch Punch
26 minecraft:flame Flame
27 minecraft:infinity Infinity
28 minecraft:luck_of_the_sea Luck of the Sea
29 minecraft:lure Lure
30 minecraft:loyalty Loyalty
31 minecraft:impaling Impaling
32 minecraft:riptide Riptide
33 minecraft:channeling Channeling
34 minecraft:multishot Multishot
35 minecraft:quick_charge Quick Charge
36 minecraft:piercing Piercing
37 minecraft:density Density
38 minecraft:breach Breach
39 minecraft:wind_burst Wind Burst
40 minecraft:mending Mending
41 minecraft:vanishing_curse Curse of Vanishing

Set Container Slot[edit | edit source]

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
protocol:
0x15

resource:
container_set_slot
Play Client Window ID VarInt The window which is being updated. 0 for player inventory. The client ignores any packets targeting a Window ID other than the current one; see below for exceptions.
State ID VarInt A server-managed sequence number used to avoid desynchronization; see #Click Container.
Slot Short The slot that should be updated.
Slot Data Slot

If Window ID is 0, the hotbar and offhand slots (slots 36 through 45) may be updated even when a different container window is open. (The vanilla server does not appear to utilize this special case.) Updates are also restricted to those slots when the player is looking at a creative inventory tab other than the survival inventory. (The vanilla server does not handle this restriction in any way, leading to MC-242392.)

If Window ID is -1, the item being dragged with the mouse is set. In this case, State ID and Slot are ignored.

If Window ID is -2, any slot in the player's inventory can be updated irrespective of the current container window. In this case, State ID is ignored, and the vanilla server uses a bogus value of 0. Used by the vanilla server to implement the #Pick Item functionality.

When a container window is open, the server never sends updates targeting Window ID 0—all of the window types include slots for the player inventory. The client must automatically apply changes targeting the inventory portion of a container window to the main inventory; the server does not resend them for ID 0 when the window is closed. However, since the armor and offhand slots are only present on ID 0, updates to those slots occurring while a window is open must be deferred by the server until the window's closure.

Cookie Request (play)[edit | edit source]

Requests a cookie that was previously stored.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x16

resource:
cookie_request
Play Client Key Identifier The identifier of the cookie.

Set Cooldown[edit | edit source]

Applies a cooldown period to all items with the given type. Used by the vanilla 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
protocol:
0x17

resource:
cooldown
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.

Chat Suggestions[edit | edit source]

Unused by the vanilla server. Likely provided for custom servers to send chat message completions to clients.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x18

resource:
custom_chat_completions
Play Client Action VarInt Enum 0: Add, 1: Remove, 2: Set
Entries Prefixed Array of String (32767)

Clientbound Plugin Message (play)[edit | edit source]

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 information on how it works on Dinnerbone's blog. More documentation about internal and popular registered channels are here.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x19

resource:
custom_payload
Play Client Channel Identifier Name of the plugin channel used to send the data.
Data Byte Array (1048576) Any data. The length of this array must be inferred from the packet length.

In vanilla clients, the maximum data length is 1048576 bytes.

Damage Event[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x1A

resource:
damage_event
Play Client
Entity ID VarInt The ID of the entity taking damage
Source Type ID VarInt The type of damage in the minecraft:damage_type registry, defined by the Registry Data packet.
Source Cause ID VarInt The ID + 1 of the entity responsible for the damage, if present. If not present, the value is 0
Source Direct ID VarInt The ID + 1 of the entity that directly dealt the damage, if present. If not present, the value is 0. If this field is present:
  • and damage was dealt indirectly, such as by the use of a projectile, this field will contain the ID of such projectile;
  • and damage was dealt dirctly, such as by manually attacking, this field will contain the same value as Source Cause ID.
Has Source Position Boolean Indicates the presence of the three following fields.

The vanilla server sends the Source Position when the damage was dealt by the /damage command and a position was specified

Source Position X Optional Double Only present if Has Source Position is true
Source Position Y Optional Double Only present if Has Source Position is true
Source Position Z Optional Double Only present if Has Source Position is true

Debug Sample[edit | edit source]

Sample data that is sent periodically after the client has subscribed with Debug Sample Subscription.

The vanilla server only sends debug samples to players that are server operators.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x1B

resource:
debug_sample
Play Client Sample Prefixed Array of Long Array of type-dependent samples.
Sample Type VarInt Enum See below.

Types:

Id Name Description
0 Tick time Four different tick-related metrics, each one represented by one long on the array.

They are measured in nano-seconds, and are as follows:

  • 0: Full tick time: Aggregate of the three times below;
  • 1: Server tick time: Main server tick logic;
  • 2: Tasks time: Tasks scheduled to execute after the main logic;
  • 3: Idle time: Time idling to complete the full 50ms tick cycle.

Note that the vanilla client calculates the timings used for min/max/average display by subtracting the idle time from the full tick time. This can cause the displayed values to go negative if the idle time is (nonsensically) greater than the full tick time.

Delete Message[edit | edit source]

Removes a message from the client's chat. This only works for messages with signatures, system messages cannot be deleted with this packet.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x1C

resource:
delete_chat
Play Client Message ID VarInt The message Id + 1, used for validating message signature. The next field is present only when value of this field is equal to 0.
Signature Optional Byte Array (256) The previous message's signature. Always 256 bytes and not length-prefixed.

Disconnect (play)[edit | edit source]

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
protocol:
0x1D

resource:
disconnect
Play Client Reason Text Component Displayed to the client when the connection terminates.

Disguised Chat Message[edit | edit source]

Main article: Chat

Sends the client a chat message, but without any message signing information.

The vanilla server uses this packet when the console is communicating with players through commands, such as /say, /tell, /me, among others.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x1E

resource:
disguised_chat
Play Client Message Text Component This is used as the content parameter when formatting the message on the client.
Chat Type VarInt The type of chat in the minecraft:chat_type registry, defined by the Registry Data packet.
Sender Name Text Component The name of the one sending the message, usually the sender's display name.

This is used as the sender parameter when formatting the message on the client.

Target Name Prefixed Optional Text Component The name of the one receiving the message, usually the receiver's display name.

This is used as the target parameter when formatting the message on the client.

Entity Event[edit | edit source]

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
protocol:
0x1F

resource:
entity_event
Play Client Entity ID Int
Entity Status Byte Enum See Entity statuses for a list of which statuses are valid for each type of entity.

Teleport Entity[edit | edit source]

The Mojang-specified name of this packet was changed in 1.21.2 from teleport_entity to entity_position_sync. There is a new teleport_entity, which this document more appropriately calls Synchronize Vehicle Position. That packet has a different function and will lead to confusing results if used in place of this one.

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
protocol:
0x20

resource:
entity_position_sync
Play Client Entity ID VarInt
X Double
Y Double
Z Double
Velocity X Double
Velocity Y Double
Velocity Z Double
Yaw Float Rotation on the X axis, in degrees.
Pitch Float Rotation on the Y axis, in degrees.
On Ground Boolean

Explosion[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x21

resource:
explode
Play Client X Double
Y Double
Z Double
Has Player Velocity Boolean
Player Velocity X Optional Double X velocity of the player being pushed by the explosion. Only present if Has Player Velocity is true.
Player Velocity Y Optional Float Y velocity of the player being pushed by the explosion. Only present if Has Player Velocity is true.
Player Velocity Z Optional Float Z velocity of the player being pushed by the explosion. Only present if Has Player Velocity is true.
Explosion Particle ID VarInt The particle ID listed in Particles.
Explosion Particle Data Varies Particle data as specified in Particles.
Explosion Sound ID or Sound Event ID in the minecraft:sound_event registry, or an inline definition.

Unload Chunk[edit | edit source]

Tells the client to unload a chunk column.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x22

resource:
forget_level_chunk
Play Client Chunk Z Int Block coordinate divided by 16, rounded down.
Chunk X Int Block coordinate divided by 16, rounded down.

Note: The order is inverted, because the client reads this packet as one big-endian Long, with Z being the upper 32 bits.

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

Game Event[edit | edit source]

Used for a wide variety of game events, from weather to bed use to game mode to demo messages.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x23

resource:
game_event
Play Client Event Unsigned Byte See below.
Value Float Depends on Event.

Events:

Event Effect Value
0 No respawn block available Note: Displays message 'block.minecraft.spawn.not_valid' (You have no home bed or charged respawn anchor, or it was obstructed) to the player.
1 Begin raining
2 End raining
3 Change game mode 0: Survival, 1: Creative, 2: Adventure, 3: Spectator.
4 Win game 0: Just respawn player.
1: Roll the credits and respawn player.
Note that 1 is only sent by vanilla server when player has not yet achieved advancement "The end?", else 0 is sent.
5 Demo event 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 hit player Note: Sent when any player is struck by an arrow.
7 Rain level change Note: Seems to change both sky color and lighting.
Rain level ranging from 0 to 1.
8 Thunder level change Note: Seems to change both sky color and lighting (same as Rain level change, but doesn't start rain). It also requires rain to render by vanilla client.
Thunder level ranging from 0 to 1.
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).
12 Limited crafting 0: Disable limited crafting.
1: Enable limited crafting (sent when the doLimitedCrafting gamerule changes).
13 Start waiting for level chunks Instructs the client to begin the waiting process for the level chunks.
Sent by the server after the level is cleared on the client and is being re-sent (either during the first, or subsequent reconfigurations).

Open Horse Screen[edit | edit source]

This packet is used exclusively for opening the horse GUI. Open Screen is used for all other GUIs. The client will not open the inventory if the Entity ID does not point to an horse-like animal.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x24

resource:
horse_screen_open
Play Client Window ID VarInt Same as the field of Open Screen.
Inventory columns count VarInt How many columns of horse inventory slots exist in the GUI, 3 slots per column.
Entity ID Int The "owner" entity of the GUI. The client should close the GUI if the owner entity dies or is cleared.

Hurt Animation[edit | edit source]

Plays a bobbing animation for the entity receiving damage.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x25

resource:
hurt_animation
Play Client Entity ID VarInt The ID of the entity taking damage
Yaw Float The direction the damage is coming from in relation to the entity

Initialize World Border[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x26

resource:
initialize_border
Play Client 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 vanilla 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 Blocks VarInt In meters.
Warning Time VarInt In seconds as set by /worldborder warning time.

The vanilla 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;
}

Clientbound Keep Alive (play)[edit | edit source]

The server will frequently send out a keep-alive, each containing a random ID. The client must respond with the same payload (see Serverbound Keep Alive). If the client does not respond to a Keep Alive packet within 15 seconds after it was sent, 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 vanilla 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
protocol:
0x27

resource:
keep_alive
Play Client Keep Alive ID Long

Chunk Data and Update Light[edit | edit source]

Sent when a chunk comes into the client's view distance, specifying its terrain, lighting and block entities.

The chunk must be within the view area previously specified with Set Center Chunk; see that packet for details.

It is not strictly necessary to send all block entities in this packet; it is still legal to send them with Block Entity Data later.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x28

resource:
level_chunk_with_light
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)
Data Chunk Data
Light Light Data

Unlike the Update Light packet which uses the same format, setting the bit corresponding to a section to 0 in both of the block light or sky light masks does not appear to be useful, and the results in testing have been highly inconsistent.

World Event[edit | edit source]

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), effect 1028 (enderdragon death), and effect 1038 (end portal opening); it is ignored on other effects.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x29

resource:
level_event
Play Client Event Int The event, see below.
Location Position The location of the event.
Data Int Extra data for certain events, see below.
Disable Relative Volume Boolean See above.

Events:

ID Name Data
Sound
1000 Dispenser dispenses
1001 Dispenser fails to dispense
1002 Dispenser shoots
1004 Firework shot
1009 Fire extinguished
1010 Play record An ID in the minecraft:item registry, corresponding to a record item. If the ID doesn't correspond to a record, the packet is ignored. Any record already being played at the given location is overwritten. See Data Generators for information on item IDs.
1011 Stop record
1015 Ghast warns
1016 Ghast shoots
1017 Ender dragon shoots
1018 Blaze shoots
1019 Zombie attacks wooden door
1020 Zombie attacks iron door
1021 Zombie breaks wooden 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 dies
1029 Anvil destroyed
1030 Anvil used
1031 Anvil lands
1032 Portal travel
1033 Chorus flower grows
1034 Chorus flower dies
1035 Brewing stand brews
1038 End portal created
1039 Phantom bites
1040 Zombie converts to drowned
1041 Husk converts to zombie by drowning
1042 Grindstone used
1043 Book page turned
1044 Smithing table used
1045 Pointed dripstone landing
1046 Lava dripping on cauldron from dripstone
1047 Water dripping on cauldron from dripstone
1048 Skeleton converts to stray
1049 Crafter successfully crafts item
1050 Crafter fails to craft item
Particle
1500 Composter composts
1501 Lava converts block (either water to stone, or removes existing blocks such as torches)
1502 Redstone torch burns out
1503 Ender eye placed in end portal frame
1504 Fluid drips from dripstone
1505 Bone meal particles and sound How many particles to spawn.
2000 Dispenser activation smoke Direction, see below.
2001 Block break + block break sound Block state ID (see Chunk Format#Block state registry).
2002 Splash potion. Particle effect + glass break sound. RGB color as an integer (e.g. 8364543 for #7FA1FF).
2003 Eye of ender entity break animation — particles and sound
2004 Spawner spawns mob: smoke + flames
2006 Dragon breath
2007 Instant splash potion. Particle effect + glass break sound. RGB color as an integer (e.g. 8364543 for #7FA1FF).
2008 Ender dragon destroys block
2009 Wet sponge vaporizes
2010 Crafter activation smoke Direction, see below.
2011 Bee fertilizes plant How many particles to spawn.
2012 Turtle egg placed How many particles to spawn.
2013 Smash attack (mace) How many particles to spawn.
3000 End gateway spawns
3001 Ender dragon resurrected
3002 Electric spark
3003 Copper apply wax
3004 Copper remove wax
3005 Copper scrape oxidation
3006 Sculk charge
3007 Sculk shrieker shriek
3008 Block finished brushing Block state ID (see Chunk Format#Block state registry)
3009 Sniffer egg cracks If 1, 3-6, if any other number, 1-3 particles will be spawned.
3011 Trial spawner spawns mob (at spawner)
3012 Trial spawner spawns mob (at spawn location)
3013 Trial spawner detects player Number of players nearby
3014 Trial spawner ejects item
3015 Vault activates
3016 Vault deactivates
3017 Vault ejects item
3018 Cobweb weaved
3019 Ominous trial spawner detects player Number of players nearby
3020 Trial spawner turns ominous If 0, the sound will be played at 0.3 volume. Otherwise, it is played at full volume.
3021 Ominous item spawner spawns item

Smoke directions:

ID Direction
0 Down
1 Up
2 North
3 South
4 West
5 East

Particle[edit | edit source]

Displays the named particle

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x2A

resource:
level_particles
Play Client Long Distance Boolean If true, particle distance increases from 256 to 65536.
Always Visible Boolean Whether this particle should always be visible.
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().
Max Speed Float
Particle Count Int The number of particles to create.
Particle ID VarInt The particle ID listed in Particles.
Data Varies Particle data as specified in Particles.

Update Light[edit | edit source]

Updates light levels for a chunk. See Light for information on how lighting works in Minecraft.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x2B

resource:
light_update
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)
Data Light Data

A bit will never be set in both the block light mask and the empty block light mask, though it may be present in neither of them (if the block light does not need to be updated for the corresponding chunk section). The same applies to the sky light mask and the empty sky light mask.

Login (play)[edit | edit source]

This section is missing information about: Although the number of portal cooldown ticks is included in this packet, the whole portal usage process is still dictated entirely by the server. What kind of effect does this value have on the client, if any?.
 
Please expand the section to include this information. Further details may exist on the talk page.

See protocol encryption for information on logging in.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x2C

resource:
login
Play Client Entity ID Int The player's Entity ID (EID).
Is hardcore Boolean
Dimension Names Prefixed Array of Identifier Identifiers for all dimensions on the server.
Max Players VarInt Was once used by the client to draw the player list, but now is ignored.
View Distance VarInt Render distance (2-32).
Simulation Distance VarInt The distance that the client will process specific things, such as entities.
Reduced Debug Info Boolean If true, a vanilla 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.
Do limited crafting Boolean Whether players can only craft recipes they have already unlocked. Currently unused by the client.
Dimension Type VarInt The ID of the type of dimension in the minecraft:dimension_type registry, defined by the Registry Data packet.
Dimension Name Identifier Name of the dimension being spawned into.
Hashed seed Long First 8 bytes of the SHA-256 hash of the world's seed. Used client side for biome noise
Game mode Unsigned Byte 0: Survival, 1: Creative, 2: Adventure, 3: Spectator.
Previous Game mode Byte -1: Undefined (null), 0: Survival, 1: Creative, 2: Adventure, 3: Spectator. The previous game mode. Vanilla client uses this for the debug (F3 + N & F3 + F4) game mode switch. (More information needed)
Is Debug Boolean True if the world is a debug mode world; debug mode worlds cannot be modified and have predefined blocks.
Is Flat Boolean True if the world is a superflat world; flat worlds have different void fog and a horizon at y=0 instead of y=63.
Has death location Boolean If true, then the next two fields are present.
Death dimension name Optional Identifier Name of the dimension the player died in.
Death location Optional Position The location that the player died at.
Portal cooldown VarInt The number of ticks until the player can use the portal again.
Sea level VarInt
Enforces Secure Chat Boolean

Map Data[edit | edit source]

Updates a rectangular area on a map item.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x2D

resource:
map_item_data
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)
Locked Boolean True if the map has been locked in a cartography table
Icon Type Prefixed Optional Prefixed 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
Display Name Prefixed Optional Text Component
Color Patch Columns Unsigned Byte Number of columns updated
Rows Optional Unsigned Byte Only if Columns is more than 0; number of rows updated
X Optional Unsigned Byte Only if Columns is more than 0; x offset of the westernmost column
Z Optional Unsigned Byte Only if Columns is more than 0; z offset of the northernmost row
Data Optional Prefixed 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 Monument
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
27 Desert Village
28 Plains Village
29 Savanna Village
30 Snowy Village
31 Taiga Village
32 Jungle Temple
33 Swamp Hut
34 Trial Chambers

Merchant Offers[edit | edit source]

The list of trades a villager NPC is offering.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x2E

resource:
merchant_offers
Play Client Window ID VarInt The ID of the window that is open; this is an int rather than a byte.
Trades Input item 1 Prefixed Array Trade Item See below. The first item the player has to supply for this villager trade. The count of the item stack is the default "price" of this trade.
Output item Slot The item the player will receive from this villager trade.
Input item 2 Prefixed Optional Trade Item The second item the player has to supply for this villager trade.
Trade disabled Boolean True if the trade is disabled; false if the trade is enabled.
Number of trade uses Int Number of times the trade has been used so far. If equal to the maximum number of trades, the client will display a red X.
Maximum number of trade uses Int Number of times this trade can be used before it's exhausted.
XP Int Amount of XP the villager will earn each time the trade is used.
Special Price Int Can be zero or negative. The number is added to the price when an item is discounted due to player reputation or other effects.
Price Multiplier Float Can be low (0.05) or high (0.2). Determines how much demand, player reputation, and temporary effects will adjust the price.
Demand Int If positive, causes the price to increase. Negative values seem to be treated the same as zero.
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.

Trade Item:

Field Name Field Type Meaning
Item ID VarInt The item ID. Item IDs are distinct from block IDs; see Data Generators for more information.
Item Count VarInt The item count.
Components Component type Prefixed Array VarInt Enum The type of component. See Structured components for more detail.
Component data Varies The component-dependent data. See Structured components for more detail.

Modifiers can increase or decrease the number of items for the first input slot. The second input slot and the output slot never change the number of items. The number of items may never be less than 1, and never more than the stack size. If special price and demand are both zero, only the default price is displayed. If either is non-zero, then the adjusted price is displayed next to the crossed-out default price. The adjusted prices is calculated as follows:

Adjusted price = default price + floor(default price x multiplier x demand) + special price

The merchant UI, for reference

Update Entity Position[edit | edit source]

This packet is sent by the server when an entity moves a small distance. The change in position is represented as a fixed-point number with 12 fraction bits and 4 integer bits. As such, the maximum movement distance along each axis is 8 blocks in the negative direction, or 7.999755859375 blocks in the positive direction. If the movement exceeds these limits, Teleport Entity should be sent instead.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x2F

resource:
move_entity_pos
Play Client Entity ID VarInt
Delta X Short Change in X position as currentX * 4096 - prevX * 4096.
Delta Y Short Change in Y position as currentY * 4096 - prevY * 4096.
Delta Z Short Change in Z position as currentZ * 4096 - prevZ * 4096.
On Ground Boolean

Update Entity Position and Rotation[edit | edit source]

This packet is sent by the server when an entity rotates and moves. See #Update Entity Position for how the position is encoded.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x30

resource:
move_entity_pos_rot
Play Client Entity ID VarInt
Delta X Short Change in X position as currentX * 4096 - prevX * 4096.
Delta Y Short Change in Y position as currentY * 4096 - prevY * 4096.
Delta Z Short Change in Z position as currentZ * 4096 - prevZ * 4096.
Yaw Angle New angle, not a delta.
Pitch Angle New angle, not a delta.
On Ground Boolean

Move Minecart Along Track[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x31

resource:
move_minecart_along_track
Play Client Entity ID VarInt
Steps X Prefixed Array Double
Y Double
Z Double
Velocity X Double
Velocity Y Double
Velocity Z Double
Yaw Angle
Pitch Angle
Weight Float

Update Entity Rotation[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x32

resource:
move_entity_rot
Play Client Entity ID VarInt
Yaw Angle New angle, not a delta.
Pitch Angle New angle, not a delta.
On Ground Boolean

Move Vehicle[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x33

resource:
move_vehicle
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[edit | edit source]

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
protocol:
0x34

resource:
open_book
Play Client Hand VarInt Enum 0: Main hand, 1: Off hand .

Open Screen[edit | edit source]

This is sent to the client when it should open an inventory, such as a chest, workbench, furnace, or other container. Resending this packet with already existing window id, will update the window title and window type without closing the window.

This message is not sent to clients opening their own inventory, nor do clients inform the server in any way when doing so. From the server's perspective, the inventory is always "open" whenever no other windows are.

For horses, use Open Horse Screen.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x35

resource:
open_screen
Play Client Window ID VarInt An identifier for the window to be displayed. vanilla server implementation is a counter, starting at 1. There can only be one window at a time; this is only used to ignore outdated packets targeting already-closed windows. Note also that the Window ID field in most other packets is only a single byte, and indeed, the vanilla server wraps around after 100.
Window Type VarInt The window type to use for display. Contained in the minecraft:menu registry; see Inventory for the different values.
Window Title Text Component The title of the window.

Open Sign Editor[edit | edit source]

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 Update first.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x36

resource:
open_sign_editor
Play Client Location Position
Is Front Text Boolean Whether the opened editor is for the front or on the back of the sign

Ping (play)[edit | edit source]

Packet is not used by the vanilla server. When sent to the client, client responds with a Pong packet with the same id.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x37

resource:
ping
Play Client ID Int

Ping Response (play)[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x38

resource:
pong_response
Play Client Payload Long Should be the same as sent by the client.

Place Ghost Recipe[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x39

resource:
place_ghost_recipe
Play Client Window ID VarInt
Recipe Display Recipe Display

Player Abilities (clientbound)[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x3A

resource:
player_abilities
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 vanilla server will use the same value as the movement speed sent in the Update Attributes 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

If Flying is set but Allow Flying is unset, the player is unable to stop flying.

Player Chat Message[edit | edit source]

Main article: Chat

Sends the client a chat message from a player.

Currently a lot is unknown about this packet, blank descriptions are for those that are unknown

Packet ID State Bound To Sector Field Name Field Type Notes
protocol:
0x3B

resource:
player_chat
Play Client Header Sender UUID Used by the vanilla client for the disableChat launch option. Setting both longs to 0 will always display the message regardless of the setting.
Index VarInt
Message Signature bytes Prefixed Optional Byte Array (256) Cryptography, the signature consists of the Sender UUID, Session UUID from the Player Session packet, Index, Salt, Timestamp in epoch seconds, the length of the original chat content, the original content itself, the length of Previous Messages, and all of the Previous message signatures. These values are hashed with SHA-256 and signed using the RSA cryptosystem. Modifying any of these values in the packet will cause this signature to fail. This buffer is always 256 bytes long and it is not length-prefixed.
Body Message String (256) Raw (optionally) signed sent message content.

This is used as the content parameter when formatting the message on the client.

Timestamp Long Represents the time the message was signed as milliseconds since the epoch, used to check if the message was received within 2 minutes of it being sent.
Salt Long Cryptography, used for validating the message signature.
Prefixed Array (20) Message ID VarInt The message Id + 1, used for validating message signature. The next field is present only when value of this field is equal to 0.
Signature Optional Byte Array (256) The previous message's signature. Contains the same type of data as Message Signature bytes (256 bytes) above. Not length-prefxied.
Other Unsigned Content Prefixed Optional Text Component
Filter Type VarInt Enum If the message has been filtered
Filter Type Bits Optional BitSet Only present if the Filter Type is Partially Filtered. Specifies the indexes at which characters in the original message string should be replaced with the # symbol (i.e. filtered) by the vanilla client
Chat Formatting Chat Type VarInt The type of chat in the minecraft:chat_type registry, defined by the Registry Data packet. This should not be 0, meaning it is likely index+1
Sender Name Text Component The name of the one sending the message, usually the sender's display name.

This is used as the sender parameter when formatting the message on the client.

Target Name Prefixed Optional Text Component The name of the one receiving the message, usually the receiver's display name.

This is used as the target parameter when formatting the message on the client.

Player Chat Handling Logic

Filter Types:

The filter type mask should NOT be specified unless partially filtered is selected

ID Name Description
0 PASS_THROUGH Message is not filtered at all
1 FULLY_FILTERED Message is fully filtered
2 PARTIALLY_FILTERED Only some characters in the message are filtered

End Combat[edit | edit source]

Unused by the vanilla client. This data was once used for twitch.tv metadata circa 1.8.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x3C

resource:
player_combat_end
Play Client Duration VarInt Length of the combat in ticks.

Enter Combat[edit | edit source]

Unused by the vanilla client. This data was once used for twitch.tv metadata circa 1.8.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x3D

resource:
player_combat_enter
Play Client no fields

Combat Death[edit | edit source]

Used to send a respawn screen.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x3E

resource:
player_combat_kill
Play Client Player ID VarInt Entity ID of the player that died (should match the client's entity ID).
Message Text Component The death message.

Player Info Remove[edit | edit source]

Used by the server to remove players from the player list.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x3F

resource:
player_info_remove
Play Client UUIDs Prefixed Array of UUID UUIDs of players to remove.

Player Info Update[edit | edit source]

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

The EnumSet type is only used here and it is currently undocumented
Packet ID State Bound To Field Name Field Type Notes
protocol:
0x40

resource:
player_info_update
Play Client Actions EnumSet Determines what actions are present.
Players UUID Prefixed Array UUID The player UUID
Player Actions Array of Player Actions The length of this array is determined by the number of Player Actions that give a non-zero value when applying its mask to the actions flag. For example given the decimal number 5, binary 00000101. The masks 0x01 and 0x04 would return a non-zero value, meaning the Player Actions array would include two actions: Add Player and Update Game Mode.


Player Actions
Action Mask Field Name Type Notes
Add Player 0x01 Name String (16)
Property Name Prefixed Array (16) String (64)
Value String (32767)
Signature Prefixed Optional String (1024)
Initialize Chat 0x02 Data Chat session ID Prefixed Optional UUID
Public key expiry time Long Key expiry time, as a UNIX timestamp in milliseconds. Only sent if Has Signature Data is true.
Encoded public key Prefixed Array (512) of Byte The player's public key, in bytes. Only sent if Has Signature Data is true.
Public key signature Prefixed Array (4096) of Byte The public key's digital signature. Only sent if Has Signature Data is true.
Update Game Mode 0x04 Game Mode VarInt
Update Listed 0x08 Listed Boolean Whether the player should be listed on the player list.
Update Latency 0x10 Ping VarInt Measured in milliseconds.
Update Display Name 0x20 Display Name Prefixed Optional Text Component Only sent if Has Display Name is true.
Update List Priority 0x40 Priority VarInt See below.
Update Hat 0x80 Visible Boolean Whether the player's hat skin layer is shown.

The properties included in this packet are the same as in Login Success, for the current player.

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.

The order of players in the player list is determined as follows:

  • Players with higher priorities are sorted before those with lower priorities.
  • Among players of equal priorities, spectators are sorted after non-spectators.
  • Within each of those groups, players are sorted into teams. The teams are ordered case-sensitively by team name in ascending order. Players with no team are listed first.
  • The players of each team (and non-team) are sorted case-insensitively by name in ascending order.

Look At[edit | edit source]

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
protocol:
0x41

resource:
player_look_at
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.

Synchronize Player Position[edit | edit source]

Teleports the client, e.g. during login, when using an ender pearl, in response to invalid move packets, etc.

Due to latency, the server may receive outdated movement packets sent before the client was aware of the teleport. To account for this, the server ignores all movement packets from the client until a Confirm Teleportation packet with an ID matching the one sent in the teleport packet is received.

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 (see MC-90097).

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
protocol:
0x42

resource:
player_position
Play Client Teleport ID VarInt Client should confirm this packet with Confirm Teleportation containing the same Teleport ID.
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.
Velocity X Double
Velocity Y Double
Velocity Z Double
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 Teleport Flags

Player Rotation[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x43

resource:
player_rotation
Play Client Yaw Float Rotation on the X axis, in degrees.
Pitch Float Rotation on the Y axis, in degrees.

Recipe Book Add[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x44

resource:
recipe_book_add
Play Client Recipes Recipe ID Prefixed Array VarInt ID to assign to the recipe.
Display Recipe Display
Group ID VarInt
Category ID VarInt ID in the minecraft:recipe_book_category registry.
Ingredients Prefixed Optional Prefixed Array of ID Set IDs in the minecraft:item registry, or an inline definition.
Flags Byte 0x01: show notification; 0x02: highlight as new
Replace Boolean Replace or Add to known recipes

Recipe Book Remove[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x45

resource:
recipe_book_remove
Play Client Recipes Prefixed Array of VarInt IDs of recipes to remove.

Recipe Book Settings[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x46

resource:
recipe_book_settings
Play Client 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.
Blast Furnace Recipe Book Open Boolean If true, then the blast furnace recipe book will be open when the player opens its inventory.
Blast Furnace Recipe Book Filter Active Boolean If true, then the filtering option is active when the players opens its inventory.
Smoker Recipe Book Open Boolean If true, then the smoker recipe book will be open when the player opens its inventory.
Smoker Recipe Book Filter Active Boolean If true, then the filtering option is active when the players opens its inventory.

Remove Entities[edit | edit source]

Sent by the server when an entity is to be destroyed on the client.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x47

resource:
remove_entities
Play Client Entity IDs Prefixed Array of VarInt The list of entities to destroy.

Remove Entity Effect[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x48

resource:
remove_mob_effect
Play Client Entity ID VarInt
Effect ID VarInt See this table.

Reset Score[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x49

resource:
reset_score
Play Client Entity Name String (32767) The entity whose score this is. For players, this is their username; for other entities, it is their UUID.
Objective Name Prefixed Optional String (32767) The name of the objective the score belongs to.

Remove Resource Pack (play)[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x4A

resource:
resource_pack_pop
Play Client UUID Optional UUID The UUID of the resource pack to be removed.

Add Resource Pack (play)[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x4B

resource:
resource_pack_push
Play Client UUID UUID The unique identifier of the resource pack.
URL String (32767) The URL to the resource pack.
Hash String (40) A 40 character hexadecimal, case-insensitive SHA-1 hash of the resource pack file.
If it's not a 40 character hexadecimal string, the client will not use it for hash verification and likely waste bandwidth.
Forced Boolean The vanilla client will be forced to use the resource pack from the server. If they decline they will be kicked from the server.
Prompt Message Prefixed Optional Text Component This is shown in the prompt making the client accept or decline the resource pack.

Respawn[edit | edit source]

This section is missing information about: Although the number of portal cooldown ticks is included in this packet, the whole portal usage process is still dictated entirely by the server. What kind of effect does this value have on the client, if any?.
 
Please expand the section to include this information. Further details may exist on the talk page.

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
protocol:
0x4C

resource:
respawn
Play Client Dimension Type VarInt The ID of type of dimension in the minecraft:dimension_type registry, defined by the Registry Data packet.
Dimension Name Identifier Name of the dimension being spawned into.
Hashed seed Long First 8 bytes of the SHA-256 hash of the world's seed. Used client side for biome noise
Game mode Unsigned Byte 0: Survival, 1: Creative, 2: Adventure, 3: Spectator.
Previous Game mode Byte -1: Undefined (null), 0: Survival, 1: Creative, 2: Adventure, 3: Spectator. The previous game mode. Vanilla client uses this for the debug (F3 + N & F3 + F4) game mode switch. (More information needed)
Is Debug Boolean True if the world is a debug mode world; debug mode worlds cannot be modified and have predefined blocks.
Is Flat Boolean True if the world is a superflat world; flat worlds have different void fog and a horizon at y=0 instead of y=63.
Has death location Boolean If true, then the next two fields are present.
Death dimension Name Optional Identifier Name of the dimension the player died in.
Death location Optional Position The location that the player died at.
Portal cooldown VarInt The number of ticks until the player can use the portal again.
Sea level VarInt
Data kept Byte Bit mask. 0x01: Keep attributes, 0x02: Keep metadata. Tells which data should be kept on the client side once the player has respawned.

In the vanilla implementation, this is context dependent:

  • normal respawns (after death) keep no data;
  • exiting the end poem/credits keeps the attributes;
  • other dimension changes (portals or teleports) keep all data.
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). Before 1.16, 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.

Set Head Rotation[edit | edit source]

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
protocol:
0x4D

resource:
rotate_head
Play Client Entity ID VarInt
Head Yaw Angle New angle, not a delta.

Update Section Blocks[edit | edit source]

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

Changing blocks in chunks not loaded by the client is unsafe (see note on Block Update).
Packet ID State Bound To Field Name Field Type Notes
protocol:
0x4E

resource:
section_blocks_update
Play Client Chunk section position Long Chunk section coordinate (encoded chunk x and z with each 22 bits, and section y with 20 bits, from left to right).
Blocks Prefixed Array of VarLong Each entry is composed of the block state id, shifted left by 12, and the relative block position in the chunk section (4 bits for x, z, and y, from left to right).

Chunk section position is encoded:

((sectionX & 0x3FFFFF) << 42) | (sectionY & 0xFFFFF) | ((sectionZ & 0x3FFFFF) << 20);

and decoded:

sectionX = long >> 42;
sectionY = long << 44 >> 44;
sectionZ = long << 22 >> 42;

Blocks are encoded:

blockStateId << 12 | (blockLocalX << 8 | blockLocalZ << 4 | blockLocalY)
//Uses the local position of the given block position relative to its respective chunk section

and decoded:

blockStateId = long >> 12;
blockLocalX = (long >> 8) & 0xF;
blockLocalY = long & 0xF;
blockLocalZ = (long >> 4) & 0xF;

Select Advancements Tab[edit | edit source]

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
protocol:
0x4F

resource:
select_advancements_tab
Play Client Identifier Prefixed Optional Identifier See below.

The Identifier must be one of the following if no custom data pack is loaded:

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.

Server Data[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x50

resource:
server_data
Play Client MOTD Text Component
Icon Prefixed Optional Prefixed Array of Byte Icon bytes in the PNG format.

Set Action Bar Text[edit | edit source]

Displays a message above the hotbar. Equivalent to System Chat Message with Overlay set to true, except that chat message blocking isn't performed. Used by the vanilla server only to implement the /title command.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x51

resource:
set_action_bar_text
Play Client Action bar text Text Component

Set Border Center[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x52

resource:
set_border_center
Play Client X Double
Z Double

Set Border Lerp Size[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x53

resource:
set_border_lerp_size
Play Client 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 vanilla 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.

Set Border Size[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x54

resource:
set_border_size
Play Client Diameter Double Length of a single side of the world border, in meters.

Set Border Warning Delay[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x55

resource:
set_border_warning_delay
Play Client Warning Time VarInt In seconds as set by /worldborder warning time.

Set Border Warning Distance[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x56

resource:
set_border_warning_distance
Play Client Warning Blocks VarInt In meters.

Set Camera[edit | edit source]

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 vanilla 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
protocol:
0x57

resource:
set_camera
Play Client Camera ID VarInt ID of the entity to set the client's camera to.

The vanilla client 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

Set Center Chunk[edit | edit source]

Sets the center position of the client's chunk loading area. The area is square-shaped, spanning 2 × server view distance + 7 chunks on both axes (width, not radius!). Since the area's width is always an odd number, there is no ambiguity as to which chunk is the center.

The vanilla client ignores attempts to send chunks located outside the loading area, and immediately unloads any existing chunks no longer inside it.

The center chunk is normally the chunk the player is in, but apart from the implications on chunk loading, the (vanilla) client takes no issue with this not being the case. Indeed, as long as chunks are sent only within the default loading area centered on the world origin, it is not necessary to send this packet at all. This may be useful for servers with small bounded worlds, such as minigames, since it ensures chunks never need to be resent after the client has joined, saving on bandwidth.

The vanilla server sends this packet 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
protocol:
0x58

resource:
set_chunk_cache_center
Play Client Chunk X VarInt Chunk X coordinate of the loading area center.
Chunk Z VarInt Chunk Z coordinate of the loading area center.

Set Render Distance[edit | edit source]

Sent by the integrated singleplayer server when changing render distance. This packet is sent by the server when the client reappears in the overworld after leaving the end.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x59

resource:
set_chunk_cache_radius
Play Client View Distance VarInt Render distance (2-32).

Set Cursor Item[edit | edit source]

Replaces or sets the inventory item that's being dragged with the mouse.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x5A

resource:
set_cursor_item
Play Client Carried item Slot

Set Default Spawn Position[edit | edit source]

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.

The client uses this as the default position of the player upon spawning, though it's a good idea to always override this default by sending Synchronize Player Position. When converting the position to floating point, 0.5 is added to the x and z coordinates and 1.0 to the y coordinate, so as to place the player centered on top of the specified block position.

Before receiving this packet, the client uses the default position 8, 64, 8, and angle 0.0 (resulting in a default player spawn position of 8.5, 65.0, 8.5).

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x5B

resource:
set_default_spawn_position
Play Client Location Position Spawn location.
Angle Float The angle at which to respawn at.

Display Objective[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x5C

resource:
set_display_objective
Play Client Position VarInt 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 (32767) The unique name for the scoreboard to be displayed.

Set Entity Metadata[edit | edit source]

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
protocol:
0x5D

resource:
set_entity_data
Play Client Entity ID VarInt
Metadata Entity Metadata

Link Entities[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x5E

resource:
set_entity_link
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.

Set Entity Velocity[edit | edit source]

Velocity is 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
protocol:
0x5F

resource:
set_entity_motion
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.

Set Equipment[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x60

resource:
set_equipment
Play Client Entity ID VarInt Entity's ID.
Equipment Slot Array Byte Enum The length of the array is unknown, it must be read until the most significant bit is 1 ((Slot >>> 7 & 1) == 1) Equipment slot (see below). Also has the top bit set if another entry follows, and otherwise unset if this is the last item in the array.
Item Slot

Equipment slot can be one of the following:

ID Equipment slot
0 Main hand
1 Off hand
2 Boots
3 Leggings
4 Chestplate
5 Helmet
6 Body

Set Experience[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x61

resource:
set_experience
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.

Set Health[edit | edit source]

Sent by the server to 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. New players logging in or respawning 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
protocol:
0x62

resource:
set_health
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.

Set Held Item (clientbound)[edit | edit source]

Sent to change the player's slot selection.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x63

resource:
set_held_slot
Play Client Slot VarInt The slot which the player has selected (0–8).

Update Objectives[edit | edit source]

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
protocol:
0x64

resource:
set_objective
Play Client Objective Name String (32767) A 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 Text Component 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".
Has Number Format Optional Boolean Only if mode is 0 or 2. Whether this objective has a set number format for the scores.
Number Format Optional VarInt Enum Only if mode is 0 or 2 and the previous boolean is true. Determines how the score number should be formatted.
Number Format Field Name
0: blank no fields Show nothing.
1: styled Styling Compound Tag The styling to be used when formatting the score number. Contains the text component styling fields.
2: fixed Content Text Component The text to be used as placeholder.

Set Passengers[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x65

resource:
set_passengers
Play Client Entity ID VarInt Vehicle's EID.
Passengers Prefixed Array of VarInt EIDs of entity's passengers.

Set Player Inventory Slot[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x66

resource:
set_player_inventory
Play Client Slot VarInt
Slot Data Slot

Update Teams[edit | edit source]

Creates and updates teams.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x67

resource:
set_player_team
Play Client Team Name String (32767) A unique name for the team. (Shared with scoreboard).
Method Byte Determines the layout of the remaining packet.
0: create team Team Display Name Text Component
Friendly Flags Byte Bit mask. 0x01: Allow friendly fire, 0x02: can see invisible players on same team.
Name Tag Visibility String Enum (40) always, hideForOtherTeams, hideForOwnTeam, never.
Collision Rule String Enum (40) always, pushOtherTeams, pushOwnTeam, never.
Team Color VarInt Enum Used to color the name of players on the team; see below.
Team Prefix Text Component Displayed before the names of players that are part of this team.
Team Suffix Text Component Displayed after the names of players that are part of this team.
Entities Prefixed Array of String (32767) 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 Text Component
Friendly Flags Byte Bit mask. 0x01: Allow friendly fire, 0x02: can see invisible entities on same team.
Name Tag Visibility String Enum (40) always, hideForOtherTeams, hideForOwnTeam, never
Collision Rule String Enum (40) always, pushOtherTeams, pushOwnTeam, never
Team Color VarInt Enum Used to color the name of players on the team; see below.
Team Prefix Text Component Displayed before the names of players that are part of this team.
Team Suffix Text Component Displayed after the names of players that are part of this team.
3: add entities to team Entities Prefixed Array of String (32767) Identifiers for the added entities. For players, this is their username; for other entities, it is their UUID.
4: remove entities from team Entities Prefixed Array of String (32767) Identifiers for the removed entities. 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 in Text formatting#Colors.
16 Obfuscated
17 Bold
18 Strikethrough
19 Underlined
20 Italic
21 Reset

Update Score[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x68

resource:
set_score
Play Client Entity Name String (32767) The entity whose score this is. For players, this is their username; for other entities, it is their UUID.
Objective Name String (32767) The name of the objective the score belongs to.
Value VarInt The score to be displayed next to the entry.
Display Name Prefixed Optional Text Component The custom display name.
Number Format Prefixed Optional VarInt Enum Determines how the score number should be formatted.
Number Format Field Name
0: blank no fields Show nothing.
1: styled Styling Compound Tag The styling to be used when formatting the score number. Contains the text component styling fields.
2: fixed Content Text Component The text to be used as placeholder.

Set Simulation Distance[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x69

resource:
set_simulation_distance
Play Client Simulation Distance VarInt The distance that the client will process specific things, such as entities.

Set Subtitle Text[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x6A

resource:
set_subtitle_text
Play Client Subtitle Text Text Component

Update Time[edit | edit source]

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
protocol:
0x6B

resource:
set_time
Play Client World Age Long In ticks; not changed by server commands.
Time of day Long The world (or region) time, in ticks.
Time of day increasing Boolean If true, the client should automatically advance the time of day according to its ticking rate.

Set Title Text[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x6C

resource:
set_title_text
Play Client Title Text Text Component

Set Title Animation Times[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x6D

resource:
set_titles_animation
Play Client Fade In Int Ticks to spend fading in.
Stay Int Ticks to keep the title displayed.
Fade Out Int Ticks to spend fading out, not when to start fading out.

Entity Sound Effect[edit | edit source]

Plays a sound effect from an entity, either by hardcoded ID or Identifier. Sound IDs and names can be found here.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x6E

resource:
sound_entity
Play Client Sound Event ID or Sound Event ID in the minecraft:sound_event registry, or an inline definition.
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 vanilla clients.
Pitch Float Float between 0.5 and 2.0 by vanilla clients.
Seed Long Seed used to pick sound variant.

Sound Effect[edit | edit source]

Plays a sound effect at the given location, either by hardcoded ID or Identifier. Sound IDs and names can be found here.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x6F

resource:
sound
Play Client Sound Event ID or Sound Event ID in the minecraft:sound_event registry, or an inline definition.
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 vanilla clients.
Pitch Float Float between 0.5 and 2.0 by vanilla clients.
Seed Long Seed used to pick sound variant.

Start Configuration[edit | edit source]

Sent during gameplay in order to redo the configuration process. The client must respond with Acknowledge Configuration for the process to start.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x70

resource:
start_configuration
Play Client no fields

This packet switches the connection state to configuration.

Stop Sound[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x71

resource:
stop_sound
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 Custom 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

Store Cookie (play)[edit | edit source]

Stores some arbitrary data on the client, which persists between server transfers. The vanilla client only accepts cookies of up to 5 kiB in size.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x72

resource:
store_cookie
Play Client Key Identifier The identifier of the cookie.
Payload Prefixed Array (5120) of Byte The data of the cookie.

System Chat Message[edit | edit source]

Main article: Chat

Sends the client a raw system message.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x73

resource:
system_chat
Play Client Content Text Component Limited to 262144 bytes.
Overlay Boolean Whether the message is an actionbar or chat message. See also #Set Action Bar Text.

Set Tab List Header And Footer[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x74

resource:
tab_list
Play Client Header Text Component To remove the header, send a empty text component: {"text":""}.
Footer Text Component To remove the footer, send a empty text component: {"text":""}.

Tag Query Response[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x75

resource:
tag_query
Play Client Transaction ID VarInt Can be compared to the one sent in the original query packet.
NBT NBT The NBT of the block or entity. May be a TAG_END (0) in which case no NBT is present.

Pickup Item[edit | edit source]

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 Set Player Position (and Set Player Position And Rotation) 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 vanilla server only uses this for items, experience orbs, and the different varieties of arrows.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x76

resource:
take_item_entity
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.

Synchronize Vehicle Position[edit | edit source]

Teleports the entity on the client without changing the reference point of movement deltas in future Update Entity Position packets. Seems to be used to make relative adjustments to vehicle positions; more information needed.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x77

resource:
teleport_entity
Play Client Entity ID VarInt
X Double
Y Double
Z Double
Velocity X Double
Velocity Y Double
Velocity Z Double
Yaw Float Rotation on the Y axis, in degrees.
Pitch Float Rotation on the Y axis, in degrees.
Flags Teleport Flags
On Ground Boolean

Set Ticking State[edit | edit source]

Used to adjust the ticking rate of the client, and whether it's frozen.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x78

resource:
ticking_state
Play Client Tick rate Float
Is frozen Boolean

Step Tick[edit | edit source]

Advances the client processing by the specified number of ticks. Has no effect unless client ticking is frozen.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x79

resource:
ticking_step
Play Client Tick steps VarInt

Transfer (play)[edit | edit source]

Notifies the client that it should transfer to the given server. Cookies previously stored are preserved between server transfers.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x7A

resource:
transfer
Play Client Host String The hostname or IP of the server.
Port VarInt The port of the server.

Update Advancements[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x7B

resource:
update_advancements
Play Client Reset/Clear Boolean Whether to reset/clear the current advancements.
Advancement mapping Key Prefixed Array Identifier The identifier of the advancement.
Value Advancement See below
Identifiers Prefixed Array of Identifier The identifiers of the advancements that should be removed.
Progress mapping Key Prefixed Array Identifier The identifier of the advancement.
Value Advancement progress See below.

Advancement structure:

Field Name Field Type Notes
Parent id Prefixed Optional Identifier The identifier of the parent advancement.
Display data Prefixed Optional Advancement display See below.
Nested requirements Prefixed Array Prefixed Array of String (32767) Array with a sub-array of criteria. To check if the requirements are met, each sub-array must be tested and mapped with the OR operator, resulting in a boolean array.

These booleans must be mapped with the AND operator to get the result.

Sends telemetry data Boolean Whether the client should include this achievement in the telemetry data when it's completed.

The vanilla client only sends data for advancements on the minecraft namespace.

Advancement display:

Field Name Field Type Notes
Title Text Component
Description Text Component
Icon Slot
Frame type VarInt Enum 0 = task, 1 = challenge, 2 = goal.
Flags Int 0x01: has background texture; 0x02: show_toast; 0x04: 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
Criteria Criterion identifier Prefixed Array Identifier The identifier of the criterion.
Date of achieving Prefixed Optional Long Present if achieved. As returned by Date.getTime.

Update Attributes[edit | edit source]

Sets attributes on the given entity.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x7C

resource:
update_attributes
Play Client Entity ID VarInt
Property Id Prefixed Array VarInt ID in the minecraft:attribute registry. See also Attribute#Attributes.
Value Double See below.
Modifiers Prefixed Array of Modifier Data See Attribute#Modifiers. Modifier Data defined below.

Modifier Data structure:

Field Name Field Type Notes
Id Identifier
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[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x7D

resource:
update_mob_effect
Play Client Entity ID VarInt
Effect ID VarInt See this table.
Amplifier VarInt Vanilla client displays effect level as Amplifier + 1.
Duration VarInt Duration in ticks. (-1 for infinite)
Flags Byte Bit field, see below.
This section is missing information about: What exact effect does the blend bit flag have on the client? What happens if it is used on effects besides DARKNESS?.
 
Please expand the section to include this information. Further details may exist on the talk page.

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.
  • 0x08: Blend - should the effect's hard-coded blending be applied? Currently only used in the DARKNESS effect to apply extra void fog and adjust the gamma value for lighting.

Update Recipes[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x7E

resource:
update_recipes
Play Client Property Sets Property Set ID Prefixed Array Identifier
Items Prefixed Array of VarInt IDs in the minecraft:item registry.
Stonecutter Recipes Ingredients Prefixed Array ID Set
Slot Display Slot Display

Update Tags (play)[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x7F

resource:
update_tags
Play Client Registry to tags map Registry Prefixed Array Identifier Registry identifier (Vanilla expects tags for the registries minecraft:block, minecraft:item, minecraft:fluid, minecraft:entity_type, and minecraft:game_event)
Tags Prefixed Array of Tag (See below)

A tag looks like this:

Field Name Field Type Notes
Tag name Identifier
Entries Prefixed Array of VarInt Numeric IDs of the given type (block, item, etc.). This list replaces the previous list of IDs for the given tag. If some preexisting tags are left unmentioned, a warning is printed.

See Tag on the Minecraft Wiki for more information, including a list of vanilla tags.

Projectile Power[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x80

resource:
projectile_power
Play Client Entity ID VarInt
Power Double

Custom Report Details[edit | edit source]

Contains a list of key-value text entries that are included in any crash or disconnection report generated during connection to the server.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x81

resource:
custom_report_details
Play Client Details Title Prefixed Array (32) String (128)
Description String (4096)

Server Links[edit | edit source]

This packet contains a list of links that the vanilla client will display in the menu available from the pause menu. Link labels can be built-in or custom (i.e., any text).

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x82

resource:
server_links
Play Client Links Is built-in Prefixed Array Boolean Determines if the following label is built-in (from enum) or custom (text component).
Label VarInt Enum / Text Component See below.
URL String Valid URL.
ID Name Notes
0 Bug Report Displayed on connection error screen; included as a comment in the disconnection report.
1 Community Guidelines
2 Support
3 Status
4 Feedback
5 Community
6 Website
7 Forums
8 News
9 Announcements

Serverbound[edit | edit source]

Confirm Teleportation[edit | edit source]

Sent by client as confirmation of Synchronize Player Position.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x00

resource:
accept_teleportation
Play Server Teleport ID VarInt The ID given by the Synchronize Player Position packet.

Query Block Entity Tag[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x01

resource:
block_entity_tag_query
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.

Bundle Item Selected[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x02

resource:
bundle_item_selected
Play Server Slot of Bundle VarInt
Slot in Bundle VarInt

Change Difficulty[edit | edit source]

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
protocol:
0x03

resource:
change_difficulty
Play Server New difficulty Unsigned Byte Enum 0: peaceful, 1: easy, 2: normal, 3: hard.

Acknowledge Message[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x04

resource:
chat_ack
Play Server Message Count VarInt

Chat Command[edit | edit source]

Main article: Chat
Packet ID State Bound To Field Name Field Type Notes
protocol:
0x05

resource:
chat_command
Play Server Command String (32767) The command typed by the client.

Signed Chat Command[edit | edit source]

Main article: Chat
Packet ID State Bound To Field Name Field Type Notes
protocol:
0x06

resource:
chat_command_signed
Play Server Command String (32767) The command typed by the client.
Timestamp Long The timestamp that the command was executed.
Salt Long The salt for the following argument signatures.
Array of argument signatures Argument name Prefixed Array (8) String (16) The name of the argument that is signed by the following signature.
Signature Byte Array (256) The signature that verifies the argument. Always 256 bytes and is not length-prefixed.
Message Count VarInt
Acknowledged Fixed BitSet (20)

Chat Message[edit | edit source]

Main article: Chat

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.

The server will broadcast a Player Chat Message packet with Chat Type minecraft:chat to all players that haven't disabled chat (including the player that sent the message). See Chat#Processing chat for more information.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x07

resource:
chat
Play Server Message String (256)
Timestamp Long
Salt Long The salt used to verify the signature hash.
Signature Prefixed Optional Byte Array (256) The signature used to verify the chat message's authentication. When present, always 256 bytes and not length-prefixed.
Message Count VarInt
Acknowledged Fixed BitSet (20)

Player Session[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x08

resource:
chat_session_update
Play Server Session Id UUID
Public Key Expires At Long The time the play session key expires in epoch milliseconds.
Public Key Prefixed Array (512) of Byte A byte array of an X.509-encoded public key.
Key Signature Prefixed Array (4096) of Byte The signature consists of the player UUID, the key expiration timestamp, and the public key data. These values are hashed using SHA-1 and signed using Mojang's private RSA key.

Chunk Batch Received[edit | edit source]

Notifies the server that the chunk batch has been received by the client. The server uses the value sent in this packet to adjust the number of chunks to be sent in a batch.

The vanilla server will stop sending further chunk data until the client acknowledges the sent chunk batch. After the first acknowledgement, the server adjusts this number to allow up to 10 unacknowledged batches.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x09

resource:
chunk_batch_received
Play Server Chunks per tick Float Desired chunks per tick.

Client Status[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0A

resource:
client_command
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 respawn after death.
1 Request stats Sent when the client opens the Statistics menu.

Client Tick End[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0B

resource:
client_tick_end
Play Server no fields

Client Information (play)[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0C

resource:
client_information
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 Chat#Client chat mode for more information.
Chat Colors Boolean “Colors” multiplayer setting. The vanilla server stores this value but does nothing with it (see MC-64867). Third-party servers such as Hypixel disable all coloring in chat and system messages when it is false.
Displayed Skin Parts Unsigned Byte Bit mask, see below.
Main Hand VarInt Enum 0: Left, 1: Right.
Enable text filtering Boolean Enables filtering of text on signs and written book titles. The vanilla client sets this according to the profanityFilterPreferences.profanityFilterOn account attribute indicated by the /player/attributes Mojang API endpoint. In offline mode it is always false.
Allow server listings Boolean Servers usually list online players, this option should let you not show up in that list.
Particle Status VarInt Enum 0: all, 1: decreased, 2: minimal

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.

Command Suggestions Request[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0D

resource:
command_suggestion
Play Server Transaction Id VarInt The id of the transaction that the server will send back to the client in the response of 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).

Acknowledge Configuration[edit | edit source]

Sent by the client upon receiving a Start Configuration packet from the server.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x0E

resource:
configuration_acknowledged
Play Server no fields

This packet switches the connection state to configuration.

Click Container Button[edit | edit source]

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
protocol:
0x0F

resource:
container_button_click
Play Server Window ID VarInt The ID of the window sent by Open Screen.
Button ID VarInt 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 Container[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x10

resource:
container_click
Play Server Window ID VarInt The ID of the window which was clicked. 0 for player inventory. The server ignores any packets targeting a Window ID other than the current one, including ignoring 0 when any other window is open.
State ID VarInt The last received State ID from either a Set Container Slot or a Set Container Content packet.
Slot Short The clicked slot number, see below.
Button Byte The button used in the click, see below.
Mode VarInt Enum Inventory operation mode, see below.
Array of changed slots Slot number Prefixed Array (128) Short
Slot data Slot New data for this slot, in the client's opinion; see below.
Carried item Slot Item carried by the cursor. Has to be empty (item ID = -1) for drop mode, otherwise nothing will happen.

See Inventory for further information about how slots are indexed.

After performing the action, the server compares the results to the slot change information included in the packet, as applied on top of the server's view of the container's state prior to the action. For any slots that do not match, it sends Set Container Slot packets containing the correct results. If State ID does not match the last ID sent by the server, it will instead send a full Set Container Content to resynchronize the client.

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
0 -999 Left click outside inventory (drop cursor stack)
1 -999 Right click outside inventory (drop cursor single item)
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
Button is used as the slot index (impossible in vanilla clients)
40 Normal Offhand swap key F
3 2 Normal Middle click, only defined for creative players in non-player inventories.
4 0 Normal Drop key (Q)
1 Normal Control + Drop key (Q)
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.
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.
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.
6 0 Normal Double click
1 Normal Pickup all but check items in reverse order (impossible in vanilla clients)

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.

Close Container[edit | edit source]

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

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x11

resource:
container_close
Play Server Window ID VarInt This is the ID of the window that was closed. 0 for player inventory.

Change Container Slot State[edit | edit source]

This packet is sent by the client when toggling the state of a Crafter.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x12

resource:
container_slot_state_changed
Play Server Slot ID VarInt This is the ID of the slot that was changed.
Window ID VarInt This is the ID of the window that was changed.
State Boolean The new state of the slot. True for enabled, false for disabled.

Cookie Response (play)[edit | edit source]

Response to a Cookie Request (play) from the server. The vanilla server only accepts responses of up to 5 kiB in size.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x13

resource:
cookie_response
Play Server Key Identifier The identifier of the cookie.
Payload Prefixed Optional Prefixed Array (5120) of Byte The data of the cookie.

Serverbound Plugin Message (play)[edit | edit source]

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: https://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
protocol:
0x14

resource:
custom_payload
Play Server Channel Identifier Name of the plugin channel used to send the data.
Data Byte Array (32767) Any data, depending on the channel. minecraft: channels are documented here. The length of this array must be inferred from the packet length.

In vanilla servers, the maximum data length is 32767 bytes.

Debug Sample Subscription[edit | edit source]

Subscribes to the specified type of debug sample data, which is then sent periodically to the client via Debug Sample.

The subscription is retained for 10 seconds (the vanilla server checks that both 10.001 real-time seconds and 201 ticks have elapsed), after which the client is automatically unsubscribed. The vanilla client resends this packet every 5 seconds to keep up the subscription.

The vanilla server only allows subscriptions from players that are server operators.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x15

resource:
debug_sample_subscription
Play Server Sample Type VarInt Enum The type of debug sample to subscribe to. Can be one of the following:
  • 0 - Tick time

Edit Book[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x16

resource:
edit_book
Play Server Slot VarInt The hotbar slot where the written book is located
Entries Prefixed Array (100) of String (1024) Text from each page. Maximum string length is 1024 chars.
Title Prefixed Optional String (32) Title of book. Present if book is being signed, not present if book is being edited.

Query Entity Tag[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x17

resource:
entity_tag_query
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[edit | edit source]

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

A vanilla 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.

The target X, Y, and Z fields represent the difference between the vector location of the cursor at the time of the packet and the entity's position.

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x18

resource:
interact
Play Server Entity ID VarInt The ID of the entity to interact. Note the special case described below.
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.
Sneak Key Pressed Boolean If the client is pressing the sneak key. Has the same effect as a Player Command Press/Release sneak key preceding the interaction, and the state is permanently changed.

Interaction with the ender dragon is an odd special case characteristic of release deadline–driven design. 8 consecutive entity IDs following the dragon's ID (id + 1, id + 2, ..., id + 8) are reserved for the 8 hitboxes that make up the dragon:

ID offset Description
0 The dragon itself (never used in this packet)
1 Head
2 Neck
3 Body
4 Tail 1
5 Tail 2
6 Tail 3
7 Wing 1
8 Wing 2

Jigsaw Generate[edit | edit source]

Sent when Generate is pressed on the Jigsaw Block interface.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x19

resource:
jigsaw_generate
Play Server Location Position Block entity location.
Levels VarInt Value of the levels slider/max depth to generate.
Keep Jigsaws Boolean

Serverbound Keep Alive (play)[edit | edit source]

The server will frequently send out a keep-alive (see Clientbound 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
protocol:
0x1A

resource:
keep_alive
Play Server Keep Alive ID Long

Lock Difficulty[edit | edit source]

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
protocol:
0x1B

resource:
lock_difficulty
Play Server Locked Boolean

Set Player Position[edit | edit source]

Updates the player's XYZ position on the server.

If the player is in a vehicle, the position is ignored (but in case of Set Player Position and Rotation, the rotation is still used as normal). No validation steps other than value range clamping are performed in this case.

If the player is sleeping, the position (or rotation) is not changed, and a Synchronize Player Position is sent if the received position deviated from the server's view by more than a meter.

The vanilla server silently clamps the x and z coordinates between -30,000,000 and 30,000,000, and the y coordinate between -20,000,000 and 20,000,000. A similar condition has historically caused a kick for "Illegal position"; this is no longer the case. However, infinite or NaN coordinates (or angles) still result in a kick for multiplayer.disconnect.invalid_player_movement.

As of 1.20.6, checking for moving too fast is achieved like this (sic):

  • Each server tick, the player's current position is stored.
  • When the player moves, the offset from the stored position to the requested position is computed (Δx, Δy, Δz).
  • The requested movement distance squared is computed as Δx² + Δy² + Δz².
  • The baseline expected movement distance squared is computed based on the player's server-side velocity as Vx² + Vy² + Vz². The player's server-side velocity is a somewhat ill-defined quantity that includes among other things gravity, jump velocity and knockback, but not regular horizontal movement. A proper description would bring much of Minecraft's physics engine with it. It is accessible as the Motion NBT tag on the player entity.
  • The maximum permitted movement distance squared is computed as 100 (300 if the player is using an elytra), multiplied by the number of movement packets received since the last tick, including this one, unless that value is greater than 5, in which case no multiplier is applied.
  • If the requested movement distance squared minus the baseline distance squared is more than the maximum squared, the player is moving too fast.

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

Checking for block collisions is achieved like this:

  • A temporary collision-checked move of the player is attempted from its current position to the requested one.
  • The offset from the resulting position to the requested position is computed. If the absolute value of the offset on the y axis is less than 0.5, it (only the y component) is rounded down to 0.
  • If the magnitude of the offset is greater than 0.25 and the player isn't in creative or spectator mode, it is logged that "<player> moved wrongly!", and the player is teleported back to their current (before this packet) server-side position.
  • In addition, if the player's hitbox stationary at the requested position would intersect with a block, and they aren't in spectator mode, they are teleported back without a log message.

Checking for illegal flight is achieved like this:

  • When a movement packet is received, a flag indicating whether or not the player is floating mid-air is updated. The flag is set if the move test described above detected no collision below the player and the y component of the offset from the player's current position to the requested one is greater than -0.5, unless any of various conditions permitting flight (creative mode, elytra, levitation effect, etc., but not jumping) are met.
  • Each server tick, it is checked if the flag has been set for more than 80 consecutive ticks. If so, and the player isn't currently sleeping, dead or riding a vehicle, they are kicked for multiplayer.disconnect.flying.
Packet ID State Bound To Field Name Field Type Notes
protocol:
0x1C

resource:
move_player_pos
Play Server X Double Absolute position.
Feet Y Double Absolute feet position, normally Head Y - 1.62.
Z Double Absolute position.
Flags Byte Bit field: 0x01: on ground, 0x02: pushing against wall.

Set Player Position and Rotation[edit | edit source]

A combination of Move Player Rotation and Move Player Position.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x1D

resource:
move_player_pos_rot
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.
Flags Byte Bit field: 0x01: on ground, 0x02: pushing against wall.

Set Player Rotation[edit | edit source]

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
protocol:
0x1E

resource:
move_player_rot
Play Server Yaw Float Absolute rotation on the X Axis, in degrees.
Pitch Float Absolute rotation on the Y Axis, in degrees.
Flags Byte Bit field: 0x01: on ground, 0x02: pushing against wall.

Set Player Movement Flags[edit | edit source]

This packet as well as Set Player Position, Set Player Rotation, and Set Player Position and Rotation are called the “serverbound movement packets”. Vanilla clients will send Move 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
protocol:
0x1F

resource:
move_player_status_only
Play Server Flags Byte Bit field: 0x01: on ground, 0x02: pushing against wall.

Move Vehicle[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x20

resource:
move_vehicle
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.
On Ground Boolean (This value does not seem to exist)

Paddle Boat[edit | edit source]

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
protocol:
0x21

resource:
paddle_boat
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 held.

Pick Item From Block[edit | edit source]

Used for pick block functionality (middle click) on blocks to retrieve items from the inventory in survival or creative mode or create them in creative mode. See Controls#Pick_Block for more information.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x22

resource:
pick_item_from_block
Play Server Location Position The location of the block.
Include Data Boolean Used to tell the server to include block data in the new stack, works only if in creative mode.

Pick Item From Entity[edit | edit source]

Used for pick block functionality (middle click) on entities to retrieve items from the inventory in survival or creative mode or create them in creative mode. See Controls#Pick_Block for more information.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x23

resource:
pick_item_from_entity
Play Server Entity ID VarInt The ID of the entity to pick.
Include Data Boolean Unused by the vanilla server.

Ping Request (play)[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x24

resource:
ping_request
Play Server Payload Long May be any number. vanilla clients use a system-dependent time value which is counted in milliseconds.

Place Recipe[edit | edit source]

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
protocol:
0x25

resource:
place_recipe
Play Server Window ID VarInt
Recipe ID VarInt ID of recipe previously defined in Recipe Book Add.
Make all Boolean Affects the amount of items processed; true if shift is down when clicked.

Player Abilities (serverbound)[edit | edit source]

The vanilla client sends this packet when the player starts/stops flying with the Flags parameter changed accordingly.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x26

resource:
player_abilities
Play Server Flags Byte Bit mask. 0x02: is flying.

Player Action[edit | edit source]

Sent when the player mines a block. A vanilla server only accepts digging packets with coordinates within a 6-unit radius between the center of the block and the player's eyes.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x27

resource:
player_action
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).
Sequence VarInt Block change sequence number (see #Acknowledge Block Change).

Status can be one of seven values:

Value Meaning Notes
0 Started digging Sent when the player starts digging a block. If the block was instamined or the player is in creative mode, the client will not send Status = Finished digging, and will assume the server completed the destruction. To detect this, it is necessary to calculate the block destruction speed server-side.
1 Cancelled digging Sent when the player lets go of the Mine Block key (default: left click). Face is always set to -Y.
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: Control or Command, depending on OS). Location is always set to 0/0/0, Face is always set to -Y. Sequence is always set to 0.
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. Sequence is always set to 0.
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. Sequence is always set to 0.
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. Sequence is always set to 0.

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

Player Command[edit | edit source]

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
protocol:
0x28

resource:
player_command
Play Server Entity ID VarInt Player ID (ignored by the vanilla server)
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 Press sneak key
1 Release sneak key
2 Leave bed
3 Start sprinting
4 Stop sprinting
5 Start jump with horse
6 Stop jump with horse
7 Open vehicle 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 in the morning.

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

Player Input[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x29

resource:
player_input
Play Server Flags Unsigned Byte Bit mask; see below

The flags are as follows:

Hex Mask Field
0x01 Forward
0x02 Backward
0x04 Left
0x08 Right
0x10 Jump
0x20 Sneak
0x40 Sprint

Player Loaded[edit | edit source]

Sent by the client after the server starts sending chunks and the player's chunk has loaded.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x2A

resource:
player_loaded
Play Server no fields

Pong (play)[edit | edit source]

Response to the clientbound packet (Ping) with the same id.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x2B

resource:
pong
Play Server ID Int id is the same as the ping packet

Change Recipe Book Settings[edit | edit source]

Replaces Recipe Book Data, type 1.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x2C

resource:
recipe_book_change_settings
Play Server Book ID VarInt Enum 0: crafting, 1: furnace, 2: blast furnace, 3: smoker.
Book Open Boolean
Filter Active Boolean

Set Seen Recipe[edit | edit source]

Sent when recipe is first seen in recipe book. Replaces Recipe Book Data, type 0.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x2D

resource:
recipe_book_seen_recipe
Play Server Recipe ID VarInt ID of recipe previously defined in Recipe Book Add.

Rename Item[edit | edit source]

Sent as a player is renaming an item in an anvil (each keypress in the anvil UI sends a new Rename 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 50 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
protocol:
0x2E

resource:
rename_item
Play Server Item name String (32767) The new name of the item.

Resource Pack Response (play)[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x2F

resource:
resource_pack
Play Server UUID UUID The unique identifier of the resource pack received in the Add Resource Pack (play) request.
Result VarInt Enum Result ID (see below).

Result can be one of the following values:


ID Result
0 Successfully downloaded
1 Declined
2 Failed to download
3 Accepted
4 Downloaded
5 Invalid URL
6 Failed to reload
7 Discarded

Seen Advancements[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x30

resource:
seen_advancements
Play Server Action VarInt Enum 0: Opened tab, 1: Closed screen.
Tab ID Optional Identifier Only present if action is Opened tab.

Select Trade[edit | edit source]

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

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x31

resource:
select_trade
Play Server Selected slot VarInt The selected slot in the players current (trading) inventory.

Set Beacon Effect[edit | edit source]

Changes the effect of the current beacon.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x32

resource:
set_beacon
Play Server Primary Effect Prefixed Optional VarInt A Potion ID.
Secondary Effect Prefixed Optional VarInt A Potion ID.

Set Held Item (serverbound)[edit | edit source]

Sent when the player changes the slot selection.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x33

resource:
set_carried_item
Play Server Slot Short The slot which the player has selected (0–8).

Program Command Block[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x34

resource:
set_command_block
Play Server Location Position
Command String (32767)
Mode VarInt Enum 0: chain, 1: repeating, 2: impulse.
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.

Program Command Block Minecart[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x35

resource:
set_command_minecart
Play Server Entity ID VarInt
Command String (32767)
Track Output Boolean If false, the output of the previous command will not be stored within the command block.

Set Creative Mode Slot[edit | edit source]

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
protocol:
0x36

resource:
set_creative_mode_slot
Play Server Slot Short Inventory slot.
Clicked Item Slot

Program Jigsaw Block[edit | edit source]

Sent when Done is pressed on the Jigsaw Block interface.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x37

resource:
set_jigsaw_block
Play Server Location Position Block entity location
Name Identifier
Target Identifier
Pool Identifier
Final state String (32767) "Turns into" on the GUI, final_state in NBT.
Joint type String (32767) rollable if the attached piece can be rotated, else aligned.
Selection priority VarInt
Placement priority VarInt

Program Structure Block[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x38

resource:
set_structure_block
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 (32767)
Offset X Byte Between -48 and 48.
Offset Y Byte Between -48 and 48.
Offset Z Byte Between -48 and 48.
Size X Byte Between 0 and 48.
Size Y Byte Between 0 and 48.
Size Z Byte Between 0 and 48.
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 (128)
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 vanilla client uses update data to indicate no special action should be taken (i.e. the done button).

Update Sign[edit | edit source]

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
protocol:
0x39

resource:
sign_update
Play Server Location Position Block Coordinates.
Is Front Text Boolean Whether the updated text is in front or on the back of the sign
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.

Swing Arm[edit | edit source]

Sent when the player's arm swings.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x3A

resource:
swing
Play Server Hand VarInt Enum Hand used for the animation. 0: main hand, 1: off hand.

Teleport To Entity[edit | edit source]

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

The vanilla 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.

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x3B

resource:
teleport_to_entity
Play Server Target Player UUID UUID of the player to teleport to (can also be an entity UUID).

Use Item On[edit | edit source]

Packet ID State Bound To Field Name Field Type Notes
protocol:
0x3C

resource:
use_item_on
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 Action).
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.
World Border Hit Boolean Seems to always be false, even when interacting with blocks around or outside the world border, or while the player is outside the border.
Sequence VarInt Block change sequence number (see #Acknowledge Block Change).

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[edit | edit source]

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
protocol:
0x3D

resource:
use_item
Play Server Hand VarInt Enum Hand used for the animation. 0: main hand, 1: off hand.
Sequence VarInt Block change sequence number (see #Acknowledge Block Change).
Yaw Float Player head rotation along the Y-Axis.
Pitch Float Player head rotation along the X-Axis.

The player's rotation is permanently updated according to the Yaw and Pitch fields before performing the action, unless there is no item in the specified hand.

Navigation[edit | edit source]

This article is licensed under a Creative Commons Attribution-ShareAlike 3.0 license.
 
This article has been imported from wiki.vg or is a derivative of such a page. Thus, the wiki's usual license does not apply.
Derivative works must be licensed using the same or a compatible license.