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
I spent a lot of time thinking about |35.r15, which I just assumed was coming. I don't think there's any way for me to break through on top, although 36.q12 37.t12 38.p10 39.t7 40.s9 41.u9 could potentially be useful in a combination.
I probably would have tried 36.q19, but it looks awfully complicated to me.
Kind of disappointed not to play it out.
37.t16 38.q14 39.s14 40.r12 41.t12 42.q10 OR
37.t14 38.u14 39.q17 40.q12 41.s13 42.p10 43.s9 44.q5 45.q8 46.o9 47.t7 48.s4 49.w4 50.u4 OR
41.u12 42.t9
|35.r15 36.s15 37.t16 38.q14 39.s14 40.r12 41.t12 42.q10 43.t7
That being the case, perhaps Q19 would have been best after all.