Difference between revisions of "Server List Ping"

From wiki.vg
Jump to navigation Jump to search
(First update for 1.6. Feel free to expand/change around/etc)
(No difference)

Revision as of 04:15, 2 July 2013

Minecraft supports querying the MOTD, player count, max players and server version via the usual port. Unlike Query, the server list ping interface is always enabled.

1.6 -

Client -> Server

The client initiates a TCP connection to the minecraft server on the standard port. Instead of doing auth and logging in (as detailed in Protocol Encryption), it sends the following data, expressed in hexadecimal:

  1. FE - packet identifier for a server list ping
  2. 01 - server list ping's payload (always 1)
  3. FA - packet identifier for a plugin message
  4. 00 0B - length of following string, in characters, as a big-endian short (always 11)
  5. 00 4D 00 43 00 7C 00 50 00 69 00 6E 00 67 00 48 00 6F 00 73 00 74 - the string "MC|PingHost" encoded as a big-endian UCS-2 string
  6. XX XX - length of the rest of the packet, as a big-endian short
  7. XX - protocol version - currently 73 (decimal)
  8. XX XX - length of following string, in characters, as a big-endian short
  9. XX XX ... - hostname the client is connecting to, as a big-endian UCS-2 string
  10. XX XX - port the client is connecting to, as a big-endian short.

Server -> Client

The server responds with a 0xFF kick packet. The packet begins with a single byte identifier ff, then a two-byte big endian short giving the length of the proceeding string in characters. You can actually ignore the length because the server closes the connection after the response is sent.

After the first 3 bytes, the packet is a big-endian UCS-2 string. It begins with two characters: §1, followed by a null character. On the wire these look like 00 a7 00 31 00 00.

The remainder is null character (that is 00 00) delimited fields:

  1. Protocol version (e.g. 47)
  2. Minecraft server version (e.g. 1.4.2)
  3. Message of the day (e.g. A Minecraft Server)
  4. Current player count
  5. Max players

The entire packet looks something like this:

                   <---> first character
   0000000: ff00 2300 a700 3100 0000 3400 3700 0000  ....§.1...4.7...
   0000010: 3100 2e00 3400 2e00 3200 0000 4100 2000  1...4...2...A. .
   0000020: 4d00 6900 6e00 6500 6300 7200 6100 6600  M.i.n.e.c.r.a.f.
   0000030: 7400 2000 5300 6500 7200 7600 6500 7200  t. .S.e.r.v.e.r.
   0000040: 0000 3000 0000 3200 30                   ..0...2.0

1.4 - 1.5

Prior to the Minecraft 1.6, the client -> server operation is much simpler, and only sends FE 01, with none of the following data beginning FA ...

Beta 1.8 - 1.3

Prior to Minecraft 1.6, the client only sends FE.

Additionally, the response from the server only contains 3 fields delimited by §:

  1. Message of the day (e.g. A Minecraft Server)
  2. Current player count
  3. Max players

The entire packet looks something like this:

                   <---> first character
   0000000: ff00 1700 4100 2000 4d00 6900 6e00 6500  ....A. .M.i.n.e.
   0000010: 6300 7200 6100 6600 7400 2000 5300 6500  c.r.a.f.t. .S.e.
   0000020: 7200 7600 6500 7200 a700 3000 a700 3100  r.v.e.r.§.0.§.1.
   0000030: 30                                       0


Sample code