Protocol FAQ

Revision as of 21:36, 31 December 2015 by Javaprophet (talk | contribs) (→‎What's the normal login sequence for a client?: Noted that you don't need to necessarily need to send a Client Status.)
Jump to navigation Jump to search

People very, very often have questions regarding the Minecraft Modern Protocol, so we'll try to address some of the most common ones on this document. If you're still having trouble, join us on IRC, channel #mcdevs on

Is the protocol documentation complete?

Depending on your definition, yes! 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 pre-release protocol changes, allowing us to quickly document new releases.

What's the normal login sequence for a client?

See Authentication for communication with Mojang's servers.

Warning.png Information might not be totally up to date

The recommended login sequence looks like this, where C is the client and S is the server:

  1. Client connects to server
  2. C→S: Handshake State=2
  3. C→S: Login Start
  4. S→C: Encryption Request
  5. Client auth
  6. C→S: Encryption Response
  7. Server auth, both enable encryption
  8. S→C: Login Success
  9. S→C: Join Game
  10. S→C: Spawn Position (“home” spawn, not where the client will spawn on login)
  11. S→C: Player Abilities
  12. S→C: Player Position And Look (tells the client they're ready to spawn)
  13. C→S: Player Position And Look (to confirm the spawn position)
  14. C→S: Client Status (sent either before or while receiving chunks, further testing needed, server handles correctly if not sent)
  15. S→C: inventory, Map Chunk Bulk, entities, etc

I think I've done everything right, but…

…my player isn't spawning!

After sending the common-sense packets (Handshake, Login Start, inventory, compass, and chunks), you need to finally send the player their initial position for them to leave the “Loading Map” screen.

Note that if the following steps are taken, a Minecraft client will spawn the player:

  1. Do Handshake (see Protocol Encryption)
  2. Send Spawn Position packet
  3. Send Player Position And Look packet

While the above steps are sufficient for Minecraft 1.4.5, it is good form to send packets that inform the client about the world around the player before allowing the player to spawn.

…my client isn't receiving complete map chunks!

Main article: How to Write a Client

The standard Minecraft server sends full chunks only when your client is sending player status update packets (any of Player (0x03) through Player Position And Look (0x06)).

…all connecting clients spasm and jerk uncontrollably!

For newer clients, your server needs to send 49 chunks ahead of time, not just one. Send a 7×7 square of chunks, centered on the connecting client's position, before spawning them.