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
If 25.l5 then 26.j8
if 25.i8 then 26.h9 with either 27.h10 28.m5 or 27.l5 28.j8
Black's problems seem to have started with the idea that |8.n7 could form a viable threat across the top to the left (over i9). Instead, maybe |8.o10, because it's downstream to both j13 and L17, and by that I mean 9.m15 10.l12 11.m11 12.m10 13.n9 14.n8 and 9.j12 10.n16 11.o15 12.o14 13.p13 14.p12 15.q11 16.q9. Both of those lines are just to demonstrate the threat. What one might actually expect in response is something like 9.h17 or 9.j14 or something else that breaks both of the above threats.