Difference between revisions of "Directory Client Protocol"
From ASSS Wiki
m (forgot my wiki markup) |
m (more specific about the ping protocol) |
||
| Line 4: | Line 4: | ||
The list request is sent as reliable. On the traditional directory servers (not catid's), traffic is always encrypted, even if you send a null encryption key. | The list request is sent as reliable. On the traditional directory servers (not catid's), traffic is always encrypted, even if you send a null encryption key. | ||
| − | Directory servers listen on port 4990 for client connections, and 4991 for updates to each zone's data using the [[Server to Directory Server Protocol]] as well as pings using the [[Ping Protocol]]. | + | Directory servers listen on port 4990 for client connections, and 4991 for updates to each zone's data using the [[Server to Directory Server Protocol]] as well as pings using the old [[Ping Protocol]]. |
<pre> | <pre> | ||
Revision as of 06:02, 28 September 2006
Core protocol is used as usual. Dirserv specific c2s/s2c protocol.
Continuum sends a sync request and SubSpace doesn't. The list request is sent as reliable. On the traditional directory servers (not catid's), traffic is always encrypted, even if you send a null encryption key.
Directory servers listen on port 4990 for client connections, and 4991 for updates to each zone's data using the Server to Directory Server Protocol as well as pings using the old Ping Protocol.
c2s 0x01 list request offset size comment 0 1 type 0x01 1 4 minimum players s2c 0x01 list data offset size comment 0 1 type 0x01 1 4 ip 5 2 port 7 2 player count 9 2 billing (on 0x01 0x00) 11 4 version (0x86 0x00 0x00 0x00) 15 64 name 79 ? description packet repeats from offset 1 until end
