ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/kgsueme/doc/protocol.xml
Revision: 1.44
Committed: Wed Jan 28 17:30:52 2004 UTC (20 years, 4 months ago) by pcg
Content type: text/xml
Branch: MAIN
Changes since 1.43: +16 -4 lines
Log Message:
*** empty log message ***

File Contents

# Content
1 <?xml version="1.0" encoding="utf-8"?>
2 <html>
3 <head>
4 <title>KGS Protocol Description</title>
5 <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
6 <!--
7 Copyright (C) 2003 Marc Lehmannn &lt;pcg@goof.com&gt;
8
9 You can redistribute and/or modify this document under the terms of
10 the GNU General Public License as published by the Free Software
11 Foundation; either version 2 of the License, or (at your option) any
12 later version.
13
14 This document is distributed in the hope that it will be useful,
15 but WITHOUT ANY WARRANTY; without even the implied warranty of
16 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
17 General Public License for more details.
18
19 You should have received a copy of the GNU General Public License
20 along with this program; if not, write to the Free Software
21 Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
22 -->
23 </head>
24 <body>
25
26 <h1>$Revision: 1.43 $</h1>
27
28 <h1>KGS Protocol Description</h1>
29
30 <p>This XML document describes the KGS protocol. It is also used
31 to automatically generate the perl parser for all the messages and
32 structures in the protocol. Adapting it to other languages should be
33 almost trivial.</p>
34
35 <p><b>Please note that wms has told me that he will change the
36 protocol in response to my efforts. No problems with changing the
37 protocol for good, but he does this just to make it more difficult
38 to reverse-engineer it, since his changes are neither required, nor
39 useful (they just make the protocol less robust, without adding added
40 value). He doesn't even care that this locks out some users who cannot
41 upgrade (cgoban2 isn't available for their platform anymore). It hurts
42 to see such a waste of time and efforts that could have been used to
43 fix bugs or improve the client...</b></p>
44
45 <p>If you feel you need to update the visual appearance of this
46 document, feel free to look <tt>doc/doc2html.xsl</tt> and improve
47 it.</p>
48
49 <p>The current version of this document can always be found at
50 <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/kgsueme/kgsueme/doc/protocol.xml?rev=HEAD&amp;content-type=text/xml">here</a>, while
51 the HTML version of it can be found
52 <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/kgsueme/kgsueme/doc/protocol.html?rev=HEAD&amp;content-type=text/html">here</a>.
53 (update: sourceforge is weeks behind on their anonymous cvs servers so the above might be out-of-date. sorry.)</p>
54
55 <h2>Structure and conventions of this document and the protocol</h2>
56
57 <p>"ORIGIN: CLIENT" means messages send from the client to the server,
58 while "ORIGIN: SERVER" means messages send by the server to the
59 client.</p>
60
61 <p>Everything on the wire is in little-endian format (what a shame).</p>
62
63 <p>Primitive types are mostly integers (signed
64 "<code>I</code>&lt;bits&gt;", unsigned "<code>U</code>&lt;bits&gt;"),
65 ascii strings ("<code>username</code>"), or zero-terminated
66 UCS2-Strings ("<code>STRING</code>"). Yes, I know java is supposed to
67 do UTF-16, but no implementation seems to care...</p>
68
69 <p>For the rest, go figure or bug me, <a href="mailto:pcg@goof.com">Marc Lehmann &lt;pcg@goof.com&gt;</a></p>
70
71 <h2>Stream and message structure.</h2>
72
73 <p>After connecting to the server, a handshake byte is sent. It's
74 the major version number of the protocol the client expects to
75 receive. Version 3 and 4 are mostly the same, except that Version 4
76 clients expect server messages to be compressed, version 3 clients
77 not.</p>
78
79 <p>The server sends back his protocol number, which is always 3 in
80 the current protocol. Most of the protocol variation is determined by
81 the server using the client version that is used in the initial login
82 message, not the initial handshake byte.</p>
83
84 <p>After the initial handshake, the client sends uncompressed
85 messages, while the server sends back a zlib-compressed
86 stream (<a href="http://rfc1950.x42.com/">rfc1950</a> and <a
87 href="http://rfc1950.x42.com/">rfc1951</a>).</p>
88
89 <p>All messages have the same header:</p>
90
91 <struct name="message_header">
92 <member name="_unknown" type="U16"/>
93 <member name="length" type="U16"/>
94
95 <p>The length is the length of the full message including the header.</p>
96
97 <p>Beginning with version 2.5.x, a number is xored into the low
98 byte of the length in <em>sent</em> packages only, as given by the
99 following recurrence: <code>rand[0] = 0; rand[i+1] = msg[i].length
100 + (rand[i] * 0x04c2af9b + 0xfffffffb); xorbyte = rand &gt;&gt;
101 24</code>, all in 32 bit unsigned iso-c arithmetic.</p>
102
103 <member name="type" type="U16"/>
104 <p>If the type is &gt;= 0x4000 this is a message for a specific channel. The channel
105 number is always the next U16.</p>
106
107 <p>Beginning with version 2.5.x, a number is <em>added</em> on <em>received</em>
108 messages only. The algorithm is as follows:
109
110 <pre>
111 msglen &lt; 44: type = typefield
112 msglen &gt; 44: type = (typefield + rand[i]) % 0x10000
113 rand[0] = 0
114 rand[i+1] = username[type % length username] + rand[i] * (type - 0x6cdd)
115 where username is the user name of the logged-in user. coooool.
116 </pre>
117 </p>
118
119 </struct>
120
121 <h2>Primitive types used in the protocol.</h2>
122
123 <p>Apart from the basic types, I need to define some extra types to
124 deal with fixed-point values (based on integer types) or fixed-length
125 strings (either 7-bit-ascii or more limited (<code>A</code>), or UCS-2
126 based (<code>S</code>)).</p>
127
128 <type name="username" type="A" length="10"/>
129
130 <p>The basic user or login name, used throughout the protocol
131 as a handle to the user.</p>
132
133 <type name="roomname" type="S" length="25"/><!-- argh, how horribly broken -->
134
135 <p>Many strings in the protocol are fixed-width for no good reason
136 (maybe this is one reason for using compression in newer versions, as
137 the packets itself are wasting lots of space.</p>
138
139 <type name="realname" type="S" length="50"/>
140 <type name="email" type="S" length="70"/>
141 <type name="userinfo" type="S" length="1000"/>
142 <type name="url" type="A" length="100"/>
143
144 <p>Used in user_record.</p>
145
146 <type name="locale" type="A" length="5"/>
147
148 <p>A kind of locale specifier. It seems the general format seems to be
149 lowercase language, underscore, uppercase location, e.g. en_US. More
150 fancy specifications don't fit.</p>
151
152 <type name="flag" type="U8" multiplier="1"/>
153
154 <p>Just a simple boolean value. 0 means false, and 1 generally true,
155 but I suggest accepting != 0 as true.</p>
156
157 <type name="komi16" type="I16" multiplier="2"/>
158 <type name="komi32" type="I32" multiplier="2"/>
159 <type name="komi324" type="I32" multiplier="4"/>
160
161 <p>Komi values are multiplied by 2 to make them integer in the
162 protocol. Well, *most* of the time at least...</p>
163
164 <type name="result" type="I32" multiplier="2"/>
165
166 <p>The game result is also multiplied by two to give it higher
167 resolution. There are also special values for wins by time etc., either
168 in result or in the score* types, or both :)</p>
169
170 <type name="score16" type="I16" multiplier="4"/>
171 <type name="score32" type="I32" multiplier="4"/>
172 <type name="score1000" type="I32" multiplier="1000"/>
173
174 <p>A score value (used for displaying the score at the end of a game)
175 are multiplied by four for a change (the 0.25 resolution is not
176 used). In game structures it is encoded by dividing by two, though, so
177 watch out! And in some others, it's encoded by multiplying by 1000...
178 yuck!</p>
179
180 <type name="time" type="U32" multiplier="1000"/>
181
182 <p>Time values are multiplied by 1000, giving them millisecond
183 accuracy.</p>
184
185 <type name="timestamp" type="U64" multiplier="1000"/>
186
187 <p>64 bit timeval, milliseconds since posix epoch, e.g. <code>my
188 ($year, $month, $day) = (gmtime $date * 0.001)[5,4,3];</code></p>
189
190 <type name="password" type="U64"/>
191
192 <p>Password is a number calculated as follows (VERY insecure, basically
193 plaintext!): <code>password = 0; for char in characters do password ←
194 password * 1055 + ascii_code (char)</code></p>
195
196 <h2>Enumeration and set types used in the protocol.</h2>
197
198 <enum name="GAMETYPE">
199 <member name="DEMONSTRATION" value="0"/>
200 <member name="TEACHING" value="1"/>
201 <member name="FREE" value="2"/>
202 <member name="RATED" value="3"/>
203 <member name="TYPE4" value="4"/>
204 Probably not used, but the protocol has space for it it seems.
205 </enum>
206
207 <enum name="GAMEOPT">
208 <member name="NONE" value="0"/>
209 <member name="LECTURE" value="1"/>
210 <member name="PRIVATE" value="2"/>
211 <member name="SIMUL" value="3"/>
212 </enum>
213
214 <set name="GAMEFLAG">
215 <member name="SCORED" value="1"/>
216 <member name="ADJOURNED" value="2"/>
217 <member name="UPLOADED" value="4"/>
218 </set>
219
220 <set name="ROOMFLAG">
221 <member name="ADMIN" value="0x01"/>
222 <p>Admins only(?)</p>
223 <member name="DEFAULT" value="0x04"/>
224 <p>Seems to be set on the english room. Or maybe not.</p>
225 <member name="PRIVATE" value="0x10"/>
226 <p>This room is private.</p>
227 </set>
228
229 <set name="GAMESTATUS">
230 <member name="INPLAY" value="0x80"/>
231 </set>
232
233 <enum name="SCORE">
234 <p>Special score values, in addition to numerical scores. Some are also used with their
235 negative value.</p>
236
237 <member name="TIMEOUT" value="16384 / 4"/>
238 Also used negatively to score for white instead of black.
239
240 <member name="RESIGN" value="16385 / 4"/>
241 Also used negatively to score for white instead of black.
242
243 <member name="FORFEIT" value=" 0 / 4"/>
244 Also used negatively to score for white instead of black.
245
246 <member name="JIGO" value="16386 / 4"/>
247
248 <member name="NO_RESULT" value="16386 / 4"/>
249 <member name="ADJOURNED" value="16387 / 4"/>
250 <member name="UNKNOWN" value="16389 / 4"/>
251 </enum>
252
253 <enum name="RULESET">
254 <member name="JAPANESE" value="0"/>
255 <member name="CHINESE " value="1"/>
256 <member name="AGA" value="2"/>
257 <member name="NEW_ZEALAND" value="3"/>
258 </enum>
259
260 <enum name="TIMESYS">
261 <member name="NONE" value="0"/>
262 <member name="ABSOLUTE" value="1"/>
263 <member name="BYO_YOMI" value="2"/>
264 <member name="CANADIAN" value="3"/>
265 </enum>
266
267 <enum name="COLOUR">
268 <p>Convinience constants used in several places.</p>
269 <member name="BLACK" value="0"/>
270 <member name="WHITE" value="1"/>
271 </enum>
272
273 <h2>Structs used in send &amp; receive messages</h2>
274
275 <struct name="user" class="KGS::User">
276
277 <p>Almost everywhere a user + flags is required, even used in some places
278 where only a username is required. I see no general rule on when a
279 complete user and when a partial user is required.</p>
280
281 <member name="name" type="username"/>
282 <member name="flags" type="U32" value="1"/>
283 </struct>
284
285 <struct name="rules" class="KGS::Rules">
286
287 <p>This structure is used for challanges as well as in the special
288 TREE "subprotocol". It tightly encodes the game parameters.</p>
289
290 <member name="ruleset" type="U8"/>
291 <member name="size" type="U8"/>
292 <member name="handicap" type="U8"/>
293 <member name="komi" type="komi16"/>
294 <member name="timesys" type="U8"/>
295 <member name="time" type="U32"/>
296 <member name="interval" type="U32"/>
297 byo-yomi time / canadian time
298 <member name="count" type="U16"/>
299 periods / moves
300 </struct>
301
302 <h2>Structs used in messages from the client</h2>
303
304 <h2>Client-generated messages</h2>
305
306 <message type="0000" name="login" src="client">
307
308 <p>Sent to login, usually the first message sent. The password needs to be set when the
309 guest flag is true.
310 Possible replies: <ref reply="login"/>. Followed by: <ref reply="timewarning_default"/> <ref reply="chal_defaults"/>
311 </p>
312
313 <member name="ver_major" type="U32" value="2"/>
314 <member name="ver_minor" type="U32" value="5"/>
315 <member name="ver_micro" type="U32" value="2"/>
316 <member name="name" type="username"/>
317 <member name="password" type="password" value="0"/>
318 <member name="guest" type="flag" value="1"/>
319 <member name="_unknown3" type="U16" value="0"/>
320 <member name="locale" type="locale" value='"en_US"'/>
321 <member name="clientver" type="DATA" value='"1.4.1_01:Swing app:Sun Microsystems Inc."'/>
322 The "default" is the java vm version, not exactly he client version. However,
323 you should always send a text like "Jonathan's C client bersion 0.6" or somesuch,
324 so the server can, if necessary, block broken clients or client versions.
325 </message>
326
327 <message type="0007" name="req_userinfo" src="client">
328 <p>Request info about a certain user. Possible reply: <ref reply="userinfo"/></p>
329 <member name="name" type="username"/>
330 </message>
331
332 <message type="0007" name="req_userinfo" src="client">
333 <p>Request userinfo(?). unverified...</p>
334 <member name="name" type="username"/>
335 </message>
336
337 <message type="0007" name="update_userinfo" src="client">
338 <p>Update user info. Message structure is very similar
339 to <ref ref="userinfo"/>.</p>
340 <member name="setpass" type="flag"/>
341 Should the password be updated?
342 <member name="password" type="password" value="0"/>
343 <member name="realname" type="realname"/>
344 <member name="email" type="email"/>
345 <member name="info" type="userinfo"/>
346 <member name="homepage" type="url"/>
347 <member name="_unused" type="U64" value="0"/>
348 <member name="_unused" type="U64" value="0"/>
349 </message>
350
351 <message type="0013" name="msg_chat" src="client">
352 <p>This message is sent to initiate or continue a private chat with
353 a user. You'll always receive a copy of what you have sent back
354 from the server (as usual).</p>
355
356 <member name="name" type="username"/>
357 Name of sender ("yourself").
358 <member name="name2" type="username"/>
359 Name of recipient.
360 <member name="message" type="STRING"/>
361 The message.
362 </message>
363
364 <message type="0014" name="req_stats" src="client">
365 <p>Request server statistics. Replied with <ref reply="stats"/></p>
366 </message>
367
368 <message type="0016" name="idle_reset" src="client">
369 <p>Send in response to <ref reply="idle_warn"/> to keep the server from disconnecting.</p>
370 </message>
371
372 <message type="001d" name="ping" src="client">
373 <p>Wild guess, I send it in <ref ref="idle_warn"/>.</p>
374 </message>
375
376 <message type="001e" name="req_usergraph" src="client">
377 <p>Request user graph data, replied with <ref reply="usergraph"/>.</p>
378 <member name="name" type="username"/>
379 </message>
380
381 <message type="001f" name="fetch_memos" src="client">
382 <p>Unclear. Fetch all outstanding memos? Replied with <ref reply="memo"/></p>
383 </message>
384
385 <message type="0021" name="req_pic" src="client">
386 <p>Request a user picture from the server. Results in a <ref reply="userpic"/>
387 or a timeout.</p>
388 <member name="name" type="username"/>
389 </message>
390
391 <message type="0021" name="upload_pic" src="client">
392 Same code as pic_req, but with an additional data section that
393 must contain a JPEG image that is &lt;=7KB. It must have 141×200 pixels.
394 <member name="name" type="username"/>
395 <member name="data" type="DATA"/>
396 </message>
397
398 <message type="0023" name="send_memo" src="client">
399 <member name="name" type="username"/>
400 <member name="msg" type="STRING"/>
401 </message>
402
403 <message type="0100" name="gnotice" src="client">
404 <p>Send a global message. Maybe. Never tried, for obvious reasons :/. Results
405 in a <ref reply="gnotice"/> sent to all users.</p>
406 <member name="notice" type="STRING"/>
407 </message>
408
409 <message type="0200" name="notify_add" src="client">
410
411 <p>Probably setting a notifier on a username, to get informed about
412 changes using <ref reply="notify_upd"/> messages. sending your own
413 username gives you a disconnect, so don't do that at home, kids!</p>
414
415 <member name="name" type="username"/>
416 </message>
417
418 <message type="0201" name="notify_del" src="client">
419
420 <p>Probably remove the notifier again.</p>
421
422 <member name="name" type="username"/>
423 </message>
424
425 <message type="0318" name="list_rooms" src="client">
426 <p>List the rooms in a specific group/category. Results in a <ref reply="upd_rooms"/> message.</p>
427 <member name="group" type="U8"/>
428 </message>
429
430 <message type="031a" name="new_room" src="client">
431 Create a new room. Not verified.
432 <member name="name" type="username"/>
433 <member name="i1" type="U32" value="0"/>
434 <member name="b1" type="U8" value="0"/>
435 <member name="b2" type="U8" value="255"/>
436 <member name="b3" type="U8" value="255"/>
437 <member name="group" type="U8" value="1"/>
438 <member name="name" type="STRING"/>
439 <member name="description" type="STRING"/>
440 <member name="flags" type="U8"/>
441 See ROOMFLAGs
442 </message>
443
444 <message type="0413" name="req_game_record" src="client">
445 <p>Requests part of the users game record to be sent. Results in a <ref reply="game_record"/> or maybe a timeout.</p>
446 <member name="name" type="username"/>
447 <member name="timestamp" type="timestamp"/>
448 If zero, start at the newest games, else only send games
449 before the given timestap.
450 </message>
451
452 <message type="4300" name="join_room" src="client">
453 <p>Joins the given room. <ref reply="join_room"/> messages for yourself
454 and all users in that room, as well as the initial gamelist, are
455 send if the room exists. If not, timeout...</p>
456 <member name="channel" type="U16"/>
457 <member name="user" type="user"/>
458 </message>
459
460 <message type="4301" name="msg_room" src="client">
461 Send a message to the room.
462 <member name="channel" type="U16"/>
463 <member name="name" type="username"/>
464 Must be the login-name of the user.
465 <member name="message" type="STRING"/>
466 </message>
467
468 <message type="4302" name="part_room" src="client">
469 Remove yourself (or maybe others as admin) from a room.
470 <member name="channel" type="U16"/>
471 <member name="name" type="username"/>
472 </message>
473
474 <message type="4305" name="new_game" src="client">
475 <p>Unclear. Start a new game.
476 <p>Clone: 00000: 20202020 20202020 20202020 20203238 28
477 00010: 9d000543 0d000000 00000000 00130201 ...C............
478 00020: 0000ffff ffffffff ffffffff 00000000 ..ÿÿÿÿÿÿÿÿÿÿ....</p>
479 </p>
480
481 <member name="channel" type="U16"/>
482 <p>The room where to start the new game</p>
483 <member name="id" type="U16"/>
484 <member name="gametype" type="U32"/>
485 <member name="rules" type="rules"/>
486 <p>When cloning a game, the rules are set up like this:
487 count => 65535, ruleset => 0, time => 4294967295, timesys => 0, interval => 4294967295.
488 Cloning itself seems to be implemented solely in the client (somewhat sane, for a change).
489 </p>
490 <member name="notes" type="STRING"/>
491 </message>
492
493 <message type="430a" name="load_game" src="client">
494 Load an existing game into a room(?)
495 There is no indication that a new game is there except
496 for a upd_observers message with your name in it. Which means
497 you have to watch upd_observers messages that are not for any
498 currently open game and open one. Ugh.
499 <member name="channel" type="U16"/>
500 The room to load the game into.
501 <member name="timestamp" type="timestamp"/>
502 From the game record.
503 <member name="user" type="username"/>
504 <member name="flags" type="U8"/>
505 0 == public, 2 == private
506 </message>
507
508 <message type="430b" name="req_games" src="client">
509 Request to update room game list (send this once per minute to get
510 updated). Results in upd_games messages.
511 <member name="channel" type="U16"/>
512 </message>
513
514 <message type="4319" name="req_desc" src="client">
515 Request room description.
516 <member name="channel" type="U16"/>
517 </message>
518
519 <message type="4400" name="send_challenge" src="client">
520 Unclear.
521 <member name="channel" type="U16"/>
522 <member name="black" type="username"/>
523 <member name="white" type="username"/>
524 More following... TREE or challenge.
525 </message>
526
527 <message type="4403" name="join_game" src="client">
528 Join a game. See join_room.
529 <member name="channel" type="U16"/>
530 <member name="user" type="user"/>
531 </message>
532
533 <message type="4404" name="part_game" src="client">
534 Leave (or kick as admin?) a certain user from a game.
535 <member name="channel" type="U16"/>
536 <member name="name" type="username"/>
537 </message>
538
539 <message type="4405" name="set_tree" src="client">
540 Possibly upload an initial game to an empty room. Not tested.
541
542 <member name="channel" type="U16"/>
543 <member name="tree" type="TREE"/>
544 </message>
545
546 <message type="4406" name="upd_tree" src="client">
547 Upload a partial game tree to the server. This is used to send moves
548 and even in-game comments to the server. For the comments, the
549 server prepends the username and rank.
550
551 <member name="channel" type="U16"/>
552 <member name="tree" type="TREE"/>
553 </message>
554
555 <message type="4408" name="get_tree" src="client">
556 Request the game tree starting at a given node. This is used
557 when the server only sends a partial tree (with end code "more").
558 <member name="channel" type="U16"/>
559 <member name="node" type="U32"/>
560 </message>
561
562 <message type="440c" name="claim_win" src="client">
563 Unclear.
564 <member name="channel" type="U16"/>
565 <member name="_byte" type="U8 "/>
566 Player colour maybe? Unclear.
567 </message>
568
569 <message type="440d" name="add_time" src="client">
570 Not checked.
571
572 <member name="channel" type="U16"/>
573 <member name="time" type="U32"/>
574 <member name="player" type="U8"/>
575 </message>
576
577 <message type="440f" name="grant_undo" src="client">
578 Can be send after a req_undo message was received to grant the undo.
579 <member name="channel" type="U16"/>
580 </message>
581
582 <message type="4410" name="resign_game" src="client">
583 Resign the game.
584 <member name="channel" type="U16"/>
585 <member name="player" type="U8"/>
586 </message>
587
588 <message type="441a" name="set_teacher" src="client">
589 Change the teacher to somebody else (or possibly yourself == take it).
590 <member name="channel" type="U16"/>
591 <member name="name" type="username"/>
592 </message>
593
594 <message type="4422" name="allow_user" src="client">
595 Unclear. Maybe allow users to talk? No idea, really.
596
597 <member name="channel" type="U16"/>
598 <member name="othername" type="username"/>
599 <member name="name" type="username"/>; # gives user access to the game (to what? ;)
600 </message>
601
602 <message type="4423" name="set_privacy" src="client">
603 Probably sets the "quiet" flag. Not checked.
604 <member name="channel" type="U16"/>
605 <member name="private" type="U8"/>
606 </message>
607
608 <message type="4429" name="reject_challenge" src="client">
609 Reject a challenge from a given user. Not checked.
610
611 <member name="channel" type="U16"/>
612 <member name="name" type="username"/>
613 </message>
614
615 <message type="4433" name="req_result" src="client">
616 I forgot.
617
618 <member name="channel" type="U16"/>
619 </message>
620
621 <message type="4436" name="msg_game" src="client">
622 <member name="channel" type="U16"/>
623 <member name="message" type="STRING"/>
624 </message>
625
626 <message type="ffff" name="quit" src="client">
627 <p>Sent by the client just before it logs out.</p>
628 </message>
629
630 <h2>Structs mainly used in messages send by the server</h2>
631
632 <struct name="challenge_defaults">
633 Send soon after log-in to set the defaults for game challenges.
634 <member name="gametype" type="U32"/>
635 <member name="size" type="U32"/>
636 <member name="timesys" type="U32"/>
637 <member name="time" type="U32"/>
638 <member name="byo_time" type="U32"/>
639 <member name="byo_periods" type="U32"/>
640 <member name="can_time" type="U32"/>
641 <member name="can_stones" type="U32"/>
642 </struct>
643
644 <struct name="challenge" class="KGS::Challenge">
645 A challenge.
646
647 <member name="user1" type="user"/>
648 <member name="user2" type="user"/>
649 <member name="gametype" type="U32"/>
650 <member name="rules" type="rules"/>
651 Maybe the rules" are in TREE format. I forgot.
652 </struct>
653
654 <struct name="game" class="KGS::Game">
655 Basic information about a game. Used in rooms for the gamelist and
656 in games to detect when a game is saved, changed type (e.g. R => D)
657 etc.
658
659 <member name="channel" type="U16"/>
660 <member name="type" type="U8"/>
661 <member name="user1" type="user"/>
662 White
663 <member name="user2" type="user"/>
664 Black
665 <member name="user3" type="user"/>
666 Owner
667 <member name="size" type="U8"/>
668 <member name="handicap" type="I8"/>
669 &lt; 0 not fully setup
670 <member name="komi" type="komi16"/>
671 <member name="moves" type="I16"/>
672 This field reflects either the movenum or the score, sorry, not even guards help, as
673 the flags to determine that are _after_ the field. Arg. Divide by two to get the actual
674 score (NOT score16!) (arg²).
675 <member name="flags" type="U16"/>
676 <member name="observers" type="U32"/>
677 <member name="saved" type="flag"/>
678 <member name="notes" type="STRING" guard-member="handicap" guard-cond="&lt; 0"/>
679 </struct>
680
681 <struct name="room_obs">
682 Obsolete.
683
684 <member name="name" type="roomname"/>
685 <member name="channel" type="U16"/>
686 <member name="flags" type="U32"/>
687 <member name="users" type="U32"/>
688 </struct>
689
690 <struct name="room" class="KGS::Room">
691 <member name="channel" type="U16"/>
692 <member name="flags" type="U8"/>
693 <member name="group" type="U8"/>
694 <member name="users" type="U16"/>
695 <member name="games" type="U16"/>
696 <member name="name" type="STRING"/>
697 </struct>
698
699 <struct name="scorevalues" class="KGS::Score">
700 <member name="score" type="score32"/>
701 <member name="territory" type="U32"/>
702 <member name="captures" type="U32"/>
703 <member name="i3" type="U32"/>
704 <member name="f2" type="U32"/>
705 <member name="komi" type="komi324"/>
706 <member name="i4" type="U32"/>
707 Apparently the i3, f2, i4 are zero.
708 </struct>
709
710 <struct name="game_record" class="KGS::GameRecord">
711 <p>A single game record entry, as seen in <ref ref="userinfo"/>.</p>
712
713 <member name="timestamp" type="timestamp"/>
714 Time this game was played.
715 <member name="flags1" type="U8"/>
716 <p>0:3 == handicap, 4:7 == gametype:0:4</p>
717 <member name="user1" type="user"/>
718 White, flags contain low 8 bits of revision (bits 16-23).
719 <member name="user2" type="user"/>
720 Black, flags contain high 8 bits of revision (bits 16-23).
721 <member name="user3" type="user"/>
722
723 <p><p>Owner (or empty)</p>
724
725 <p>The bits 16-24 of user1.flags and user2.flags give the high and
726 low bits of a revision number in case there are multiple similar
727 games.</p></p>
728
729 <member name="flags2" type="U16"/>
730 <p>0:11 == komi / 2, 12:14 == high 3 bits of gametype, 15: == sign bit</p>
731 <member name="score" type="score16"/>
732 <member name="flags3" type="U8"/>
733
734 <p>0:5 == boardsize; 6: == no idea; 7: == inplay?</p>
735
736 </struct>
737
738 <h2>Server-generated messages</h2>
739
740 <message type="0001" name="login" src="server">
741 <member name="message" type="CONSTANT" value='login successful'/>
742 <member name="success" type="CONSTANT" value="1"/>
743 </message>
744
745 <message type="0002" name="login" src="server">
746 <member name="message" type="CONSTANT" value='login successful: client version is outdated.'/>
747 <member name="success" type="CONSTANT" value="1"/>
748 </message>
749
750 <message type="0003" name="login" src="server">
751 <member name="message" type="CONSTANT" value='login failed: client version out of date'/>
752 ** maybe more following? **
753 </message>
754
755 <message type="0004" name="login" src="server">
756 <member name="message" type="CONSTANT" value='login failed: wrong password'/>
757 ** maybe more following? **
758 </message>
759
760 <message type="0005" name="login" src="server">
761 <member name="message" type="CONSTANT" value='login failed: specified user does not exist'/>
762 </message>
763
764 <message type="0006" name="login" src="server">
765 <member name="message" type="CONSTANT" value='login failed: registered user of same name exists'/>
766 </message>
767
768 <message type="0008" name="userinfo" src="server">
769 User info.
770 <member name="_unused0" type="flag"/>
771 <member name="user" type="user"/>
772 <member name="_unused1" type="U64"/>
773 <member name="realname" type="realname"/>
774 <member name="email" type="email"/>
775 <member name="info" type="userinfo"/>
776 <member name="homepage" type="url"/>
777 <member name="regdate" type="timestamp"/>
778 When the user registered (0 == never registered).
779 <member name="lastlogin" type="timestamp"/>
780 When the user logged in for the last time.
781 <!-- maybe more? -->
782 </message>
783
784 <message type="0009" name="upd_userinfo_result" src="server">
785 <member name="name" type="username"/>
786 <member name="message" type="CONSTANT" value='Thanks for registering.'/>
787 </message>
788
789 <message type="000a" name="upd_userinfo_result" src="server">
790 <member name="name" type="username"/>
791 <member name="message" type="CONSTANT" value='The user &quot;%s&quot; has been successfully updated.'/>
792 </message>
793
794 <message type="000b" name="upd_userinfo_result" src="server">
795 <member name="name" type="username"/>
796 <member name="message" type="CONSTANT" value='There is no user &quot;%s&quot;. Update failed.'/>
797 </message>
798
799 <message type="0012" name="userinfo_failed" src="server">
800 <p>Sent when no userinfo for the requested user could be found(?)</p>
801 <member name="name" type="username"/>
802 </message>
803
804 <message type="0013" name="msg_chat" src="server">
805 <member name="name" type="username"/>
806 Name of sender (either yourself (echo) or other)
807 <member name="name2" type="username"/>
808 Name of recipient.
809 <member name="message" type="STRING"/>
810 </message>
811
812 <message type="0015" name="stats" src="server">
813 <member name="ver_major" type="U16"/>
814 <member name="ver_minor" type="U16"/>
815 <member name="ver_micro" type="U16"/>
816 <member name="boot_time" type="timestamp"/>
817 <member name="users_cur" type="U32"/>
818 <member name="users_max" type="U32"/>
819 <member name="users_lim" type="U32"/>
820 <member name="accts_cur" type="U32"/>
821 <member name="accts_max" type="U32"/>
822 <member name="unknown1" type="U32"/>
823 <member name="work_max" type="U32"/>
824 <member name="rooms_cur" type="U32"/>
825 <member name="rooms_max" type="U32"/>
826 <member name="rooms_lim" type="U32"/>
827 <member name="games_cur" type="U32"/>
828 <member name="games_max" type="U32"/>
829 <member name="games_lim" type="U32"/>
830 <member name="results_cur" type="U32"/>
831 <member name="results_max" type="U32"/>
832 <member name="unknown2" type="U32"/>
833 <member name="params_cur" type="U32"/>
834 <member name="params_max" type="U32"/>
835 <member name="bytes_in" type="U64"/>
836 <member name="packets_in" type="U64"/>
837 <member name="bytes_out" type="U64"/>
838 <member name="packets_out" type="U64"/>
839 </message>
840
841 <message type="0016" name="idle_warn" src="server">
842 idle warning, autologout soon (10 minutes...)
843 </message>
844
845 <message type="0018" name="login" src="server">
846 <member name="message" type="CONSTANT" value='logged out: another client logged in with your username'/>
847 </message>
848
849 <message type="001c" name="login" src="server">
850 <member name="message" type="CONSTANT" value='logged out: idle for too long'/>
851 </message>
852
853 <message type="0020" name="error" src="server">
854 <member name="message" type="CONSTANT" value='Sorry, you have too many unfinished games. You cannot turn on your rank. Please finish some of your games, then try again.'/>
855 </message>
856
857 <message type="0022" name="login" src="server">
858 I was blocked sooo many times for developing this client that it was
859 easy to figure out. The KGS admins sure need no extra nazi training
860 :(
861 <member name="reason" type="STRING"/>
862 <member name="result" type="CONSTANT" value='user or ip blocked'/>
863 </message>
864
865 <message type="001b" name="timewarning_default" src="server">
866 WILD guess
867 <member name="channel" type="U16"/>
868 <member name="time" type="U16"/>
869 </message>
870
871 <message type="001c" name="idle_err" src="server">
872 autologout
873 </message>
874
875 <message type="001d" name="ping" src="server">
876 Sent by the server regularly, but not answering them
877 isn't valid. Strange form of keepalive?
878 </message>
879
880 <message type="001e" name="usergraph" src="server">
881 User graph data.
882 <member name="name" type="username"/>
883 <member name="data" type="I16" array="yes"/>
884 If empty, no graph is available. The unit seems to
885 be centi-kyu, with 1 dan == 0, 2 dan == 100, 1 kyu == -100.
886 There is probably one entry per day, the newest one last.
887 </message>
888
889 <message type="001f" name="memo" src="server">
890 Unclear. "Leave Message"?
891 6 strings following.
892 <member name="s1" type="STRING"/>
893 <member name="s2" type="STRING"/>
894 <member name="s3" type="STRING"/>
895 <member name="s4" type="STRING"/>
896 <member name="s5" type="STRING"/>
897 <member name="s6" type="STRING"/>
898 </message>
899
900 <message type="0021" name="userpic" src="server">
901 <member name="name" type="username"/>
902 Reply to pic_req, contains an image in jpeg format.
903 <member name="data" type="DATA"/>
904 </message>
905
906 <message type="0100" name="gnotice" src="server">
907 global notice, sent to everybody
908 <member name="notice" type="STRING"/>
909 </message>
910
911 <message type="0202" name="notify_event" src="server">
912 # maybe soe notify? Totally unclear.
913 # loc 0" type="userinfo, flags etc. loc 1 => gameinfo?, loc 2 => game result (more data)
914 <member name="event" type="U32"/>
915 <member name="user" type="user"/>
916 <member name="gamerecord" type="game_record" guard-member="event" guard-cond="== 2"/>
917 <p>Game result record?</p>
918
919 </message>
920
921 <message type="0310" name="priv_room" src="server">
922 "permission denied" when joining a room
923 <member name="name" type="STRING"/>
924 </message>
925
926 <message type="0318" name="upd_rooms" src="server">
927 <member name="rooms" type="room" array="yes"/>
928 </message>
929
930 <message type="0411" name="chal_defaults" src="server">
931 <member name="channel" type="U16"/>
932 <member name="defaults" type="challenge_defaults"/>
933 </message>
934
935 <message type="0412" name="game_error" src="server">
936 Unable to create challenge. The channel is be optional.
937 <member name="message" type="CONSTANT" value='Sorry, you are already playing in one game, so you can&apos;t start playing in another.'/>
938 <member name="channel" type="U16"/>
939 </message>
940
941 <message type="0414" name="game_record" src="server">
942 The users game record.
943 <member name="name" type="username"/>
944 <member name="more" type="flag"/>
945 Wether more games are available (must be requested manually)
946 <member name="games" type="game_record" array="yes"/>
947 </message>
948
949 <message type="0417" name="error" src="server">
950 <member name="message" type="CONSTANT" value='Sorry, your opponent is currently not logged in, so you can&apos;t resume this game.'/>
951 </message>
952
953 <message type="0418" name="error" src="server">
954 <member name="message" type="CONSTANT" value='Sorry, your opponent is already playing in a game, so you cannot continue this one.'/>
955 </message>
956
957 <message type="0419" name="error" src="server">
958 <member name="message" type="CONSTANT" value='Sorry, the server is out of boards! Please wait a few minutes and try to start a game again.'/>
959 </message>
960
961 <message type="041c" name="upd_game2" src="server">
962 Unclear.
963 <member name="channel_junk" type="U16"/>
964 <member name="game" type="game"/>
965 </message>
966
967 <message type="041f" name="error" src="server">
968 <member name="message" type="CONSTANT" value='Sorry, the game you tried to load was not correctly saved...probably caused by the server crashing. It cannot be recovered.'/>
969 </message>
970
971 <message type="0420" name="error" src="server">
972 <member name="message" type="CONSTANT" value='Sorry, user &quot;%s&quot; has left the game you are starting before you could challenge them. You will have to play against somebody else.'/>
973 </message>
974
975 <message type="0421" name="error" src="server">
976 <member name="message" type="CONSTANT" value='Sorry, this game is a private lesson. You will not be allowed to observe it.'/>
977 </message>
978
979 <!-- added recently -->
980 <message type="043a" name="unknown_43b" src="server">
981 Probably updates the open games list? The format is just a VERY VERY WILD GUESS.
982
983 The first channel is probably a game id.
984
985 <member name="channel" type="U16"/>
986 <member name="game" type="game"/>
987 </message>
988
989 <h3>Room messages</h3>
990
991 <p>Not all room messages are for rooms only, and rooms need to parse
992 not only these messages. Orthogonality, what for?</p>
993
994 <message type="4300" name="join_room" src="server">
995 <member name="channel" type="U16"/>
996 <member name="users" type="user" array="yes"/>
997 </message>
998
999 <message type="4301" name="msg_room" src="server">
1000 <member name="channel" type="U16"/>
1001 <member name="name" type="username"/>
1002 <member name="message" type="STRING"/>
1003 </message>
1004
1005 <message type="4302" name="part_room" src="server">
1006 <member name="channel" type="U16"/>
1007 <member name="user" type="user"/>
1008 </message>
1009
1010 <message type="4303" name="del_room" src="server">
1011 <member name="channel" type="U16"/>
1012 </message>
1013
1014 <message type="4304" name="upd_games" src="server">
1015 <member name="channel" type="U16"/>
1016 <member name="games" type="game" array="yes"/>
1017 </message>
1018
1019 <message type="4319" name="desc_room" src="server">
1020 <member name="channel" type="U16"/>
1021 <member name="owner" type="username"/>
1022 <member name="description" type="STRING"/>
1023 </message>
1024
1025 <h3>Game messages</h3>
1026
1027 <message type="4400" name="upd_challenge" src="server">
1028 Unclear.
1029 <member name="channel" type="U16"/>
1030 <member name="challenge" type="challenge"/>
1031 </message>
1032
1033 <message type="4401" name="upd_game" src="server">
1034 <member name="channel" type="U16"/>
1035 <member name="game" type="game"/>
1036 </message>
1037
1038 <message type="4402" name="del_game" src="server">
1039 <member name="channel" type="U16"/>
1040 </message>
1041
1042 <message type="4403" name="upd_observers" src="server">
1043 <member name="channel" type="U16"/>
1044 <member name="users" type="user" array="yes"/>
1045 </message>
1046
1047 <message type="4404" name="del_observer" src="server">
1048 <member name="channel" type="U16"/>
1049 <member name="name" type="username"/>
1050 </message>
1051
1052 <message type="4405" name="set_tree" src="server">
1053 <member name="channel" type="U16"/>
1054 <member name="tree" type="TREE"/>
1055 </message>
1056
1057 <message type="4406" name="upd_tree" src="server">
1058 <member name="channel" type="U16"/>
1059 <member name="tree" type="TREE"/>
1060 </message>
1061
1062 <message type="4409" name="superko" src="server">
1063 Superko-warning.
1064 <member name="channel" type="U16"/>
1065 </message>
1066
1067 <message type="440b" name="final_result" src="server">
1068 <member name="channel" type="U16"/>
1069 <member name="blackscore" type="scorevalues"/>
1070 <member name="whitescore" type="scorevalues"/>
1071 </message>
1072
1073 <message type="440e" name="req_undo" src="server">
1074 <member name="channel" type="U16"/>
1075
1076 </message>
1077
1078 <message type="4410" name="resign_game" src="server">
1079 <member name="channel" type="U16"/>
1080 <member name="player" type="U8"/>
1081 </message>
1082
1083 <message type="4415" name="game_error" src="server">
1084 <member name="channel" type="U16"/>
1085 <member name="message" type="CONSTANT" value='Sorry, this is a lecture game. Only authorized players are allowed to make comments.'/>
1086 </message>
1087
1088 <message type="441a" name="set_teacher" src="server">
1089 <member name="channel" type="U16"/>
1090 <member name="name" type="username"/>
1091 </message>
1092
1093 <message type="441d" name="owner_left" src="server">
1094 <member name="channel" type="U16"/>
1095 <member name="message" type="CONSTANT" value='Sorry, the owner of this game has left. Nobody will be allowed to edit it until the owner returns.'/>
1096 </message>
1097
1098 <message type="441e" name="teacher_left" src="server">
1099 Unclear.
1100 <member name="channel" type="U16"/>
1101 </message>
1102
1103 <message type="4422" name="allow_user_result" src="server">
1104 <member name="message" type="CONSTANT" value='User &quot;%s&quot; will now be allowed full access to your game.'/>
1105 <member name="channel" type="U16"/>
1106 </message>
1107
1108 <message type="4424" name="allow_user_result" src="server">
1109 <member name="message" type="CONSTANT" value='Sorry, user &quot;%s&quot; is a guest and cannot be allowed full access to your game.'/>
1110 <member name="channel" type="U16"/>
1111 </message>
1112
1113 <message type="4425" name="allow_user_result" src="server">
1114 <member name="message" type="CONSTANT" value='Sorry, user &quot;%s&quot; does not seem to exist and cannot be allowed into your game.'/>
1115 <member name="channel" type="U16"/>
1116 </message>
1117
1118 <message type="4428" name="add_tree" src="server">
1119 <p>See <ref ref="set_tree"/>. In addition, flags the tree as being
1120 uploaded completely.</p>
1121 <member name="channel" type="U16"/>
1122 <member name="tree" type="TREE"/>
1123 </message>
1124
1125 <message type="4429" name="reject_challenge" src="server">
1126 Reject a challenge by a given user. Not checked.
1127
1128 <member name="channel" type="U16"/>
1129 <member name="name" type="username"/>
1130 </message>
1131
1132 <message type="442f" name="new_game" src="client">
1133 <p>Notifies the client that a new game has been created. This
1134 message is sent long *after* upd_observers etc. has been received.
1135 *sigh*</p>
1136
1137 <member name="channel" type="U16"/>
1138 <p>The enwly created game.</p>
1139 <member name="id" type="U16"/>
1140 <p>Probably the ID sent to the server in new_game.</p>
1141 </message>
1142
1143 <message type="4433" name="req_result" src="server">
1144 Unclear.
1145 <member name="channel" type="U16"/>
1146 # # recv_result(?)
1147 </message>
1148
1149 <message type="4434" name="unknown4434" src="server">
1150 <member name="channel" type="U16"/>
1151 <member name="b1" type="U8"/>
1152 ?? !demonstration game??
1153 </message>
1154
1155 <!-- added recently -->
1156 <message type="443b" name="unknown_443b" src="server">
1157 No idea yet, both id's are probably channel ids and have sth. to
1158 do with the open games list(?). They have never been observed to be different, btw.
1159 <member name="channel" type="U16"/>
1160 <member name="game" type="U16"/>
1161 </message>
1162 </body>
1163 </html>
1164