From a48539e06b408867b4c817a8b11ca49899690203 Mon Sep 17 00:00:00 2001 From: t4 Date: Sat, 18 Jun 2011 05:12:36 +0000 Subject: [PATCH] Update MediaWiki page '317 Protocol' --- 317-Protocol.mediawiki | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/317-Protocol.mediawiki b/317-Protocol.mediawiki index 01625b0..e1dd876 100644 --- a/317-Protocol.mediawiki +++ b/317-Protocol.mediawiki @@ -6,7 +6,7 @@ When the client sends a packet to the server, the first byte encapsulates its opcode. This specific opcode is encrypted with a value generated by the ISAAC PRNG seeded with a dynamically server generated key during the login block. The server decrypts it and associates the opcode to the packet's respective predefined size. If the packet does not contain a fixed size, the opcode will be followed by either a byte or a word - varying per packet - for its proper size. This is then followed by the payload. == '''Login''' == -Every connection to the RuneScape main 'gateway' server sends a single byte of data, mostly well known as the connection type. The connection type tells the main server which type of connection you wish to initiate. The old engine list consists of: +Every connection to the main 'gateway' server sends a single byte of data, mostly well known as the connection type. The connection type tells the main server which type of connection you wish to initiate. The old engine list consists of: * Login request - connection type 14 * Update - connection type 15 * New connection login - connection type 16