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
9.E9 Same here.
Instead of Q14, the bot recommends |17.J13 cutting me off, for example 18.j19 19.o16 20.l14 21.m17 22.l18 23.r13 24.k12 25.r8
After |25.j13 then 26.L15 would not work, but I could play 26.j19 instead.
What about 27.j17 28.l18 29.h18 30.h20 31.d20 32.g18 33.d16?
|25.j13 26.j19 27.j17 28.l18 29.h18 30.h20 31.d20 32.f19 looks better than G18,
33.d16 34.e20 35.f21 36.c19 37.d18 38.d17 39.e19 40.g17 41.d12 42.f16 or 39.f17 40.g21 or 33.e18 34.g17