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
peyrol vs yupina, 1 March 2022 15+10
|1.f6 2.k17 3.q15 4.p13 5.r12 6.q10 7.j14 8.i16 9.h15 10.g15 11.t11 12.s9 13.n12 14.n14 15.p11 16.s16 17.s14 18.p19 19.u19 20.r18 21.resign
If 17.n16 18.m16 19.s14 20.p17 21.p18 22.o19 23.r17 24.q20 25.u19 26.r18 black wins.
Perhaps I should have tried 11.n14 or 11.s10.
Move 16 is very interesting, I haven't seen this kind of setup before but it seems like it works. 11.s10 does seem more promising for white.