Protocol - Revision history

Admin.tofuman: /* Packets */

2019-05-13T15:42:06Z

‎Packets

Admin.tofuman: /* Packets */

2016-11-02T17:46:10Z

‎Packets

Admin.tofuman: /* Packets */

2016-10-27T15:42:58Z

‎Packets

Admin.tofuman: /* Information */

2016-10-27T13:46:56Z

‎Information

Admin.tofuman: /* Structure */

2016-10-26T11:12:42Z

‎Structure

Admin.tofuman: /* Structure */

2016-10-26T11:12:24Z

‎Structure

Admin.tofuman: /* Structure */

2016-10-26T11:08:10Z

‎Structure

Admin.tofuman at 11:07, 26 October 2016

2016-10-26T11:07:35Z

Admin.tofuman: Created page with "= Information = SBOL uses a networking protocol provided by MultiTerm. This network protocol is a part of their "MassPlayer System" (MPS). MPS was mainly used by consoles (PS2..."

2016-10-26T09:43:41Z

Created page with "= Information = SBOL uses a networking protocol provided by MultiTerm. This network protocol is a part of their "MassPlayer System" (MPS). MPS was mainly used by consoles (PS2..."

New page

= Information =
SBOL uses a networking protocol provided by MultiTerm. This network protocol is a part of their "MassPlayer System" (MPS). MPS was mainly used by consoles (PS2 and Gamecude) to integrate online play. There doesn't appear to be any documentation on the system online and MultiTerm has long been shutdown.

One thing to keep in mind when working the the protocol in SBOL is that MPS uses big endian byte ordering. Unlike many x86 based systems which use little endian. This is likely something carried over from the libraries being largely developed for systems that processed bytes as big endian. The client uses the ntohl/ntohs functions to switch these bytes when processing them (network to host long/short. A winsock function but I guess why write a function when its already available in the libraries you're using).
= Packets =
*[[0x0100]] - Authentication
*[[0x0200]] - ???
*[[0x0300]] - ???
*[[0x0400]] - ???
*[[0x0500]] - ???
*[[0x0600]] - ???
*[[0x0700]] - ???
*[[0x0800]] - ???
*[[0x0900]] - ???
*[[0x0A00]] - ???
*[[0x0B00]] - ???
*[[0x0C00]] - ???
*[[0x0D00]] - ???
*[[0x0E00]] - User Creation
*[[0x0F00]] - ???
*[[0x1000]] - ???
*[[0x1100]] - ???
*[[0x1200]] - ???
*[[0x1300]] - ???

@@ Line 2: / Line 2: @@
 SBOL uses a networking protocol provided by MultiTerm. This network protocol is a part of their "MassPlayer System" (MPS). MPS was mainly used by consoles (PS2 and Gamecude) to integrate online play. There doesn't appear to be any documentation on the system online and MultiTerm has long been shutdown.
-One thing to keep in mind when working the the protocol in SBOL is that MPS uses big endian byte ordering. Unlike many x86 based systems which use little endian. This is likely something carried over from the libraries being largely developed for systems that processed bytes as big endian. The client uses the ntohl/ntohs functions to switch these bytes when processing them (network to host long/short. A winsock function but I guess why write a function when its already available in the libraries you're using).
+One thing to keep in mind when working with the protocol in SBOL is that MPS uses big endian byte ordering. Unlike many x86 based systems which use little endian. This is likely something carried over from the libraries being largely developed for systems that processed bytes as big endian. The client uses the ntohl/ntohs functions to switch these bytes when processing them (network to host long/short. A winsock function but I guess why write a function when its already available in the libraries you're using).
 = Structure =
 Client:<br />

@@ Line 12: / Line 12: @@
 PS PS PT PT ST ST PD PD PD PD PD ..
 </code><br /><br />
-PS = '''P'''acket '''S'''ize: Data type Short (the packet size is the site minus 2)<br />
+PS = '''P'''acket '''S'''ize: Data type Short (the packet size is the size minus 2)<br />
 PT = '''P'''acket '''T'''ype: Data type Short<br />
 ST = Packet '''S'''ub '''T'''ype: Data type Short<br />

@@ Line 7: / Line 7: @@
 <code>
 PS PS PT PT PD PD PD PD PD ..
-</code><br />
+</code><br /><br />
 Server:<br />
 <code>
 PS PS PT PT ST ST PD PD PD PD PD ..
-</code><br />
+</code><br /><br />
 PS = '''P'''acket '''S'''ize: Data type Short (the packet size is the site minus 2)<br />
 PT = '''P'''acket '''T'''ype: Data type Short<br />

@@ Line 4: / Line 4: @@
 One thing to keep in mind when working the the protocol in SBOL is that MPS uses big endian byte ordering. Unlike many x86 based systems which use little endian. This is likely something carried over from the libraries being largely developed for systems that processed bytes as big endian. The client uses the ntohl/ntohs functions to switch these bytes when processing them (network to host long/short. A winsock function but I guess why write a function when its already available in the libraries you're using).
 = Structure =
-Client:
+Client:<br />
 <code>
 PS PS PT PT PD PD PD PD PD ..
-</code>
+</code><br />
-Server:
+Server:<br />
 <code>
 PS PS PT PT ST ST PD PD PD PD PD ..
-</code>
+</code><br />
 PS = '''P'''acket '''S'''ize: Data type Short (the packet size is the site minus 2)<br />
 PT = '''P'''acket '''T'''ype: Data type Short<br />
 ST = Packet '''S'''ub '''T'''ype: Data type Short<br />
 PD = '''P'''acket '''D'''ata array of bytes structure is specific to the type of packet
 = Packets =
 *[[0x0100]] - Authentication

@@ Line 19: / Line 19: @@
 = Packets =
-*[[0x0000]] - ???
+*[[0x0000]] - Keep Alive
 *[[0x0100]] - Authentication
-*[[0x0200]] - ???
+*[[0x0200]] - Car Information
-*[[0x0300]] - ???
+*[[0x0300]] - Course Information
-*[[0x0400]] - ???
+*[[0x0400]] - Player Actions
 *[[0x0500]] - ???
 *[[0x0600]] - Chat
-*[[0x0700]] - Movement/Player Actions
+*[[0x0700]] - Player Movement
 *[[0x0800]] - ???
 *[[0x0900]] - Shop
-*[[0x0A00]] - ???
+*[[0x0A00]] - Ping
 *[[0x0B00]] - ???
-*[[0x0C00]] - ???
+*[[0x0C00]] - Rival Information
 *[[0x0D00]] - ???
 *[[0x0E00]] - User Creation
 *[[0x0F00]] - ???
-*[[0x1000]] - ???
+*[[0x1000]] - career Data
 *[[0x1100]] - ???
 *[[0x1200]] - ???
 *[[0x1300]] - ???