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 had. I had failed to note that the p15 peg might give me some additional leverage against the Achilles.
And 27.r19 eventually led to a win for self. But, I'm wondering if Flemming had a chance to salvage it.
In any event, thanks Flemming!
29.q19 30.q18 31.p21 32.s17
or 29.s22 30.t19 31.q17 32.q22 33.o18 34.m19 35.l19 36.k20 37.n18 38.n19 39.j20 40.o17 41.m16 42.n15 43.l14 44.m13
or 29.o20 30.n21 31.q19 32.q20 33.s18 34.o19 35.p21 36.p22