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
But it seems that 27.s17 works with 28.t17 29.u18.
What is the point ? I don't understand.
I would like to propose something:
|25.v14 26.u17 27.f17
The idea is:
|25.v14 26.u17 27.f17 28.f19 29.h18 30.h20 31.k21 32.j21 33.s17 34.t17 35.q16 36.r18 37.o20 38.p21 39.n18 40.n22 41.m20 42.l22 43.m22
Which seems to be a nice trap.
Of course |25.v14 26.u17 27.f17 28.g14 is probably still winning for black.
In fact, I did not see this coming until 24.r16 were it was too late already.