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.q10 15.n9 16.o11 17.j14 18.i11 19.n10 looked good for white.
My |23.H11 might have been (at least) one move too late. And |21.N16 was probably too committal. Maybe |21.H11 was better. For example |21.h11 22.i16 23.l17
Michal called |30.J18 a mistake, but what would have been better?
|30.l21 31.l22 32.m19 33.j21 34.k15 35.e20 36.f13 that's what!
|38.e11 39.g13 40.g7 41.g9 42.e6 43.j6 does not work for black.
but maybe |28.g16 would be much better?
or just |30.q14 and waiting for white move?