Core Protocol - Revision history

Cheese: moved Core protocol to Core Protocol over redirect

2015-02-16T17:59:23Z

moved Core protocol to Core Protocol over redirect

CypherJF: added core packet addendum for reliable packet handling

2010-11-15T04:13:28Z

added core packet addendum for reliable packet handling

BaK: spacing

2008-03-18T05:39:20Z

spacing

BaK: observed some undocumented packets "in the wild" so I'd figure I'd add them

2008-03-18T05:38:56Z

observed some undocumented packets "in the wild" so I'd figure I'd add them

CypherJF: fixed spelling; please use a spell check (ie: Firefox 2.0+) in the future ;)

2007-10-12T22:00:12Z

fixed spelling; please use a spell check (ie: Firefox 2.0+) in the future ;)

Doc flabby: packets can be nested

2007-10-12T13:52:12Z

packets can be nested

Smong: took out the tcp protocol part to avoid distracting from the main article

2007-10-09T19:04:31Z

took out the tcp protocol part to avoid distracting from the main article

CypherJF: added link to TCP Billing Protocol

2007-10-07T18:25:34Z

added link to TCP Billing Protocol

BaK: 468 isn't max

2006-09-28T10:49:18Z

468 isn't max

Mine GO BOOM: Reverted edit of Zc321, changed back to last version by Cyan~Fire

2005-11-30T07:54:01Z

Reverted edit of Zc321, changed back to last version by Cyan~Fire

@@ Line 22: / Line 22: @@
       4    ~client key (negative)
-x03 reliable header
+x03 reliable header (see reliable packet addendum below)
 offset size comment
       1    type 0x00
       1    type 0x03
-      4    packet id
+      4    packet id (ie: ACK_ID)
-      ?    payload (514 max)
+      ?    payload (514 bytes max)
-x04 reliable acknowledge
+x04 reliable acknowledge (see reliable packet addendum below)
 offset size comment
       1    type 0x00
       1    type 0x04
-      4    packet id
+      4    packet id (ie: ACK_ID)
 x05 sync
@@ Line 108: / Line 108: @@
       6   ??
 </pre>
 [[Category: Protocol]]

@@ Line 96: / Line 96: @@
 packet repeats from offset 2 until end, process contents as arbitrary packet
-x10 Continuum alternate encryption response(s2c)?
+x10 Continuum alternate encryption response (s2c)?
 offset size comment
       1    type 0x00

@@ Line 95: / Line 95: @@
       ?    payload with length as above
 packet repeats from offset 2 until end, process contents as arbitrary packet
 </pre>
 [[Category: Protocol]]

@@ Line 6: / Line 6: @@
 *All integers are little endian
 *All core packets begin with the type byte 0x00
-*Packets can be nested (They are usually processed recursivly)
+*Packets can be nested (They are usually processed recursively)
 <pre>

@@ Line 6: / Line 6: @@
 *All integers are little endian
 *All core packets begin with the type byte 0x00
 <pre>

← Older revision	Revision as of 17:59, 16 February 2015
(No difference)

← Older revision		Revision as of 19:04, 9 October 2007
Line 1:		Line 1:
−	This protocol is UDP and bi-directional. It can be thought of as another layer within an application's network layer. [[Subgame]], [[ASSS]], [[Continuum]], VIE's [[SubSpace]] client, the [[Directory server]], and ~~the~~ [[Billing Server]] utilize this protocol~~, though [[Grelminar]] has designed a [[TCP Billing Protocol\|TCP Billing Server protocol]]~~.	+	This protocol is UDP and bi-directional. It can be thought of as another layer within an application's network layer. [[Subgame]], [[ASSS]], [[Continuum]], VIE's [[SubSpace]] client, the [[Directory server]], and some [[Billing Server\|Billing Servers]] utilize this protocol.

	There is support for reliable ordered packets, large packets and cluster packets.		There is support for reliable ordered packets, large packets and cluster packets.

← Older revision		Revision as of 18:25, 7 October 2007
Line 1:		Line 1:
−	This protocol is UDP and bi-directional. It can be thought of as another layer within an application's network layer. [[Subgame]], [[ASSS]], [[Continuum]], VIE's [[SubSpace]] client, the [[Directory server]], and the [[Billing Server]] utilize this protocol, though [[Grelminar]] has designed a TCP Billing Server protocol.	+	This protocol is UDP and bi-directional. It can be thought of as another layer within an application's network layer. [[Subgame]], [[ASSS]], [[Continuum]], VIE's [[SubSpace]] client, the [[Directory server]], and the [[Billing Server]] utilize this protocol, though [[Grelminar]] has designed a [[TCP Billing Protocol\|TCP Billing Server protocol]].

	There is support for reliable ordered packets, large packets and cluster packets.		There is support for reliable ordered packets, large packets and cluster packets.

@@ Line 73: / Line 73: @@
       1    type 0x0A
       4    total length of all segments
-      ?    payload (expect 468 max)
+      ?    payload
 keep appending payloads until total length is reached then process contents as
 a non-core packet.

← Older revision		Revision as of 07:54, 30 November 2005
Line 1:		Line 1:
−	~~apple cows~~	+	This protocol is UDP and bi-directional. It can be thought of as another layer within an application's network layer. [[Subgame]], [[ASSS]], [[Continuum]], VIE's [[SubSpace]] client, the [[Directory server]], and the [[Billing Server]] utilize this protocol, though [[Grelminar]] has designed a TCP Billing Server protocol.
		+
		+	There is support for reliable ordered packets, large packets and cluster packets.
		+
		+	*The maximum packet size is 520 bytes
		+	*All integers are little endian
		+	*All core packets begin with the type byte 0x00
		+
		+	<pre>
		+	0x01 login
		+	offset size comment
		+	0 1 type 0x00
		+	1 1 type 0x01
		+	2 4 client key
		+	6 2 protocol version (vie = 0x01, ctm = 0x11)
		+
		+	0x02 login response
		+	offset size comment
		+	0 1 type 0x00
		+	1 1 type 0x02
		+	2 4 ~client key (negative)
		+
		+	0x03 reliable header
		+	offset size comment
		+	0 1 type 0x00
		+	1 1 type 0x03
		+	2 4 packet id
		+	6 ? payload (514 max)
		+
		+	0x04 reliable acknowledge
		+	offset size comment
		+	0 1 type 0x00
		+	1 1 type 0x04
		+	2 4 packet id
		+
		+	0x05 sync
		+	offset size comment
		+	0 1 type 0x00
		+	1 1 type 0x05
		+	2 4 local time
		+	6 4 packets sent
		+	10 4 packets received
		+
		+	0x06 sync response
		+	offset size comment
		+	0 1 type 0x00
		+	1 1 type 0x06
		+	2 4 time from last received 0x05 packet
		+	6 4 server time
		+
		+	0x07 disconnect
		+	offset size comment
		+	0 1 type 0x00
		+	1 1 type 0x07
		+
		+	0x08 small chunk
		+	offset size comment
		+	0 1 type 0x00
		+	1 1 type 0x08
		+	2 ? payload (expect 472 max)
		+	keep appending payloads until 0x09 chunk tail is received
		+
		+	0x09 chunk tail
		+	offset size comment
		+	0 1 type 0x00
		+	1 1 type 0x09
		+	2 ? payload (expect 472 or less)
		+	append this payload then process contents as a non-core packet
		+
		+	0x0A stream
		+	offset size comment
		+	0 1 type 0x00
		+	1 1 type 0x0A
		+	2 4 total length of all segments
		+	6 ? payload (expect 468 max)
		+	keep appending payloads until total length is reached then process contents as
		+	a non-core packet.
		+
		+	0x0B cancel stream request
		+	offset size comment
		+	0 1 type 0x00
		+	1 1 type 0x0B
		+
		+	0x0C cancel stream acknowledge
		+	offset size comment
		+	0 1 type 0x00
		+	1 1 type 0x0C
		+
		+	0x0E cluster
		+	offset size comment
		+	0 1 type 0x00
		+	1 1 type 0x0E
		+	2 1 length
		+	3 ? payload with length as above
		+	packet repeats from offset 2 until end, process contents as arbitrary packet
		+	</pre>
		+
		+	[[Category: Protocol]]