Difference between revisions of "Edge template III2f"
From HexWiki
(Explanation of '1') |
(Converted to new hexboard diagrams) |
||
Line 1: | Line 1: | ||
− | + | Template III2-f is a 3rd row [[edge template]] with 2 stones. | |
<hexboard size="3x5" | <hexboard size="3x5" | ||
coords="hide" | coords="hide" | ||
− | + | edges="bottom" | |
+ | visible="-a1 a2" | ||
+ | contents="R b1 d1" | ||
/> | /> | ||
− | + | Both red stones are connected to the bottom (i.e., Red does not have to choose which of the two stones to connect). | |
(From Mike Amling, see: [http://www.drking.org.uk/hexagons/hex/templates.html www.drking.org.uk]) | (From Mike Amling, see: [http://www.drking.org.uk/hexagons/hex/templates.html www.drking.org.uk]) | ||
− | Red has | + | == Defending the template == |
+ | |||
+ | Red has three main threats, using [[edge template II]], [[edge template III2b]], and the [[ziggurat]], respectively: | ||
<hexboard size="3x5" | <hexboard size="3x5" | ||
coords="hide" | coords="hide" | ||
− | + | edges="bottom" | |
+ | visible="-a1 a2" | ||
+ | contents="R b1 d1 R A:b2 S a3 b2 b3" | ||
/> | /> | ||
− | |||
− | |||
− | |||
<hexboard size="3x5" | <hexboard size="3x5" | ||
coords="hide" | coords="hide" | ||
− | contents=" | + | edges="bottom" |
+ | visible="-a1 a2" | ||
+ | contents="R b1 d1 R B:c2 S (all-b1 a3 b3)" | ||
/> | /> | ||
− | + | <hexboard size="3x5" | |
− | + | coords="hide" | |
− | + | edges="bottom" | |
− | + | visible="-a1 a2" | |
+ | contents="R b1 d1 R C:c1 S (all-b1 a3 b2)" | ||
+ | /> | ||
+ | Because these threats do not overlap, Blue cannot prevent Red from connecting to the bottom. | ||
== See also == | == See also == |
Latest revision as of 17:28, 10 December 2020
Template III2-f is a 3rd row edge template with 2 stones.
Both red stones are connected to the bottom (i.e., Red does not have to choose which of the two stones to connect).
(From Mike Amling, see: www.drking.org.uk)
Defending the template
Red has three main threats, using edge template II, edge template III2b, and the ziggurat, respectively:
Because these threats do not overlap, Blue cannot prevent Red from connecting to the bottom.