Talk:Pocket Minecraft Protocol

Got 0x1c when I sent 0x02 to a server

I've been playing around with this protocol and acting as a connecting client, I found that the protocol seems to be different than what is listed on this page. I sent these hex values to my iPod running Minecraft PE (full) v0.1.2 alpha: 02 00 00 00 00 00 a1 a2 41 00 ff ff 00 fe fe fe fe fd fd fd fd 12 34 56 78. It replied with 1c 00 00 00 00 00 a1 a2 41 00 00 00 00 79 1b 2d 6d 00 ff ff 00 fe fe fe fe fd fd fd fd 12 34 56 78 00 0b 4d 43 43 50 50 3b 44 65 6d 6f 3b 00 00 00 00 00 00. The 0x0c packet isn't listed at all on the page, so I think this is something new.

Here's a more readable way of writing this. I sent:

• int8 = 0x02 (packet type ID)
• int64 = ping ID
• MAGIC

The server replied:

• int8 = 0x1c (packet type ID)
• int64 = ping ID from client
• int64 = unknown (server ID??), "00 00 00 00 79 1b 2d 6d"
• MAGIC
• a long array that can indicate server visibility:
  • "00 11 4d 43 43 50 50 3b 44 65 6d 6f 3b 6f 78 67 75 79 33" if server is visible
  • "00 0b 4d 43 43 50 50 3b 44 65 6d 6f 3b 00 00 00 00 00 00" if server is invisible

I don't know where to go from here. :P I'm interesting in writing computer-run server software, but clearly it will take some time to figure out the protocol. I might use Wireshark later and monitor two iPods communicating (if I can figure out my brother's passcode XD).