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
|33.t7 34.q10 was more complicated, for example 35.t11 36.s15 37.r12 38.h18 39.q17 40.p14 or 39.q15 40.r17 or 35.p10 36.o11 37.r9 38.p9 39.q11 40.q19 41.q17 42.p17 43.o16 44.o15
My R13 was a mistake. white could have played |27.p8 and then after 28.j13 29.g13 30.i15 31.h15 32.h18 33.p15 white has too many threats. |26.r14 might have been better
34.s11 35.s10 36.t8 37.u8 38.w5 39.v6 40.t4 41.w4 42.v2 43.u3 44.t3 45.w2 46.h18 47.q15
I wonder what would have happened if White had used |27.p12.
28.h18 29.q15 30.o12 31.n11 32.q13 33.o14 34.m13 35.m15