$Revision: 1.28 $

KGS Protocol Description

This XML document describes the KGS protocol. It is also used to automatically generate the perl parser for all the messages and structures in the protocol. Adapting it to other languages should be trivial.

Please note that the author of KGS has told me that he will change the protocol in response to my efforts. Unfortunately, he does this just to make it more difficult to reverse-engineer it, since his changes are neither required, nor useful (they just make the protocol less robust, without adding added value).

If you feel you need to update the visual appearance of this document, feel free to look doc/doc2html.xsl and improve it.

The current version of this document can always be found at here, while the HTML version of it can be found here.

Changes for server version 2.5

Sorry - I have little time to dissect the protocol, but as far as I can see, there was no deeper need for the protocol change, as the protocol itself didn't change in a significant way. The only significant change was the addition of a linear congruence generator that is xor'ed into the packet length, and some heavy foolery to change receive packets. It seems that wms prefers to lock out many of his own users than to have a few people write their own client. I didn't really expect that from him, but instead expected real changes for the good, as he is claiming all the time.

Well, that is just what he accouned earlier, so he just did what he said...

Anything I know about changes in 2.5.x are reflected in this document already. You can log-in, chat, log-out, watch games, but you cannot comment games nor play nor privately chat.

Structure and conventions of this document and the protocol

"Send" means messages send from the client to the server, while "received" means messages send by the server to the client.

Everything on the wire is in little-endian format (what a shame).

Primitive types are mostly integers (signed "I<bits>", unsigned "U<bits>"), ascii strings ("username"), or zero-terminated UCS2-Strings ("STRING"). Yes, I know java is supposed to do UTF-16, but no implementation seems to care...

For the rest, go figure or bug me, Marc Lehmann <pcg@goof.com>

Stream and message structure.

After connecting to the server, a handshake byte is sent. It's the major version number of the protocol the client expects to receive. Version 3 and 4 are mostly the same, except that Version 4 clients expect server messages to be compressed, version 3 clients not.

The server sends back his protocol number, which is always 3 in the current protocol. Most of the protocol variation is determined by the server using the client version that is used in the initial login message, not the initial handshake byte.

After the initial handshake, the client sends uncompressed messages, while the server sends back a zlib-compressed stream (rfc1950 and rfc1951).

All messages have the same header:

STRUCTURE message_header

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
_unknown	U16
length	U16
type	U16

Primitive types used in the protocol.

Apart from the basic types, I need to define some extra types to deal with fixed-point values (based on integer types) or fixed-length strings (either 7-bit-ascii or more limited (A), or UCS-2 based (S)).

TYPE username

BASE TYPE A, LENGTH 10, MULTIPLIER

The basic user or login name, used throughout the protocol as a handle to the user.

TYPE roomname

BASE TYPE S, LENGTH 25, MULTIPLIER

Many strings in the protocol are fixed-width for no good reason (maybe this is one reason for using compression in newer versions, as the packets itself are wasting lots of space.

TYPE realname

BASE TYPE S, LENGTH 50, MULTIPLIER

TYPE email

BASE TYPE S, LENGTH 70, MULTIPLIER

TYPE userinfo

BASE TYPE S, LENGTH 1000, MULTIPLIER

TYPE url

BASE TYPE A, LENGTH 100, MULTIPLIER

Used in user_record.

TYPE locale

BASE TYPE A, LENGTH 5, MULTIPLIER

A kind of locale specifier. It seems the general format seems to be lowercase language, underscore, uppercase location, e.g. en_US. More fancy specifications don't fit.

TYPE flag

BASE TYPE U8, LENGTH , MULTIPLIER 1

Just a simple boolean value. 0 means false, and 1 generally true, but I suggest ccepting != 0 as true.

TYPE komi16

BASE TYPE I16, LENGTH , MULTIPLIER 2

TYPE komi32

BASE TYPE I32, LENGTH , MULTIPLIER 2

TYPE komi324

BASE TYPE I32, LENGTH , MULTIPLIER 4

Komi values are multiplied by 2 to make them integer in the protocol. Well, *most* of the time at least...

TYPE result

BASE TYPE I32, LENGTH , MULTIPLIER 2

The game result is also multiplied by two to give it higher resolution. There are also special values for wins by time etc., either in result or in the score* types, or both :)

TYPE score16

BASE TYPE I16, LENGTH , MULTIPLIER 4

TYPE score32

BASE TYPE I32, LENGTH , MULTIPLIER 4

TYPE score1000

BASE TYPE I32, LENGTH , MULTIPLIER 1000

A score value (used for displaying the score at the end of a game) are multiplied by four for a change (the 0.25 resolution is not used). In game structures it is encoded by dividing by two, though, so watch out! And in some others, it's encoded by multiplying by 1000... yuck!

TYPE time

BASE TYPE U32, LENGTH , MULTIPLIER 1000

Time values are multiplied by 1000, giving them millisecond accuracy.

TYPE timestamp

BASE TYPE U64, LENGTH , MULTIPLIER 1000

64 bit timeval, milliseconds since posix epoch, e.g. my ($year, $month, $day) = (gmtime $date * 0.001)[5,4,3];

TYPE password

BASE TYPE U64, LENGTH , MULTIPLIER

Password is a number calculated as follows (VERY insecure, basically plaintext!): password = 0; for char in characters do password ← password * 1055 + ascii_code (char)

Constants, enumeration and set types used in the protocol.

Baaah... not yet.

Structs used in send & receive messages

STRUCTURE user

CLASS: KGS::User

Everywhere a user + flags is required, even used in some places where only a username is required. I see no general rule on when a complete user and when a partial user is required.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
name	username
flags	U32	1

STRUCTURE rules

CLASS: KGS::Rules

This structure is used for challanges as well as in the special TREE "subprotocol". It tightly encodes the game parameters.

NAME	TYPE	DESCRIPTION
ruleset	U8
size	U8
handicap	U8
komi	komi16
timesys	U8
time	U32
interval	U32	byo-yomi time / canadian time
count	U16	periods / moves

Structs used in send messages

Send messages

SEND MESSAGE login

NUMERIC TYPE (hex): 0000

Sent to login, usually the first message sent. The password needs to be set when the guest flag is true. Possible replies: login(0001) login(0002) login(0003) login(0004) login(0005) login(0006) login(0018) login(0022). Followed by: timewarning_default(001b) chal_defaults(0411)

NAME	TYPE	DEFAULT	DESCRIPTION
ver_major	U32	2
ver_minor	U32	5
ver_micro	U32	1
name	username
password	password	0
guest	flag	1
_unknown3	U16	0
locale	locale	"en_US"
clientver	DATA	"1.4.1_01:Swing app:Sun Microsystems Inc."	The "default" is the java vm version, not exactly he client version. However, you should always send a text like "Jonathan's C client bersion 0.6" or somesuch, so the server can, if necessary, block broken clients or client versions.

SEND MESSAGE req_userinfo

NUMERIC TYPE (hex): 0007

Request info about a certain user. Possible reply: userinfo(0008)

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
name	username

SEND MESSAGE update_userinfo

NUMERIC TYPE (hex): 0007

Update user info. Message structure is very similar to userinfo(0008).

NAME	TYPE	DEFAULT	DESCRIPTION
setpass	flag		Should the password be updated?
password	password	0
realname	realname
email	email
info	userinfo
homepage	url
_unused	U64	0
_unused	U64	0

SEND MESSAGE req_stats

NUMERIC TYPE (hex): 0014

Request server statistics. Replied with stats(0015)

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD

SEND MESSAGE ping

NUMERIC TYPE (hex): 001d

Wild guess, I send it in idle_warn(0016).

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD

SEND MESSAGE req_usergraph

NUMERIC TYPE (hex): 001e

Request user graph data, replied with usergraph(001e).

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
name	username

SEND MESSAGE fetch_memos

NUMERIC TYPE (hex): 001f

Unclear. Fetch all outstanding memos? Replied with memo(001f)

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD

SEND MESSAGE req_pic

NUMERIC TYPE (hex): 0021

Request a user picture from the server. Results in a userpic(0021) or a timeout.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
name	username

SEND MESSAGE upload_pic

NUMERIC TYPE (hex): 0021

Same code as pic_req, but with an additional data section that must contain a JPEG image that is <=7KB. It must have 141×200 pixels.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
name	username
data	DATA

SEND MESSAGE gnotice

NUMERIC TYPE (hex): 0100

Send a global message. Maybe. Never tried, for obvious reasons :/. Results in a gnotice(0100) sent to all users.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
notice	STRING

SEND MESSAGE list_rooms

NUMERIC TYPE (hex): 0318

List the rooms in a specific group/category. Results in a upd_rooms(0318) message.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
group	U8

SEND MESSAGE new_room

NUMERIC TYPE (hex): 031a

Create a new room. Not verified.

NAME	TYPE	DEFAULT	DESCRIPTION
name	username
i1	U32	0
b1	U8	0
b2	U8	255
b3	U8	255
group	U8	1
name	STRING
description	STRING
flags	U8		0x10 .. private room etc.. see code

SEND MESSAGE req_game_record

NUMERIC TYPE (hex): 0413

Requests part of the users game record to be sent. Results in a game_record(0414) or maybe a timeout.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
name	username
timestamp	timestamp		If zero, start at the newest games, else only send games before the given timestap.

SEND MESSAGE join_room

NUMERIC TYPE (hex): 4300

Joins the given room. join_room(4300) messages for yourself and all users in that room, as well as the initial gamelist, are send if the room exists. If not, timeout...

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
user	user

SEND MESSAGE msg_room

NUMERIC TYPE (hex): 4301

Send a message to the room.

NAME	TYPE	DESCRIPTION
channel	U16
name	username	Must be the login-name of the user.
message	STRING

SEND MESSAGE part_room

NUMERIC TYPE (hex): 4302

Remove yourself (or maybe others as admin) from a room.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
name	username

SEND MESSAGE new_game

NUMERIC TYPE (hex): 4305

Unclear. Start a new game.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
id	U16
gametype	U32
rules	rules
notes	STRING

SEND MESSAGE req_games

NUMERIC TYPE (hex): 430b

Request to update room game list (send this once per minute to get updated). Results in upd_games messages.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16

SEND MESSAGE req_desc

NUMERIC TYPE (hex): 4319

Request room description.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16

SEND MESSAGE send_chal

NUMERIC TYPE (hex): 4400

Unclear.

NAME	TYPE	DESCRIPTION
channel	U16
black	username
white	username	More following... TREE or challenge.

SEND MESSAGE join_game

NUMERIC TYPE (hex): 4403

Join a game. See join_room.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
user	user

SEND MESSAGE part_game

NUMERIC TYPE (hex): 4404

Leave (or kick as admin?) a certain user from a game.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
name	username

SEND MESSAGE upd_tree

NUMERIC TYPE (hex): 4406

Upload a partial game tree to the server. This is used to send moves and even in-game comments to the server. For the comments, the server prepends the username and rank.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
tree	TREE

SEND MESSAGE get_tree

NUMERIC TYPE (hex): 4408

Request the game tree starting at a given node. This is used when the server only sends a partial tree (with end code "more").

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
node	U32

SEND MESSAGE claim_win

NUMERIC TYPE (hex): 440c

Unclear.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
_byte	U8		Player colour maybe? Unclear.

SEND MESSAGE add_time

NUMERIC TYPE (hex): 440d

Not checked.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
time	U32
player	U8

SEND MESSAGE grant_undo

NUMERIC TYPE (hex): 440f

Can be send after a req_undo message was received to grant the undo.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16

SEND MESSAGE resign_game

NUMERIC TYPE (hex): 4410

Resign the game.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
player	U8

SEND MESSAGE set_teacher

NUMERIC TYPE (hex): 441a

Change the teacher to somebody else (or possibly yourself == take it).

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
name	username

SEND MESSAGE add_user

NUMERIC TYPE (hex): 4422

Unclear. Maybe allow users to talk? No idea, really.

NAME	TYPE	DESCRIPTION
channel	U16
othername	username
name	username	; # gives user access to the game (to what? ;)

SEND MESSAGE set_privacy

NUMERIC TYPE (hex): 4423

Probably sets the "quiet" flag. Not checked.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
private	U8

SEND MESSAGE reject_chal

NUMERIC TYPE (hex): 4429

Reject a challenge from a given user. Not checked.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
name	username

SEND MESSAGE req_result

NUMERIC TYPE (hex): 4433

I forgot.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16

Structs mainly used in receive messages

STRUCTURE challenge_defaults

Send soon after log-in to set the defaults for game challenges.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
gametype	U32
size	U32
timesys	U32
time	U32
byo_time	U32
byo_periods	U32
can_time	U32
can_stones	U32

STRUCTURE challenge

CLASS: KGS::Challenge

A challenge.

NAME	TYPE	DESCRIPTION
user1	user
user2	user
gametype	U32
rules	rules	Maybe the rules" are in TREE format. I forgot.

STRUCTURE game

CLASS: KGS::Game

Basic information about a game. Used in rooms for the gamelist and in games to detect when a game is saved, changed type (e.g. R => D) etc.

NAME	TYPE	DESCRIPTION	DEC-GUARD
channel	U16
type	U8
user1	user	White
user2	user	Black
user3	user	Owner
size	U8
handicap	I8	< 0 not fully setup
komi	komi16
moves	I16	This field reflects either the movenum or the score, sorry, not even guards help, as the flags to determine that are _after_ the field. Arg. Divide by two to get the actual score (NOT score16!) (arg²).
flags	U16
observers	U32
saved	flag
notes	STRING		handicap < 0

STRUCTURE room_obs

Obsolete.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
name	roomname
channel	U16
flags	U32
users	U32

STRUCTURE room

CLASS: KGS::Room

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
flags	U8
group	U8
users	U16
games	U16
name	STRING

STRUCTURE scorevalues

CLASS: KGS::Score

NAME	TYPE	DESCRIPTION
score	score32
territory	U32
captures	U32
i3	U32
f2	U32
komi	komi324
i4	U32	Apparently the i3, f2, i4 are zero.

STRUCTURE game_record

CLASS: KGS::GameRecord

A single game record entry, as seen in userinfo(0008).

NAME	TYPE	DESCRIPTION
timestamp	timestamp	Time this game was played.
flags	U8	High four bits are handicap, low four bits are gametype (encoded strangely? unclear).
user1	user	White, flags contain low 8 bits of revision (bits 16-23).
user2	user	Black, flags contain high 8 bits of revision (bits 16-23).
user3	user	Owner (or empty)
komi	komi16
score	score16
status	U8	0x80 inprogress

Receive messages

RECV MESSAGE login

NUMERIC TYPE (hex): 0001 (possibly in response to login(0000) )

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
result	CONSTANT	"login ok"
success	CONSTANT	1

RECV MESSAGE login

NUMERIC TYPE (hex): 0002 (possibly in response to login(0000) )

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
result	CONSTANT	"guest login ok"
success	CONSTANT	1

RECV MESSAGE login

NUMERIC TYPE (hex): 0003 (possibly in response to login(0000) )

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
result	CONSTANT	"login error 3"	maybe more following?

RECV MESSAGE login

NUMERIC TYPE (hex): 0004 (possibly in response to login(0000) )

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
result	CONSTANT	"wrong password"	maybe more following?

RECV MESSAGE login

NUMERIC TYPE (hex): 0005 (possibly in response to login(0000) )

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
result	CONSTANT	"user unknown"	maybe more following?

RECV MESSAGE login

NUMERIC TYPE (hex): 0006 (possibly in response to login(0000) )

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
result	CONSTANT	"user exists"	maybe more following?

RECV MESSAGE userinfo

NUMERIC TYPE (hex): 0008 (possibly in response to req_userinfo(0007) )

User info.

NAME	TYPE	DESCRIPTION
user	user
_unused	U64
realname	realname
email	email
info	userinfo
homepage	url
regdate	timestamp	When the user registered (0 == never registered).
lastlogin	timestamp	When the user logged in for the last time.

RECV MESSAGE login

NUMERIC TYPE (hex): 0018 (possibly in response to login(0000) )

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
result	CONSTANT	"login error 18"	maybe more following?

RECV MESSAGE login

NUMERIC TYPE (hex): 0022 (possibly in response to login(0000) )

I was blocked sooo many times for developing this client that it was easy to figure out. The KGS admins sure need no extra nazi training :(

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
reason	STRING
result	CONSTANT	"user or ip blocked"

RECV MESSAGE msg_chat

NUMERIC TYPE (hex): 0013

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
user1	username
user2	username
message	STRING

RECV MESSAGE stats

NUMERIC TYPE (hex): 0015 (possibly in response to req_stats(0014) )

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
ver_major	U16
ver_minor	U16
ver_micro	U16
boot_time	timestamp
users_cur	U32
users_max	U32
users_lim	U32
accts_cur	U32
accts_max	U32
unknown1	U32
work_max	U32
rooms_cur	U32
rooms_max	U32
rooms_lim	U32
games_cur	U32
games_max	U32
games_lim	U32
results_cur	U32
results_max	U32
unknown2	U32
params_cur	U32
params_max	U32
bytes_in	U64
packets_in	U64
bytes_out	U64
packets_out	U64

RECV MESSAGE idle_warn

NUMERIC TYPE (hex): 0016

idle warning, autologout soon (10 minutes...)

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD

RECV MESSAGE timewarning_default

NUMERIC TYPE (hex): 001b (possibly in response to login(0000) )

WILD guess

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
time	U16

RECV MESSAGE idle_err

NUMERIC TYPE (hex): 001c

autologout

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD

RECV MESSAGE ping

NUMERIC TYPE (hex): 001d

Sent by the server regularly, but not answering them isn't valid. Strange form of keepalive?

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD

RECV MESSAGE usergraph

NUMERIC TYPE (hex): 001e (possibly in response to req_usergraph(001e) )

User graph data.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
data	I16		If empty, no graph is available. The unit seems to be centi-kyu, with 1 dan == 0, 2 dan == 100, 1 kyu == -100. There is probably one entry per day, the newest one last.

RECV MESSAGE memo

NUMERIC TYPE (hex): 001f (possibly in response to fetch_memos(001f) )

Unclear. "Leave Message"? 6 strings following.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
s1	STRING
s2	STRING
s3	STRING
s4	STRING
s5	STRING
s6	STRING

RECV MESSAGE userpic

NUMERIC TYPE (hex): 0021 (possibly in response to req_pic(0021) )

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
name	username		Reply to pic_req, contains an image in jpeg format.
data	DATA

RECV MESSAGE gnotice

NUMERIC TYPE (hex): 0100 (possibly in response to gnotice(0100) )

global notice, sent to everybody

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
notice	STRING

RECV MESSAGE upd_user

NUMERIC TYPE (hex): 0202

# maybe soe notify? Totally unclear. # loc 0" type="chat(?) loc 1 => gameinfo?, loc 2 => game result (more data)

NAME	TYPE	DEC-GUARD
location	U32
user	user
lotsofinfo	DATA	location == 2

RECV MESSAGE priv_room

NUMERIC TYPE (hex): 0310

"permission denied" when joining a room

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
name	STRING

RECV MESSAGE upd_rooms

NUMERIC TYPE (hex): 0318 (possibly in response to list_rooms(0318) )

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
rooms	room

RECV MESSAGE chal_defaults

NUMERIC TYPE (hex): 0411 (possibly in response to login(0000) )

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
defaults	challenge_defaults

SEND MESSAGE rej_game

NUMERIC TYPE (hex): 0412

Unable to create challenge. The channel might be optional.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16

RECV MESSAGE game_record

NUMERIC TYPE (hex): 0414 (possibly in response to req_game_record(0413) )

The users game record.

NAME	TYPE	DESCRIPTION
name	username
more	flag	Wether more games are available (must be requested manually)
games	game_record

RECV MESSAGE upd_game2

NUMERIC TYPE (hex): 041c

Unclear.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel_junk	U16
game	game

Room messages

Not all room messages are for rooms only, and rooms need to parse not only these messages. Orthogonality, what for?

RECV MESSAGE join_room

NUMERIC TYPE (hex): 4300 (possibly in response to join_room(4300) )

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
users	user

RECV MESSAGE msg_room

NUMERIC TYPE (hex): 4301

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
name	username
message	STRING

RECV MESSAGE part_room

NUMERIC TYPE (hex): 4302

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
user	user

RECV MESSAGE del_room

NUMERIC TYPE (hex): 4303

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16

RECV MESSAGE upd_games

NUMERIC TYPE (hex): 4304

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
games	game

RECV MESSAGE desc_room

NUMERIC TYPE (hex): 4319

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
owner	username
description	STRING

Game messages

RECV MESSAGE upd_chal

NUMERIC TYPE (hex): 4400

Unclear.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
challenge	challenge

RECV MESSAGE upd_game

NUMERIC TYPE (hex): 4401

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
game	game

RECV MESSAGE del_game

NUMERIC TYPE (hex): 4402

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16

RECV MESSAGE upd_observers

NUMERIC TYPE (hex): 4403

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
users	user

RECV MESSAGE del_observer

NUMERIC TYPE (hex): 4404

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
name	username

RECV MESSAGE set_tree

NUMERIC TYPE (hex): 4405

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
tree	TREE

RECV MESSAGE upd_tree

NUMERIC TYPE (hex): 4406

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
tree	TREE

RECV MESSAGE superko

NUMERIC TYPE (hex): 4409

Superko-warning.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16

RECV MESSAGE final_result

NUMERIC TYPE (hex): 440b

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
blackscore	scorevalues
whitescore	scorevalues

RECV MESSAGE req_undo

NUMERIC TYPE (hex): 440e

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16

RECV MESSAGE resign_game

NUMERIC TYPE (hex): 4410

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
player	U8

RECV MESSAGE set_teacher

NUMERIC TYPE (hex): 441a

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
name	username

RECV MESSAGE owner_left

NUMERIC TYPE (hex): 441d

Unclear.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16

RECV MESSAGE teacher_left

NUMERIC TYPE (hex): 441e

Unclear.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16

RECV MESSAGE unknown4422

NUMERIC TYPE (hex): 4422

change teacher? something to do with editing?

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
name1	username
name2	username

RECV MESSAGE add_tree

NUMERIC TYPE (hex): 4428

See set_tree(4405). In addition, flags the tree as being uploaded completely.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
tree	TREE

RECV MESSAGE req_result

NUMERIC TYPE (hex): 4433

Unclear.

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16		# # recv_result(?)

RECV MESSAGE unknown4434

NUMERIC TYPE (hex): 4434

NAME	TYPE	DEFAULT	DESCRIPTION	DEC-GUARD
channel	U16
b1	U8		?? !demonstration game??