Move sequences are automatically highlighted and made clickable. If the previous move number appears earlier in the comment, the sequence continues from that move. Otherwise, it's treated as a variation from the main line. This can be error-prone with multiple sequences in one comment, so please use the Preview button to check your work before posting.
To force a sequence to be treated as a main line variation, precede it with a vertical bar
(|). The copy variation button (⧉) includes this bar automatically.
For more complex discussions, you can name a sequence by adding the name in square
brackets at the end, e.g. 15.p9 [a]. Later in the same comment, or in
any following comment, you can branch off that variation by wrapping the name in vertical
bars, like this:|a| 16.o13
The variation name must start with
a letter, contain only letters, numbers, and dashes (-), and is case-sensitive.
Comments use UTF-8 encoding, so you can include emojis 😉, non-English characters, and other Unicode symbols.
You can also use HTML entities like — for an em-dash (—) or → for a right arrow (→).
For safety reasons, most HTML tags are stripped, except:
<b>, <i>, <u> — bold, italic, underline<em>, <strong> — emphasis, strong text<s>, <strike> — <sup>, <sub> — superscript, subscript<blockquote> — indented quotes
<code> — fixed-width font<pre> — multi-line preformatted text
<br> — forces a line break
but instead 34.i21 wins for black.
|29.q17 30.m13 threatens black Q13, so then 31.q13 32.r18 33.o18 34.n18 35.m17 36.l17 37.k13 38.l13 with a connection to L9.
11.E17 was a strong idea, threatening to win along the left. Maybe |11.d18 would have coordinated better with white G15. For example 12.m7 13.g8
I thought I had |27.r18 covered with 28.s20 but the bot points out that after 29.s21 30.q19 31.t19 I can either play 32.r17 33.t16 34.t14 35.u14 36.s16 37.s18 38.v13 39.r16 and lose, or I can play 32.r13 33.o13 34.r17 35.m16 and lose.