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
11.r8 perhaps handed the win back to me. Instead 11.r6 12.n8 13.o9 14.k12 15.i12 16.j10 17.h10 18.i4 19.i8 20.l9 21.i3 and white wins.
|14.n3 looks unusual, but it contains a double threat. Now my attack through the center with K12 works again, and at the same time I threaten R6.
If 23.i8 24.L9 25.i3 26.h2 27.j5 28.j3 and this time black holds the line.
Loic made some very sharp moves on the right side. After |25.r15 I wasn't sure if I had a win or not.
Instead of |37.t16, the crucial line looks like 37.t14 38.r6 39.t5 40.u9 41.v8 42.t11 43.u12 44.r12 black wins.