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
So, back to the present-day Championship 15:
I didn't realize until days after this game ended that it was a forfeit. I just figured he resigned. It would have been reasonable to do so. The unfortunate thing is that it means this 1.b5 doesn't get counted in my first move statistics.
Passenger got off the beaten track right away. |4.l16 is not a good block. It's a 2-5 gap from my J11 peg, so I could easily pass it on the left with |5.j16 or |5.h16. But as much as I'd like it to be that easy, it didn't look like I had a guaranteed connection to the top. I needed some horizontal spread. But because his move isn't a real block, I didn't have to put a real block on him, either; just a light touch like |5.n14 was enough to make a double threat. He can easily pass that on the right with |6.n17, but then I can move left with something like 7.j16; or he could block it on the left with |6.j17, but then I can move on the right with 7.o16. So he was wise to continue the dipper pattern. |6.m10 kept his hopes alive. At that point, he has multiple threats: J9 or J7, L12, O19, etc. Reviewing his threats, it seemed to me that they were generally unbalanced to the left, leaving the right weak, so it was a good idea to make a move to the right. With |7.p13, I have a threat of a path to the bottom, and the threat of going up on the left or the right of his L10 peg. But keep in mind that my J16 or H16 threats are still alive, so this is actually something of an H shape, not the typical Y.
The |8.m6 9.h6 exchange turned it into a Y (upside down), and the stem was strong, so he really needed to play down in the branches. And it needed to be a bold play. Maybe |10.i19. I'm not sure what. But |10.h16 wasn't it. That probably sealed his loss. At that point, I put in my defensive windmill peg at |11.r14, which secured my path to the bottom and made 2 viable threats to the top: S8 or K13. |12.l12 dealt with only K13, so then I had a linear commitment on the right. It was nice to have a big dividing line so that the problem is pretty much in two parts. |15.n17 was not obvious, nor was |19.m20, but I think there was nothing passenger could do. After |20.o18, there may have been some hope that I'd get overconfident and not see |21.l18 22.n16 23.m15 24.m14. The top half didn't have anything as tricky as that. If played out, it might have ended with something like: |22.u11 23.s9 24.q8 25.r12 26.s4 27.q7 28.n4 29.q4 30.q5 31.p6 32.r8 33.p9.