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
White had one more chance, though. The problem with |13.i7 is the lack of supporting material in the upper right after 14.j4. It might seem counterintuitive, but |13.j8 works. Now if 14.j4, White has room to go around it with 15.m5. And if Black doesn't link, for example, then 14.m5 15.h4.
Also not immediately obvious, the upper left does not work because Black's h16 peg catches the retrograde ladder chase: |13.d6 14.e8 15.e9 16.f10 17.d7 18.f6 19.f11 20.g12 21.g13 22.h14 23.f15 24.f19
11.j8 12.k7 13.h9 14.i6 15.e6
Or
|11.j8 12.i7 13.k10 14.k6 15.n7 16.m7 17.m9 18.o6 19.p6 20.q5 21.r5 22.s4 23.t4