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
But |22.i8 23.e9 so what about |22.h9 23.j13 24.l10 25.o13 26.o7 ?
|22.h9 23.j13 24.l10 25.l12 26.n9 27.r9 28.r5 29.p8 30.m5
Playing |40.p10 I had 41.t11 42.o8 on my mind but it doesn't work because of 43.r7 44.n6 45.r3.
|41.t11 is indeed losing as shown in the game but there was also |41.u10: 42.o12 43.t17 44.t16 45.u15 46.u14 47.v13 48.v12 49.w11.
My plan was: |41.u10 42.o12 43.t17 44.t13 45.t14 46.u15 47.r11 48.t16 49.u16 50.v17 and |41.u10 42.o12 43.t17 44.t13 45.t12 46.r9 47.r7 48.v14.
So is |40.p10 really winning? I thought it could lose but I don't see a good white move there.