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
14.u16 15.t17 16.s15 17.v16 or
14.u17 15.t17 16.s16 17.r16 or
(here's the tricky one)
14.v19 15.t17 16.t20 17.o16 18.n18 19.q20
|12.r17 13.u14 14.v19 15.t17 16.t20 17.o16 18.o20 19.m17 20.j20 and now if 21.l20 22.m19 23.j19 24.l17 black can turn the corner, although it's not very clear whether black has an advantage or not.
In view of this, perhaps it would be better for black to play something like |12.K7, which threatens to cut across the top and also serves as a downstream peg for the above variation. But this is just based on a cursory examination of the rest of the board.
Anyway, it's done. Thanks for alerting me to this.