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
For example 25.s8 26.t10 27.l11 28.k12 29.m9 30.m7 31.n7 32.o6 33.p6 34.q5 35.q7 36.o7 37.q6 38.p7
Black might work.
Twixtbot likes 32.n9 33.q7 34.o6 35.m5 36.o7 and now all White can do is take p7 or q6, and Black takes the other one, and White can't stop Black from connecting.
The bot can't find a good line for White after |23.t6. The threat of going down the right side appears to fizzle out. That said, the bot is not perfect, it can't look down all the lines, and this is a deep and interesting variation. Even if it wouldn't work against a bot, it certainly could have worked against a human. Nevertheless, the bot sides with 6174quest. Black appears to still be winning.
Backing up a bit, |19.i17?
Edit: you commented before I finished my bot analysis, David. You found the same line as the bot, but with some extra moves that make it a draw.
I got an idea for white after |23.t6 24.r7 25.t10 26.s6
27.r5 28.u7 29.l11 30.j6 31.m9 32.n7 33.n6 34.o5 35.l7 36.m4 37.i4
EDIT 35.r18 36.o21 37.p19 38.q22 39.m20 40.l22 41.j21 42.l18 43.n20 44.n21 45.k19 White still wins.
I ran this at MCTS=4800, which is pretty high, and let it run for a couple of hours, and got this.
|23.t6 24.r7 25.t10 26.s6 27.r5
28.s21 29.n16 30.m15 31.p17 32.n21 33.q19 34.r15 35.r9 36.q5 37.s8 38.s4 39.u3 40.t2 41.t1 42.u5 43.o6 44.w4 45.q7 46.j4 47.n4 48.s13 49.r12 50.o14 51.s15 52.m3 53.m2 54.p21 55.s20 56.t19 57.t18 58.q22 59.l19 60.k21 61.i20 62.h22 63.h21 64.g20 65.g19
White prevails at the end.
I understand how the bot works.