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
3.i12 doesn't look very characteristic of TwixtBot and 15.s8 seems like a clear mistake. I wonder what happened under the hood?
I'm glad I could beat TwixtBot after you in Japan.
3.i12 is not like the usual TwixtBot, I thought so too.
But then, it occurred to me that if black was directly linked to something like i9 or i7, he may have wanted to create a route to either v20 or a connection to i12 by occupying the top right corner.
4.k12 was an experimental move for me, but I thought that even if white moved to i8, there would still be a way to get to the left side, and I wanted to be able to connect to the right side from either k8 or k12, so I moved it.
I didn't make any mistakes in my subsequent moves either, which I think led to my victory.
The 15.s8 was the answer with a little thought, but in my opinion it is the move that people are most likely to get wrong. I think that's why TwixtBot resisted.
I feel that coming up with 4.k12 was the factor that allowed me to beat TwixtBot.
Since it's a move I don't usually see much of, it's possible that it was a move that wasn't valued in TwixtBot's data.
I've fought over 600 TwixtBot battles before this victory.
So happy to have won!
Sorry for the weird English, it's an automatic translation.
3.i12 is too early in the game for me to judge.
Maybe BonyJordan could tell us what the computer evaluations were at each move. |15.r8 looks much better for white, because of the peg on V20. But after 16.p10 17.s10 18.s13 19.t12 20.r15 21.u14 22.u18 it looks like black still wins. Maybe the bot did not realize this until it was already committed to this defense on the right side. Sometimes, when the computer sees that the main line is losing, it will look at alternatives until it runs out of time, and then it will play a bad move because it did not have enough time to see that this bad move also loses.
Even as early as move 7, white apparently assumed that white N10 was a threat. My guess is that 7.k13 was the losing move |7.g8 looks much better.