https://wiki.sasgaming.net/index.php?action=history&feed=atom&title=Minecraft%3AJava_Edition_protocol%2FFAQ 2026-06-10T23:05:28Z Revision history for this page on the wiki MediaWiki 1.43.8 https://wiki.sasgaming.net/index.php?title=Minecraft:Java_Edition_protocol/FAQ&diff=141122&oldid=prev 2026-06-10T11:15:04Z

<p>Sync: new page from Minecraft</p> <p><b>New page</b></p><div>People very, very often have questions regarding the [[Minecraft:Java Edition protocol|&#039;&#039;Java Edition&#039;&#039; protocol]], so we&#039;ll try to address some of the most common ones on this document. If you&#039;re still having trouble, join us on the [[Minecraft:MCW:Discord|Minecraft Wiki&#039;s Discord server]], the [https://discord.gg/Tf4xwK3Ke7 Minecraft Protocol Discord server], or our IRC channel [ircs://irc.libera.chat:6697/mcdevs #mcdevs on irc.libera.chat].<br /> <br /> == Is the protocol documentation complete? ==<br /> Depending on your definition, &#039;&#039;yes&#039;&#039;! All packet types are known and their layout documented. Some finer details are missing, but everything you need to make functional programs is present. We also collect information on the [[Minecraft:Java Edition protocol/Development version|pre-release protocol]] changes, allowing us to quickly document new releases.<br /> <br /> == What&#039;s the normal login sequence for a client? ==<br /> <br /> (This is about joining a Minecraft server. See [[Minecraft:Microsoft authentication]] for how to log in to a Minecraft account, and [[Minecraft:protocol encryption]] for details on player authentication during server login.)<br /> <br /> The recommended login sequence as of 1.21 looks like this, where &#039;&#039;&#039;C&#039;&#039;&#039; is the client and &#039;&#039;&#039;S&#039;&#039;&#039; is the server:<br /> # Client connects to the server<br /> # &#039;&#039;&#039;C&#039;&#039;&#039;→&#039;&#039;&#039;S&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Handshake|Handshake]] State=2<br /> # &#039;&#039;&#039;C&#039;&#039;&#039;→&#039;&#039;&#039;S&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Login Start|Login Start]]<br /> # &#039;&#039;&#039;S&#039;&#039;&#039;→&#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Encryption Request|Encryption Request]] (optional)<br /> # Client auth (Only if server sent Encryption Request)<br /> # &#039;&#039;&#039;C&#039;&#039;&#039;→&#039;&#039;&#039;S&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Encryption Response|Encryption Response]] (Only if server sent Encryption Request)<br /> # Server auth, both enable encryption (Only if server sent Encryption Request)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Set Compression|Set Compression]] (Optional, enables compression)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Login Success|Login Success]]<br /> # &#039;&#039;&#039;C&#039;&#039;&#039; → &#039;&#039;&#039;S&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Login Acknowledged|Login Acknowledged]]<br /> # &#039;&#039;&#039;C&#039;&#039;&#039; → &#039;&#039;&#039;S&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Serverbound Plugin Message (configuration)|Serverbound Plugin Message]] (Optional, &lt;code&gt;[[Minecraft:Java Edition protocol/Plugin channels#Brand|minecraft:brand]]&lt;/code&gt; with the client&#039;s brand)<br /> # &#039;&#039;&#039;C&#039;&#039;&#039; → &#039;&#039;&#039;S&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Client Information (configuration)|Client Information]] (Optional)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Clientbound Plugin Message (configuration)|Clientbound Plugin Message]] (Optional, &lt;code&gt;[[Minecraft:Java Edition protocol/Plugin channels#Brand|minecraft:brand]]&lt;/code&gt; with the server&#039;s brand)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Feature Flags|Feature Flags]] (Optional)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Clientbound Known Packs|Clientbound Known Packs]] (Optional)<br /> # &#039;&#039;&#039;C&#039;&#039;&#039; → &#039;&#039;&#039;S&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Serverbound Known Packs|Serverbound Known Packs]] (Optional)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Registry Data 2|Registry Data]] (Multiple)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Update Tags (configuration)|Update Tags]] (Optional)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Finish Configuration|Finish Configuration]]<br /> # &#039;&#039;&#039;C&#039;&#039;&#039; → &#039;&#039;&#039;S&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Acknowledge Finish Configuration|Acknowledge Finish Configuration]]<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Login (play)|Login (play)]]<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Change Difficulty|Change Difficulty]] (Optional)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Player Abilities (clientbound)|Player Abilities]] (Optional)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Set Held Item (clientbound)|Set Held Item]] (Optional)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Update Recipes|Update Recipes]] (Optional)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Entity Event|Entity Event]] (Optional, for the [[Minecraft:Server.properties#op-permission-level|OP permission level]]; see [[Minecraft:Minecraft Wiki:Projects/wiki.vg merge/Entity statuses#Player|Entity statuses#Player]])<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Commands|Commands]] (Optional)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Update Recipe Book|Update Recipe Book]] (Optional)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Synchronize Player Position|Synchronize Player Position]]<br /> # &#039;&#039;&#039;C&#039;&#039;&#039; → &#039;&#039;&#039;S&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Confirm Teleportation|Confirm Teleportation]]<br /> # &#039;&#039;&#039;C&#039;&#039;&#039; → &#039;&#039;&#039;S&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Set Player Position and Rotation|Set Player Position and Rotation]] (Optional, to confirm the spawn position)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Server Data|Server Data]] (Optional)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Player Info Update|Player Info Update]] (Add Player action, all players except the one joining (the vanilla server separates these, you don&#039;t need to))<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Player Info Update|Player Info Update]] (Add Player action, joining player)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Initialize World Border|Initialize World Border]] (Optional)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Update Time|Update Time]] (Optional)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Set Default Spawn Position|Set Default Spawn Position]] (Optional, “home” spawn, not where the client will spawn on login)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Game Event|Game Event]] (Start waiting for level chunks event, required for the client to spawn. Despite the name, a custom server may choose to send some chunks before sending this packet)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Set Ticking State|Set Ticking State]] (Optional)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Step Tick|Step Tick]] (Optional, the vanilla server sends this regardless of ticking state)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Set Center Chunk|Set Center Chunk]]<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Chunk Data and Update Light|Chunk Data and Update Light]] (One sent for each chunk in a circular area centered on the player&#039;s position)<br /> # &#039;&#039;&#039;C&#039;&#039;&#039; → &#039;&#039;&#039;S&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Player Loaded|Player Loaded]] (After the &quot;Loading terrain...&quot; screen has closed (see [[#…my_player_isn&#039;t_spawning!|below]]), or skipped if 60 ticks pass before then)<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: inventory, entities, etc.<br /> <br /> === Offline mode ===<br /> If the vanilla server is in offline mode, it will not send the [[Minecraft:Java Edition protocol/Packets#Encryption Request|Encryption Request]] packet, and likewise, the client should not send [[Minecraft:Java Edition protocol/Packets#Encryption Response|Encryption Response]]. In this case, encryption is never enabled, and no authentication is performed.<br /> <br /> Clients can tell that a server is in offline mode if the server sends a [[Minecraft:Java Edition protocol/Packets#Login Success|Login Success]] without sending [[Minecraft:Java Edition protocol/Packets#Encryption Request|Encryption Request]].<br /> <br /> Versions 1.20.5 and newer support protocol encryption in offline mode, in which case the [[Minecraft:Java Edition protocol/Packets#Encryption Request|Encryption Request]] packet can be sent with Should Authenticate set to false, and both the client and server should not authenticate with Mojang. However, it&#039;s currently not possible to configure the vanilla server to do this.<br /> <br /> == What does the normal status ping sequence look like? ==<br /> When a vanilla client and server exchange information in a status ping, the exchange of packets will be as follows:<br /> <br /> # &#039;&#039;&#039;C&#039;&#039;&#039; → &#039;&#039;&#039;S&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Handshake|Handshake]] with Next State set to 1 ([[Minecraft:Java Edition protocol/Packets#Status|Status]])<br /> # Client and Server set protocol state to [[Minecraft:Java Edition protocol/Packets#Status|Status]].<br /> # &#039;&#039;&#039;C&#039;&#039;&#039; → &#039;&#039;&#039;S&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Status Request|Status Request]]<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Status Response|Status Response]]<br /> # &#039;&#039;&#039;C&#039;&#039;&#039; → &#039;&#039;&#039;S&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Ping Request (status)|Ping Request]]<br /> # &#039;&#039;&#039;S&#039;&#039;&#039; → &#039;&#039;&#039;C&#039;&#039;&#039;: [[Minecraft:Java Edition protocol/Packets#Pong Response (status)|Pong Response]]<br /> # Both sides close the connection<br /> <br /> (Note that &#039;&#039;&#039;C&#039;&#039;&#039; is the vanilla client and &#039;&#039;&#039;S&#039;&#039;&#039; is the vanilla server).<br /> <br /> The [[Minecraft:Java Edition protocol/Packets#Ping Request (status)|Ping Request]] packet may be left out, however the client will not receive a [[Minecraft:Java Edition protocol/Packets#Pong Response (status)|Pong Response]] packet and the server won&#039;t close the connection.{{more info|How long does it take for the connection to time out if this occurs?}}<br /> <br /> == I think I&#039;ve done everything right, but… ==<br /> === …my player isn&#039;t spawning! ===<br /> <br /> The Minecraft client will wait at the &quot;Loading Terrain...&quot; screen until late in the login sequence. As of 1.21.4 (and starting with 1.20.3), in order for the client to spawn, it must have received a [[Minecraft:Java Edition protocol/Packets#Game Event|Game Event]] packet with event 13 (&quot;Start waiting for level chunks&quot;), and at least one of the following conditions must be met:<br /> <br /> * The player is in a loaded chunk (sent via [[Minecraft:Java Edition protocol/Packets#Chunk Data and Update Light|Chunk Data and Update Light]]).<br /> * The player is below the minimum world height or above the maximum world height (teleported via [[Minecraft:Java Edition protocol/Packets#Synchronize Player Position|Synchronize Player Position]], or moved by gravity after the [[Minecraft:Java Edition protocol/Packets#Player Loaded|Player Loaded]] timeout has expired).<br /> * The player is in spectator mode (set via [[Minecraft:Java Edition protocol/Packets#Player Info Update|Player Info Update]], &#039;&#039;not&#039;&#039; the Game Mode field in Login (play)!)<br /> * The player is dead (set via [[Minecraft:Java Edition protocol/Packets#Set Health|Set Health]] or [[Minecraft:Java Edition protocol/Packets#Combat Death|Combat Death]]).<br /> <br /> The client will also spawn after spending 30 seconds in the loading screen, even if it never received Game Event 13.<br /> <br /> In past versions, you could either (1.19.3 through 1.20.2) send the default spawn position packet or (pre-1.19.3) send the player position packet. In general, try sending packets that inform the client about the player&#039;s position in the world in order to get past the loading terrain screen.<br /> <br /> As of 1.21.4, the minimum packets that need to be received and sent by the server in order to get the client past the loading terrain screen and into the world appear to be:<br /> <br /> # Receive [[Minecraft:Java Edition protocol/Packets#Handshake|Handshake]]<br /> # Receive [[Minecraft:Java Edition protocol/Packets#Login Start|Login Start]]<br /> # Send [[Minecraft:Java Edition protocol/Packets#Login Success|Login Success]]<br /> # Receive [[Minecraft:Java Edition protocol/Packets#Login Acknowledged|Login Acknowledged]]<br /> # Send multiple [[Minecraft:Java Edition protocol/Packets#Registry Data 2|Registry Data]] (one for each registry, must contain NBT unless the server also negotiates [[Minecraft:Java Edition protocol/Registries#Known packs negotiation|known packs]] and the client indicates support in the reply)<br /> # Send [[Minecraft:Java Edition protocol/Packets#Finish Configuration|Finish Configuration]]<br /> # Receive [[Minecraft:Java Edition protocol/Packets#Acknowledge Finish Configuration|Acknowledge Finish Configuration]]<br /> # Send [[Minecraft:Java Edition protocol/Packets#Login .28play.29|Login (Play)]]<br /> # Send [[Minecraft:Java Edition protocol/Packets#Game Event|Game Event]], Start waiting for level chunks<br /> # Send [[Minecraft:Java Edition protocol/Packets#Chunk Data and Update Light|Chunk Data and Update Light]] and/or [[Minecraft:Java Edition protocol/Packets#Synchronize Player Position|Synchronize Player Position]] (see above)<br /> <br /> The most difficult part of this may be sending the Registry Data packets required to define the contents of server-side data packs (including the vanilla data pack) which the client needs to know about. The amount of data that is strictly required is rather small compared to the amount sent by a vanilla server, but depending on your expectations and chosen approach, it may be easier to send all vanilla entries anyway. A complete list of requirements can be found at [[Minecraft:Java Edition protocol/Registries#List of synchronized registries]].<br /> <br /> Possible approaches include:<br /> <br /> * Parse the JSON files in the vanilla data pack (and possibly custom data packs), convert them to NBT, and send them as entries in Registry Data packets. The vanilla client is rather lenient in its interpretation of NBT, so no knowledge of the schema is required to perform this conversion (though the vanilla server does use a schema, and it may be wise to do so later in development). It is also necessary to send [[Minecraft:Java Edition protocol/Packets#Update Tags (configuration)|Update Tags]] to define the tags referenced in the vanilla registry JSON. They can also be obtained from JSON files in the data pack. This was the vanilla server behavior prior to 1.21, and is still used as a fallback when known packs negotiation fails, e.g. due to mismatched game versions with the same PVN.<br /> * Gather a list of JSON files provided for each registry in the vanilla data pack. Negotiate [[Minecraft:Java Edition protocol/Registries#Known packs negotiation|known packs]], and send listings of the vanilla entries for each registry (removing the &lt;code&gt;.json&lt;/code&gt; from the names), &#039;&#039;without&#039;&#039; NBT. The client will load the JSON files from its copy of the data pack, and behave as if they were sent by the server as NBT. It is still necessary to send Update Tags as before. This is done by the vanilla server since 1.21 when known packs negotiation succeeds, in order to save bandwidth. A server may take advantage of this to avoid needing to encode NBT early in development, but serious implementations should also support the fallback case. One may also want to support a mix of fully vanilla entries that can be sourced from known packs, and custom entries/overrides, as is done by the vanilla server when custom data packs are in use.<br /> * Negotiate known packs, and send the minimum required entries without NBT. As of 1.21.10 this includes the [[Minecraft:Java Edition protocol/Registries#Damage type requirements|required damage types]], the biome &lt;code&gt;minecraft:plains&lt;/code&gt;, and one arbitrary entry for each of the registries that are required to be non-empty (variants and dimension types). As of 1.21.10 no tags are required for these vanilla entries. This is the absolute minimum amount of data required to be sent by the server, but also the least flexible approach.<br /> * Do not negotiate known packs, and send entirely custom data. There is no strict requirement to use any definitions from the vanilla data pack. The only required entries with specific names are the ones listed above, and even these do not need to have the same data as in vanilla. This approach may be preferred by servers that demand extreme customization of client behavior, and may or may not also be considered more fun/interesting by the developer.<br /> <br /> Regardless of the approach, the order in which the entries are listed in the Registry Data packets is critically important, as it determines the IDs used to refer to the entries elsewhere in the protocol. The server may choose this order arbitrarily, but it must keep track of the IDs assigned as a result.<br /> <br /> === …chunks are randomly showing and disappearing! ===<br /> The vanilla client only reliably renders chunks surrounded by other loaded chunks on all sides. See [[Minecraft:Minecraft Wiki:Projects/wiki.vg merge/Chunk Format#Tips and notes|Chunk Format#Tips and notes]].<br /> <br /> === …the client is trying to send an invalid packet that begins with 0xFE01 ===<br /> The client is attempting a [[Minecraft:Minecraft Wiki:Projects/wiki.vg merge/Server_List_Ping#1.6|legacy ping]], this happens if your server did not respond to the [[Minecraft:Minecraft Wiki:Projects/wiki.vg merge/Server List Ping|Server List Ping]] properly, including if it sent malformed JSON.<br /> <br /> === …the client disconnects after some time with a &quot;Timed out&quot; error ===<br /> The server is expected to send a [[Minecraft:Java Edition protocol/Packets#Keep Alive (clientbound)|Keep Alive]] packet every 1-15 seconds (if the server does not send a keep alive within 20 seconds of state change to Play, the client will disconnect from the server for &#039;&#039;&#039;Timed Out&#039;&#039;&#039;), and the client should respond with the serverbound version of that packet. If either party does not receive keep alives for some period of time, they will disconnect.<br /> <br /> === ...some of the packets I expect to receive seem to be missing or too short ===<br /> <br /> You may be misusing the socket API. In particular, it is invalid to assume that the amount of data returned by calls to &lt;code&gt;recv&lt;/code&gt; (or equivalent, depending on the API you&#039;re using) relates to packet boundaries in any way. There are no &quot;borders&quot; in a [[Minecraft:wikipedia:Transmission Control Protocol|TCP]] data stream, only bytes. Regardless of how any two consecutive packets are sent, the receiver may get one packet, then the other, both at once, half of one, then the rest of both, or any other permutation of buffer sizes adding up to the total size of the packets. The only correct way to know where one packet ends and another begins is the packet length field, and you need to be prepared to handle multiple packets in one buffer, packets split across multiple buffers, etc. (as well as length fields split across multiple buffers!)<br /> <br /> Similarly, depending on the API being used, a &lt;code&gt;send&lt;/code&gt; call may also not guarantee that its whole input buffer is sent (consult the relevant documentation for details). This may also cause the connection to appear to hang during the login process, since the server will be left waiting indefinitely for the rest of the packet to arrive.<br /> <br /> One reason why packets sent separately may arrive at once is [[Minecraft:wikipedia:Nagle&#039;s algorithm|Nagle&#039;s algorithm]], a feature of many TCP implementations intended to improve efficiency particularly for applications making lots of small &lt;code&gt;send&lt;/code&gt; calls. It is not the &#039;&#039;only&#039;&#039; reason, though, and disabling it should not be seen as a solution to the problem discussed here. Nonetheless, the delays it introduces are detrimental to real-time applications like Minecraft, so the vanilla client and server disable it, and you should too. This is typically done by enabling a socket option called &lt;code&gt;TCP_NODELAY&lt;/code&gt;. Especially when disabling Nagle&#039;s algorithm, you should group multiple packets sent during the same tick in one send buffer for the best performance.<br /> <br /> == Navigation ==<br /> {{Navbox Java Edition technical|General}}<br /> <br /> [[Category:Protocol Details]]<br /> [[Category:Java Edition protocol]]<br /> {{license wiki.vg}}</div>

SyncBot