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
33.d20 was unnecessary. White could have won with
|33.n13 34.p16 35.l17 36.m19 37.j21
But as Alan Hensel pointed out,
|31.h20 would have been much simpler.
|33.g22 34.h23 35.f20 36.f22 and black wins the local battle, so white does not have a simple win with g22, although even in this line I think the n13 resource still works for white:
|33.g22 34.h23 35.f20 36.f22 37.n13 38.p16 39.l17 40.m19 41.j21
|33.g22 34.h23 35.f20 36.f22 37.d21 38.c22 39.d23 white wins locally without any need to play on the right side of the board.