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
White's P10 was stronger than I realized.
|11.n9 looks winning for white. But white T7 lets me up off the floor.
After black R5 now |15.n9 does not work because of 16.m7 17.m6 18.l5 19.o7 20.n4 21.p5 22.q3
After |25.s18 26.r13 27.o12 white is making threats on the left which black must respond to. 28.j7 29.l9 30.m10 31.n10 32.p14 33.n14 34.o16 35.j17 36.l13 37.h12 38.h8 39.j10 40.j12 41.i10 42.h20 threatening black J21 or i14.