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
I don't really think things were going to go well for me after 1.f8 2.swap, but I'm sure there was a better way to play afterward. Maybe 5.r10 and 7.12 were too timid — overly focused on spreading out without putting black's path across the middle under any pressure.
The problem with R10 IMO is that my N12 peg is too high up the board. If we had played |3.n14 4.n16 then 5.r14 would have been more effective. My personal preference as white would have been to block N12 more directly, for example |5.r12 or near there, or maybe in the center with |5.k12 followed by R12 later, but I would have to study the tactics a lot more than I am doing now.