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
|22.e19 23.e15 24.d21 25.j19 26.i19 27.i17 28.k20 29.l20 30.m21 31.t17 32.t21 33.q23 34.o20 35.r21
Which is probably good for white but better for black than the variation played.
But the real problem was:
|20.e17 21.i17 22.i12 23.j15 24.k11
Which seems unclear but I don't like this :P
?
|20.e17 21.o16 22.n18 23.i17 24.i12 25.j15 26.k11 27.m12 28.m10 29.q10 30.n12 31.n14
Maybe after o16 black van try something tricky like n22.
It allows some possibilities in the initial variation to defend bottom maybe with h21.