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
|31.f15 32.g14 33.e17 34.h12 doesn't work for white either.
Neither does |31.d15 32.g10 33.i11 34.e14
|25.k14 26.m12 27.j12 28.k9 29.g9 does win for white, but black can play 26.j15 27.m11 28.n19 29.s15 30.s21 31.j16 32.j20 instead. For example 33.h19 34.g21 35.g22 36.i20 37.j18 38.k18 39.f20 40.i17 or 35.e20 36.g17 37.f18 38.i18 39.g16 40.h16 41.f14 42.h10