HowTo: Read the first packet sent by the client

The first packet sent by the client to the server can be understood as follows:

Header:

Bytes	Description	Length
0x00-0x01	Set to 00 00 (no session ID yet)	2
0x02-0x03	The length of the packets body in bytes	2
0x04-0x07	The command (aka action aka OP code): 00010000	4
0x08-0x0B	The sequence number of the packet: 00000000	4
0x0C-0x0F	The checksum of the packets body	4
0x10-0x11	00 00	4
0x12-0x13	00 00	4

Body:

Bytes	Description	Length
0x14	Length of the following (ASCII) string	1
0x15-0x53	The client version "061004_netver:..." as ASCII string	63
0x54-0x57	Length of the following block (0x0145 bytes, byte swapped)	4
0x58-0x5B	Unknown?	4
0x5C-0x5F	Set to 04 00 00 00 if a GLS ticket follows	4
0x60-0x63	Seconds since 1970, bytes must be read "backwards"	4
0x64	Length of the following (UTF-16) string	4
0x65-0x96	The account identifier? (a GUID/UUID in UTF-16)	4
0x97-0x9a	GLS ticket length (byte swapped) 0x0102 == 258 bytes	4
0x9b-0x19c	GLS ticket generated by the launcher	4

That's all currently known behind the magic happening in the first packet.