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
|32.l11 33.n9 34.m8 35.l7 36.n10 looks like a win for black
|32.l11 33.n11 looks like a win for white
maybe |20.e15 would have worked. 21.b15 22.h7 for example. But |20.f12 was a simpler way to win: 21.e14 22.g10 23.d10 24.d7 25.c8 26.e5 27.e7 28.g6
|18.d15 19.d16 20.e13 21.b15 22.c12 looks simpler still.
|9.q16 and now 10.r17 11.l16 or 10.n15 11.m14 was a win for white.
|6.m14 Looks better for black.