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
(moves 11-14 went as expected, then) |15.d13 16.f18 17.n17 18.o18 19.m15 20.l14 21.k14 22.j13 23.i13 24.i8 25.g8 26.g9 27.e9 28.e10 29.d11 30.d12 31.b12 32.e14 33.e15 34.f16 35.f17 36.g20 37.g15
However, I shot myself in the foot before the plan ever had a chance to take off. At move 14 I became nervous about all the blank space at the top of the board - that 24.i8 above is not necessarily what would have happened - and I thought it would be a good idea to collect some freebies first: |15.t18 16.t22 17.v19 18.v23. I didn't think too hard about it. It looked safe. The thing about Pete's actual 16.n11 reply is that it completely kills the plan on the left side: 19.n17 20.o18 21.m15 22.k14. I didn't realize this until after playing 17.d13. It was probably already too late.
That awkward-looking |15.d13, by the way, was chosen for its ability to defend against 16.l20: 17.f18. The alternative 16.j20 isn't quite strong enough for Black in the middle; it leads into this familiar old pattern: 17.n17 18.o18 19.m15 20.m23 21.l21 22.k22 23.o22 24.p22 25.n22.
However, Alan found a stronger threat with 11.m19, and both that move and 13.r17 were forcing moves as I saw them. I think that |15.n17 would have been a winning move for white. I did have a response in mind for that, but I can no longer remember what it was, so I now suspect my response might not have worked.
My initial thoughts in response to 15.t18 were much the same as Alan sketched out. However, then I realized that I actually had an option for the first time since 6.k18, because16.n11 was essentially a free move that would improve my internal position, even if Alan responded with the expected |17.o10 to block. Moments after that I also realized its secondary benefit of enabling the threat from n17 to be trapped by L14.