Sylverant Wiki - User contributions [en]

Protocol:Character Data

2010-01-12T05:17:47Z

Fuzziqersoftware:

Since I'm lazy, and don't feel like doing this the hard way, this is how Sylverant declares character data for PSODC and PSOPC (the relevant struct here is player_t):

<pre>/*
Sylverant Ship Server
Copyright (C) 2009 Lawrence Sebald

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License version 3 as
published by the Free Software Foundation.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
*/

#ifndef PLAYER_H
#define PLAYER_H

#include <inttypes.h>

#ifdef PACKED
#undef PACKED
#endif

#define PACKED __attribute__((packed))

/* The header attached before the player data when sending to a lobby client. */
typedef struct dc_player_hdr {
uint32_t tag;
uint32_t guildcard;
uint32_t ip_addr;
uint32_t client_id;
char name[16];
} PACKED dc_player_hdr_t;

typedef struct pc_player_hdr {
uint32_t tag;
uint32_t guildcard;
uint32_t ip_addr;
uint32_t client_id;
uint16_t name[16];
} PACKED pc_player_hdr_t;

/* These structures heavily based on those in newserv. */
typedef struct item {
uint16_t equipped;
uint16_t tech;
uint32_t flags;

union {
uint8_t data_b[12];
uint16_t data_w[6];
uint32_t data_l[3];
};

uint32_t item_id;

union {
uint8_t data2_b[4];
uint16_t data2_w[2];
uint32_t data2_l;
};
} PACKED item_t;

typedef struct inventory {
uint8_t item_count;
uint8_t hpmats_used;
uint8_t tpmats_used;
uint8_t language;
item_t items[30];
} PACKED inventory_t;

typedef struct player {
inventory_t inv;
uint16_t atp;
uint16_t mst;
uint16_t evp;
uint16_t hp;
uint16_t dfp;
uint16_t ata;
uint16_t lck;
uint16_t unk1;
uint32_t unk2[2];
uint32_t level;
uint32_t exp;
uint32_t meseta;
char name[16];
uint32_t unk3[2];
uint32_t name_color;
uint8_t model;
uint8_t unused[15];
uint32_t name_color_checksum;
uint8_t section;
uint8_t ch_class;
uint8_t v2flags;
uint8_t version;
uint32_t v1flags;
uint16_t costume;
uint16_t skin;
uint16_t face;
uint16_t head;
uint16_t hair;
uint16_t hair_r;
uint16_t hair_g;
uint16_t hair_b;
float prop_x;
float prop_y;
uint8_t config[0x48];
uint8_t techniques[0x14];
} PACKED player_t;

#undef PACKED

#endif /* !PLAYER_H */
</pre>

The following is newserv's definition of PSOGC and PSOBB player data (from player.h):

<pre>// in this segment:
// PLAYER_ITEM is the same as item_t
// PLAYER_INVENTORY is the same as inventory_t
// ITEM_DATA is the same as item_t without the first three fields

// an item in a player's bank (BB)
typedef struct {
ITEM_DATA data;
WORD amount;
WORD showflags; } PLAYER_BANK_ITEM;

// a player's bank (BB)
typedef struct {
DWORD numItems;
DWORD meseta;
PLAYER_BANK_ITEM items[200]; } PLAYER_BANK;

////////////////////////////////////////////////////////////////////////////////

// simple player stats (kept in a separate struct in order to facilitate leveling up for BB players)
typedef struct {
WORD atp;
WORD mst;
WORD evp;
WORD hp;
WORD dfp;
WORD ata;
WORD lck; } PLAYER_STATS;

// PC/GC player appearance and stats data
typedef struct {
PLAYER_STATS stats;
WORD unknown1;
DWORD unknown2[2];
DWORD level;
DWORD exp;
DWORD meseta;
char playername[16];
DWORD unknown3[2];
DWORD nameColor;
BYTE extraModel;
BYTE unused[15];
DWORD nameColorChecksum;
BYTE sectionID;
BYTE charClass;
BYTE v2flags;
BYTE version;
DWORD v1flags;
WORD costume;
WORD skin;
WORD face;
WORD head;
WORD hair;
WORD hairRed;
WORD hairGreen;
WORD hairBlue;
float propX;
float propY;
BYTE config[0x48];
BYTE techLevels[0x14]; } PCGC_PLAYER_DISPDATA; // 0xD0 in size

// BB player appearance and stats data
typedef struct {
PLAYER_STATS stats;
WORD unknown1;
DWORD unknown2[2];
DWORD level;
DWORD exp;
DWORD meseta;
char guildcard[16];
DWORD unknown3[2];
DWORD nameColor;
BYTE extraModel;
BYTE unused[11];
DWORD playTime; // not actually a game field; used only by newserv
DWORD nameColorChecksum;
BYTE sectionID;
BYTE charClass;
BYTE v2flags;
BYTE version;
DWORD v1flags;
WORD costume;
WORD skin;
WORD face;
WORD head;
WORD hair;
WORD hairRed;
WORD hairGreen;
WORD hairBlue;
float propX;
float propY;
wchar_t playername[16];
BYTE config[0xE8];
BYTE techLevels[0x14];
} BB_PLAYER_DISPDATA;

// BB player preview format
typedef struct {
DWORD exp;
DWORD level;
char guildcard[16];
DWORD unknown3[2];
DWORD nameColor;
BYTE extraModel;
BYTE unused[15];
DWORD nameColorChecksum;
BYTE sectionID;
BYTE charClass;
BYTE v2flags;
BYTE version;
DWORD v1flags;
WORD costume;
WORD skin;
WORD face;
WORD head;
WORD hair;
WORD hairRed;
WORD hairGreen;
WORD hairBlue;
float propX;
float propY;
wchar_t playername[16];
DWORD playTime;
} BB_PLAYER_DISPDATA_PREVIEW;

// complete BB player data format (used in E7 command)
typedef struct {
PLAYER_INVENTORY inventory; // 0000 // player
BB_PLAYER_DISPDATA disp; // 034C // player
BYTE unknown[0x0010]; // 04DC //
DWORD optionFlags; // 04EC // account
BYTE questData1[0x0208]; // 04F0 // player
PLAYER_BANK bank; // 06F8 // player
DWORD serialNumber; // 19C0 // player
wchar_t name[0x18]; // 19C4 // player
wchar_t teamname[0x10]; // 19C4 // player
wchar_t guildcarddesc[0x58]; // 1A14 // player
BYTE reserved1; // 1AC4 // player
BYTE reserved2; // 1AC5 // player
BYTE sectionID; // 1AC6 // player
BYTE charClass; // 1AC7 // player
DWORD unknown3; // 1AC8 //
BYTE symbolchats[0x04E0]; // 1ACC // account
BYTE shortcuts[0x0A40]; // 1FAC // account
wchar_t autoreply[0x00AC]; // 29EC // player
wchar_t infoboard[0x00AC]; // 2B44 // player
BYTE unknown5[0x001C]; // 2C9C //
BYTE challengeData[0x0140]; // 2CB8 // player
BYTE techMenuConfig[0x0028]; // 2DF8 // player
BYTE unknown6[0x002C]; // 2E20 //
BYTE questData2[0x0058]; // 2E4C // player
BB_KEY_TEAM_CONFIG keyConfig; // 2EA4 // account
} BB_COMPLETE_PLAYER_DATA_FORMAT; // total size: 39A0
</pre>

[[Category:PSO Server Protocol]]

Protocol:Packet 0xDA

2010-01-12T05:06:17Z

Fuzziqersoftware: Created page with 'The server sends Packet 0xDA to change the holiday theme of the current lobby. ==Dreamcast Packet Format== {| border="1" ! Bytes !! Meaning |- | 0x00 || Packet Type (0xDA) |- | …'

The server sends Packet 0xDA to change the holiday theme of the current lobby.

==Dreamcast Packet Format==
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Packet Type (0xDA)
|-
| 0x01 || Flags (Event ID; see below)
|-
| 0x02-0x03 || Packet Size (0x0004)
|}

{| border="1"
! Value !! Event
|-
| 0x00 || No event
|-
| 0x01 || Christmas
|-
| 0x02 || No event (on PSO v3; may exist on PSO v1/v2)
|-
| 0x03 || Valentine's Day
|-
| 0x04 || Easter
|-
| 0x05 || Halloween
|-
| 0x06 || Sonic
|-
| 0x07 || New Year's Day
|-
| 0x08 || Spring
|-
| 0x09 || White Day
|-
| 0x0A || Wedding
|-
| 0x0B || Autumn
|-
| 0x0C || Summer (with striped background)
|-
| 0x0D || Spring (with striped background)
|-
| 0x0E || Summer
|}

[[Category:PSO Server Protocol]]

Protocol:Packet 0x62

2010-01-12T05:01:26Z

Fuzziqersoftware:

{| align="right"
| __TOC__
|}
Clients send Packet 0x62 to the server to forward a "game command" to another client. This is used for various things in game, including requesting drops (clients "ask" the party leader what should be dropped).

PSO v3 (GameCube, Xbox, Blue Burst) sometimes uses packet 0x6D, which has exactly the same format and function as 0x62.

==Main Packet Format==
===Dreamcast===
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Packet Type (0x62 or 0x6D)
|-
| 0x01 || Flags (destination client ID)
|-
| 0x02-0x03 || Packet Size (Variable)
|-
| 0x04 || Subcommand Type
|-
| 0x05 || Subcommand Size (in 32-bit increments)
|-
| 0x06-0x07 || Unused?
|-
| 0x08... || Subcommand Data
|}

==Subcommands==
Various subcommands are sent with this packet, and this is not necessarily meant to be an exhaustive list of them (although, I'd love it if it were eventually).

===Subcommand 0x06===
Subcommand 0x06 is used to send a client's Guildcard to another client.

====Dreamcast====
{| border="1"
! Bytes !! Meaning
|-
| 0x00-0x03 || Player Tag (0x00010000)
|-
| 0x04-0x07 || Guildcard Number
|-
| 0x08-0x1F || Player Name
|-
| 0x20-0x77 || Guildcard Text
|-
| 0x78 || Unused
|-
| 0x79-0x7A || ??? (both set to 1)
|-
| 0x7B || Section ID
|-
| 0x7C || Character Class
|-
| 0x7D-0x7F || Padding (all zeroes)
|}

===Subcommand 0x60===
Subcommand 0x60 is used to request a item drop from the party leader. It is used when a box is opened (I haven't looked at what is sent when an enemy is killed yet, sorry).

====Dreamcast====
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Map Area
|-
| 0x01 || ??? (seems to always be 0x02 for boxes)
|-
| 0x02-0x03 || Request ID (might only be one byte, not sure)
|-
| 0x04-0x07 || Map X Position
|-
| 0x08-0x0B || Map Y Position
|-
| 0x0C-0x13 || ???
|}

[[Category:PSO Server Protocol]]

Protocol:Packet 0x60

2010-01-12T05:01:09Z

Fuzziqersoftware:

{| align="right"
| __TOC__
|}
Clients send Packet 0x60 to the server to forward a "game command" to all clients in the lobby. This is used for various things in game, including telling clients what items are dropped when a box is opened (clients "ask" the party leader what should be dropped with a form of [[Packet 0x62#Subcommand 0x60|Packet 0x62]] and the party leader replies with a [[Packet 0x60#Subcommand 0x5F|Subcommand 0x5F]]).

PSO v3 (GameCube, Xbox, Blue Burst) sometimes uses packet 0x6C, which has exactly the same format and function as 0x60.

PSO Episode 3 sometimes uses packets 0xC9 and 0xCB in games, which also behave exactly like 0x60. Sending an 0xC9 or 0xCB to a non-Episode 3 client would cause that client to disconnect.

==Main Packet Format==
===Dreamcast===
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Packet Type (0x60 or 0x6C)
|-
| 0x01 || Flags
|-
| 0x02-0x03 || Packet Size (Variable)
|-
| 0x04 || Subcommand Type
|-
| 0x05 || Subcommand Size (in 32-bit increments)
|-
| 0x06-0x07 || Unused?
|-
| 0x08... || Subcommand Data
|}

==Subcommands==
Various subcommands are sent with this packet, and this is not necessarily meant to be an exhaustive list of them (although, I'd love it if it were eventually).

===Subcommand 0x5F===
Subcommand 0x5F is used to tell clients what item dropped from an opened box.

{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Area of the Drop
|-
| 0x01 || What kind of thing are we asking about?
|-
| 0x02-0x03 || Request ID (might only be one byte)
|-
| 0x04-0x07 || X Coordinate
|-
| 0x08-0x0B || Y Coordinate
|-
| 0x0C-0x0F || Unknown (0x00000010 works)
|-
| 0x10-0x1B || Item Code (first 3 32-bit values)
|-
| 0x1C-0x1F || Unknown ((request_id | 0x06010100) seems to work)
|-
| 0x20-0x23 || Item Code (last 32-bit value)
|-
| 0x24-0x27 || Unknown (0x00000002)
|}

[[Category:PSO Server Protocol]]

Packet 0xCB

2010-01-12T04:59:41Z

Fuzziqersoftware: Redirected page to Packet 0x60

#REDIRECT [[Packet 0x60]]

[[Category:PSO Server Protocol]]

Packet 0xC9

2010-01-12T04:59:29Z

Fuzziqersoftware: Redirected page to Packet 0x60

#REDIRECT [[Packet 0x60]]

[[Category:PSO Server Protocol]]

Protocol:Packet 0x60

2010-01-12T04:58:42Z

Fuzziqersoftware:

{| align="right"
| __TOC__
|}
Clients send Packet 0x60 to the server to forward a "game command" to all clients in the lobby. This is used for various things in game, including telling clients what items are dropped when a box is opened (clients "ask" the party leader what should be dropped with a form of [[Packet 0x62#Subcommand 0x60|Packet 0x62]] and the party leader replies with a [[Packet 0x60#Subcommand 0x5F|Subcommand 0x5F]]).

PSO v3 (GameCube, Xbox, Blue Burst) sometimes used packet 0x6C, which has exactly the same format and function as 0x60.

==Main Packet Format==
===Dreamcast===
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Packet Type (0x60 or 0x6C)
|-
| 0x01 || Flags
|-
| 0x02-0x03 || Packet Size (Variable)
|-
| 0x04 || Subcommand Type
|-
| 0x05 || Subcommand Size (in 32-bit increments)
|-
| 0x06-0x07 || Unused?
|-
| 0x08... || Subcommand Data
|}

==Subcommands==
Various subcommands are sent with this packet, and this is not necessarily meant to be an exhaustive list of them (although, I'd love it if it were eventually).

===Subcommand 0x5F===
Subcommand 0x5F is used to tell clients what item dropped from an opened box.

{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Area of the Drop
|-
| 0x01 || What kind of thing are we asking about?
|-
| 0x02-0x03 || Request ID (might only be one byte)
|-
| 0x04-0x07 || X Coordinate
|-
| 0x08-0x0B || Y Coordinate
|-
| 0x0C-0x0F || Unknown (0x00000010 works)
|-
| 0x10-0x1B || Item Code (first 3 32-bit values)
|-
| 0x1C-0x1F || Unknown ((request_id | 0x06010100) seems to work)
|-
| 0x20-0x23 || Item Code (last 32-bit value)
|-
| 0x24-0x27 || Unknown (0x00000002)
|}

[[Category:PSO Server Protocol]]

Protocol:Packet 0x62

2010-01-12T04:58:28Z

Fuzziqersoftware:

{| align="right"
| __TOC__
|}
Clients send Packet 0x62 to the server to forward a "game command" to another client. This is used for various things in game, including requesting drops (clients "ask" the party leader what should be dropped).

PSO v3 (GameCube, Xbox, Blue Burst) sometimes used packet 0x6D, which has exactly the same format and function as 0x62.

==Main Packet Format==
===Dreamcast===
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Packet Type (0x62 or 0x6D)
|-
| 0x01 || Flags (destination client ID)
|-
| 0x02-0x03 || Packet Size (Variable)
|-
| 0x04 || Subcommand Type
|-
| 0x05 || Subcommand Size (in 32-bit increments)
|-
| 0x06-0x07 || Unused?
|-
| 0x08... || Subcommand Data
|}

==Subcommands==
Various subcommands are sent with this packet, and this is not necessarily meant to be an exhaustive list of them (although, I'd love it if it were eventually).

===Subcommand 0x06===
Subcommand 0x06 is used to send a client's Guildcard to another client.

====Dreamcast====
{| border="1"
! Bytes !! Meaning
|-
| 0x00-0x03 || Player Tag (0x00010000)
|-
| 0x04-0x07 || Guildcard Number
|-
| 0x08-0x1F || Player Name
|-
| 0x20-0x77 || Guildcard Text
|-
| 0x78 || Unused
|-
| 0x79-0x7A || ??? (both set to 1)
|-
| 0x7B || Section ID
|-
| 0x7C || Character Class
|-
| 0x7D-0x7F || Padding (all zeroes)
|}

===Subcommand 0x60===
Subcommand 0x60 is used to request a item drop from the party leader. It is used when a box is opened (I haven't looked at what is sent when an enemy is killed yet, sorry).

====Dreamcast====
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Map Area
|-
| 0x01 || ??? (seems to always be 0x02 for boxes)
|-
| 0x02-0x03 || Request ID (might only be one byte, not sure)
|-
| 0x04-0x07 || Map X Position
|-
| 0x08-0x0B || Map Y Position
|-
| 0x0C-0x13 || ???
|}

[[Category:PSO Server Protocol]]

Protocol:Packet 0x62

2010-01-12T04:58:10Z

Fuzziqersoftware:

{| align="right"
| __TOC__
|}
Clients send Packet 0x62 to the server to forward a "game command" to another client. This is used for various things in game, including requesting drops (clients "ask" the party leader what should be dropped).

PSO v3 (GameCube, Xbox, Blue Burst) sometimes used packet 0x6D, which has exactly the same format and function as 0x62.

==Main Packet Format==
===Dreamcast===
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Packet Type (0x62)
|-
| 0x01 || Flags (destination client ID)
|-
| 0x02-0x03 || Packet Size (Variable)
|-
| 0x04 || Subcommand Type
|-
| 0x05 || Subcommand Size (in 32-bit increments)
|-
| 0x06-0x07 || Unused?
|-
| 0x08... || Subcommand Data
|}

==Subcommands==
Various subcommands are sent with this packet, and this is not necessarily meant to be an exhaustive list of them (although, I'd love it if it were eventually).

===Subcommand 0x06===
Subcommand 0x06 is used to send a client's Guildcard to another client.

====Dreamcast====
{| border="1"
! Bytes !! Meaning
|-
| 0x00-0x03 || Player Tag (0x00010000)
|-
| 0x04-0x07 || Guildcard Number
|-
| 0x08-0x1F || Player Name
|-
| 0x20-0x77 || Guildcard Text
|-
| 0x78 || Unused
|-
| 0x79-0x7A || ??? (both set to 1)
|-
| 0x7B || Section ID
|-
| 0x7C || Character Class
|-
| 0x7D-0x7F || Padding (all zeroes)
|}

===Subcommand 0x60===
Subcommand 0x60 is used to request a item drop from the party leader. It is used when a box is opened (I haven't looked at what is sent when an enemy is killed yet, sorry).

====Dreamcast====
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Map Area
|-
| 0x01 || ??? (seems to always be 0x02 for boxes)
|-
| 0x02-0x03 || Request ID (might only be one byte, not sure)
|-
| 0x04-0x07 || Map X Position
|-
| 0x08-0x0B || Map Y Position
|-
| 0x0C-0x13 || ???
|}

[[Category:PSO Server Protocol]]

Packet 0x6D

2010-01-12T04:57:51Z

Fuzziqersoftware: Redirected page to Packet 0x62

#REDIRECT [[Packet 0x62]]

[[Category:PSO Server Protocol]]

Protocol:Packet 0x60

2010-01-12T04:57:31Z

Fuzziqersoftware:

{| align="right"
| __TOC__
|}
Clients send Packet 0x60 to the server to forward a "game command" to all clients in the lobby. This is used for various things in game, including telling clients what items are dropped when a box is opened (clients "ask" the party leader what should be dropped with a form of [[Packet 0x62#Subcommand 0x60|Packet 0x62]] and the party leader replies with a [[Packet 0x60#Subcommand 0x5F|Subcommand 0x5F]]).

PSO v3 (GameCube, Xbox, Blue Burst) sometimes used packet 0x6C, which has exactly the same format and function as 0x60.

==Main Packet Format==
===Dreamcast===
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Packet Type (0x60)
|-
| 0x01 || Flags
|-
| 0x02-0x03 || Packet Size (Variable)
|-
| 0x04 || Subcommand Type
|-
| 0x05 || Subcommand Size (in 32-bit increments)
|-
| 0x06-0x07 || Unused?
|-
| 0x08... || Subcommand Data
|}

==Subcommands==
Various subcommands are sent with this packet, and this is not necessarily meant to be an exhaustive list of them (although, I'd love it if it were eventually).

===Subcommand 0x5F===
Subcommand 0x5F is used to tell clients what item dropped from an opened box.

{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Area of the Drop
|-
| 0x01 || What kind of thing are we asking about?
|-
| 0x02-0x03 || Request ID (might only be one byte)
|-
| 0x04-0x07 || X Coordinate
|-
| 0x08-0x0B || Y Coordinate
|-
| 0x0C-0x0F || Unknown (0x00000010 works)
|-
| 0x10-0x1B || Item Code (first 3 32-bit values)
|-
| 0x1C-0x1F || Unknown ((request_id | 0x06010100) seems to work)
|-
| 0x20-0x23 || Item Code (last 32-bit value)
|-
| 0x24-0x27 || Unknown (0x00000002)
|}

[[Category:PSO Server Protocol]]

Packet 0x6C

2010-01-12T04:56:27Z

Fuzziqersoftware: Redirected page to Packet 0x60

#REDIRECT [[Packet 0x60]]

[[Category:PSO Server Protocol]]

Packet 0x89

2010-01-12T04:50:27Z

Fuzziqersoftware:

Clients send Packet 0x89 to the server to change the color of the arrow above their head. The server will then send out a [[Packet 0x88]] to the lobby to inform them of the new arrow color.

==Dreamcast Packet Format==
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Packet Type (0x89)
|-
| 0x01 || Flags (Arrow Color; see below)
|-
| 0x02-0x03 || Packet Size (0x0004)
|}

{| border="1"
! Value !! Color
|-
| 0x00 || No arrow
|-
| 0x01 || Red
|-
| 0x02 || Blue
|-
| 0x03 || Green
|-
| 0x04 || Yellow
|-
| 0x05 || Purple
|-
| 0x06 || Cyan
|-
| 0x07 || Orange
|-
| 0x08 || Pink
|-
| 0x09 || White
|-
| 0x0A || White
|-
| 0x0B || White
|-
| 0x0C || Black
|}

[[Category:PSO Server Protocol]]

Packet 0x88

2010-01-12T04:47:19Z

Fuzziqersoftware:

The server sends out Packet 0x88 to clients to inform them of the colors of arrows of all players in the lobby. This is typically brought on when a client sends a [[Packet 0x89]] to the server to change their arrow color, but is also sent when a client initially joins if anyone has arrows above their heads.

If this packet is sent while a player is loading into a lobby, some versions of PSO will ignore it, so the server must wait a couple of seconds before sending this packet to a player who just entered a lobby.

==Dreamcast Packet Format==
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Packet Type (0x88)
|-
| 0x01 || Flags (Number of entries)
|-
| 0x02-0x03 || Packet Size (Variable)
|-
| 0x04... || Arrow entries (see below for format)
|}

===Arrow color entry format===
{| border="1"
! Bytes !! Meaning
|-
| 0x00-0x03 || Player Tag (0x00010000)
|-
| 0x04-0x07 || Player Guildcard Number
|-
| 0x08 || Player Arrow Color
|-
| 0x09-0x0B || Padding (all zeroes)
|}

[[Category:PSO Server Protocol]]

Packet 0x83

2010-01-12T04:45:44Z

Fuzziqersoftware:

The server sends clients Packet 0x83 to communicate the list of default (non-game) lobbies available.

Note that PSO Episode 3 has five more lobbies than other versions, for a total of 20. The last five entries in the lobby list below describe the CARD lobbies (which are placed first in the list presented to the player).

==Dreamcast Packet Format==
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Packet Type (0x83)
|-
| 0x01 || Flags (0x0F -- 15 lobbies)
|-
| 0x02-0x03 || Packet Size (0x00C4)
|-
| 0x04... || Lobby Entries (see below for format)
|}

===Lobby Entry Format===
Each lobby has one entry, plus one at the end as padding. These entries are as follows (so there's a total of 16 of these in the packet -- the last is all zeroes):
{| border="1"
! Bytes !! Meaning
|-
| 0x00-0x03 || Menu ID
|-
| 0x04-0x07 || Item ID
|-
| 0x08-0x0B || Padding (all zeroes)
|}

[[Category:PSO Server Protocol]]

Packet 0x81

2010-01-12T04:44:16Z

Fuzziqersoftware:

Clients send Packet 0x81 to the server to send a simple mail to a recipient. The server sends it to clients to deliver the mail. Note, a lot of this packet is pretty much not understood by me, but I do know enough to actually translate messages DC<->PC enough that they work.

It seems that the game doesn't clear the entire message buffer before sending a message, so some random data (probably meaningless) ends up in the sent packet. Simple Mail packets can be shortened by the server (to remove excess garbage), and clients will still accept them.

==Dreamcast Packet Format==
{| border="1"
! Bytes !! Meaning
|-
| 0x0000 || Packet Type (0x81)
|-
| 0x0001 || Flags (0x00)
|-
| 0x0002-0x0003 || Packet Size (0x0220)
|-
| 0x0004-0x0007 || Player Tag (0x00010000)
|-
| 0x0008-0x000B || Guildcard Number of Sender
|-
| 0x000C-0x001B || Name of Sender
|-
| 0x001C-0x001F || Guildcard Number of Destination
|-
| 0x0020-0x00B0 || Message to be sent
|-
| 0x00B1-0x021F || Unknown
|}

[[Category:PSO Server Protocol]]

Protocol:Packet 0x1A

2010-01-12T04:39:36Z

Fuzziqersoftware:

The server sends clients a Packet 0x1A to pop up a large message box on the client's screen (it covers most of the screen). Schtserv uses this packet format to show the welcome message once a client is in the lobby on PSO for Dreamcast.

For PSO v3 and later (GameCube, Xbox, Blue Burst), packet 0xD5 does the same thing as 0x1A. On PSO Episodes 1 & 2 (GC/Xbox), the client will respond with a packet 0xD6 when the user presses A or B to close the message box. "Later" versions of PSO v3 (PSO Plus and Episode 3) will send an 0xD6 only if the player has not yet joined a lobby in the current session. Blue Burst will never send an 0xD6.

==Dreamcast Packet Format==
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Packet Type (0x1A or 0xD5)
|-
| 0x01 || Flags (0x00)
|-
| 0x02-0x03 || Packet Size (Variable)
|-
| 0x04... || Message to show
|}

[[Category:PSO Server Protocol]]

Protocol:Packet 0x1A

2010-01-12T04:39:24Z

Fuzziqersoftware:

The server sends clients a Packet 0x1A to pop up a large message box on the client's screen (it covers most of the screen). Schtserv uses this packet format to show the welcome message once a client is in the lobby on PSO for Dreamcast.

For PSO v3 and later (GameCube, Xbox, Blue Burst), packet 0xD5 does the same thing as 0x1A. On PSO Episodes 1 & 2 (GC/Xbox), the client will respond with a packet 0xD6 when the user presses A or B to close the message box. "Later" versions of PSO v3 (PSO Plus and Episode 3) will send an 0xD6 only if the player has not yet joined a lobby in the current session. Blue Burst will never send an 0xD6.

==Dreamcast Packet Format==
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Packet Type (0x1A)
|-
| 0x01 || Flags (0x00)
|-
| 0x02-0x03 || Packet Size (Variable)
|-
| 0x04... || Message to show
|}

[[Category:PSO Server Protocol]]

Protocol:Packet 0xD5

2010-01-12T04:36:09Z

Fuzziqersoftware: Redirected page to Packet 0x1A

#REDIRECT [[Packet 0x1A]]

[[Category:PSO Server Protocol]]

Protocol:Packet 0x05

2010-01-12T04:32:49Z

Fuzziqersoftware:

Packet 0x05 is sent by clients when they're getting ready to close a connection to the server. For all intents and purposes, Sylverant pretty much ignores these packets.

For most versions of PSO, sending an 0x05 to a client will cause it to disconnect.

==Dreamcast Packet Format==
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Packet Type (0x05)
|-
| 0x01 || Flags (0x00)
|-
| 0x02-0x03 || Packet Size (0x0004)
|}

[[Category:PSO Server Protocol]]

Protocol:Packet 0x02

2010-01-12T04:31:24Z

Fuzziqersoftware:

The server sends Packets 0x02 and 0x17 to non-Blue Burst clients to verify that a server is in place where the client is connecting, as well as to communicate the encryption vectors that will be in use for the rest of the connection.

Packet 0x02 is used for ship/block ports, and 0x17 is used for the login server.

Sending an 0x17 to a GameCube client will cause it to reply with an 0xDB, but only for the first 0x17 received in the client's session.

==Dreamcast Packet Format==
{| border="1"
! Bytes !! Meaning
|-
| 0x00 || Packet Type (0x02 or 0x17)
|-
| 0x01 || Flags (0x00)
|-
| 0x02-0x03 || Packet Size (At least 0x004C, everything after byte 0x4B will be ignored)
|-
| 0x04-0x43 || Copyright Message (see below)
|-
| 0x44-0x47 || Server Encryption Vector
|-
| 0x48-0x4B || Client Encryption Vector
|}

The Copyright Message that must be included in the above copyright message field is one of the two following things:
* For Ship/Block Servers: "DreamCast Lobby Server. Copyright SEGA Enterprises. 1999"
* For the Login Server: "DreamCast Port Map. Copyright SEGA Enterprises. 1999"

[[Category:PSO Server Protocol]]