Difference between revisions of "Packet 0x93"

From Sylverant
Jump to navigationJump to search
(Add BB definition (handler details forthcoming))
 
(One intermediate revision by the same user not shown)
Line 45: Line 45:
 
| 0x02-0x03 || Packet Type (0x93)
 
| 0x02-0x03 || Packet Type (0x93)
 
|-
 
|-
| 0x04-0x07 || Flags (padding)
+
| 0x04-0x07 || Flags (usually 0x00)
 
|-
 
|-
 
| 0x08-0x0F || Unknown
 
| 0x08-0x0F || Unknown
Line 61: Line 61:
 
| 0x4C-0x5B || Password
 
| 0x4C-0x5B || Password
 
|-
 
|-
| 0x5C-0x83 || Padding
+
| 0x5C-0x83 || Padding (0x00)
 
|-
 
|-
| 0x84-0x8B || Hardware info
+
| 0x84-0x8B || Hardware info (client-specific string)
 
|-
 
|-
 
| 0x8C-0xB4 || Version String *
 
| 0x8C-0xB4 || Version String *
  
 
[[Category:PSO Server Protocol]]
 
[[Category:PSO Server Protocol]]

Latest revision as of 04:05, 9 January 2015

PSOv1 clients send Packet 0x93 to the server in order to log in to the ship/block server. BlueBurst clients send this packet both to the login and character ports of the login server. The data should be interpreted differently depending on which of these two receives the packet.

Dreamcast Packet Format

Bytes Meaning
0x00 Packet Type (0x93)
0x01 Flags (0x00)
0x02-0x03 Packet Size (Variable)
0x04-0x07 Player Tag (0x00010000)
0x08-0x0B Guildcard Number
0x0C-0x1B Unknown
0x1C-0x23 Serial Number (ASCII)
0x24-0x2C Padding (all zeroes)
0x2D-0x34 Access Key (ASCII)
0x35-0x3D Padding (all zeroes)
0x3E-0x45 Some sort of Dreamcast-specific ID?
0x46-0x9D Padding (all zeroes)
0x9E-0xAD Character Name
0xAE-0xAF Padding (all zeroes)
0xB0... Data set in Packet 0x04, if any.

BlueBurst Packet Format (Little Endian)

Bytes Meaning
0x00-0x01 Packet Length (0xb4)
0x02-0x03 Packet Type (0x93)
0x04-0x07 Flags (usually 0x00)
0x08-0x0F Unknown
0x10-0x11 Client Version
0x12-0x17 Unknown
0x18-0x1B Team Id *
0x1C-0x2B Username
0x2C-0x4B Padding (0x00)
0x4C-0x5B Password
0x5C-0x83 Padding (0x00)
0x84-0x8B Hardware info (client-specific string)
0x8C-0xB4 Version String *