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