Difference between revisions of "Directory Client Protocol"

From ASSS Wiki
Jump to: navigation, search
m ("clinet" connections)
(added some detail on description max length)
 
(8 intermediate revisions by 3 users not shown)
Line 2: Line 2:
  
 
Continuum sends a sync request and SubSpace doesn't.
 
Continuum sends a sync request and SubSpace doesn't.
The list request is sent as reliable.
+
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 zone's data.
+
Directory servers listen on port 4990 for [[client]] connections.
  
 
<pre>
 
<pre>
Line 25: Line 25:
 
11    4    version (0x86 0x00 0x00 0x00)
 
11    4    version (0x86 0x00 0x00 0x00)
 
15    64  name
 
15    64  name
79    ?    description
+
79    ?    description (should not be longer than around 480-490 in length)
 
packet repeats from offset 1 until end
 
packet repeats from offset 1 until end
 
</pre>
 
</pre>
 +
 +
=== See also ===
 +
* [[Directory Game Server Protocol]]
  
 
[[Category: Protocol]]
 
[[Category: Protocol]]

Latest revision as of 11:08, 6 May 2009

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.

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 (should not be longer than around 480-490 in length)
packet repeats from offset 1 until end

See also