ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/kgsueme/doc/protocol.xml
Revision: 1.61
Committed: Sun May 30 03:03:37 2004 UTC (20 years ago) by pcg
Content type: text/xml
Branch: MAIN
Changes since 1.60: +11 -5 lines
Log Message:
*** empty log message ***

File Contents

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