Search results

Create the page "Direct connection" on this wiki! See also the search results found.

• Intermediate (strategy guide)
  ''(See also the article [[Loose connection]])'' ...best connection when even more distance is required is called the '''loose connection''' — a [[Hex (board element)|hex]] that is a bridge plus an adjacent
  26 KB (4,694 words) - 01:56, 18 May 2022
• Edge template VI2a
  The Red piece at D4 is connected to the bottom. Blue has two direct attempts to block: Red's F5 piece is connected to the bottom. To prevent its connection to the top, Blue must move in one of the marked tiles.
  9 KB (1,560 words) - 14:36, 11 May 2023
• Advanced (strategy guide)
  ...ggurat]] and to the rest of Red's group by double threat at "*". Thus, the connection is complete. ...ily preferable to other connection moves because you only need to get some connection; you don't win extra points by connecting more strongly.
  31 KB (5,861 words) - 00:58, 9 February 2022
• Ziggurat
  These moves lead to easy direct connection. Because there is no common empty [[hex (board element)|hex]] used in both
  2 KB (384 words) - 07:16, 11 February 2022
• Edge template III1b
  These moves lead to an easy direct connection. Because there is no common [[hex (board element)|hex]] used in both threat
  830 B (141 words) - 05:32, 9 December 2020
• James A. Cook vs. Niall, December 2010
  *** (I11) starting at J2 blue can force a connection to the RHS to get to E8 in sente, then play G11 ** G6 (F7) F5 (E5) G2 (E3) - reds connection goes: {top->E3/E4/E5 -> F7/F8 -> bottom}
  13 KB (2,704 words) - 02:27, 11 May 2023
• Jonathan Rydh's strategy guide
  ...are all various kinds of nodes. Two nodes are connected with some kind of connection if there exists a path from one to another. === Solid connection ===
  14 KB (2,557 words) - 20:29, 11 September 2021
• Edge template III2a
  These moves lead to an easy direct connection. Because there is no common [[hex (board element)|hex]] used in both threat
  740 B (117 words) - 17:30, 10 December 2020
• Edge template III2b
  These moves lead to an easy direct connection. Because there is no common [[hex (board element)|hex]] used in both threat
  745 B (118 words) - 04:54, 9 December 2020
• Edge template III2c
  These moves lead to an easy direct connection. Because there is no common [[hex (board element)|hex]] used in both threat
  888 B (158 words) - 17:32, 10 December 2020
• Edge template III2d
  These moves lead to an easy direct connection. Because there is no common [[hex (board element)|hex]] used in both threat
  816 B (130 words) - 15:19, 14 February 2022
• Edge template III2e
  These moves lead to an easy direct connection. Because there is no common empty [[hex (board element)|hex]] used in both
  968 B (168 words) - 00:59, 8 December 2020
• Strategic advice from KataHex
  ...strategy advice "up-to-date". There's a lot of random insights; most are a direct result of playing around with KataHex evaluations for hundreds of hours, in ...f moves to reconnect the two blue stones. In practice, Blue will try for a connection elsewhere, and probabilistically, the two blue stones are unlikely to be ve
  21 KB (3,605 words) - 16:08, 14 January 2024